Community
Participate
Working Groups
Build Identifier: 20100917-0705 When trying to run a J2EE Dynamic Web Project under GlassFish vía the contextual menus commands Run AS -> Run on Server, if the project embeds another Eclipse project (in my case, a JPA project which only has some entities defined), the application fails saying GlassFish couldn´t find the first entity invoked by the DAO module. If you export the WAR module created from the same project using the contextual menu command Export -> WAR File and loading it to the application server as a GlassFish application via GlassFish console, it works OK. The application used to work OK until the Glassfish plugin was updated by Oracle to version 1.6.1. From the on, it gave the same problem whenever you try to embed a project in another one. The funny thing is, when you display the WAR file resulting from the Run on Server operation in the Glassfish directories, the WEB-INF/lib path shows the JAR file created from the embedded project. Reproducible: Always Steps to Reproduce: 1.Create a project (say, a JPA project) and create a package with a java program in it. 2.Create a Dynamic Web Project which uses GlassFish as the application server (of course, you have to have a Glassfish server definition) 3.Build the application in the Glassfish server via Run on Server. You'll get an error message stating that some class belonging to the embedded module is not found.
Moving to WTP Java EE tools.
Moving to Server Tools, but if the problem was caused by the Glassfish plugin, then this is NOT_ECLIPSE- you will have to contact them (Oracle) to get this resolved.
Created attachment 184805 [details] Error log from Eclipse while trying to run the GFNanbeiWebUser_SpV3 application
This doesn't sound like a problem with the framework but rather something in the Server adapter, it could be in the launchableDelegate, or the server adapter objects. Taking a look a the log that you just updated reinforces my thinking. Please report the problem directly to the GlassFish server adapter.
(In reply to comment #4) > This doesn't sound like a problem with the framework but rather something in > the Server adapter, it could be in the launchableDelegate, or the server > adapter objects. > > Taking a look a the log that you just updated reinforces my thinking. > > Please report the problem directly to the GlassFish server adapter. Ok, I'll do that. Thank you.
