juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (Jira)" <juddi-...@ws.apache.org>
Subject [jira] [Updated] (JUDDI-1006) Saving an Access Point Type
Date Tue, 23 Jun 2020 02:20:00 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Alex O'Ree updated JUDDI-1006:
    Fix Version/s: 3.3.9

> 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
>             Fix For: 3.3.9
> 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: “[[test@email.com|mailto:[test@email.com]|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

View raw message