[
https://issues.apache.org/jira/browse/JUDDI-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13899268#comment-13899268
]
Kurt T Stam commented on JUDDI-850:
-----------------------------------
To reproduce, run jUDDI v2 and set the following connection info the uddi.xml
of the console:
{code:title=uddi.xml|borderStyle=solid}
<node>
<!-- required 'default' node -->
<name>default</name>
<description>UDDIv2 Node (localhost)</description>
<!-- JAX-WS Transport -->
<proxyTransport>org.apache.juddi.v3.client.transport.JAXWSv2TranslationTransport</proxyTransport>
<inquiryUrl>http://localhost:8080/juddi/inquiry</inquiryUrl>
<publishUrl>http://localhost:8080/juddi/publish</publishUrl>
</node>
{code}
> 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)
