facebook

Jetty 7.2.x deployments and MyEclipse limitations?

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #314617 Reply

    krishy
    Member

    I have been trying to get MyEclipse work well with Jetty 7.2 and I am running into couple of limitations/problems. Would be great if some one from support can clarify.

    1. There is no way to specify a custom Jetty context XML while deploying from MyEclipse. Having a custom context deployer allows us to create web app scoped JNDI entries and without this ability to specify these custom context deployers we are constrained to not do deployments from MyEclipse. Is this a known limitation?

    2. The context deployer that MyEclipse generates seems to be broken as it seems to refer to a non-existent class – org.eclipse.jetty.plus.webapp.Configuration. This class does not exist in Jetty anymore. This results in the webapp refusing to start. I see another thread also raising the same issue. But the answer provided is not clear. Is Jetty 7.2 supported or not?

    Krishna

    #314618 Reply

    krishy
    Member

    BTW, I am using version 8.6.1-20101117

    #314661 Reply

    support-swapna
    Moderator

    krishy,

    I could replicate the Jetty 7.2 issue and a fix is targeted for the MyEclipse 9.1 release.
    There is no support for the custom context xml file right now and it will be investigated along with the Jetty 7.2 support.
    Sorry for the inconvenience caused.

    #315122 Reply

    SISAL_PSS
    Participant

    we have the same problem:
    java.lang.ClassNotFoundException: org.eclipse.jetty.plus.webapp.EnvConfiguration
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at org.eclipse.jetty.util.Loader.loadClass(Loader.java:90)
    at org.eclipse.jetty.util.Loader.loadClass(Loader.java:70)
    at org.eclipse.jetty.webapp.WebAppContext.loadConfigurations(WebAppContext.java:781)
    at org.eclipse.jetty.webapp.WebAppContext.preConfigure(WebAppContext.java:375)
    at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:435)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
    at org.eclipse.jetty.deploy.bindings.StandardStarter.processBinding(StandardStarter.java:36)
    at org.eclipse.jetty.deploy.AppLifeCycle.runBindings(AppLifeCycle.java:180)
    at org.eclipse.jetty.deploy.DeploymentManager.requestAppGoal(DeploymentManager.java:479)
    at org.eclipse.jetty.deploy.DeploymentManager.addApp(DeploymentManager.java:136)
    at org.eclipse.jetty.deploy.providers.ScanningAppProvider.fileAdded(ScanningAppProvider.java:137)
    at org.eclipse.jetty.deploy.providers.ScanningAppProvider$1.fileAdded(ScanningAppProvider.java:50)
    at org.eclipse.jetty.util.Scanner.reportAddition(Scanner.java:477)
    at org.eclipse.jetty.util.Scanner.reportDifferences(Scanner.java:389)
    at org.eclipse.jetty.util.Scanner.scan(Scanner.java:339)
    at org.eclipse.jetty.util.Scanner.start(Scanner.java:275)
    at org.eclipse.jetty.deploy.providers.ScanningAppProvider.doStart(ScanningAppProvider.java:114)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
    at org.eclipse.jetty.deploy.DeploymentManager.startAppProvider(DeploymentManager.java:540)
    at org.eclipse.jetty.deploy.DeploymentManager.doStart(DeploymentManager.java:219)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
    at org.eclipse.jetty.util.component.AggregateLifeCycle.doStart(AggregateLifeCycle.java:42)
    at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:52)
    at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:96)
    at org.eclipse.jetty.server.Server.doStart(Server.java:258)
    at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
    at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1068)
    at java.security.AccessController.doPrivileged(Native Method)
    at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:993)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.eclipse.jetty.start.Main.invokeMain(Main.java:477)
    at org.eclipse.jetty.start.Main.start(Main.java:623)
    at org.eclipse.jetty.start.Main.parseCommandLine(Main.java:273)
    at org.eclipse.jetty.start.Main.main(Main.java:81)

Viewing 4 posts - 1 through 4 (of 4 total)
Reply To: Jetty 7.2.x deployments and MyEclipse limitations?

You must be logged in to post in the forum log in