Re: [jboss-dev] Re: your opinion on an EAR/JBoss issue (maven ear plugin)
AFAIK, this will actually work, but I don't think it is supposed to?
JBoss will only deploy stuff that is listed in application.xml or
jboss-app.xml but it doesn't actually check that the listed
deployment matches the specified type.
Only the <web/> (context-root) and <java/> (potentially
could be added to some available list of client applications
for download) tags have any real semantics assocation with them.
e.g. this would probably also work :-)
<application>
<module>
<web><web-uri>mydatasource-ds.xml</web-uri></web>
</module>
</application>
I'd imagine we will probably make this more strict in some future
release.
So for future compatibility, the correct mechanism for non-spec
deployments is to add a META-INF/jboss-app.xml
<jboss-app>
<module>
<service>mydatasource-ds.xml</service>
</module>
</jboss-app>
On Fri, 2007-06-15 at 09:39 -0700, Scott M Stark wrote:
No, this requires a jboss-app.xml descriptor. The ear
application.xml
java module type is only for app client jars. It does also update the
ear classpath, but that is a questionable feature.
Ian Springer wrote:
> Stephane,
>
> This isn't my area of expertise. I'm forwarding to the JBoss development
> list. Can someone help out Stephane?
>
> Regards,
> Ian
>
> Stephane Nicoll wrote:
>> Hi,
>>
>> I'd like your opinion on an issue to confirm this is officially
>> supported by JBoss.
>>
>> http://jira.codehaus.org/browse/MEAR-52
>>
>> Thanks,
>> Stéphane
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx