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

Jeff Faath resolved JUDDI-139.
------------------------------

    Resolution: Fixed

This has been completed.  Key generation policy:

1)      A "root" publisher will be installed with jUDDI.  This publisher is an 
Administrator and owns the top-level domain key generator (ex. 
"uddi:juddi.apache.org:keygenerator").  This top level domain is configurable 
by the jUDDI implementer.
2)      A "uddi" publisher will be installed with jUDDI that owns all the 
keyGenerators described in the spec (among many other pre-defined entities).  
This publisher will only be used for UDDI-specific publishing which will really 
only occur whenever the spec changes.
3)      Other publishers can publish as many keyGenerators as they want, BELOW 
the root key generator (ex. "uddi:juddi.apache.org:mykeygen:keygenerator").  
4)      Once a key generator is "reserved", no other publisher can own a key 
generator in the same "key space".
5)      When a publisher provides a key for a new entity, it will be checked 
against all the key generators it owns to ensure it is valid.  It is up to the 
publisher to organize the keys  as they see fit (consistent with spec).
6)      When publisher has no key generators, yet tries to publish a new entity 
without a key, key is generated using root key generator and appending a UUID.
7)      When publisher has key generators, yet tries to publish a new entity 
without a key, key is generated using root key generator and appending a UUID.  
It is not up to jUDDI to determine which key generator they might want to use.


> Create key generation strategy
> ------------------------------
>
>                 Key: JUDDI-139
>                 URL: https://issues.apache.org/jira/browse/JUDDI-139
>             Project: jUDDI
>          Issue Type: Task
>    Affects Versions: 3.0
>            Reporter: Jeff Faath
>            Assignee: Jeff Faath
>             Fix For: 3.0
>
>
> UDDI v3 allows users to supply their own key for entities they save.  
> However, they are also allowed to pass a null value, thereby relying on the 
> UDDI implementation to generate the key.
> Consult the UDDI v3 spec to determine the best way to generate keys:
> http://uddi.org/pubs/uddi-v3.0.2-20041019.htm

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