[juddi-Developers] RE: Open request for jUDDI feature ideas

[Jin Tong <ni...@yahoo.com>]

Hello:

Here is my list regarding feature ideas:

1. I think some default/simple security implementation
should be in 
place for a 1.0 release, so people can use it out of
box. (Isn't the 
security check now simply returns when the name of the
user is defined 
in the publisher table?) I'd like to see a simple
UI-based user 
management piece and real validation of the user
creditials (password 
will be fine). People can still programmticall plug-in
their own 
authentication backend at the same time.

2. Some value-added APIs on top of what UDDI spec
offers. E.g.: UDDI's 
find_service will only return a simple service data
object, I'd like an 
API call to do a "find" but return all the details
like those returned 
by get_serviceDetail API. Systinet UDDI also has a set
of so-call 
"super-inquiry" API. The purpose is to offer locked-in
users performance 
-- less round-trips to the UDDI in SOAP calls. These
value-added APIs 
should also be exposed through java client-side API.

3. Open-up the server-side API in Java via RMI/ejb or
just direct 
library invocation. This would benefit people who are
embedding a UDDI 
server inside their apps.

Jin


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com