[
https://issues.apache.org/jira/browse/JUDDI-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899667#comment-13899667
]
Alex O'Ree commented on JUDDI-850:
----------------------------------
root causes:
1) having juddiv2.war deployed in tomcat with juddi-gui caused some kind of
class path issue with jaxb. see
http://stackoverflow.com/questions/17114090/java-lang-classcastexception-com-sun-xml-bind-v2-runtime-jaxbcontextimpl-cannot
2) The Mapper, which enables us to use UDDI v2 interfaces using UDDIv3 code,
did not remove non-UDDIv2 compliant find qualifiers, namely approximateMatch.
> juddi-console supporting UDDIv2
> -------------------------------
>
> Key: JUDDI-850
> URL: https://issues.apache.org/jira/browse/JUDDI-850
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-gui
> Affects Versions: 3.2
> Reporter: Kurt T Stam
> Assignee: Alex O'Ree
> Fix For: 3.2.1
>
>
> By allowing the user to select a uddiv2 connection, I think we are saying
> that we support this combination?
> When I try to use the console with juddi v2, I get a the following exception
> when it is trying to create a subscription connection in the UDDIHub:
> org.apache.juddi.v3.client.transport.TransportException:
> com.sun.xml.bind.v2.runtime.JAXBContextImpl cannot be cast to
> com.sun.xml.bind.api.JAXBRIContext
> when it is trying to:
> subscription = transport.getUDDISubscriptionService();
> Which is understandable since the UDDI v2 protocol does not support this.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
