[ http://jira.codehaus.org/browse/MEAR-15?page=comments#action_68117 ]
Ian Springer commented on MEAR-15:
----------------------------------
The correct way to configure a SAR bundled in an EAR is not via a connector
module, but by adding a service module entry in META-INF/jboss-app.xml, e.g.:
<!DOCTYPE jboss-app PUBLIC "-//JBoss//DTD J2EE Application 1.4//EN"
"http://www.jboss.org/j2ee/dtd/jboss-app_4_0.dtd";>
<jboss-app>
<module>
<service>my.sar</service>
</module>
</jboss-app>
This tells JBoss to load the JBoss service from the file my.sar located in the
root directory of the EAR.
I suggest adding a JBoss-specfic section in the EAR plugin's configuration for
configuring stuff that needs to be written to jboss-app.xml, e.g.:
<configuration>
<jboss>
<jbossVersion>4</jbossVersion>
...
</jboss>
</configuration>
The jbossVersion would tell the plugin which version of JBoss is being
targeted, which would determine the docType of the file (a bunch of new
elements were added in JBoss 4.x - for example, the ability to deploy Hibernate
archives (HARs).
> Support of sar files
> --------------------
>
> Key: MEAR-15
> URL: http://jira.codehaus.org/browse/MEAR-15
> Project: Maven 2.x Ear Plugin
> Type: Bug
> Environment: Maven 2.0.1, maven-ear-plugin 2.0, Windows XP.
> Reporter: Jay Stramel
> Assignee: Stephane Nicoll
> Fix For: 2.1
>
>
> Building an ear file will fail if the ear file requires a SAR file as one of
> it's components.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
