[jboss-dev] jars in sars visible from ears, my arse!

Jason T. Greene jason.greene at redhat.com
Mon Sep 21 11:53:43 EDT 2009

Right, the application.xml will cause the deployment to be treated as an 
EAR. You don't need this for sars, they deploy all nested content 
anyway, so deleting it should solve the issue.

Anil Saldhana wrote:
> A sar uses jboss-service.xml as its DD just as an EAR uses application.xml
> I think that may be your predicament at the moment.
> Andrew Dinn wrote:
>>>>> Apologies for the title. A more pictorial perspective might help.
>>>>> server/default/deploy
>>>>>    jbossxts.sar
>>>>>      META-INF/application.xml
>>> Why do you have an application.xml in your sar file?
>> Because the sar contains, amongst other things, several war files. The 
>> application.xml contains module entries of type web which advertise the 
>> presence of these wars and specify their context-root. Is this not 
>> considered kosher for a .sar file? If not then what is?
>> n.b. I have tried to advertise the presence of the .jar files in the 
>> .sar by adding module entries of type java to the application.xml but 
>> this makes no difference to their visibility outside of the .sar file.
>> regards,
>> Andrew Dinn
>> -----------
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development

Jason T. Greene
JBoss, a division of Red Hat

More information about the jboss-development mailing list