juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Luisser (Jira)" <juddi-...@ws.apache.org>
Subject [jira] [Created] (JUDDI-1007) Not saving an Access Point Type correctly in the database when using juddiv2
Date Fri, 26 Jun 2020 13:35:00 GMT
Steve Luisser created JUDDI-1007:
------------------------------------

             Summary: 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


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)

Mime
View raw message