|
| Re: web-fragment.xml causes nested jar on deployment [message #539114 is a reply to message #539073] |
Wed, 09 June 2010 16:36   |
 Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
On 6/9/2010 10:48 AM, Ramonus wrote:
> Hi,
>
> I'm having trouble deploying my Dynamic Web Project with a specific jar
> (WEB-INF\lib\primefaces-2.0.0.jar) using the latest Eclipse Helios JEE RC3.
> Because this jar contains the file \META-INF\web-fragment.xml, the jar
> gets nested in itself after deployment to the server
> (primefaces-2.0.0.jar first entry is primefaces-2.0.0.jar). Resulting
> the server not finding the classes in the jar. When I manually remove
> web-fragment.xml from the jar, the deployed jar is just fine.
> I'm using Glassfish v3.0.1 with the Eclipse server plugin "GlassFish v3
> Java EE 6 runtime".
> Is this a bug, with an older Helios milestone, this problem didn't occur?
> Anyone?
>
> Regards,
> Ramon
This is a behavior change in WTP 3.2 that server adapters may have to be
updated to handle. The built-in Tomcat and Generic server adapters have
already done so. It looks like the Glassfish server adapter will have
to as well. The behavior change is documented in Bug 309206[1]. The
bugs for this behavior in the Tomcat and the Generic server adapters
were Bug 306732[2] and Bug 310647[3], respectively. You may want to
report this issue on a Glassfish forum.
Cheers,
Larry
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=309206
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=306732
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=310647
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03316 seconds
] 
Search
Help
Register
Login
Home
