UDDI API -- findService (WLS 7.0)

Group,
I have published a Web Service in the UDDI Directory Explorer. Is there any way
using the WebLogic UDDI client API to do a search on keywords in the service
description?
The API allows finding a service by name, by category, by tModel, by key. But
I can't find any way to search the service descriptions.
David Chung
[email protected]

Hello,
Right, the service description is an optional element and is not part of their
search mechanism that uses identifiers. Check out Appendix A of the following doc
on their usage of identifiers
http://www.uddi.org/pubs/DataStructure-V2.03-Published-20020719.pdf
Use the tModel (like they illustrate in Appendix E) to search for various parts.
The UDDI v3.0 (spec just out a few weeks ago) has enhanced many of the features of
the current v2.0 such as adding more complex queries.
http://www.uddi.org/pubs/uddi_v3_features.htm
Hope this helps,
Bruce
David Chung wrote:
Group,
I have published a Web Service in the UDDI Directory Explorer. Is there any way
using the WebLogic UDDI client API to do a search on keywords in the service
description?
The API allows finding a service by name, by category, by tModel, by key. But
I can't find any way to search the service descriptions.
David Chung
[email protected]

Similar Messages

How to get the service name of a webservice using UDDI API

Hi,
Iam working on setting up a dynamic partner link in a BPEL, by passing the endpoint of a web service queried from the UDDI (Oracle Service Registry 10.3 ) using the API. Iam able to do it successfully.
Now, for example I have two operations in my wsdl, one to createCustomer and the other to bookTicket. I need to get the operation name using UDDI API so that i can pass it along with the endpoint to the partner link. ie. When i need to createCustomer, my UDDI API code will need to get the service name createCustomer and the endpoint and I would pass them to the partnerlink and the createCustomer operation of my webservice would be called.
Can any one help me to get the service names of the wsdl using UDDI APIs.
Thanks,
Ananth

Hi sia,
1. Table is APQI
2. field name for session name is GROUPID
regards,
amit m.

Connection to UDDI via /uddi/api/inquiry

Hi,
I was reading the blogs and threads written on UDDI and the use of the publishing services. I have two questions that I would like to ask if anyone could please assist me with them:
- When using the local registry is it possible to login into the UDDI via the enquiry api. In other words can you login using http://<localhost>:port/uddi/api/inquiry? Do you perhaps know of some documentation I could use to work aound this. I have done the configuration but when I login I get a API-URL not found error.
- Which log is used to log failures to use UDDI?
Thanks,
Marcus Mbatha

Hi,
I'm facing exactly the same problem (404 Error when trying to connect the UDDI-API).
Unfortunately, I can not provide a solution for this, but there's another API, the one of the Services Registry, which is built on top of the UDDIv3 by SAP.
A list of the functions of this Web Service API can be found here: http://help.sap.com/saphelp_nwce10/helpdata/en/45/bc01c4900b0039e10000000a11466f/frameset.htm
The corresponding WSDL on your system can be found here:
http://DOMAINNAME:50000/ServicesRegistrySiService/ServicesRegistrySiPort?wsdl
(see also my post in this forum on Mar 20, 2008 1:42 PM )
I was able to invoke this Web Service from within my Java Application, so maybe you try this too.
One major drawback is of course, that this Services Registry API does not provide all of the functionality the official UDDI API does. For example, security, subscription etc...
If you find a solution for the UDDI API issue, pleas let me know!
Best regards,
Paul

Where can I download the JMS C API for WLS 12c?

Where can I download the JMS C API for WLS 12c? It doeesn't appear to be bundled with the standard or supplemental WLS zip files, nor obvious as a separate download bundle. Searching oracle.com finds plenty of documents which reference its existence, but not how to obtain it (unless I missed something). Pointers appreciated, thanks.

Thanks. Unfortunately, that's just a reference to the documentation. As I said, there's lots of reference to the C API in the documentation but I need the source code (I have an existing application running against WLS8.1/Solaris that I want to port to WLS12c/linux).

Oracle Service Registry: UDDI API v3 WSDL returns unknown-location-uri

Hi,
I've tried to access the UDDI API v3 wsdl and it's showing unknown-location-uri for all 3 APIs (security, publication, inquiry). I've tried updating tModels related to these 3 APIs and the results are the same. Does anyone know how to make it return a valid address location?
WSDL link: http://192.100.1.1:8021/registry/uddi/doc/wsdl/uddi_api_v3.wsdl
Result:
<?xml version="1.0" encoding="UTF-8" ?>
- <definitions name="UDDI_API_V3" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:api_v3_binding="urn:uddi-org:api_v3_binding" xmlns:tns="urn:uddi-org:api_v3" targetNamespace="urn:uddi-org:api_v3">
<documentation>Copyright 2001-2005 Systinet Corp. All rights reserved. Use is subject to license terms. WSDL SOAP/HTTP binding for UDDI V3 Security, Publication and Inquiry APIs.</documentation>
<import namespace="urn:uddi-org:api_v3_binding" location="uddi_api_v3_binding.wsdl" />
- <service name="UDDI_Security_SoapService">
- <port name="UDDI_Security_PortType" binding="api_v3_binding:UDDI_Security_SoapBinding">
<soap:address location="urn:unknown-location-uri" />
</port>
</service>
- <service name="UDDI_Publication_SoapService">
- <port name="UDDI_Publication_PortType" binding="api_v3_binding:UDDI_Publication_SoapBinding">
<soap:address location="urn:unknown-location-uri" />
</port>
</service>
- <service name="UDDI_Inquiry_SoapService">
- <port name="UDDI_Inquiry_PortType" binding="api_v3_binding:UDDI_Inquiry_SoapBinding">
<soap:address location="urn:unknown-location-uri" />
</port>
</service>
</definitions>

perhaps it may help others .
It SSL handshake which is failing and that's because certificate is not trusted. certificates need be added to keystore of server.

JavaMail API on WLS 5.1

Hello everyone!
I'm not sure if this goes here.
How can I implement Java Mail API on WLS 5.1
Any references or examples will be appreciate.!
Thanks&Regards
-Mauricio

Hi Giri,
Again, thanks for your help, this is what I looking for!
Best Regards.!
"Giri Alwar" <[email protected]> wrote:
Here's a simple example on sending email (you can find more through any
search engine):
http://www.javacommerce.com/articles/sendingmail.htm
Giri
"Mauricio Del Moral" <[email protected]> wrote in message
news:3b044d95$[email protected]..
Giri,
I've been looking the link information about Java Mail Implemetationand
the code
showed there, but do you know if there's something more easy in anotherplace, an
example like "HelloWorld".
Thanks in advance
-Mauricio
"Mauricio Del Moral" <[email protected]> wrote:
Giri,
Thanks for your help, I saw the message postesd in "misc", sorry for
that.
Best Regards
-Mauricio
"Giri Alwar" <[email protected]> wrote:
Normally, you would need two jars from Sun that contain Sun's
implementation
of the mail transport (mail.jar and activation.jar). Luckily,
"weblogicaux.jar" contains these implementation classes from sun.The
only
thing you need is to have weblogicaux.jar in your classpath.
To use the mail API, here is an article that is useful:
http://softwaredev.earthweb.com/vc/winvc/helpvc/article/0,,12690_618741,00
..h
tml
Giri
"Mauricio Del Moral" <[email protected]> wrote in message
news:3b04055d$[email protected]..
Hello everyone!
I'm not sure if this goes here.
How can I implement Java Mail API on WLS 5.1
Any references or examples will be appreciate.!
Thanks&Regards
-Mauricio

UDDI API s not able to find service in registry

Hello,
I added a service to Weblogic's private registry using Weblogic's UDDI explorer.
But a sample program to find the service that I just registered cannot find the
service. I have tried this with Weblogic UDDI Client API, JAXR and UDDI4J. However,
when I publish a different service to Weblogic's private registry programatically
(using Weblogic UDDI Client API) I'm then able to successfully find the service
using all the above APIs. Has anyone faced similar problems ?
Thanks
Sara

Hi Sara,
The WLS 8.1 product is outstanding, without equal; so I'd recommend to
your customers to upgrade if possible. For WLS 6.x, UDDI is not
supported. For the WLS 7.x, there are a couple of options: you could
provide a simple routine using the API client to update the service
registry, leaving the UDDI explorer as a read-only browser. You could
also seek the assistance of our award winning support team:
http://support.bea.com or [email protected]
Bruce
Sara wrote:
>
Hi Bruce:
Thanks for the reply. You're right, it did resolve to www.nothing.com. Is there
a patch for WLS 7.0 ? Or any workaround ? Our customers are all on Weblogic 6.x
or 7.x. What kind of recommendations can we give them regarding Weblogic UDDI
explorer ?
Thanks
-Sara
Bruce Stephens <[email protected]> wrote:
Hi Sara,
There was a bug in the WLS 7.0 UDDI Explorer where the AccessPoint URL
value was forced to http://www.nothing.com. This has been resolved in
WLS 8.1
Bruce
Sara wrote:
Hello,
I added a service to Weblogic's private registry using Weblogic's UDDIexplorer.
But a sample program to find the service that I just registered cannotfind the
service. I have tried this with Weblogic UDDI Client API, JAXR andUDDI4J. However,
when I publish a different service to Weblogic's private registry programatically
(using Weblogic UDDI Client API) I'm then able to successfully findthe service
using all the above APIs. Has anyone faced similar problems ?
Thanks
Sara

Problem using Java Mail API with WLS 7.0

Hi All,
I am trying to use the Java Mail API provided by WLS 7.0. I have made the
settings metioned in the WLS 7.0 docs. However when I try to run the program I
am getting the following error:
javax.naming.NoInitialContextException: Need to specify class name in environment
or system property, or as an applet parameter, or in an application resource file:
java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
46)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
a:283)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
The code that I have written is as follows
import java.util.*;
import javax.activation.*;
import javax.mail.*;
import javax.mail.internet.*;
import javax.naming.*;
import java.io.*;
import java.net.InetAddress;
import java.util.Properties;
import java.util.Date;
public class MailTo {
     public static void main(String args[])
          try
               //Context ic = getInitialContext();
               InitialContext ic = new InitialContext();
/* My jndi name is "testSession" */
               Session session = (Session) ic.lookup("testSession"); /* THE PROBLEM IS SHOWN
IN THIS LINE */
               Properties props = new Properties();
               props.put("mail.transport.protocol", "smtp");
               props.put("mail.smtp.host", "XX.XX.XX.XX");
/* For security reasons I have written the ip add in this format */
               props.put("mail.from", "[email protected]"); /* for security reasons i have
changed the mail address */
               Session session2 = session.getInstance(props);
               Message msg = new MimeMessage(session2);
               msg.setFrom();
               msg.setRecipients(Message.RecipientType.TO, InternetAddress.parse("[email protected]",
false));
               msg.setSubject("Test Message");
               msg.setSentDate(new Date());
               MimeBodyPart mbp = new MimeBodyPart();
               mbp.setText("This is a mail sent to you using JAVA Mail API and Weblogic Server");
               Multipart mp = new MimeMultipart();
               mp.addBodyPart(mbp);
               msg.setContent(mp);
               Transport.send(msg);
          catch(Exception e)
               e.printStackTrace();
     }//end of main
public static Context getInitialContext()
     throws NamingException
          Properties p = new Properties();
          p.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
          p.put(Context.PROVIDER_URL, "t3://localhost:7501/testWebApp");
               p.put(Context.SECURITY_PRINCIPAL, "weblogic");
               p.put(Context.SECURITY_CREDENTIALS, "weblogic");
          return new InitialContext(p);
}//end of class
Can anyone please tell me what is the problem. I thought that we cannot directly
do
InitialContext ic = new InitialContext();
So I had written a method getInitialContext() as shown in the above piece of code,
but that too did not work.
Eagerly awaiting a response.
Jimmy Shah

You can use InitialContext ic = new InitialContext() only if you are using a startup class, servlet or a JSP i.e
server side code.
If you are using a java client you need to use Context ic = getInitialContext();
Try this code
import java.util.*;
import javax.activation.*;
import javax.mail.*;
import javax.mail.internet.*;
import javax.naming.*;
import java.io.*;
import java.net.InetAddress;
import java.util.Properties;
import java.util.Date;
public class MailTo {
public static void main(String args[])
try {
Properties h = new Properties();
h.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
h.put(Context.PROVIDER_URL, "t3://localhost:7001");
Context ic = new InitialContext(h);
Session session = (Session) ic.lookup("testSession");
Properties props = new Properties();
props.put("mail.transport.protocol", "smtp");
props.put("mail.smtp.host", "XX.XX.XX.XX");
props.put("mail.from", "[email protected]");
Session session2 = session.getInstance(props);
Message msg = new MimeMessage(session2);
msg.setFrom();
msg.setRecipients(Message.RecipientType.TO,InternetAddress.parse("[email protected]",false));
msg.setSubject("Test Message");
msg.setSentDate(new Date());
MimeBodyPart mbp = new MimeBodyPart();
mbp.setText("This is a mail sent to you using JAVA Mail API and Weblogic Server");
Multipart mp = new MimeMultipart();
mp.addBodyPart(mbp);
msg.setContent(mp);
Transport.send(msg);
catch(Exception e)
e.printStackTrace();
}//end of main
}//end of class
We have shipped a javamail example in the samples\server\src\examples\javamail folder.
Jimmy Shah wrote:
Hi All,
I am trying to use the Java Mail API provided by WLS 7.0. I have made the
settings metioned in the WLS 7.0 docs. However when I try to run the program I
am getting the following error:
javax.naming.NoInitialContextException: Need to specify class name in environment
or system property, or as an applet parameter, or in an application resource file:
java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
46)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
a:283)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
The code that I have written is as follows
import java.util.*;
import javax.activation.*;
import javax.mail.*;
import javax.mail.internet.*;
import javax.naming.*;
import java.io.*;
import java.net.InetAddress;
import java.util.Properties;
import java.util.Date;
public class MailTo {
public static void main(String args[])
try
//Context ic = getInitialContext();
InitialContext ic = new InitialContext();
/* My jndi name is "testSession" */
Session session = (Session) ic.lookup("testSession"); /* THE PROBLEM IS SHOWN
IN THIS LINE */
Properties props = new Properties();
props.put("mail.transport.protocol", "smtp");
props.put("mail.smtp.host", "XX.XX.XX.XX");
/* For security reasons I have written the ip add in this format */
props.put("mail.from", "[email protected]"); /* for security reasons i have
changed the mail address */
Session session2 = session.getInstance(props);
Message msg = new MimeMessage(session2);
msg.setFrom();
msg.setRecipients(Message.RecipientType.TO, InternetAddress.parse("[email protected]",
false));
msg.setSubject("Test Message");
msg.setSentDate(new Date());
MimeBodyPart mbp = new MimeBodyPart();
mbp.setText("This is a mail sent to you using JAVA Mail API and Weblogic Server");
Multipart mp = new MimeMultipart();
mp.addBodyPart(mbp);
msg.setContent(mp);
Transport.send(msg);
catch(Exception e)
e.printStackTrace();
}//end of main
public static Context getInitialContext()
throws NamingException
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
p.put(Context.PROVIDER_URL, "t3://localhost:7501/testWebApp");
p.put(Context.SECURITY_PRINCIPAL, "weblogic");
p.put(Context.SECURITY_CREDENTIALS, "weblogic");
return new InitialContext(p);
}//end of class
Can anyone please tell me what is the problem. I thought that we cannot directly
do
InitialContext ic = new InitialContext();
So I had written a method getInitialContext() as shown in the above piece of code,
but that too did not work.
Eagerly awaiting a response.
Jimmy Shah--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

UDDI registry in WLS 7.0

I've set up a UDDI registry using uddiexplorer in WLS 7.0. I want to be able to
do inquiries aginst this registry from other development tools, such as the CapeClear
Developer Studio. When I used this particular tool it couldn't find any of the
services I registered in the WLS UDDI registry.
Is the problem with CapeClear, WLS, or me ? Can the BEA UDDI registry be interrogated
from other Developer Tools ?
We want to build a large UDDI registry, but it must be on a platform that works
with other vendor's products.
Dave

Thanks,
My client is UDDI v 1, which explains the problem. Can you recommend a dev
tool that uses UDDI v 2 to find services ?
Dave
"Babak Mozaffari" <[email protected]> wrote:
>
Dear Dave,
As Bruce mentioned, you will be able to make standard UDDI calls to the
said url.
I would only like to add that our UDDI registry is UDDI v2.0 compliant,
so make
sure that any UDDI client you use is v2.0 and not v1.0. The UDDI spec
provides
for registries to verify version information and simply return an error
if the
call uses a different version. Look at the generic attribute (generic="1.0"
or
generic="2.0") to find out which version your client is using.
Regards,
Babak
"Dave" <[email protected]> wrote:
I've set up a UDDI registry using uddiexplorer in WLS 7.0. I want to
be able to
do inquiries aginst this registry from other development tools, such
as the CapeClear
Developer Studio. When I used this particular tool it couldn't findany
of the
services I registered in the WLS UDDI registry.
Is the problem with CapeClear, WLS, or me ? Can the BEA UDDI registry
be interrogated
from other Developer Tools ?
We want to build a large UDDI registry, but it must be on a platform
that works
with other vendor's products.
Dave

Com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail messa

Dear All,
When we try to publish a Web Service using Service Registry, following error appears, even though my user has the roles UDDI_Admin and SERVICE_REGISTRY_READ_WRITE
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='DISPOSITION_REPORT_UDDI_SERVER', Arguments: ['http://host:port/uddi/api/inquiry/', 'http://host:port/uddi/api/publish/', 'Fatal: A serious technical error has occurred while processing the request. ']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.server.proxy.depl.v3.DispositionReport
Note: We have also configured the UDDI destination as described in sap help @ http://help.sap.com/saphelp_nwpi71/helpdata/en/45/c1ea61a1194432e10000000a155369/frameset.htm
Thanks in Advance,
Immy.

Hi Rajesh,
Many thanks for your prompt reply, however this note 1267817 was already applied before posting message.
B/W I have observed that in spite of the error the service published multiple times in the registry (perhaps each try to publish resulted a entry in SR).
Really crazy error, any other suggestion??
Regards, Immy.

UDDI - inquiry/publish API

Hi all,
i want to use the UDDI server from XI. With the UDDI client from XI i can publish my web services.
But now i want to configure the UDDI Client in transaction suddireg in order to get access to UDDI from ERP (transaction wsadmin). But i have a problem with both rfc destinations.
In the documentation the standard URLs are like the following:
http://<host>:<port>/uddi/api/inquiry
http://<host>:<port>/uddi/api/publish
I have created a rfc destination with type G.
host = XI host
port = XI port
path prefix: /uddi/api/inquiry
But the rfc destionation is not working.
Whats wrong?
Please don't refer to whole documentations!!!
Only helpful answers are rewarded.
regards

HI
Could you pls tell me what is the parameters you are using for the rfc destination..
Host Name Findings .. Go to System--->Status find the Host Name
Path prefix use : /rep
I think it will work,if not do let me know,
Regards
Manas.

WLS 8.1 and JMX 1.2 remote API

I am developing a web app that uses JMX 1.2 remote API to manager remote MBean
servers. Even I put the JMX 1.2 jar files to the classpath, WLS still loads the
previous version (1.0) of JMX bundled in weblogic.jar file, I think. And I am
not eager to mess up weblogic.jar file either.
Is there anyway to use JMX 1.2 remote API in WLS 8.1? If not, is there a patch
from BEA? And when will JMX 1.2 be supported by WLS? Thanks,
Jack

The next release of WLS is tentatively scheduled some time early next
year. JMX 1.2 will be supported in that release.
Thanks,
-satya
Jack Liu wrote:
Thanks for the reply. I heard BEA will release WLS 8.1 SP3 in June. Based on your
message, JMX 1.2 will not be supported by any WLS 8.1. So can you give me an estimate
of which release and when will JMX 1.2 be supported? Thanks!
Satya Ghattu <[email protected]> wrote:
Jack,
JMX 1.2 Remote API will be supported in the next version of WLS. There
is no patch available for 8.1 and as of now there are no intentions to
support 8.1 with JMX 1.2.
Thanks,
-satya
Jack Liu wrote:
I am developing a web app that uses JMX 1.2 remote API to manager remoteMBean
servers. Even I put the JMX 1.2 jar files to the classpath, WLS stillloads the
previous version (1.0) of JMX bundled in weblogic.jar file, I think.And I am
not eager to mess up weblogic.jar file either.
Is there anyway to use JMX 1.2 remote API in WLS 8.1? If not, is therea patch
from BEA? And when will JMX 1.2 be supported by WLS? Thanks,
Jack

UDDI sample clinet not setting the wsdl location

Hi
I am using the uddi PublishService2UDDI.java of dev2dev and am trying to register
a deployed service with a name and a wsdl url location. The program runs successfully
and registers the service but the "overview url" where the wsdl url is supposed
to be is blank!.
Is this a problem with the code? or a bug in the 7.0 sp1? If I try it from the
GUI it registers the service perfectly.
thanks
Anamitra

Hi Anamitra,
Sounds like you are making good progress. You can reach the overview
structure by doing the getTModelDetail with tModel key. There is an
established convention for this, you might want to take a look at the
UDDI Best Practice for Using WSDL in a UDDI Registry.
http://www.oasis-open.org/committees/uddi-spec/doc/bp/uddi-spec-tc-bp-using-wsdl-v108-20021110.htm
Concerning the UDDI explorer, we have made improvements to this tool in
WLS v8.1, however it is not a full GUI interface to the registry, but
simply a browser.
HTHs,
Bruce
Anamitra wrote:
>
Hi Bruce
I now tested the findTmodel and found both the models registered by JAX R client
and the Weblogic client. But am only able to get handle to the TModelList. TModelList
gives TModelInfos which gives TModelInfo - which has no api to access the overview
url. That is there only if I get the handle to the TModel object which has the
api to getOverviewDoc() which has sthe wsdl url. How do I get a handle to the
TMdoel?
Also why is the uddiexplorer not showing me the TMdels?
thanks
Anamitra
Bruce Stephens <[email protected]> wrote:
Hi Anamitra,
The overview URL is hung off the tModel and the PublishService2UDDI does
a save service. You can add this code if you wish, an example of the
client code can be found here: http://webservice.bea.com/index.html#qz42
Right, you can use any UDDI v2 compliant client to access the WLS UDDI
server, including SUN's JAXR or UDDI4j for example.
Also, we've made a number of usability improvements to the UDDI Explorer
for WLS 8.1 (http://host:port/uddiexplorer/index.jsp) and specifically
I
believe what you would be looking for in your case is the "access URL"
that points to the saved service.
HTHs,
Bruce
Anamitra wrote:
On 2nd thoughts can I use the SUN's jaxr implementation to invoke WL7.0UDDI registry
ie to query or publish in that registry.
thanks
Anamitra
"Anamitra" <[email protected]> wrote:
Hi
I am using the uddi PublishService2UDDI.java of dev2dev and am trying
to register
a deployed service with a name and a wsdl url location. The program
runs
successfully
and registers the service but the "overview url" where the wsdl urlis
supposed
to be is blank!.
Is this a problem with the code? or a bug in the 7.0 sp1? If I tryit
from the
GUI it registers the service perfectly.
thanks
Anamitra

Weblogic.uddi.client.* javadocs?

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.

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: (416) 491-1419 Ext: 224
Cell: (416) 727-6947
Fax: (416) 491-3070
[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.

UDDI Exception : publishing the service registry

Hi,
have anybody faced the error below :
com.sap.esi.uddi.sr.api.exceptions.SRExceptionerror code: null detail message: com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='REMOTE_EXCEPTION_UDDI_SERVER', Arguments: ['http://dvjcen00:*****/uddi/api/inquiry/', 'http://dvjcen00:*****/uddi/api/publish/']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.esi.uddi.sr.impl.uddi.wsdl.validation.UDDIServerRemoteException: <Localization failed: ResourceBundle='com.sap.engine.services.webservices.wscm.validation.accessors.validation', ID='REMOTE_EXCEPTION_UDDI_SERVER', Arguments: ['http://dvjcen00:*****/uddi/api/inquiry/', 'http://dvjcen00:******/uddi/api/publish/']> : Can't find bundle for base name com.sap.engine.services.webservices.wscm.validation.accessors.validation, locale en->com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (401). Server <http://dvjcen00:******/uddi/api/publish/> returned message <Unauthorized
Can anybody suggest on that . At the time of Publish the service registry it comes.
Rgds,
Deep

Hello Deep,
Have you tried to assign the SERVICES_REGISTRY_READ_WRITE role to the user that is trying to publish?
Thanks & Regards
SU

UDDI API -- findService (WLS 7.0)

Similar Messages

Maybe you are looking for