I actually discussed this with Sanjiva after going through the specs. He's in the view that the schema defined in the WSDL needs to have the targetNamespace attribute even though it is not mandatory according to the schema spec. The reason is that if the elements are unqualified then the messages section might have a problem refering to the elements.These facts do not seem to be documented anywhere :(
However I feel Jaya's solution seems to be valid since it serves the WSDL's purpose!
Thoughts ?
On 8/24/05, Davanum Srinivas <[EMAIL PROTECTED]> wrote:
check the xsd schema's schema. if it is mandatory then throw exception
if it is absent otherwise don't.
-- dims
On 8/24/05, jayachandra <[EMAIL PROTECTED] > wrote:
> Ajith!
> If the content inside the <xsd:schema> element is(are) just an import
> statement(s) then, I guess, there need not be a targetNamespace.
> However if any information other than import elements appear (viz.
> element declarations, include statements etc.) then we should throw
> that exception. Just my thought, though
>
> Thank you
> Jayachandra
>
> On 8/24/05, Ajith Ranabahu < [EMAIL PROTECTED]> wrote:
> > Hi all,
> > the following piece of WSDL is from the WSRF WSDL at
> > http://docs.oasis-open.org/wsrf/rpw-1
> >
> > <wsdl:types>
> > <xsd:schema>
> > <xsd:import
> > namespace="http://docs.oasis-open.org/wsrf/rp-1 "
> > schemaLocation="
> http://docs.oasis-open.org/wsrf/rp-1" />
> > </xsd:schema>
> > </wsdl:types>
> > Axis2 code generator is configured to throw an exception if it encounters a
> > schema element that does not declare a target namespace. Is that correct in
> > this case ?
> > --
> > Ajith Ranabahu
>
>
> --
> -- Jaya
>
--
Davanum Srinivas : http://wso2.com/ - Oxygenating The Web Service Platform
--
Ajith Ranabahu
