- This topic has 6 replies, 5 voices, and was last updated 20 years, 9 months ago by
.
-
Posts
-
When I add modules to my ear project, i am only able to add ejb and web modules using the add module screens in my eclipse. This then overwrites any changes I have made to my app.xml file for the ear. MyEclipse should allow me to add modules other than EJB and Web(eg.. java)
I assume that by requesting other modules you have something in mind for our deployer to do with them? We certainly know how to handle web and EJB projects in an EAR, as the spec tells us that. What functionality do you have in mind that adding a plain Java project should provide? If we had some details on what your ultimate goal is we’ll be able to more accurately assess your enhancement request.
Currently I have several utility projects/packages that my ear depends on. They do not have EJB’s in them, but are just simple java projects. What I have done to work around the tool is to create them as EJB projects so they can be deployed in an exploded structure with the ejb and web modules. Although not technically correct, they work. If I understand the ear application.xml dtd properly, those projects should be of type java? and will be jar’ed seperately. Let me know if my understanding of an ear is wrong.
Scott, I think this thread is the same issue.. https://www.genuitec.com/forums/topic/support-for-utility-jars-and-external-ejbs-enhancement/
This is very similar to some other people’s requests of the deployment tool, essentially this:
1) They have 2 or 3 utility java projects
2) They build these projects into JARs (projectA-lib.jar, projectB-lib.jar, etc.)
3) In their EJB project, they setup references to these JARs (because they make use of the APIs)
4) When they deploy, they want the JARs to be deployed along with the EJB project because they are dependencies.The additions to the deployment process in the next release will help to cover some of these missing abilities that most people have asked for. It sounds to me that you are 90% similar to this situation, except you are referencing an entire project, not just a resulting build JAR from that project. If you are able to setup Ant scripts for those other Java Projects, and have the script build you JARs that you reference in your EJB project, the next release should handle deployment of dependencies for you.
For clarity the current release cycle is focused on finishing up 2.7/3.7 GA which has been struts and XML specific feature centric. The timeframe is approx. 2 weeks. We have a lot going on at EclipseCon this week. The 2.8/3.8 releases will focus on significant improvements in project flexibility, deployment and server improvements, and possibly JSP 2.0 support.
@support-michael wrote:
The 2.8/3.8 releases will focus on significant improvements in project flexibility, deployment and server improvements, and possibly JSP 2.0 support.
Ooh, yes please! Although I’m already using 2.7 for JSP 2.0 development with no problems except a huge number of warnings for my taglib statements where I’m using tagdir instead of uri.
