anonymous wrote :
| I think with the latest change if an ear doesn't have a jboss-app.xml, deployment
will fail with an NPE at EARDeployer line 275.
|
I dont think so as J2eeApplicationMetaData is taking care of this .
| //Get the Deployment Ordering style
| Element moduleOrderElement = getOptionalChild(rootElement,
"module-order");
| if (moduleOrderElement != null)
| {
| moduleOrder = getElementContent(moduleOrderElement);
| }
| else
| {
| moduleOrder = "implicit";
| }
|
anonymous wrote :
| With this WARN log, anyone who upgrades to 4.0.5 and doesn't add this new config
element will get a WARN log. A WARN in a production app is a serious problem; to make it
go away the users will have to add the new element.
|
The warn will appear only if the user is not using the module order as strict or implicit
, say the user has typed errstrict in the module-order ie
| <module-order>errstrict</module-order>
|
The value of implicit will be taken , there will be no failure but the warning will be
displayed .
anonymous wrote :
| This is causing o.j.t.cluster.test.CrossContextCallsTestCase to fail.
|
I am not sure why this fails can you give me some more details on this ?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3967729#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...