Posted: Sun Aug 09, 2015 6:14 am Post subject: Using Shared Classes Jar File in Message Broker
Master
Joined: 07 Sep 2008 Posts: 240
Hi Team... We are using Java Compute Node in our flow and the Java stuff is given to us in a Jar file to be deployed under broker. We have deployed the jar file under broker shared class folder.
The Java is using the Aspose.Word license to convert the RTF in to XML and our client has taken a license to have the development task done. But now the license for our Aspose.Word is going to expire and We are NOT going to have any change in our code in the existing env. Since the Client is NOT going to have any change in future they do not want to renew the license.
My question is if the license is expired then will broker experience any issues with the deployed jar file under the shared classed path.
What I understand is the license is only for development task and we may not do any changes/enhancements in future and there should be NO impact of the license expiry to the running jar file with the broker.
Could you please help me to understand more on this or is my understanding correct ?
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
Obviously as the license is expired you won't be able to do any support/bugfixes without a new license.
Get thet clearly understood by the client in writing and possibly agreed by the lawyers for both sides. This is strictly a damage limitation operation on your part.
I'd then write a stub in Java that returns a known bit of XML when called.
Replace the licensed Jar file with this and get on with life, the universe and everything.
If the client comes back you can replace the stub with a new jar and do the changes.
You may have to declare that you have deleted all copies of the licensed JAR file. Some vendors require this as part of their license terms. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Thanks smdavies99. The client is already aware of this. As I said they are NOT expecting any change in future so they are ok that they do not have to change anything.
But the concern here is if the license expires then will this impact the current jar file which is deployed on broker. If No then there is NO issue with the client.
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
I would guess that unless you try to use the jar file then all would be ok.
However I still think my idea of createing a simple stub JAR is the best way forward. Then the issue of a license is moot.
You could make the string returned say something like
Code:
<AAAAA>This is a stub response. Replace thise jar with a licensed one when needed</AAAAA>
Then it does not really matter if you call it or not. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum