[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-4023) share seam classes betwee webapps

Pete Muir (JIRA) jira-events at lists.jboss.org
Thu Mar 19 05:35:23 EDT 2009

     [ https://jira.jboss.org/jira/browse/JBSEAM-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pete Muir closed JBSEAM-4023.

    Resolution: Rejected

This will happen in Seam 3 based on the Web Beans core.

> share seam classes betwee webapps
> ---------------------------------
>                 Key: JBSEAM-4023
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4023
>             Project: Seam
>          Issue Type: Feature Request
>            Reporter: David Schlotfeldt
>            Priority: Minor
> It would be nice if we didn't have to package seam jars with ever webapp. We attempted putting the seam jar in the shared lib directory but doing so causes JSF webapps that don't have the seam servlet-listener in place get a NPE when you make a request to the site. This happens because the faces-config.xml in the seam jar is loaded by all JSF webapps -- so even the ones with one the servlet-listener load it.
> Keeping the seam jar in shared location will greatly decrease perm gen space usage for those with multiple seam webapps.
> Possible solutions:
> A) remove faces-config.xml from the jboss-seam jar. Place it in a new jar. Each webapp that needs seam then includes the new jar that only contains the faces-config.xml (This is the current solution I am using
> B) rename the faces-config.xml file in the jar so its not auto loaded. Then make the servlet-listener some how load it. (If this is technically possible this is of course the best solution since it is "backwards compatible".)
> Thanks!

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list