Home » Language IDEs » ServerTools (WTP) » Case problem with org.eclipse.wst.wsdl
Case problem with org.eclipse.wst.wsdl [message #195596] |
Tue, 03 July 2007 15:36  |
Eclipse User |
|
|
|
Originally posted by: jdoyleoss.gmail.com
I'm having a problem using org.eclipse.wst.wsdl. I'm creating a resource
from a WSDL and a ClassNotFoundException is occurring. I have debugged it
down to the point where the EPackage from the org.eclipse.wst.wsdl plugin
is called to resolve the EClassifier for the wsdl:definitions tag. It
seems that the EPackage is only aware of Definitions, not definitions as a
name. This seems like a defect to me, since it is defined as
wsdl:definitions in the wsdl schema. I imagine this code should be case
sensitive, but think it should be aware of the lower case name.
I didn't find a defect logged. Has anyone seen this before?
Thanks
~jd
|
|
| |
Re: Case problem with org.eclipse.wst.wsdl [message #195698 is a reply to message #195604] |
Thu, 05 July 2007 10:41   |
Eclipse User |
|
|
|
Originally posted by: jdoyleoss.gmail.com
My plugin is running in an eclipse based environment and uses the
org.eclipse.wst.wsdl plugin. I haven't registered as you describe because
I am in an eclipse env. When I create the resource the resource
implementaion you noted is implementation that is created for me. My code
is this:
Resource res = resourceSet.getResource(uri, true);
Resulting in the following stack:
Thread [main] (Suspended (entry into method <init> in
ClassNotFoundException))
ClassNotFoundException.<init>(String, EFactory, String, int,
int) line: 28
SAXXMIHandler(XMLHandler).validateCreateObjectFromFactory(EF actory,
String, EObject) line: 1402
SAXXMIHandler(XMLHandler).createObjectByType(String, String,
boolean) line: 755
SAXXMIHandler(XMLHandler).createTopObject(String, String)
line: 765
SAXXMIHandler(XMLHandler).processElement(String, String,
String) line: 462
SAXXMIHandler(XMIHandler).processElement(String, String,
String) line: 65
SAXXMIHandler(XMLHandler).startElement(String, String, String)
line: 449
SAXWrapper.startElement(String, String, String, Attributes)
line: 73
SAXParserImpl$JAXPSAXParser(AbstractSAXParser).startElement( QName,
XMLAttributes, Augmentations) line: not available
XMLDTDValidator.startElement(QName, XMLAttributes,
Augmentations) line: not available
XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanS tartElement()
line: not available
XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook ()
line: not available
XMLDocumentScannerImpl$ContentDispatcher(XMLDocumentFragment ScannerImpl$FragmentContentDispatcher).dispatch(boolean)
line: not available
XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanD ocument(boolean)
line: not available
XIncludeAwareParserConfiguration(XML11Configuration).parse(b oolean) line:
not available
XIncludeAwareParserConfiguration(XML11Configuration).parse(X MLInputSource)
line: not available
SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource)
line: not available
SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSo urce) line:
not available
SAXParserImpl$JAXPSAXParser.parse(InputSource) line: not
available
SAXParserImpl(SAXParser).parse(InputSource, DefaultHandler)
line: not available
XMILoadImpl(XMLLoadImpl).load(XMLResource, InputStream, Map)
line: 140
XMIResourceImpl(XMLResourceImpl).doLoad(InputStream, Map)
line: 169
XMIResourceImpl(ResourceImpl).load(InputStream, Map) line: 977
XMIResourceImpl(ResourceImpl).load(Map) line: 832
ResourceSetImpl.demandLoad(Resource) line: 249
ResourceSetImpl.demandLoadHelper(Resource) line: 264
ResourceSetImpl.getResource(URI, boolean) line: 349
The specific call that fails leading to the exception is
getEClassifier("definitions") call on the WSLDPackageImpl that is created
by the call to getResource(). If I change the value from "definitions" to
"Definitions", the call succeeds (then fails on the next call with
"types"). The version of the wsdl jar is 1.1.0 (200602061610). Perhaps
this is to old.
~john
|
|
|
Re: Case problem with org.eclipse.wst.wsdl [message #195706 is a reply to message #195698] |
Thu, 05 July 2007 11:03   |
Eclipse User |
|
|
|
Originally posted by: valentinbaciu.hotmail.com
For some reason it seems that your code actually ends up trying to load a
definition instance using the default EMF XML resource implementation
instead of the WSDL resource implementation. You can see this by following
the stack trace. Are you sure your URI references a file with a .wsdl
extension? If possible post a concrete example plug-in as a zip file here.
"jd" <jdoyleoss@gmail.com> wrote in message
news:1caba969c41398d6f13abd60ba59a62a$1@www.eclipse.org...
> My plugin is running in an eclipse based environment and uses the
> org.eclipse.wst.wsdl plugin. I haven't registered as you describe because
> I am in an eclipse env. When I create the resource the resource
> implementaion you noted is implementation that is created for me. My code
> is this:
>
>
> Resource res = resourceSet.getResource(uri, true);
>
> Resulting in the following stack:
>
> Thread [main] (Suspended (entry into method <init> in
> ClassNotFoundException))
> ClassNotFoundException.<init>(String, EFactory, String, int,
> int) line: 28
>
> SAXXMIHandler(XMLHandler).validateCreateObjectFromFactory(EF actory,
> String, EObject) line: 1402
> SAXXMIHandler(XMLHandler).createObjectByType(String, String,
> boolean) line: 755
> SAXXMIHandler(XMLHandler).createTopObject(String, String) line:
> 765
> SAXXMIHandler(XMLHandler).processElement(String, String,
> String) line: 462
> SAXXMIHandler(XMIHandler).processElement(String, String,
> String) line: 65
> SAXXMIHandler(XMLHandler).startElement(String, String, String)
> line: 449
> SAXWrapper.startElement(String, String, String, Attributes)
> line: 73
>
> SAXParserImpl$JAXPSAXParser(AbstractSAXParser).startElement( QName,
> XMLAttributes, Augmentations) line: not available
> XMLDTDValidator.startElement(QName, XMLAttributes,
> Augmentations) line: not available
>
> XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanS tartElement()
> line: not available
> XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook ()
> line: not available
>
> XMLDocumentScannerImpl$ContentDispatcher(XMLDocumentFragment ScannerImpl$FragmentContentDispatcher).dispatch(boolean)
> line: not available
>
> XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanD ocument(boolean)
> line: not available
>
>
> XIncludeAwareParserConfiguration(XML11Configuration).parse(b oolean) line:
> not available
>
> XIncludeAwareParserConfiguration(XML11Configuration).parse(X MLInputSource)
> line: not available
> SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource)
> line: not available
>
> SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSo urce) line:
> not available
>
> SAXParserImpl$JAXPSAXParser.parse(InputSource) line: not
> available
> SAXParserImpl(SAXParser).parse(InputSource, DefaultHandler)
> line: not available
> XMILoadImpl(XMLLoadImpl).load(XMLResource, InputStream, Map)
> line: 140
> XMIResourceImpl(XMLResourceImpl).doLoad(InputStream, Map) line:
> 169
> XMIResourceImpl(ResourceImpl).load(InputStream, Map) line: 977
> XMIResourceImpl(ResourceImpl).load(Map) line: 832
>
> ResourceSetImpl.demandLoad(Resource) line: 249
> ResourceSetImpl.demandLoadHelper(Resource) line: 264
> ResourceSetImpl.getResource(URI, boolean) line: 349
>
> The specific call that fails leading to the exception is
> getEClassifier("definitions") call on the WSLDPackageImpl that is created
> by the call to getResource(). If I change the value from "definitions" to
> "Definitions", the call succeeds (then fails on the next call with
> "types"). The version of the wsdl jar is 1.1.0 (200602061610). Perhaps
> this is to old.
>
> ~john
>
|
|
| | | | | | | |
Goto Forum:
Current Time: Wed Jul 23 17:33:09 EDT 2025
Powered by FUDForum. Page generated in 0.31501 seconds
|