[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1321) Could possibly remove the requirement to specify SeamListener in web.xml

Mike Quilleash (JIRA) jira-events at lists.jboss.org
Wed May 30 03:44:08 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBSEAM-1321?page=comments#action_12363507 ] 
Mike Quilleash commented on JBSEAM-1321:

This functionality is in JSP2.0 and JSP2.1 (I didn't check earlier versions) so Tomcat 5+ will be fine.

See section 7.1.9 in http://jcp.org/aboutJava/communityprocess/final/jsr152/

> 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
>             Fix For: 1.3.0.ALPHA
> 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


More information about the seam-issues mailing list