You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "ASF subversion and git services (JIRA)" <ju...@ws.apache.org> on 2014/02/13 16:44:20 UTC
[jira] [Commented] (JUDDI-850) Filter invalid find qualifiers from
UDDIv2 Mappers
[ https://issues.apache.org/jira/browse/JUDDI-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900435#comment-13900435 ]
ASF subversion and git services commented on JUDDI-850:
-------------------------------------------------------
Commit 1567953 from [~spyhunter99] in branch 'juddi/trunk'
[ https://svn.apache.org/r1567953 ]
JUDDI-850 minor code updates to support UDDIv2 TCK test cases. filtering out case insensitive Match for uddiv3 to v2
JUDDI-821 fixing missed typo
> Filter invalid find qualifiers from UDDIv2 Mappers
> --------------------------------------------------
>
> 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)