[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim McConnell closed GERONIMODEVTOOLS-184. ------------------------------------------ Resolution: Fixed The changes in r568286 to update devtools\eclipse-plugin\trunk to support the 2.0.1 version of the Geronimo server have fixed this problem. The problem resulted from not having all the dependencies required for 2.0.1 (namely geronimo-schema-jee_5-1.1.jar). I've also published a new version of the plugin to the unstable repo. > An internal error occurred during: "Publishing to Apache Geronimo v2.0 Server > at localhost..." when deploy sample within Eclipse > -------------------------------------------------------------------------------------------------------------------------------- > > Key: GERONIMODEVTOOLS-184 > URL: > https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-184 > Project: Geronimo-Devtools > Issue Type: Bug > Components: eclipse-plugin > Affects Versions: 2.0 > Environment: Windows xp sp2, Eclipse Version: 3.3.0 > Reporter: Song > Assignee: Tim McConnell > Fix For: 2.0 > > > After deployed samples (such as cviewer) to the server within Eclipse, Run > As--Run on Server,An internal error occurred. > In fact, the cviewer sample can be deployed and executed successfully via the > command line. > Detailed error message see the below: > ----------------------------------------------------------------------------------- > java.lang.NoSuchMethodError: > org/apache/xmlbeans/XmlBeans.typeSystemForClassLoader(Ljava/lang/ClassLoader;Ljava/lang/String;)Lorg/apache/xmlbeans/SchemaTypeSystem; > at org.apache.geronimo.deployment.xbeans.EnvironmentDocument.<clinit>(Unknown > Source) > at java.lang.J9VMInternals.initializeImpl(Native Method) > at java.lang.J9VMInternals.initialize(J9VMInternals.java:192) > at > org.apache.geronimo.st.v20.core.GeronimoV20Utils.getConfigId2(GeronimoV20Utils.java:94) > at > org.apache.geronimo.st.v20.core.GeronimoV20VersionHandler.getConfigID(GeronimoV20VersionHandler.java:36) > at > org.apache.geronimo.st.core.DeploymentUtils.getLastKnownConfigurationId(DeploymentUtils.java:202) > at > org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.getLastKnowConfigurationId(GeronimoServerBehaviourDelegate.java:456) > at > org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.doAdded(GeronimoServerBehaviourDelegate.java:402) > at > org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.invokeCommand(GeronimoServerBehaviourDelegate.java:367) > at > org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModule(GeronimoServerBehaviourDelegate.java:267) > at > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:749) > at > org.apache.geronimo.st.core.GeronimoServerBehaviourDelegate.publishModules(GeronimoServerBehaviourDelegate.java:234) > at > org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:669) > at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:887) > at org.eclipse.wst.server.core.internal.Server.publish(Server.java:874) > at > org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:72) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.