Hi,
We are experiencing a problem on Websphere 6.1.0.11 with Tuscany 1.0.
When we set all classloader properties, as mentioned before, we are
getting the following exception when we try to call Websphere's
AdminService.getAttribute:
Stack Dump = java.lang.ClassCastException:
org.apache.xerces.jaxp.SAXParserFactoryImpl incompatible with
javax.xml.parsers.SAXParserFactory
at javax.xml.parsers.SAXParserFactory.newInstance(Unknown Source)
at
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.makeParser(XMLLoadImpl.java:299)
at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:140)
at
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:179)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.basicDoLoad(CompatibilityXMIResourceImpl.java:180)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.doLoad(CompatibilityXMIResourceImpl.java:173)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1094)
at
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:900)
at
org.eclipse.wst.common.internal.emf.resource.CompatibilityXMIResourceImpl.load(CompatibilityXMIResourceImpl.java:259)
at
com.ibm.websphere.resource.WASResourceImpl.load(WASResourceImpl.java:61)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:249)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:264)
at
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource(ResourceSetImpl.java:390)
at
com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:158)
at
com.ibm.websphere.resource.WASResourceSetImpl.getResource(WASResourceSetImpl.java:143)
at
com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:325)
at
com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:298)
at
com.ibm.ws.runtime.service.ConfigRootImpl.getResource(ConfigRootImpl.java:274)
at
com.ibm.ws.runtime.component.EndPointMgrImpl.getNodeHostName(EndPointMgrImpl.java:488)
at
com.ibm.ws.management.AdminHelperImpl.getNodeHostName(AdminHelperImpl.java:116)
at
com.ibm.ws.management.component.JVMMBean.getJVMNode(JVMMBean.java:167)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.Trampoline.invoke(MethodUtil.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:265)
at
javax.management.modelmbean.RequiredModelMBean.invokeMethod(RequiredModelMBean.java:1089)
at
javax.management.modelmbean.RequiredModelMBean.invoke(RequiredModelMBean.java:971)
at
javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1373)
at
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.getAttribute(DynamicMetaDataImpl.java:114)
at
com.sun.jmx.mbeanserver.MetaDataImpl.getAttribute(MetaDataImpl.java:199)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:656)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:677)
at
com.ibm.ws.management.AdminServiceImpl.getAttribute(AdminServiceImpl.java:687)
at com.company.websphere.WebSphereServerHelper.initialise(Unknown
Source)
.....
It is really strange, because
org.apache.xerces.jaxp.SAXParserFactoryImpl is derived from
SAXParserFactory as far as I know.
Does anybody have an idea what could be causing the problem?
Thanks,
Radim
On 9/20/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> Radim Kolarik wrote:
> > Hi Sebastien,
> >
> > I can confirm that you are right, that was the problem. I would swear
> > I saw many examples that had the implementation element as last one in
> > the composite file ;-).
> >
> > Thanks again,
> > Radim
> >
> >
>
> Yeah I had to fix them all for the 1.0 release :) I guess it shows that
> this automatic validation is useful.
>
> I'm going to put together a small Eclipse plugin that will register the
> same XMLSchemas in the Eclipse WTP XML catalog. It'll help people edit
> correct .composite and .componentType files using the Eclipse XML editor
> and validate them in their IDE.
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
