You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex O'Ree (Jira)" <ju...@ws.apache.org> on 2020/07/04 02:07:00 UTC
[jira] [Resolved] (JUDDI-1007) Not saving an Access Point Type
correctly in the database when using juddiv2
[ https://issues.apache.org/jira/browse/JUDDI-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex O'Ree resolved JUDDI-1007.
-------------------------------
Resolution: Fixed
> Not saving an Access Point Type correctly in the database when using juddiv2
> ----------------------------------------------------------------------------
>
> Key: JUDDI-1007
> URL: https://issues.apache.org/jira/browse/JUDDI-1007
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.3.7
> Reporter: Steve Luisser
> Priority: Major
>
> 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: "mailto:test@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:test@email.com</ns2:accessPoint|mailto:test@email.com%3c/ns2:accessPoint]>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)