I was using JAXR before for Juddi access, only found many bugs in the sun micro JAXR package. These bugs caused me quite a bit of time to find out that my code was innocent. Because of that I switched to uddi4j and was happy with it.
-Ming -----Original Message----- From: Angel Luis Villalain Garcia [mailto:[EMAIL PROTECTED] Sent: Friday, August 19, 2005 9:33 AM To: [email protected] Subject: Re: JAXR and jUDDI problems Glenn wrote: >Hi, >I noticed a very similar issue to what I'm experiencing on this list 18 Jul 2005 'JAXR and authToken' but there were no replies to that message. > >I'm running jUDDI 0.9rc4 on Tomcat 5.5.9 with MySQL 4.1.13. I've gotten the happyjuddi working and I'm able (through the console) to find publishers. > >I've written a very simple java app (using J2SE 1.5.0_04 and JWSDP 1.6). When I try to find an organization by name the app throws an IllegalArgumentException >Request looks like: >POST /juddi/inquiry HTTP/1.1 >Content-Type: text/xml; charset=utf-8 >Content-Length: 403 >SOAPAction: "" >Cache-Control: no-cache >Pragma: no-cache >User-Agent: Java/1.5.0_04 >Host: localhost:8080 >Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2 >Connection: keep-alive > ><?xml version="1.0" encoding="utf-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";><SOAP-ENV:Hea der/><SOAP-ENV:Body><find_business xmlns="urn:uddi-org:api_v2" generic="2.0"><findQualifiers><findQualifier>sortByNameDesc</findQualifi er></findQualifiers><name xml:lang="en">juddi</name><name xml:lang="en-US">juddi</name></find_business></SOAP-ENV:Body></SOAP-ENV: Envelope> > >And the RESPONSE looks like: > >HTTP/1.1 200 OK >Server: Apache-Coyote/1.1 >Content-Type: text/xml;charset=utf-8 >Transfer-Encoding: chunked >Date: Fri, 19 Aug 2005 14:05:49 GMT > >180 ><?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";; xmlns:xsd="http://www.w3.org/2001/XMLSchema";; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>; ><soapenv:Body> ><businessList generic="2.0" operator="jUDDI.org" xmlns="urn:uddi-org:api_v2"> ><businessInfos/> ></businessList> ></soapenv:Body> ></soapenv:Envelope> >0 > >The Stack Trace: >Exception in thread "main" java.lang.IllegalArgumentException >at com.sun.xml.registry.uddi.bindings_v2.impl.runtime.UnmarshallerImpl.unma rshal(Unknown Source) >at com.sun.xml.registry.common.util.MarshallerUtil.jaxbUnmarshalObject(Unkn own Source) >at com.sun.xml.registry.uddi.Processor.processResponseJAXB(Unknown Source) >at com.sun.xml.registry.uddi.Processor.processRequestJAXB(Unknown Source) >at com.sun.xml.registry.uddi.UDDIMapper.findOrganizations(Unknown Source) >at com.sun.xml.registry.uddi.BusinessQueryManagerImpl.findOrganizations(Unk nown Source) >at com.sarnoff.uddi.Browser.findOrgByName(Browser.java:92) >at com.sarnoff.uddi.Browser.main(Browser.java:340) >Java Result: 1 > >Does anyone understand the 180 and 0 surrounding the response body ? > >When I try use credentials I get a very similar issue >The request looks well formatted but the response includes an authToken but again the body is surrounded by an extraneous 1ad and 0. > >RESPONSE >HTTP/1.1 200 OK >Server: Apache-Coyote/1.1 >Content-Type: text/xml;charset=utf-8 >Transfer-Encoding: chunked >Date: Fri, 19 Aug 2005 13:20:44 GMT > >1ad ><?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";; xmlns:xsd="http://www.w3.org/2001/XMLSchema";; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>; ><soapenv:Body> ><authToken generic="2.0" operator="jUDDI.org" xmlns="urn:uddi-org:api_v2"> ><authInfo>authToken:0C642BA0-10B4-11DA-ABA0-D4A5245F096F</authInfo> ></authToken> ></soapenv:Body> ></soapenv:Envelope> >0 > >I'd appreciate any help in understanding this problem. > >Thanks Glenn > > > > >_______________________________________________ >Join Excite! - http://www.excite.com >The most personalized portal on the Web! > > > > > I was having similar problems, so I decided to rollback tu 1.4.2, I could not been able to get juddi to run on 1.5. I was having problems similar but related to the message, something that the header should not be null, and I did not find what was the reason.
