Weblogic.uddi.client.* javadocs?

Question

I can't seem to find these in the WLS javadocs I downloaded - did I just miss them?
Also, I was curious why these pkgs are in weblogic.jar and not in the webservice
jars?
Thanks.

Answer 1

Hi Babak,
Yeah! Acumen Technologies guys are lurking on this newsgroup too :-)
I guess my point is that JAXR is targeted at developers that are writing code
to interact with a registry (like AUDDI), not registry providers like Acumen Tech.
Pete is in that targeted group, so it (the JAXR RI) maybe something he would be
interested in investigating. When I said "JAXR-compliant", I was basically referring
to products from vendors that implement the stuff in %JAXR_LIB%\jaxr-api.jar.
Sun's RI (%JAXR_LIB%\jaxr-ri.jar), is an example of what I meant by a "JAXR-compliant"
product :-)
Regards,
Mike Wooten
PS: I want to officially "get in the" for the 2.0 release!
"Babak Mozaffari" <[email protected]> wrote:
Hi Guys, sorry for jumping into the conversation so late.
As you mentioned yourselves, UDDI only defines a SOAP interface and thus
no
standard Java API for UDDI exists.
Being based on the same SOAP API, most Java APIs bear strong resemblence
to
one another, therefore somewhat simplifying migration from one client
to
another. As Mike points out, this is not the case with JAXR. In an attempt
to be generic, JAXR has dissassociated itself from the UDDI API and provides
new terminology that maps to both UDDI and ebXML.
As for Acumen's plans, our next release (2.0, due for release this October)
will include a well-designed Java client along with JavaDocs, documentation
and samples on how to use it. Though resembling UDDI4J, WebLogic UDDI
Client
and other popular client packages, it has been tuned to provide more
flexibility and ease of use. Numerous class castings required in other
clients are not necessary and utility methods facilitate the use of UDDI
to
publish and retrieve Web Services with minimal understanding of the UDDI
technology. This client can be used with all UDDI v2.0 registries and
supports HTTPS calls as well.
As for being JAXR-compliant, should we be talking about the UDDI registries,
they are all inherently JAXR-compliant and in fact it is JAXR that is
UDDI-compliant. So any JAXR implementation may be used to talk to AUDDI
(UDDI registry of WLS), including the RI. Therefore providing a
production-quality implementation of JAXR, as valuable as it may be,
does
not really fall on the shoulders of a UDDI provider.
Regards,
Babak Mozaffari
Senior Software Engineer
Acumen Advanced Technologies Inc.
www.AcumenTechnologies.com
2235 Sheppard Ave. E., Suite 1501
Toronto, ON M2J 5B5, Canada
Tel: [phone] Ext: 224
Cell: [phone]
Fax: [phone]
[email protected]
"Michael Wooten" <[email protected]> wrote in message
news:[email protected]...
Hi Pete,
Correct, "the API" is the SOAP requests and responses, not a literalset
of interfaces
(i.e. methods, etc) to implement. If you download the Acumen AUDDI1.2
upgrade
for WebLogic Server 7.0, you'll find the PDFs for "the API" and datastructure
specs inside it. Most Java implementations just deal with the datastructures
as "pure state with relationships".
Because there is no "set of programming language interfaces" for UDDI,every vendor's
UDDI implementation will most likely be different! This is, of course,not
so
good for folks that want to try out implementations from differentvendors, because
it means they have to change a bunch of code for each vendor :-) Notcool,
right?
Agreed. That's why I introduced the topic of using JAXR-compliantimplementations.
The only one I know of is the RI (Reference Implementation) that comesin
the
Summer '02 JWSDP, from Javasoft.
Unfortunately, the JAXR API doesn't look anything like the UDDI clientpackages
from most Java vendors :-( Check out thesamples/jaxr-browser/JAXRClient.java
file, in the Summer '02 JWSDP download, for the "agonizing reality"!Arrrgh!
I don't really know about BEA's plans with regards to developing aJAXR-compliant
implementation, so...
Regards,
Mike Wooten
"Peter" <[email protected]> wrote:
Michael, sure appreciate your very comprehensive and thoughtful
response
to my
questions. Let me clarify one thing you said: the UDDI spec seemsto
only prescribe
the individual UDDI SOAP messages that a UDDI operator must understand,
as well
the appropriate responses. But it does not prescribe a set of "uddiclient
function
calls", unless it is implying that each SOAP message should be a function
call?
It may be too that I am looking at a different document than you,since
the UDDI
"spec" is really a number of separate docs...
I presume BEA/Acumen will be enhancing the UDDI API to be JAXR-compliant?
Thanks again! Peter
"Michael Wooten" <[email protected]> wrote:
Hi Peter,
No, the API (i.e. function calls that must be on the inquiry and
publish
objects)
is standardized, and appears in the UDDI specification. Note thatthe
JAXR API
(http://java.sun.com/xml/downloads/jaxr.html) provides a client
interface
to UDDI
registries, also. In addition, it provides a client interface toebXML
registries.
The main reason why folks are considering using JAXR over
vendor-specific
UDDI
clients (like weblogic.uddi.client.*, and UDDI4J), is that it allows
them the
same benefit they get from JAXP - their code should work with anyJAXR-compliant
UDDI client, from any vendor :-) Which means, they can switch UDDIclient
packages
without having to change their code.
Check out the following link for more specifics:
http://java.sun.com/xml/downloads/jaxr.html
FTR (For The Record): weblogic.uddi.client.* is not JAXR-compliant
yet.
I think
it has complete support for UDDI v1.0, though :-) Not sure if itsupports
UDDI
v2.0, because I didn't see stuff like PublisherAssertions in there.The
Acumen
Technologies UDDI stuff (in $WL_HOME/server/lib/uddi.war) has support
for UDDI
v2.0, though. The developer interface (i.e. java packages, object
interfaces,
etc.) is different than the weblogic.uddi.client.* UDDI client, andI
haven't
been able to locate Javadocs for it on Acumen's web site
(http://www.acumentechnologies.com/site.asp).
Maybe, the Javadocs are in the SE (Standard Edition) eval download,available
on their site.
Regards,
Mike Wooten
"Peter" <[email protected]> wrote:
Thanks Michael - it's exactly what I was looking for. I downloaded
the
WLS javadocs
and did not find these packages there, at least not when I did it
a
week
ago.
This client API is great stuff! I just want to confirm one thing:
that
this API
has not been spec'ed out by UDDI nor is it a JSR, at this point?If
not,
it should
be! Thanks again, Peter
"Michael Wooten" <[email protected]> wrote:
Hi Peter,
The following link points to what you are looking for :-)
http://edocs.bea.com/wls/docs70/javadocs/weblogic/uddi/client/service/pa
ckage-frame.html
I'm not sure if this is in the downloadable Javadocs or not. Ionly
have
a 28.8
dialup, so I can't pull these huge jars down to look :-)
Regards,
Mike Wooten
"Peter Go" <[email protected]> wrote:
I can't seem to find these in the WLS javadocs I downloaded -
did
I
just
miss them?
Also, I was curious why these pkgs are in weblogic.jar and not
in
the
webservice
jars?
Thanks.