[
https://issues.jboss.org/browse/WELD-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12638261#comment-12638261
]
Ales Justin commented on WELD-985:
----------------------------------
jetty-web.xml is not required any more, but jetty-env.xml still is, due to
early BeanManager JNDI binding.
> Make Tomcat 6 and Jetty 6 and 7 specific configuration obsolete
> ---------------------------------------------------------------
>
> Key: WELD-985
> URL: https://issues.jboss.org/browse/WELD-985
> Project: Weld
> Issue Type: Feature Request
> Components: Bootstrap and Metamodel API
> Reporter: Geoffrey De Smet
> Priority: Critical
>
> According to the documentation:
> http://docs.jboss.org/weld/reference/1.1.0.Final/en-US/html_single/#d0e5286
> We have to add extra configuration files to deploy to certain appservers and
> certain versions.
> But the existence of those files can sometimes create issues on other
> appservers.
> For example, jetty 6 needs an WEB-INF/jetty-env.xml file (and Jetty 7 needs
> another version of that file).
> "Maven profiles" are not a solution, see WELD-984.
> Since weld-servlet's bootstrap actually detects what appserver and what
> version is in play, it should be thoroughly investigated if weld can't do
> that for us
> and only configure the content of those extra files if the correct
> appserver/version is being used.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/weld-issues
