[weld-issues] [JBoss JIRA] Commented: (WELD-879) Tomcat 7 container is identified as Tomcat 6

[Ales Justin (JIRA)]

    [ https://issues.jboss.org/browse/WELD-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593817#comment-12593817 ] 

Ales Justin commented on WELD-879:
----------------------------------

You can workaround the problem by placing proper org.jboss.weld.environment.Container file into your app's META-INF/services.


> Tomcat 7 container is identified as Tomcat 6
> --------------------------------------------
>
>                 Key: WELD-879
>                 URL: https://issues.jboss.org/browse/WELD-879
>             Project: Weld
>          Issue Type: Bug
>          Components: CDI API
>    Affects Versions: 1.1.1.Final
>         Environment: Tomcat 7.0.11
>            Reporter: Ashley Westwell
>            Assignee: Ales Justin
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
>
> Weld-servlet 1.1.1-Final identifies tomcat 7 as tomcat 6 environment.In Listener.java it executes the following code 
> container = checkContainers(cc, dump, Arrays.asList(
>   Tomcat6Container.INSTANCE,
>   Tomcat7Container.INSTANCE,
>   Jetty6Container.INSTANCE,
>   Jetty7Container.INSTANCE,
>   JettyPost72Container.INSTANCE)
> ); 
> This method returns a Tomcat6Container as Tomcat 7.0.11 at least has the class org.apache.catalina.core.ApplicationContextFacade. I would suggest reversing the order to have Tomcat7Container checked first as I from my knowledge the class org.apache.tomcat.InstanceManager is new to Tomcat 7

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira