java.lang.ClassNotFoundException

Requested Screen not found: XDATScreen_Pipeline_launch_pipeline Turbine looked in the following modules.packages path: [org.apache.turbine.app.xnat.modules, org.nrg.xnat.turbine.modules, org.nrg.xdat.turbine.modules, org.apache.turbine.app\ .xnat.modules, org.apache.turbine.modules]

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 web6256

  • Requested Screen not found: XDATScreen_Pipeline_launch_pipeline Turbine looked in the following modules.packages path: [org.apache.turbine.app.xnat.modules, org.nrg.xnat.turbine.modules, org.nrg.xdat.turbine.modules, org.apache.turbine.app\ .xnat.modules, org.apache.turbine.modules]
  • via Google Groups by Eero S, 4 months ago
    Requested Screen not found: Default Turbine looked in the following modules.packages path: [org.apache.turbine.app.xnat.modules, org.nrg.xnat.turbine.modules, org.nrg.xdat.turbine.modules, org.apache.turbine.app.xnat17.modules, org.apache.turbine.modules]
  • via Google Groups by Tim Herrmann, 6 months ago
    Requested Screen not found: Default Turbine looked in the following modules.packages path: [org.apache.turbine.app.xnat.modules, org.nrg.xnat.turbine.modules, org.nrg.xdat.turbine.modules, org.apache.turbine.app.xnat17.modules, org.apache.turbine.modules]
  • Stack trace

    • java.lang.ClassNotFoundException: Requested Screen not found: XDATScreen_Pipeline_launch_pipeline Turbine looked in the following modules.packages path: [org.apache.turbine.app.xnat.modules, org.nrg.xnat.turbine.modules, org.nrg.xdat.turbine.modules, org.apache.turbine.app\ .xnat.modules, org.apache.turbine.modules] at org.apache.turbine.modules.ScreenLoader.getInstance(ScreenLoader.java:190) at org.apache.turbine.modules.pages.DefaultPage.doBuild(DefaultPage.java:139)

    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.