java.lang.ClassNotFoundException

Requested Page not found: MyJetspeedJspPage Turbine looked in the following modules.packages path: [org.apache.jetspeed.modules, org.apache.turbine.modules, com.sterlingcommerce.neo.ui.dashboard.jetspeed] * at Appears you have not placed MyJetspeedJspPage in the correct directory relative to your module root above For example I think your MyJetspeedJspPage class needs to go under the package: com.sterlingcommerce.neo.ui.dashboard.jetspeed.pages I guess you can also put it here, but its not following recommended Turbine best practices: org.apache.jetspeed.modules.pages On Aug 13, 2016, at 12:54 PM, Usha Ladkani <ushaladkani@gmail.com> wrote: Yes in services in my TemplateService.default.extension property , TurbineResources.properties is set to .jsp. Now I am seeing this exception, Error encountered processing a template: /layouts/html/default.jspjava.lang.NullPointerException at com.sterlingcommerce.dash.jsp.WEB_002dINF.templates.jsp.layouts.html.default_jsp._jspService(default_jsp.java:75) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web9748

  • via portals-jetspeed-user by DavidSeanTaylor, 9 months ago
    MyJetspeedJspPage in the correct directory relative to your module root above For example I think your MyJetspeedJspPage class needs to go under the package: com.sterlingcommerce.neo.ui.dashboard.jetspeed.pages I guess you can also put it here, but its not
  • via portals-jetspeed-user by Usha Ladkani, 9 months ago
    it here, but its not following recommended > Turbine best practices: > > org.apache.jetspeed.modules.pages > > > > > On Aug 13, 2016, at 12:54 PM, Usha Ladkani <ushaladkani@gmail.com> > wrote: > > > > Yes in services in my
  • via portals-jetspeed-user by Usha Ladkani, 9 months ago
    can also put it here, but its not following recommended >> Turbine best practices: >> >> org.apache.jetspeed.modules.pages >> >> >> >> > On Aug 13, 2016, at 12:54 PM, Usha Ladkani <ushaladkani@gmail.com> >> wrote: >> > >> > Yes in services in my
  • Stack trace

    • java.lang.ClassNotFoundException: Requested Page not found: MyJetspeedJspPage Turbine looked in the following modules.packages path: [org.apache.jetspeed.modules, org.apache.turbine.modules, com.sterlingcommerce.neo.ui.dashboard.jetspeed] * at Appears you have not placed MyJetspeedJspPage in the correct directory relative to your module root above For example I think your MyJetspeedJspPage class needs to go under the package: com.sterlingcommerce.neo.ui.dashboard.jetspeed.pages I guess you can also put it here, but its not following recommended Turbine best practices: org.apache.jetspeed.modules.pages On Aug 13, 2016, at 12:54 PM, Usha Ladkani <ushaladkani@gmail.com> wrote: Yes in services in my TemplateService.default.extension property , TurbineResources.properties is set to .jsp. Now I am seeing this exception, Error encountered processing a template: /layouts/html/default.jspjava.lang.NullPointerException at com.sterlingcommerce.dash.jsp.WEB_002dINF.templates.jsp.layouts.html.default_jsp._jspService(default_jsp.java:75) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97) at javax.servlet.http.HttpServlet.service(HttpServlet.java:806) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:401) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:768)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.