[JBoss JIRA] Updated: (TEIIDDES-78) WSDL Importers throwing ClassNotFoundExceptions. Class Loading problems.
by Barry LaFond (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-78?page=com.atlassian.jira.pl... ]
Barry LaFond updated TEIIDDES-78:
---------------------------------
Summary: WSDL Importers throwing ClassNotFoundExceptions. Class Loading problems. (was: WSDL into Web Service importer exception)
Description:
Cannot import "WSDL to Web Service". Get nested exception initiating at the following:
Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
See attached stack trace
Also can't import "Web Service as Relational Source model"
was:
Cannot import "WSDL to Web Service". Get nested exception initiating at the following:
Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
See attached stack trace
Priority: Blocker (was: Major)
> WSDL Importers throwing ClassNotFoundExceptions. Class Loading problems.
> ------------------------------------------------------------------------
>
> Key: TEIIDDES-78
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-78
> Project: Teiid Designer
> Issue Type: Bug
> Reporter: Barry LaFond
> Assignee: Dan Florian
> Priority: Blocker
> Fix For: 6.0.0
>
> Attachments: JBEDSP_228_StackTrace.txt
>
>
> Cannot import "WSDL to Web Service". Get nested exception initiating at the following:
> Caused by: java.lang.ClassCastException: org.apache.xerces.parsers.XIncludeAwareParserConfiguration
> at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
> at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> See attached stack trace
> Also can't import "Web Service as Relational Source model"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months
[JBoss JIRA] Resolved: (TEIIDDES-106) No Need To Have Built-In (Reserved) Connector Jar Names
by Dan Florian (JIRA)
[ https://jira.jboss.org/jira/browse/TEIIDDES-106?page=com.atlassian.jira.p... ]
Dan Florian resolved TEIIDDES-106.
----------------------------------
Resolution: Done
This work was done some time ago. The class most affected was DqpExtensionsHandler as it had public methods that dealt with the built-in extension jars. The connector importer framework and some connector-related actions were also changed.
> No Need To Have Built-In (Reserved) Connector Jar Names
> -------------------------------------------------------
>
> Key: TEIIDDES-106
> URL: https://jira.jboss.org/jira/browse/TEIIDDES-106
> Project: Teiid Designer
> Issue Type: Task
> Components: Teiid Integration
> Affects Versions: 6.0.0
> Reporter: Dan Florian
> Assignee: Dan Florian
> Fix For: 6.0.0
>
>
> In 5.5.3 and prior, the Designer had a set of built-in connector jars. The Designer had a requirement that the user could not import connector or UDF jar having a name of one of those built-in jars. For Westport that requirement is gone because of changes to the DQP. Numerous classes have methods or reference methods written for this concept. All code pertaining to the built-in connector jars should be removed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 8 months