Community
Participate
Working Groups
Build Identifier: 201112091000 Dependency doesnt work with J2EE Preview Server but does work with VMware vFabric tc Server. My quick solution is to export the project as .jar to to WEB-INF/lib directory. Does the trick as long as you have not too many changes in other projects. Reproducible: Always Steps to Reproduce: 1. Create a Dynamic Web Project and a normal Java Project 2. In Web Project Properties / Deployment Assembly add the Java Project 3. Create a .jsp Page in the Web Project referencing the Java Project 4. Run as / Run on Server on the Web Project, select J2EE Server
Created attachment 210654 [details] Two projects in the not working configuration
Created attachment 210655 [details] Two projects in the a working configuration The java project exported as .jar, the index.jsp is displayed
Thanks. I'll give these a try and see what I can find.
I'm not at all familiar with the J2EE Preview server code, but from a brief scan of the source, I'm not seeing code to handle utility projects. It is up to the server publishing to assemble the utility project into a jar when publishing the web project. It would appear that the J2EE Preview server doesn't support this. I'll try to make sure about this when I have more time, but in the mean time, you should try a different server. I can promise that the Tomcat server supports utility projects.
It really seems that the J2EE Preview server simply doesn't support this. It works with Tomcat 7.0.24 (very fast), with Spring vFabric Server. I've tried it with eclipse 3.5.0, where there was a different Preference Page (Java EE Module Dependencies). The description there (see attachment) would suggest it should work but it doesnt either. At least, I have now a circumvention, I use Tomcat.
Created attachment 210783 [details] Java EE Module Dependencies in eclipse 3.5.0 See the information lines.
*** Bug 366563 has been marked as a duplicate of this bug. ***