- This topic has 2 replies, 2 voices, and was last updated 12 years, 4 months ago by
.
-
Posts
-
Hi there,
I have a kind of tricky question… I’m working on a EAR project with 3 EJB 3.0 projects and one legacy EJB 2.1 project which is a precomplied (and through ejbdeploy enhanced) JAR file.
When I deploy the EAR through ME Blue it packs the temp EAR and deploys it with an ejbdeploy call which ist perfectly ok.
Unfortunately the ejbdeploy task changes the legacy EJB 2.1 JAR too and it won’t run afterwards. So that leads me to the idea that I want to mask out the legacy EJB 2.1 from the ejbdeploy call.
Is there any – even dirty (hacking installEAR.jacl or whatever… ;-)) – possibility to achieve this?
Or has anybody a better idea?
Thx,
ThomasThomas,
What mode are you deploying the project with? If you configure your server to use the in-workspace mode, EJB Deploy will *not* be run on the project when it is deployed (that mode requires that you run ejb-deploy manually).
If you need to use the classic or enhanced modes for some reason, you could go to the project properties > MyEclipse > EAR page and turn off the EJBDeploy option; this will turn it off for all your EJB projects, but IIRC it would not be required for EJB3 anyway (I’ll have to confirm with my dev team).
Please let us know how it goes.
Brian,
thanks for your reply.
You’re right, we cannot use the “in workspace” deployment for an different reason. So we use the “exploded archive” mode currently.
Meanwhile I’ve found the mentioned option for the EBJ deploy and this works for me. Since the EJB 3 projects are only using local interfaces for the beans and there is therfore no need to create remote stubs everything works fine.
Thx again,
Thomas
