- This topic has 2 replies, 2 voices, and was last updated 20 years, 5 months ago by
.
-
Posts
-
Disclaimer: I actually hope my question is really dump and the answer is trivial – but nevertheless I’ve been unable to work it out myself.
I’d like to deploy an Enterprise Application to a Websphere 5.1 server. The deployment and automatical redeployment (after changes to java files) works perfectly fine. But the one thing I can’t figure out is how to update the “deployment code” for EJBs (Websphere needs files like EJSRemoteStateless[BEAN-NAME].class and the rmic stubs and ties). In WASD there was a menu entry “Generate > Deploy and RMIC code” for that purpose.
What do I need to do to update EJBs with Myeclipspe?Thanks a lot!
Actually, this is a great question. Since we support about 20 servers, we don’t have specific integration for updating WebSphere stubs and these are only generated when you send your application through WebSphere’s deployer. So, if you make signature changes to your EJB’s , you’ll have to go through the full deployment cycle to the new stubs can be generated. Once that’s done, you can then use the exploded deployment to keep you Java in sync. Naturally, for this to be really effective, your EJB interfaces need to be relatively static. 🙂
Actually, this is a bad answer 😉 , but I understand that supporting all servers would be hard work.
Here’s the workaround I’ve found in the mean time. Create an ant file that does the following:
Create an EJB-JAR,
run Webspheres ejbdeploy.bat (add all libraries via the -cp option) on the jar and let it create another EJB-JAR file that contains the stubs.
Unjar the latter EJB-JAR into the appropriate installedApps\… directory.There’s no need to stop the server or use the admin console for deployment in that case. If anyone has a faster solution (Generating stubs only for changed Beans etc. please let me know)
Wouldn’t it be great if a future version of MyEclipse included the support for creating stubs – at least for some servers (hint: websphere :wink:)?
