[
http://jira.jboss.com/jira/browse/JBSEAM-1321?page=comments#action_12365479 ]
Gavin King commented on JBSEAM-1321:
------------------------------------
This hasn't worked out very well, since the listener defined in the seam jar seems to
be created after the seam filter defined in web.xml. There are workarounds, of course, but
a bit messy....
Could possibly remove the requirement to specify SeamListener in
web.xml
------------------------------------------------------------------------
Key: JBSEAM-1321
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1321
Project: JBoss Seam
Issue Type: Task
Components: Core
Affects Versions: 1.2.1.GA
Environment: Tomcat 6
Reporter: Mike Quilleash
Assigned To: Gavin King
Priority: Optional
Fix For: 1.3.0.BETA2
I noticed the the JSF RI 1.2 uses a trick to avoid having to specify the <listener>
explicitly in web.xml. It has a .tld file in the META-INF directory of the implementation
jar. This gets scanned by the web container (Tomcat 6 in this case) and any
<listener> in the file get executed.
<listener>
<listener-class>com.sun.faces.config.ConfigureListener</listener-class>
</listener>
Maybe Seam could do something similar in the main seam jar. As this is a tld I guess
it's relying on the JSP spec, what version this listener was introduced in I'm not
sure, but I guess all JEE5 implementations should support this.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira