This content has been marked as final. Show 3 replies
A plain jar is not a Java EE module. I would recommend creating a dynamic web project instead. It doesn't need to have any interesting content, but you may want to include an about page. Just keep in mind that the web app's content will be visible in the consuming app so pick context root accordingly.1 person found this helpful
Thank you for your input; the WAR approach works, although I don't like the idea of publishing web pages by importing the shared library.
However, I was hoping for an approach that would use the "standard J2EE" jar packaging approach whereby a project that is marked as a utilitiy module is not placed in the APP-INF/lib (thisi is weblogic-specific) but rather placed in the EAR's root and published in the standard application.xml as:
This way I could bundle everything into the EAR, without having to include a web application in the shared library (and every app that uses it)... Could this be done using some project setup in Workshop?
<application ...> <module> <java>dummy.jar</java> </module> </application>
I think you can do that in Eclipse/Workshop if you create an app client project, but I don't think that's going to give you a valid EAR from Java EE spec perspective. You need to have a web or an ejb module.