- This topic has 2 replies, 3 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
Hello,
I see that this feature is already available in beta 1 for web projects and that’s pretty cool ! I have now two more questions:
– Will a similar feature be available in beta 2 for ejb and application projects (ears) through the manifest files ? This is cleary a requirement for us as we are working with ears only.
– If a library project is deployed automaticaly in a web project, what about 3rd party jars used by the library project. I did not find the way to tell myeclipse to add them in the WEB-INF/lib directory in the generated war. Is this a futur feature or did I miss something ?Thank you for your excellent support !
Fred
Fred,
Good questions.
– Will a similar feature be available in beta 2 for ejb and application projects (ears) through the manifest files ? This is cleary a requirement for us as we are working with ears only.
There is already support for deployment of dependent libraries for ears, although not quite automatically packaging them from projects yet. Basically, you can place any library jars that you need at the root level of your ear project and they’ll be deployed when the EAR is. At present, you’ll have to manually modify the Class-Path entries in your MANIFEST.MF files in your Web or EJB projects in order to point to the libraries so that the server’s classloader can find them. But yes, support is there.
– If a library project is deployed automaticaly in a web project, what about 3rd party jars used by the library project. I did not find the way to tell myeclipse to add them in the WEB-INF/lib directory in the generated war. Is this a futur feature or did I miss something ?
For web projects, libraries are supported two ways. First, you can simply place them directly in your WEB-INF/lib directory and they’ll be added to both your compilation classpath and will be deployed directly. Second, with our depenendent project support, any Java project that your Web project lists on its classpath will be automatically deployed. You can control this setting globally at Window > Preferences > MyEclipse > J2EE > Web Project > Web Project Build Path Deployment Policy. In addtion to this global setting, it can be overridden on a project basis by rt-clicking on the web project and selecting Properties > MyEclipse-Web. In beta 2, we’ll be adding an additional setting for web projects that will allow you to include other jars that are on the classpath, but not in WEB-INF/lib, in the deployment set also.
For Jboss (at least), changing the classpath in the manifest does NOT make utility jars available to deployed beans and webapps. Instead, you need to add a <java/> module to the application.xml. Although I can edit application.xml by hand, it’s a PITA to remember to do this every time I add a new module to the EAR.
Request that MyEclipse provide some mechanism so that (at a minimum) I can select .jar files that are rattling around loose in the top-level directory of the EAR and have the proper code generated in application.xml. I suppose that this could be as easy as listing loose .jar files as well as open J2EE modules on the selection available from the EAR contents “add” button.
