[ 
https://issues.apache.org/jira/browse/AXIS2-4901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andreas Veithen updated AXIS2-4901:
-----------------------------------

    Component/s:     (was: codegen)
                 ide plugins
        Summary: LinkageError related to DOM classes when using the codegen 
plugin for Eclipse  (was: Problems occurred when invoking code from plug-in: 
"org.eclipse.jface". )

> LinkageError related to DOM classes when using the codegen plugin for Eclipse
> -----------------------------------------------------------------------------
>
>                 Key: AXIS2-4901
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4901
>             Project: Axis2
>          Issue Type: Bug
>          Components: ide plugins
>    Affects Versions: 1.5.3
>         Environment: Eclipse : Version: Helios Service Release 1 
> Build id: 20100917-0705, OS: Windows; axis2-eclipse-codegen-plugin-1.5.3 
>            Reporter: raghutpk
>            Assignee: Andreas Veithen
>             Fix For: 1.5.4
>
>
> After installing the code gen plugin, you restart the eclipse and click on 
> the Axis2 Code Generator in the Axis2Wizards This log props out 
> An error has occurred. See error log for more details. 
> loader constraint violation in interface itable initialization: when 
> resolving method 
> "org.apache.xerces.dom.CoreDocumentImpl.getDomConfig()Lorg/w3c/dom/DOMConfiguration;"
>  the class loader (instance of 
> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current 
> class, org/apache/xerces/dom/CoreDocumentImpl, and the class loader (instance 
> of <bootloader>) for interface org/w3c/dom/Document have different Class 
> objects for the type org/w3c/dom/DOMConfiguration used in the signature.
> In addition this is the error log which throws up 
> Message: 
> Problems occurred when invoking code from plug-in: "org.eclipse.jface". 
> Exception Stack Trace: 
> java.lang.LinkageError: loader constraint violation in interface itable 
> initialization: when resolving method 
> "org.apache.xerces.dom.CoreDocumentImpl.getDomConfig()Lorg/w3c/dom/DOMConfiguration;"
>  the class loader (instance of 
> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current 
> class, org/apache/xerces/dom/CoreDocumentImpl, and the class loader (instance 
> of <bootloader>) for interface org/w3c/dom/Document have different Class 
> objects for the type org/w3c/dom/DOMConfiguration used in the signature 
> at org.apache.xerces.parsers.AbstractDOMParser.startDocument(Unknown Source) 
> at org.apache.xerces.impl.dtd.XMLDTDValidator.startDocument(Unknown Source) 
> at org.apache.xerces.impl.XMLDocumentScannerImpl.startEntity(Unknown Source) 
> at org.apache.xerces.impl.XMLVersionDetector.startDocumentParsing(Unknown 
> Source) 
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) 
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) 
> at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) 
> at org.apache.xerces.parsers.DOMParser.parse(Unknown Source) 
> at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) 
> at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(Unknown Source) 
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) 
> at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) 
> at 
> org.apache.axis2.tool.codegen.eclipse.util.WSDLPropertyReader.readWSDL(WSDLPropertyReader.java:53)
>  
> at 
> org.apache.axis2.tool.codegen.eclipse.ui.OptionsPage.populateParamsFromWSDL(OptionsPage.java:759)
>  
> [ Show ยป ] raghutpk added a comment - 29/Nov/10 12:07 PM In addition this is 
> the error log which throws up Message: Problems occurred when invoking code 
> from plug-in: "org.eclipse.jface". Exception Stack Trace: 
> java.lang.LinkageError: loader constraint violation in interface itable 
> initialization: when resolving method 
> "org.apache.xerces.dom.CoreDocumentImpl.getDomConfig()Lorg/w3c/dom/DOMConfiguration;"
>  the class loader (instance of 
> org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current 
> class, org/apache/xerces/dom/CoreDocumentImpl, and the class loader (instance 
> of <bootloader>) for interface org/w3c/dom/Document have different Class 
> objects for the type org/w3c/dom/DOMConfiguration used in the signature at 
> org.apache.xerces.parsers.AbstractDOMParser.startDocument(Unknown Source) at 
> org.apache.xerces.impl.dtd.XMLDTDValidator.startDocument(Unknown Source) at 
> org.apache.xerces.impl.XMLDocumentScannerImpl.startEntity(Unknown Source) at 
> org.apache.xerces.impl.XMLVersionDetector.startDocumentParsing(Unknown 
> Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) 
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at 
> org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at 
> org.apache.xerces.parsers.DOMParser.parse(Unknown Source) at 
> org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source) at 
> com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(Unknown Source) at 
> com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at 
> com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source) at 
> org.apache.axis2.tool.codegen.eclipse.util.WSDLPropertyReader.readWSDL(WSDLPropertyReader.java:53)
>  at 
> org.apache.axis2.tool.codegen.eclipse.ui.OptionsPage.populateParamsFromWSDL(OptionsPage.java:759)
>  
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> I reproduced the issue when I created a new wsdl in a java project in eclipse 
> and then tried to access the Axis2CodeGenerator.When I click on it the above 
> screen props out
> Please look into it asap.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to