| Author |
Message
|
| paustin_ours |
 Posted: Mon Jun 22, 2015 8:30 am Post subject: manupulating bar file |
 |
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
I have a Bar file say test.bar which has one .cmf say test.cmf.
Now i need to create a new bar file with overridden properties. which i am able to do.
my new bar file is for example is called test1.bar with overridden properties.
Now what i want is to be able to add two more flows which is exactly the same as the test.cmf with its own set of overrides.
Can i edit the broker.xml and just add two more flows so that the resulting BAR file has three flows with its own set of overrides?
Am going to try this here in a bit, just want to see what you guys thought of doing something like this. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Jun 22, 2015 8:32 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You mean keep a single .cmf file ,and merely add multiple entries in broker.xml?
No, probably not.
Also, screwing around with the broker xml or directly with the contents of the bar file in the first place is not supported. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Mon Jun 22, 2015 8:37 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
yeah i just realized that i should make copies of the .cmf and create two more like test1.cmf and test2.cmf.
| Quote: |
| Also, screwing around with the broker xml or directly with the contents of the bar file in the first place is not supported. |
we have jar files in the bar which we cant really move onto the server. Unfortunately when we deploy multiple flows with the same jar to the same EG. The EG hangs once in a while, and someitmes we get class not fouind which sounded like a clash that happens when the jar files is getting overwrriten during deploy time and a flow starts using it already.
long story short, trying to just deploy jars one time.
App and Libs doesnt work for us either, our implementation (dont ask me why) doesnt make it easy for us to adopt apps and libs. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 22, 2015 9:22 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You should be able to remove the jar files from the message flow projects, and put them in another project, and then link them as external dependencies to the flow project.
You can then deploy the jars once - into the shared-classes or better a specific JavaClassloader configurable service. |
|
| Back to top |
|
|
| paustin_ours |
| Posted: Mon Jun 22, 2015 9:36 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004
Posts: 667
Location: columbus,oh
|
I tried something like this but when i move the java files to a different project and then reference that project to the message flow project and when i build the BAR the jars get included in the BAR file.
or are you saying, instead of referencing java code, create jar files out of them and then put that in a project and reference that? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 22, 2015 9:57 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I'm saying change how you reference the jar files. There are two ways to reference java projects from another project. One treats them the way you've seen, where it builds and includes the jar files.
The other just treats them as external resources and doesn't build or include them.
When you go to the java project properties and go to the java build path, you can "Add External Jars". |
|
| Back to top |
|
|
|
|
