A customer opened a support ticket about deployment problems for an ext-plugin in JBoss 7. The root cause is related on how Jboss 7 handles class loading. The special characteristic of the plugin is that it defines a new taglib.
The best solution is to change a couple of things in the source tree of the ext-plugin:
- Add the attached "jboss-deployment-structure.xml" to the plugin WEB-INF/ dir
- Add a new dependency into "liferay-plugin-package.properties" file via portal-dependency-jars property: portal-dependency-jars=util-taglib.jar
Then package your ext-plugin and install it using the usual process.
This procedure should be documented in either one of following places (or other better one):
Note: the procedure was tested in 6.1-EE-ga1