Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID;
  b=kX71+pinnH2Ht90DXHdtUsdjeeMtHIN53phGs01DZhbXZypF+k3Fjo8lIGEs73y/EVyJMzgDepP4P1+8dxxfoFf86XE1h+kuIVwZycBRHKrKeQTpu3v5ZJ8CwzTrNd2z3+KY4ZLtc8E4BpqU17ESqIFGD7RYQ1V6AIGP9fCKMvY=;
Date: Sun, 7 Dec 2008 13:03:54 -0800 (PST)
From: Derek Adams <derek_a_adams@yahoo.com>
Reply-To: Derek Adams <derek_a_adams@yahoo.com>
Subject: Namespace problem in wsdl2java generated classes
To: users@cxf.apache.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1811204208-1228683834=:28993"
Message-ID: <712983.28993.qm@web55408.mail.re4.yahoo.com>

--0-1811204208-1228683834=:28993
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

I am having a problem with the WSDL generated from JAX-WS classes that were=
 originally created from the CXF wsdl2java tool. Basically, I have am writi=
ng=A0tool that allows you to import WSDL to generate JAX-WS interaces, then=
 allows you to fill in the implementations and deploy to a server. I am usi=
ng CXF embedded in Mule, but Mule just defers to the CXF QueryHandler to ge=
nerate the WSDL when requested over the endpoint. Here is the WSDL I am usi=
ng for testing:=0A=0A<wsdl:definitionsxmlns=3D"http://example.org/math/"xml=
ns:wsdl=3D"http://schemas.xmlsoap.org/wsdl/"xmlns:soap=3D"http://schemas.xm=
lsoap.org/wsdl/soap/"xmlns:http=3D"http://schemas.xmlsoap.org/wsdl/http/"xm=
lns:xs=3D"http://www.w3.org/2001/XMLSchema"xmlns:soapenc=3D"http://schemas.=
xmlsoap.org/soap/encoding/"xmlns:mime=3D"http://schemas.xmlsoap.org/wsdl/mi=
me/"xmlns:y=3D"http://example.org/math/"xmlns:type=3D"http://example.org/ma=
th/types/"targetNamespace=3D"http://example.org/math/"><wsdl:types><xs:sche=
maxmlns=3D"http://example.org/math/types/"targetNamespace=3D"http://example=
.org/math/types/"><xs:complexTypename=3D"MathInput"><xs:sequence><xs:elemen=
tname=3D"x"type=3D"xs:double"/><xs:elementname=3D"z"type=3D"xs:double"/></x=
s:sequence></xs:complexType><xs:complexTypename=3D"MathOutput"><xs:sequence=
><xs:elementname=3D"result"type=3D"xs:double"/></xs:sequence></xs:complexTy=
pe><xs:elementname=3D"Add"type=3D"type:MathInput"/><xs:elementname=3D"AddRe=
sponse"type=3D"type:MathOutput"/><xs:elementname=3D"Subtract"ty
pe=3D"type:MathInput"/><xs:elementname=3D"SubtractResponse"type=3D"type:Mat=
hOutput"/></xs:schema></wsdl:types><wsdl:messagename=3D"AddMessage"><wsdl:p=
artname=3D"parameters"element=3D"type:Add"/></wsdl:message><wsdl:messagenam=
e=3D"AddResponseMessage"><wsdl:partname=3D"parameters"element=3D"type:AddRe=
sponse"/></wsdl:message><wsdl:messagename=3D"SubtractMessage"><wsdl:partnam=
e=3D"parameters"element=3D"type:Subtract"/></wsdl:message><wsdl:messagename=
=3D"SubtractResponseMessage"><wsdl:partname=3D"parameters"element=3D"type:S=
ubtractResponse"/></wsdl:message><wsdl:portTypename=3D"MathInterface"><wsdl=
:operationname=3D"Add"><wsdl:inputmessage=3D"y:AddMessage"/><wsdl:outputmes=
sage=3D"y:AddResponseMessage"/></wsdl:operation><wsdl:operationname=3D"Subt=
ract"><wsdl:inputmessage=3D"y:SubtractMessage"/><wsdl:outputmessage=3D"y:Su=
btractResponseMessage"/></wsdl:operation></wsdl:portType><wsdl:bindingname=
=3D"MathSoapHttpBinding"type=3D"y:MathInterface"><soap:bindingstyle=3D"docu=
ment"transport=3D"http://schemas.xmlsoap.org/
soap/http"/><wsdl:operationname=3D"Add"><soap:operationsoapAction=3D"http:/=
/example.org/math/#Add"/><wsdl:input><soap:bodyuse=3D"literal"/></wsdl:inpu=
t><wsdl:output><soap:bodyuse=3D"literal"/></wsdl:output></wsdl:operation><w=
sdl:operationname=3D"Subtract"><soap:operationsoapAction=3D"http://example.=
org/math/#Subtract"/><wsdl:input><soap:bodyuse=3D"literal"/></wsdl:input><w=
sdl:output><soap:bodyuse=3D"literal"/></wsdl:output></wsdl:operation></wsdl=
:binding><wsdl:servicename=3D"MathService"><wsdl:portname=3D"MathEndpoint"b=
inding=3D"y:MathSoapHttpBinding"><soap:addresslocation=3D"http://localhost/=
math/math.asmx"/></wsdl:port></=0A=A0=0AEverything generates=A0without prob=
lems, but there are errors when deployed in Mule. CXF complains about bad n=
amespaces on deployment indicating that the namespaces for schema objects a=
re incorrect: =0A=A0=0A=A014:32:04,606 ERROR [STDERR] Dec 7, 2008 2:32:04 P=
M org.apache.cxf.service.factor=0Ay.ReflectionServiceFactoryBean fillInSche=
maCrossreferences=0ASEVERE: Schema element {http://example.org/math/types/}=
SubtractResponse referenc=0Aes undefined type MathOutput for service {http:=
//example.org/math/}MathInterface=0AService.=0A14:32:04,606 ERROR [STDERR] =
Dec 7, 2008 2:32:04 PM org.apache.cxf.service.factor=0Ay.ReflectionServiceF=
actoryBean fillInSchemaCrossreferences=0ASEVERE: Schema element {http://exa=
mple.org/math/types/}Subtract references undef=0Ained type MathInput for se=
rvice {http://example.org/math/}MathInterfaceService.=0A14:32:04,621 ERROR =
[STDERR] Dec 7, 2008 2:32:04 PM org.apache.cxf.service.factor=0Ay.Reflectio=
nServiceFactoryBean fillInSchemaCrossreferences=0ASEVERE: Schema element {h=
ttp://example.org/math/types/}AddResponse references un=0Adefined type Math=
Output for service {http://example.org/math/}MathInterfaceServi=0Ace.=0A14:=
32:04,621 ERROR [STDERR] Dec 7, 2008 2:32:04 PM org.apache.cxf.service.fact=
or=0Ay.ReflectionServiceFactoryBean fillInSchemaCrossreferences=0ASEVERE: S=
chema element {http://example.org/math/types/}Add references undefined=0Aty=
pe MathInput for service {http://example.org/math/}MathInterfaceService.=0A=
=A0=0AWhen I try to load the WSDL via http://endpoint?wsdl=A0in a tool like=
 SoapUI, I get errors similar to the=A0ones on deployment. After looking at=
 the annotated code generated from wsdl2java, I noticed that there is no na=
mespace declaration on the schema complex types. The elements have the corr=
ect namespace, but they reference the complex types that have no namespace =
declarations. Because of this, the generated WSDL splits the elements and c=
omplex types into separate schema sections with different target namespaces=
. I am honestly not sure if this is a CXF issue or a CXF-embedded-in-Mule i=
ssue. Has anyone else run into this?=0A=A0=0AThanks,=0ADerek</wsdl:service>=
wsdl:definitions>=0A=0A=0A      
--0-1811204208-1228683834=:28993--