For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 4 replies, 3 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
I was wondering if anyone here has any thoughts on a recommended approach for organizing and deploying an ejb module within an ear. I currently have an ear project with a single web module and i have had no problems building and deploying it to weblogic from within eclipse. I then decided to add an ejb module. As a result, i have to move a chunk of packages to a separate java project and then export it as a jar into the APP-INF/lib directory. I have a couple of problem that maybe you guys can help with.
1) i noticed that if i set up the ear to jar up the dependent java project that it ends up at the root. How come it is not deployed to the APP-INF/lib directory? Right now i manually export the jar then copy it to that directory manually.
2) perhaps this is weblogic specifc, but before myeclipse deploys the ear module doesn’t it have to create the weblogic specific stubs and what not?
thank, shane
1) Out of curiosity, why did you have to break out code into a separate Java project, is it shared by the EJB and Web module?
2) MyEclipse doesn’t do this, this is why you need to use the “deploy” functionality from your Weblogic administrative console, this is what it does during this step (one of many things).
@support-rkalla wrote:
1) Out of curiosity, why did you have to break out code into a separate Java project, is it shared by the EJB and Web module?
Yep.
@support-rkalla wrote:
2) MyEclipse doesn’t do this, this is why you need to use the “deploy” functionality from your Weblogic administrative console, this is what it does during this step (one of many things).
I have weblogic configured to deploy the ejb module, i guess i thought that the jar file had to includes the weblogic specific stubs, but maybe the stubs can also be generated at run time?
How come it is not deployed to the APP-INF/lib directory?
Because that is a weblogic extension and not the spec. By placing them in the root they are loaded by all app servers.
2) perhaps this is weblogic specifc, but before myeclipse deploys the ear module doesn’t it have to create the weblogic specific stubs and what not?
and
i guess i thought that the jar file had to includes the weblogic specific stubs, but maybe the stubs can also be generated at run time?
Like most modern application servers, WebLogic will build the stubs it needs on-the-fly at runtime if they’re not included in the EJB jar. This capability makes development much more convenient, streamlines packaging, and is used by MyEclipse to avoid a separate stub generation step. So, in short, your EAR without the stubs will work fine.
