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] [Closed] (JUDDI-590) getAssertionStatusReport does not return incomplete assertions
Date Sun, 05 May 2013 23:22:15 GMT

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

Alex O'Ree closed JUDDI-590.
----------------------------

    Resolution: Fixed
      Assignee: Alex O'Ree  (was: Kurt T Stam)
    
> getAssertionStatusReport does not return incomplete assertions
> --------------------------------------------------------------
>
>                 Key: JUDDI-590
>                 URL: https://issues.apache.org/jira/browse/JUDDI-590
>             Project: jUDDI
>          Issue Type: Bug
>            Reporter: Alex O'Ree
>            Assignee: Alex O'Ree
>             Fix For: 3.2
>
>
> snippet from the spec
> The get_assertionStatusReport API call provides administrative support for determining
the status of current and outstanding publisher assertions that involve any of the business
registrations managed by the individual publisher.  Using this API, a publisher can see the
status of assertions that they have made, as well as see assertions that others have made
that involve businessEntity structures controlled by the requesting publisher.   See Appendix
A Relationships and Publisher Assertions for more information.
> http://uddi.org/pubs/uddi-v3.0.2-20041019.htm#_Toc85908109
> code snippet - this always returns null, even when 1 of 2 publishers have asserted a
relationship on one of their owning businesses.
>  publish.getAssertionStatusReport(GetToken(), CompletionStatus.STATUS_FROM_KEY_INCOMPLETE);

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message