[
https://issues.apache.org/jira/browse/JUDDI-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17142545#comment-17142545
]
ASF subversion and git services commented on JUDDI-1006:
--------------------------------------------------------
Commit ac888830b6e710334643f4ce33e5dd9f34d52db3 in juddi's branch
refs/heads/master from Alex O'Ree
[ https://gitbox.apache.org/repos/asf?p=juddi.git;h=ac88883 ]
JUDDI-1006 fixed, along with some light refactoring
> Saving an Access Point Type
> ---------------------------
>
> Key: JUDDI-1006
> URL: https://issues.apache.org/jira/browse/JUDDI-1006
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Reporter: Alex O'Ree
> Priority: Minor
>
> Using juddi default (v3) you can create an access point type of Mailto which
> saves to the database and is displayed properly in the UI. When using
> juddiv2, the access point type displays as endpoint.
>
> Using juddiv2 create an Access Point using a random binding template key,
> access point type “Mailto” and Access Point Value:
> “[[t...@email.com|mailto:[t...@email.com]|mailto:t...@email.com]” and save
> the access point. The value endPoint is saved in the database, not Mailto.
> If the database contains a value of Mailto in the access_point_type field, it
> still displays endPoint in the UI.
>
> Note that the response from the v2 Inquire API returns the value of mailto if
> this value is in the database.
> <ns2:accessPoint
> URLType="mailto">[mailto:t...@email.com</ns2:accessPoint|mailto:t...@email.com%3c/ns2:accessPoint]>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
