|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
_______________________________________________ weld-issues mailing list weld-issues@lists.jboss.org https://lists.jboss.org/mailman/listinfo/weld-issues
It seems we need GwtDevHostedModeContainer for older GWT versions, where Jetty 6 is bundled.
We have the following options:
Let me explain the third option. Right now GwtDevHostedModeContainer is the first container we try to detect. Older versions of GWT dev bundled both Tomcat 6 and Jetty 6 classes but were using Jetty container. Therefore it was necessary to detect GWT dev before Tomcat. However I believe this is not needed anymore as we don't support Tomcat 6 in Weld 2.2+ and we use a different class to detect Tomcat 7+. So we could change the detection ordering so that GwtDevHostedModeContainer is after the regular Jetty container. The question is whether org.jboss.weld.environment.jetty.JettyContainer will work with GWT dev mode.