| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Trouble deploying a custom java plug-in |
« View previous topic :: View next topic » |
| Author |
Message
|
| edtguy |
 Posted: Wed Nov 24, 2004 8:28 am Post subject: Trouble deploying a custom java plug-in |
 |
|
Novice
Joined: 28 Oct 2004
Posts: 13
Location: Hoboken, NJ, USA
|
Hopefully, the following is attributable to "newbie error", and there is a simple answer that I have overlooked in the documentation:
Why is a java plug-in failing to deploy with the following message:
| Quote: |
BIP2241E: LIL not found for message flow node type 'Base64CodingNode' in message flow 'MyTestMsgFlow'.
The message broker received an instruction to create a message flow node of type 'Base64CodingNode', in message flow 'MyTestMsgFlow'. The broker does not have the capability to create nodes of this type because an implementation library for this node type was not found in the LIL path.
Ensure that the LIL path is correct and contains all the necessary node implementation libraries, including those supplied by IBM. Then ensure that the message flow and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center. |
Using Toolkit 5.0.4 on Windows XP, I have created a plug-in project in the Plug-in Development Perspective, and have imported a zip file of a project received from a colleague. I modified the java source, recompiled and the project reports no errors. I exported the project to a jar file, and copied it to the jplugin directory. I copied the entire project structure from the eclipse\workspace directory to the eclipse\plugins directory. I restarted the broker and the toolkit. The new plug-in node appeared in the message flow editor and I was able to use it in constructing a new message flow, which was successfully included in a bar file. When I attempt to deploy the bar file is when I get the LIL error.
I thought LIL files only pertain to C language plug-ins. Does anyone know what I'm missing?
TIA,
Ed |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Nov 24, 2004 8:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Compile this from the command line, not in the Toolkit.
Your jar file does not contain the right things.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| edtguy |
| Posted: Wed Nov 24, 2004 9:43 am Post subject: |
|
|
Novice
Joined: 28 Oct 2004
Posts: 13
Location: Hoboken, NJ, USA
|
| Thanks, but that turned out not to be the problem. The problem was that additional jar files on which the plug-in is dependent, needed to be placed in the WBIMB\classes directory. I didn't find this documented in any of the instructions I had read. The message reported in the event log is horribly misleading. It would be nice if it reported actual stack trace exception information instead. |
|
| Back to top |
|
|
| chenulu |
| Posted: Fri Nov 26, 2004 12:38 pm Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi,
You need to have the jar files in the jplugin directory and any dependent jar files that your plugin needs should be referenced via the CLASSPATH environment variable. The EG on startup reads the jar files in jplugin directory and tries to load each class from the jar file and the parent class that is being loaded fails becuase of the missing dependent class which is not in the jar files from the jplugin directory or the jar files from CLASSPATH.
-- Chenulu |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
