Thanks for clarifying that Simon.
There also seems to be some problem with the WSDL referred to by the import statement. If I send a request for the URL http://.../jupiter/World?wsdl=WEB-INF/classes/jupiter.wsdl (which is the imported WSDL file). The WSDL returned by the server has the following garbled XML tags: <{http://schemas.xmlsoap.org/ws/2004/03/partner-link/}partnerLinkType name="WorldPartnerLinkType"> <:role name="me" portType="{ http://jupiter.ptg.company.com/jupiter.wsdl}WorldPortType";> <:role name="you" portType="{ http://jupiter.ptg.company.com/jupiter.wsdl}WorldPortType";> </{http://schemas.xmlsoap.org/ws/2004/03/partner-link/}partnerLinkType> The corresponding WSDL file that actually is deployed to the server webapps folder has this content instead: <plnk:partnerLinkType name=" WorldPartnerLinkType "> <plnk:role name="me" portType="tns: WorldPortType "/> <plnk:role name="you" portType="tns: WorldPortType "/> </plnk:partnerLinkType> Please see yellowed section above corresponding to green portion below it . The URI for the plnk namespace is " http://schemas.xmlsoap.org/ws/2004/03/partner-link/"; and for tns is " http://jupiter.ptg.company.com/jupiter.wsdl"; My Tuscany component is using the BPEL implementation type and is deployed in Jetty as a war file. Regards --mac On Wed, Apr 6, 2011 at 2:30 AM, Simon Nash <[email protected]> wrote: > MAC wrote: > >> Hi , >> >> i am new to tuscany . I recently downloaded the project and tried to set >> it up . >> >> When i open wsdl in internet explorer it shows the wsdl . It has some >> extra data >> >> The line in my wsdl : >> >> <wsdl:import namespace="http://jupiter.ptg.company.com/jupiter.wsdl"; >> location="/jupiter/World?wsdl=WEB-INF/classes/jupiter.wsdl"> >> >> after ?wsdl what is =WEB-INF/classes/jupiter.wsdl and how to remove this . >> Please help me on this . >> >> -- >> thanks >> --mac >> >> The Tuscany-generated WSDL is a "wrapper" around your own WSDL. The > extra data "/jupiter/World?wsdl=WEB-INF/classes/jupiter.wsdl" is the > syntax used by Axis2 to resolve this <wsdl:import> tag to your own > WSDL file which is packaged at the specified relative location within > the webapp. > > This <wsdl:import> tag should "just work" when a client accesses the > Tuscany-generated WSDL using a tool such as WSDL4J or wsimport. > It wouldn't be a good idea to remove the extra data because this would > prevent the import from being resolved. > > Simon > > -- thanks --mac
