thx On 4/30/07, Matthew Graham <[EMAIL PROTECTED]> wrote:
Hi,OK - I've added it to the end of "Client and Server Stub generation from WSDL" page. Cheers, Matthew Tomek Sztelak wrote: > You can add this info to XFire docs. On every page there is small > [edit] link on the right side menu, so it would be great if you can > add this somewhere :D > > On 4/30/07, Matthew Graham <[EMAIL PROTECTED]> wrote: >> Hi, >> >> After digging around in the JavaDocs a bit, I discovered that the way to >> do this is: >> >> service.setWSDLWriter(new ResourceWSDL("myService.wsdl")); >> >> It would be nice if this was documented somewhere :-) >> >> Cheers, >> >> Matthew >> >> Matthew Graham wrote: >> > Hi, >> > >> > Further to this, is there any way to force the service to actually >> > return the WSDL file that was used to generate the stub code instead >> > of XFire generating it? >> > >> > Cheers, >> > >> > Matthew >> > >> > Matthew Graham wrote: >> >> Hi, >> >> >> >> I'm using XFire 1.2.2 with XmlBeans binding from a WSDL defined with: >> >> >> >> <wsdl:definitions >> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; >> >> xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"; >> >> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; >> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >> >> xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"; >> >> >> >> >> xmlns:vos.contract.1.0="http://www.net.ivoa/xml/VOSpaceContract-v1.0rc6"; >> >> >> >> xmlns:vos.types.1.0="http://www.net.ivoa/xml/VOSpaceTypes-v1.0rc6"; >> >> xmlns="http://www.net.ivoa/xml/VOSpaceContract-v1.0rc6"; >> >> targetNamespace="http://www.net.ivoa/xml/VOSpaceContract-v1.0rc6";> >> >> >> >> The stub code generated from this is in the package >> >> edu.caltech.nvo.vospace. >> >> >> >> However, when I expose my service and get its WSDL with ?wsdl, this >> >> has the package name as the main namespace: >> >> >> >> <wsdl:definitions targetNamespace="http://vospace.nvo.caltech.edu"; >> >> xmlns:tns="http://vospace.nvo.caltech.edu"; >> >> xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"; >> >> xmlns:soap12="http://www.w3.org/2003/05/soap-envelope"; >> >> xmlns:ns1="http://www.net.ivoa/xml/VOSpaceContract-v1.0rc6"; >> >> xmlns:xsd="http://www.w3.org/2001/XMLSchema"; >> >> xmlns:soapenc11="http://schemas.xmlsoap.org/soap/encoding/"; >> >> xmlns:soapenc12="http://www.w3.org/2003/05/soap-encoding"; >> >> xmlns:soap11="http://schemas.xmlsoap.org/soap/envelope/"; >> >> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";> >> >> >> >> Unfortunately this still seems to be a problem with 1.2.5. >> >> >> >> Any ideas? >> >> >> >> Cheers, >> >> >> >> Matthew >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe from this list please visit: >> >> >> >> http://xircles.codehaus.org/manage_email >> >> >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe from this list please visit: >> > >> > http://xircles.codehaus.org/manage_email >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
-- ----- When one of our products stops working, we'll blame another vendor within 24 hours. --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
