You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
i just started using htmleasy, i have been trying to configure htmleasy as
servlet impl in google appengine , but no luck, after configuring and
registering class , when i try to access a jsp page it shows , resources not
avaiable.
Is Filter is essentials (there is not documentation stat that it is required),
following is config:
<servlet>
<servlet-name>resteasy-servlet</servlet-name>
<servlet-class>
com.googlecode.htmleasy.HtmleasyServletDispatcher
</servlet-class>
<init-param>
<param-name>javax.ws.rs.Application</param-name>
<param-value>com.test.resteasygae.config.AppConfig</param-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping>
<servlet-name>resteasy-servlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
<jsp-property-group>
<description>Common config for all the JSP</description>
<url-pattern>/*</url-pattern>
<el-ignored>false</el-ignored>
</jsp-property-group>
and my app config :
public class AppConfig extends Application {
@Override
public Set<Class<?>> getClasses() {
Set<Class<?>> services = new HashSet<Class<?>>();
services.add(MainController.class);
services.addAll(HtmleasyProviders.getClasses());
return services;
}
}
controller path
@Path("/")
@GET
public View hanldeRequest() {
return new View("index.jsp");
}
and the result :
could not find resource at path http://localhost:8888/index.jsp
when i use it with filters instead of servlets , it working fine, so i just
wanted to know , wether filter is must ?
can u help ?
What version of the product are you using?
0.7
Original issue reported on code.google.com by [email protected] on 15 Jul 2013 at 2:28
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 15 Jul 2013 at 2:28The text was updated successfully, but these errors were encountered: