[ 
https://issues.apache.org/jira/browse/SCOUT-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683000#action_12683000
 ] 

Tom Cunningham commented on SCOUT-55:
-------------------------------------

Having a hard time figuring out how to do this or whether this is possible.     
 When we get the response from UDDI, we get a BusinessEntity object that has an 
authorizedName but I don't see how to reliably map that to a username - which 
is what is stored in UDDI.        There also doesn't seem to be any way of 
selecting by caller in UDDI.      I don't see a way of doing this writing 
custom methods into a UDDI implementation like jUDDI.

I've written a test for this, and extended BaseTestCase so that it can handle 
two logins, checking those in under this case.     Suggesting we defer or mark 
will not fix.

>  Scout ignores ownership of registry objects when querying with 
> BusinessQueryManager.getRegistryObjects(LifeCycleManager.ORGANIZATION)
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SCOUT-55
>                 URL: https://issues.apache.org/jira/browse/SCOUT-55
>             Project: Scout
>          Issue Type: Bug
>          Components: Scout Implementation
>         Environment: MacOS X 10.4.10, J2SE build 1.5.0_07-164, sample code 
> run from console with scout-1.0rc1.jar and jaxr-api-1.0rc1.jar from the Scout 
> web site against current jUDDI snapshot deployed in Tomcat 5.5.20 and JBoss 
> 4.0.2
>            Reporter: Javier Botana
>            Assignee: Kurt T Stam
>             Fix For: 1.0
>
>
> BusinessQueryManager.getRegistryObjects(LifeCycleManager.ORGANIZATION) to 
> query for the organization(s) owned by a specific publisher, it returns all 
> organizations regardless if there are owned by the caller

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to