[jira] Commented: (MEAR-31) add ability to configure JBoss-specific deployment options in plugin configuration that will result in a jboss-app.xml descriptor being generated
[ http://jira.codehaus.org/browse/MEAR-31?page=comments#action_71431 ] Stephane Nicoll commented on MEAR-31: - also we need to disable the connector stuff when the jboss-app.xml is generated add ability to configure JBoss-specific deployment options in plugin configuration that will result in a jboss-app.xml descriptor being generated - Key: MEAR-31 URL: http://jira.codehaus.org/browse/MEAR-31 Project: Maven 2.x Ear Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: Ian Springer Assigned To: Stephane Nicoll Fix For: 2.3 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 servicemy.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 jbossVersion4/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). We could sgtart out with just the ability to deploy SARs and perhaps HARs and eventually add support for the other items in jboss-app.xml. -- 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
[jira] Commented: (MEAR-31) add ability to configure JBoss-specific deployment options in plugin configuration that will result in a jboss-app.xml descriptor being generated
[ http://jira.codehaus.org/browse/MEAR-31?page=comments#action_71439 ] Stephane Nicoll commented on MEAR-31: - jboss app is now generated. I need to bind it to the lifecycle + disable application.xml inclusion as a connector when it makes sense. add ability to configure JBoss-specific deployment options in plugin configuration that will result in a jboss-app.xml descriptor being generated - Key: MEAR-31 URL: http://jira.codehaus.org/browse/MEAR-31 Project: Maven 2.x Ear Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: Ian Springer Assigned To: Stephane Nicoll Fix For: 2.3 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 servicemy.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 jbossVersion4/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). We could sgtart out with just the ability to deploy SARs and perhaps HARs and eventually add support for the other items in jboss-app.xml. -- 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
