Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 197389 - EAR deployment with embedded RAR fails on GlassFish 3.1
EAR deployment with embedded RAR fails on GlassFish 3.1
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: GlassFish
: P3 with 1 vote (vote)
Assigned To: Vince Kraemer
Depends on:
  Show dependency treegraph
Reported: 2011-04-04 12:40 UTC by marek.winkler
Modified: 2011-10-31 22:38 UTC (History)
1 user (show)

See Also:

NetBeans console message during deployment. (1.30 KB, text/plain)
2011-04-04 12:40 UTC, marek.winkler
GlassFish log message during deployment. (3.32 KB, text/plain)
2011-04-04 12:42 UTC, marek.winkler

Note You need to log in before you can comment on or make changes to this bug.
Description marek.winkler 2011-04-04 12:40:54 UTC
Created attachment 107467 [details]
NetBeans console message during deployment.

java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07-334-9M3326)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02-334, mixed mode)

NetBeans 7.0 RC1, using bundled Maven 3.0.3
GlassFish 3.1

When trying to deploy an EAR with embedded RAR containing a JCA connector, the deployment fails with the message that an expanded directory for RAR submodule was expected but a JAR was found. The RAR indeed contains the connector packaged in a JAR but AFAIK its expansion should not be necessary.

First it looked like a GlassFish issue, but when I deploy the same EAR from GlassFish Admin Console, everything runs fine. Using Admin Console is an obvious workaround so this issue is not a blocker.

The NetBeans and GlassFish log files are attached.

Is there any difference in the way how NetBeans deploy a module to GlassFish from the deployment using GlassFish Admin Console?
Comment 1 marek.winkler 2011-04-04 12:42:12 UTC
Created attachment 107468 [details]
GlassFish log message during deployment.
Comment 2 Vince Kraemer 2011-04-05 23:30:18 UTC
NetBeans uses directory deployment.

Folks working with GF from the command-line and console usually create archives and deploy them.

One issue that NB has is this: it does not support rar projects, so the code that prepares a directory deployment does not know that it needs to 'explode' the rar file... which is exactly what the message from the server is trying to highlight.
Comment 3 Vince Kraemer 2011-10-31 22:38:13 UTC
the fix for this really requires that NB support doing RAR development.

switching to enhancement

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo