This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 76455 - Sun configuration looking for sun-cmp-mappings.xml instead of sun-ejb-jar.xml
Summary: Sun configuration looking for sun-cmp-mappings.xml instead of sun-ejb-jar.xml
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8 (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: _ pcw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-16 23:14 UTC by _ pcw
Modified: 2006-06-04 23:45 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
stack trace (3.13 KB, text/plain)
2006-05-16 23:15 UTC, _ pcw
Details

Note You need to log in before you can comment on or make changes to this bug.
Description _ pcw 2006-05-16 23:14:44 UTC
issue 76063 has a stack trace that also shows the following trace (see
attachment for full excerpt)

NFORMATIONAL *********** Exception occurred ************ at 5:01 PM on May 16, 2006
java.lang.IllegalStateException: FileObject not found for sun-cmp-mappings.xml
	at
org.netbeans.modules.j2ee.sun.share.configbean.SunONEDeploymentConfiguration.getStorage(SunONEDeploymentConfiguration.java:1137)
	at
org.netbeans.modules.j2ee.sun.share.configbean.SunONEDeploymentConfiguration.ensureConfigurationLoaded(SunONEDeploymentConfiguration.java:1109)
	at
org.netbeans.modules.j2ee.sun.share.configbean.SunONEDeploymentConfiguration.init(SunONEDeploymentConfiguration.java:247)
...

This is the result of looking for "configFiles[0]" in the sun configuration,
which _should_ have referred to sun-ejb-jar.xml, but somehow in this case did not.

The end result could be botched initialization of the DConfigBean tree and no
and/or no access to the configuration editor so we need to resolve this.
Comment 1 _ pcw 2006-05-16 23:15:02 UTC
Created attachment 30427 [details]
stack trace
Comment 2 _ pcw 2006-05-18 22:36:51 UTC
There was apparently a change somewhere in the code that builds file systems
from layer.xml that is causing sun-cmp-mappings.xml to be the first entry even
though the layer.xml for appsrv81 module specifically lists sun-ejb-jar.xml
first.  The new ordering does not appear to be the order specified, or the
reverse order specified, or alphabetical, so I have no idea what happened.

Anyway, I updated the code for initConfiguration so that if it is initialized
for an EJB module and sun-cmp-mappings.xml is listed first, we switch it around
with sun-ejb-jar.xml so that the dominant configuration file is again always the
0th element in the configFiles[] array.  We use it as an index in various
places, so it is important that this condition be met.