Tuesday, March 1, 2016

Re: GWT 2.8-SNAPSHOT has broken JSP support in SDM & DM

Since the upgrade to Jetty 9.2 was just completed recently, I would submit a bug.

On Monday, February 29, 2016 at 11:23:41 AM UTC-7, Bauna wrote:
Hi Guys,
After updating to Jetty 9.2 in GWT 2.8 the JSP support is not working any more during debug (it doesn't matter if you use SDM o DM).
It seems that since Jetty 9.2[1] jsp support is not enabled by default and need to enabled when embedding. As a workaround you can add this snippet[2] to web.xml.
I don't know if I this expected or I should fill a bug.

[1] http://www.eclipse.org/jetty/documentation/current/configuring-jsp.html

[2] Code Snippet
 <servlet id="jsp">
    <servlet-name>jsp</servlet-name>
    <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
    <init-param>
        <param-name>logVerbosityLevel</param-name>
        <param-value>DEBUG</param-value>
    </init-param>
    <init-param>
        <param-name>fork</param-name>
        <param-value>>false</param-value>
    </init-param>
    <init-param>
        <param-name>keepgenerated</param-name>
        <param-value>>true</param-value>
    </init-param>
    <load-on-startup>0</load-on-startup>
  </servlet>
 
  <servlet-mapping>
    <servlet-name>jsp</servlet-name>
    <url-pattern>*.jsp</url-pattern>
    <url-pattern>*.jspf</url-pattern>
    <url-pattern>*.jspx</url-pattern>
    <url-pattern>*.xsp</url-pattern>
    <url-pattern>*.JSP</url-pattern>
    <url-pattern>*.JSPF</url-pattern>
    <url-pattern>*.JSPX</url-pattern>
    <url-pattern>*.XSP</url-pattern>
  </servlet-mapping>

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment