MQSeries.net :: View topic - WMB 8, IIB9 - Java libraries in Messagebroker libraries

tobi3010 · Posted: Fri Aug 08, 2014 5:04 am Post subject:

Hi,

just need an hint/answer from the experts out there.
I tried to search for this in the forum but maybe i just missed the correct keywords, or just have not found what i am looking for.

What i am trying to do, and why:
I have an environment currently wmb 8 (in future it will be iib9). I "extended" ESQL by implementing some functionality in Java and making them available in ESQL by CREATE FUNCTION .... The ESQL is in an library, the Java as usual in a separate Java-Project.
By nature the esql/java library should be available in nearly all flows as it implements some core-functionality. (e.g. like making regexp.replace available in ESQL). ESQL is the favoured language and I want to keep the technology-stack small, mainly because most colleagues like ESQL more than Java.
So i have multiple applications making use of this library. When the applications are created (in the Toolkit) they link the libraries and within the libraries the including Java-projects (as jar).
But when it comes to changes i have the feeling that the classloader does not always get the right classes. And as i dont want to deploy all flows if i have a change in the library i came to the conclusion it would be best to deploy the java-artifacts only once. (To the shared-classes, as i read is also recommanded.) I am aware that by doing so you can not remove functions or change the signature of a method without serious impacts on all flows. So in that case you still would have to redeploy all flows. But in generall you only do some extensions to the functionality of a class, or correct the behaviour. By deploying it only once i would expect the changes to be working in all flows. Thats my goal, hardening the deployment, and keeping downtimes because of changes low.
Just tried this and it seems to work in general, but with some restrictions.

My problem:
First i had the Java-Project linked in the Message Broker library. Then i removed the link and tried to deploy, but the Toolkit will always find the project containing the Java-classes and include it to the library. But that is exactly what i want to avoid. I Just want to deploy this library without the java included. When removing the Java-Project from the workspace it works great, but if it is in the workspace (even not linked by the library, even if renamed or newly created

) the toolkit will find it and include it in the library.

As i am not the only one working on this workspace and broker this seems to be dangerous to me, as if anyone deploys an application making use of the library he might, without noticing, also deploy the java-artifacts.

So far thank you for reading up to here. It's a long description, but i wanted to make sure you understand what i am trying to do and why. But here are my questions:
1) What do you think of doing it this way? (Separating the ESQL from Java in this way.)
2) Do you hava long-term experience with this and can provide some troubles one might run into doing it this way?
3) If it is ok to do it like this. Is there any preferable way of excluding the jars from this library?

Kind regards and thanks in advance,
Tobias