You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Jarmo Doc <ja...@hotmail.com> on 2006/07/11 18:21:28 UTC
schema vs. xsd:schema
Axis 1.3 java2wsdl generates 'schema' tags but most WSDL that I see contains
'xsd:schema' tags. The WSDL spec. also seems to suggest that 'xsd:schema'
is the only legal option.
What is the difference between these two tags and why does Axis generate the
former?
Thanks.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: schema vs. xsd:schema
Posted by Anne Thomas Manes <at...@gmail.com>.
You might find this short explanation of XML namespaces enlightening:
http://atmanes.blogspot.com/2006/07/short-explanation-of-xml-namespaces.html
Anne
On 7/11/06, Jarmo Doc <ja...@hotmail.com> wrote:
> Axis 1.3 java2wsdl generates 'schema' tags but most WSDL that I see contains
> 'xsd:schema' tags. The WSDL spec. also seems to suggest that 'xsd:schema'
> is the only legal option.
>
> What is the difference between these two tags and why does Axis generate the
> former?
>
> Thanks.
>
> _________________________________________________________________
> Express yourself instantly with MSN Messenger! Download today - it's FREE!
> http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: schema vs. xsd:schema
Posted by Paul Fremantle <pz...@gmail.com>.
1. Its not a bug. If you look at the schema element it looks like this:
<schema elementFormDefault="qualified"
targetNamespace="http://DefaultNamespace"
xmlns="http://www.w3.org/2001/XMLSchema">
The xmlns attribute defines the default namespace for that tag and its
children.
You can read about XML Namespaces and how they work here:
http://www.w3.org/TR/REC-xml-names/
2. Yes people do use Web Services for serious implementations across
multiple toolkits.
Paul
On 7/11/06, Jarmo Doc <ja...@hotmail.com> wrote:
> Should I just assume that this is a bug in Axis and that schema, simpleType,
> complexType and so on should always be qualified by a namespace, typically
> "xsd:"?
>
> Or is there some sneaky implicit arrangement whereby xmlns or something else
> being indicated means that I don't need qualification.
>
> <rant>Is there actually anyone out there successfully using this technology
> with multiple client types (Axis, gSOAP, WebSphere, .NET)? I don't see how
> it's possible for anything more complex than a stock quote lookup
> service.</rant>
>
>
> >From: "Jarmo Doc" <ja...@hotmail.com>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: schema vs. xsd:schema
> >Date: Tue, 11 Jul 2006 09:21:28 -0700
> >
> >Axis 1.3 java2wsdl generates 'schema' tags but most WSDL that I see
> >contains 'xsd:schema' tags. The WSDL spec. also seems to suggest that
> >'xsd:schema' is the only legal option.
> >
> >What is the difference between these two tags and why does Axis generate
> >the former?
> >
> >Thanks.
> >
> >_________________________________________________________________
> >Express yourself instantly with MSN Messenger! Download today - it's FREE!
> >http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> >For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
> _________________________________________________________________
> On the road to retirement? Check out MSN Life Events for advice on how to
> get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: RE: schema vs. xsd:schema
Posted by Martin Gainty <mg...@hotmail.com>.
Good Morning-
I agree defining a WSDL clearly defines what operations you will be Requesting from the Axis Server as well as
Input and Output parameters to those operations with stated endpoint addresses
+1
Martin--
*********************************************************************
This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed. If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy. Thank you.
----- Original Message -----
From: "Paul Fremantle" <pz...@gmail.com>
To: <ax...@ws.apache.org>
Sent: Wednesday, July 12, 2006 8:07 AM
Subject: Re: RE: schema vs. xsd:schema
> Simon
>
> Absolutely +1 to WSDL first development. It also helps if you restrict
> your use of schema to a set of fairly limited constructs.
>
> As regards the looseness of the WSDL spec, its worth looking at the
> WS-I base profile (www.ws-i.org) which gives a much much more
> interoperable approach by restricting and subsetting WSDL, and SOAP.
>
> Paul
>
> On 7/12/06, Simon Fell <sf...@salesforce.com> wrote:
>>
>>
>>
>> If interop between different stacks is important to you then I'd highly
>> recommend you do a WSDL first approach, write your WSDL first and then build
>> your code from the WSDL, and not have the WSDL generated from your code.
>>
>>
>> Cheers
>> Simon
>>
>> -----Original Message-----
>> From: Jarmo Doc [mailto:jarmod@hotmail.com]
>> Sent: Tue 7/11/2006 7:24 PM
>> To: axis-user@ws.apache.org
>> Subject: RE: RE: schema vs. xsd:schema
>>
>> Thanks very much guys (Simon, Ian, Paul). Much appreciate the help. I'm
>> finding that I'm frequently having to debug WSDL that works fine with Axis
>> but not necessarily with other client tools and it's quite a challenge to
>> determine a) who's at fault and b) what's the lowest common denominator
>> that
>> works with all.
>>
>> The 1.1 WSDL docs that I refer to are heavy on terms like "should" and
>> "can"
>> as opposed to "will" and "must". More of a discussion than a
>> specification.
>> I think the later specs are more precise, no doubt partly as a result of
>> the problems caused by the earlier ones.
>>
>> Thanks again for your help.
>>
>>
>> >From: "Simon Fell" <sf...@salesforce.com>
>> >Reply-To: axis-user@ws.apache.org
>> >To: axis-user@ws.apache.org
>> >Subject: RE: RE: schema vs. xsd:schema
>> >Date: Tue, 11 Jul 2006 16:22:34 -0700
>> >
>> >Good catch.
>> >
>> >-----Original Message-----
>> >From: Ian Brown [mailto:ian.g.brown@gmail.com]
>> >Sent: Tuesday, July 11, 2006 3:51 PM
>> >To: axis-user@ws.apache.org
>> >Subject: Re: RE: schema vs. xsd:schema
>> >
>> >Not to be a pedant, but I'm correcting a minor typo in Simon's response
>> >so Jarmo does not get confused:
>> >
>> >On 7/11/06, Simon Fell <sf...@salesforce.com> wrote:
>> > > It depends on whether the schema namespace has been made the default
>> > > namespace or not.
>> > > <schema xmlns="http://www.w3.org/2001/XMLSchema">
>> > > <element name="foo" />
>> > > </schema>
>> > >
>> > > Is equivilent to
>> > > <xsd:schema
>> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> > > <xsd:element name="foo" />
>> > > </xsd:schema>
>> >
>> >Cheers,
>> >
>> >- Ian
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail:
>> axis-user-unsubscribe@ws.apache.org
>> >For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail:
>> axis-user-unsubscribe@ws.apache.org
>> >For additional commands, e-mail: axis-user-help@ws.apache.org
>> >
>>
>> _________________________________________________________________
>> FREE pop-up blocking with the new MSN Toolbar - get it now!
>> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> axis-user-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-user-help@ws.apache.org
>>
>>
>>
>>
>>
>
>
> --
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
>
> http://bloglines.com/blog/paulfremantle
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
Re: RE: schema vs. xsd:schema
Posted by Paul Fremantle <pz...@gmail.com>.
Simon
Absolutely +1 to WSDL first development. It also helps if you restrict
your use of schema to a set of fairly limited constructs.
As regards the looseness of the WSDL spec, its worth looking at the
WS-I base profile (www.ws-i.org) which gives a much much more
interoperable approach by restricting and subsetting WSDL, and SOAP.
Paul
On 7/12/06, Simon Fell <sf...@salesforce.com> wrote:
>
>
>
> If interop between different stacks is important to you then I'd highly
> recommend you do a WSDL first approach, write your WSDL first and then build
> your code from the WSDL, and not have the WSDL generated from your code.
>
>
> Cheers
> Simon
>
> -----Original Message-----
> From: Jarmo Doc [mailto:jarmod@hotmail.com]
> Sent: Tue 7/11/2006 7:24 PM
> To: axis-user@ws.apache.org
> Subject: RE: RE: schema vs. xsd:schema
>
> Thanks very much guys (Simon, Ian, Paul). Much appreciate the help. I'm
> finding that I'm frequently having to debug WSDL that works fine with Axis
> but not necessarily with other client tools and it's quite a challenge to
> determine a) who's at fault and b) what's the lowest common denominator
> that
> works with all.
>
> The 1.1 WSDL docs that I refer to are heavy on terms like "should" and
> "can"
> as opposed to "will" and "must". More of a discussion than a
> specification.
> I think the later specs are more precise, no doubt partly as a result of
> the problems caused by the earlier ones.
>
> Thanks again for your help.
>
>
> >From: "Simon Fell" <sf...@salesforce.com>
> >Reply-To: axis-user@ws.apache.org
> >To: axis-user@ws.apache.org
> >Subject: RE: RE: schema vs. xsd:schema
> >Date: Tue, 11 Jul 2006 16:22:34 -0700
> >
> >Good catch.
> >
> >-----Original Message-----
> >From: Ian Brown [mailto:ian.g.brown@gmail.com]
> >Sent: Tuesday, July 11, 2006 3:51 PM
> >To: axis-user@ws.apache.org
> >Subject: Re: RE: schema vs. xsd:schema
> >
> >Not to be a pedant, but I'm correcting a minor typo in Simon's response
> >so Jarmo does not get confused:
> >
> >On 7/11/06, Simon Fell <sf...@salesforce.com> wrote:
> > > It depends on whether the schema namespace has been made the default
> > > namespace or not.
> > > <schema xmlns="http://www.w3.org/2001/XMLSchema">
> > > <element name="foo" />
> > > </schema>
> > >
> > > Is equivilent to
> > > <xsd:schema
> xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > > <xsd:element name="foo" />
> > > </xsd:schema>
> >
> >Cheers,
> >
> >- Ian
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> >For additional commands, e-mail: axis-user-help@ws.apache.org
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> >For additional commands, e-mail: axis-user-help@ws.apache.org
> >
>
> _________________________________________________________________
> FREE pop-up blocking with the new MSN Toolbar - get it now!
> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
>
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: RE: schema vs. xsd:schema
Posted by Simon Fell <sf...@salesforce.com>.
If interop between different stacks is important to you then I'd highly recommend you do a WSDL first approach, write your WSDL first and then build your code from the WSDL, and not have the WSDL generated from your code.
Cheers
Simon
-----Original Message-----
From: Jarmo Doc [mailto:jarmod@hotmail.com]
Sent: Tue 7/11/2006 7:24 PM
To: axis-user@ws.apache.org
Subject: RE: RE: schema vs. xsd:schema
Thanks very much guys (Simon, Ian, Paul). Much appreciate the help. I'm
finding that I'm frequently having to debug WSDL that works fine with Axis
but not necessarily with other client tools and it's quite a challenge to
determine a) who's at fault and b) what's the lowest common denominator that
works with all.
The 1.1 WSDL docs that I refer to are heavy on terms like "should" and "can"
as opposed to "will" and "must". More of a discussion than a specification.
I think the later specs are more precise, no doubt partly as a result of
the problems caused by the earlier ones.
Thanks again for your help.
>From: "Simon Fell" <sf...@salesforce.com>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: RE: RE: schema vs. xsd:schema
>Date: Tue, 11 Jul 2006 16:22:34 -0700
>
>Good catch.
>
>-----Original Message-----
>From: Ian Brown [mailto:ian.g.brown@gmail.com]
>Sent: Tuesday, July 11, 2006 3:51 PM
>To: axis-user@ws.apache.org
>Subject: Re: RE: schema vs. xsd:schema
>
>Not to be a pedant, but I'm correcting a minor typo in Simon's response
>so Jarmo does not get confused:
>
>On 7/11/06, Simon Fell <sf...@salesforce.com> wrote:
> > It depends on whether the schema namespace has been made the default
> > namespace or not.
> > <schema xmlns="http://www.w3.org/2001/XMLSchema">
> > <element name="foo" />
> > </schema>
> >
> > Is equivilent to
> > <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > <xsd:element name="foo" />
> > </xsd:schema>
>
>Cheers,
>
>- Ian
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: RE: schema vs. xsd:schema
Posted by Jarmo Doc <ja...@hotmail.com>.
Thanks very much guys (Simon, Ian, Paul). Much appreciate the help. I'm
finding that I'm frequently having to debug WSDL that works fine with Axis
but not necessarily with other client tools and it's quite a challenge to
determine a) who's at fault and b) what's the lowest common denominator that
works with all.
The 1.1 WSDL docs that I refer to are heavy on terms like "should" and "can"
as opposed to "will" and "must". More of a discussion than a specification.
I think the later specs are more precise, no doubt partly as a result of
the problems caused by the earlier ones.
Thanks again for your help.
>From: "Simon Fell" <sf...@salesforce.com>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: RE: RE: schema vs. xsd:schema
>Date: Tue, 11 Jul 2006 16:22:34 -0700
>
>Good catch.
>
>-----Original Message-----
>From: Ian Brown [mailto:ian.g.brown@gmail.com]
>Sent: Tuesday, July 11, 2006 3:51 PM
>To: axis-user@ws.apache.org
>Subject: Re: RE: schema vs. xsd:schema
>
>Not to be a pedant, but I'm correcting a minor typo in Simon's response
>so Jarmo does not get confused:
>
>On 7/11/06, Simon Fell <sf...@salesforce.com> wrote:
> > It depends on whether the schema namespace has been made the default
> > namespace or not.
> > <schema xmlns="http://www.w3.org/2001/XMLSchema">
> > <element name="foo" />
> > </schema>
> >
> > Is equivilent to
> > <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> > <xsd:element name="foo" />
> > </xsd:schema>
>
>Cheers,
>
>- Ian
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar get it now!
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: RE: schema vs. xsd:schema
Posted by Simon Fell <sf...@salesforce.com>.
Good catch.
-----Original Message-----
From: Ian Brown [mailto:ian.g.brown@gmail.com]
Sent: Tuesday, July 11, 2006 3:51 PM
To: axis-user@ws.apache.org
Subject: Re: RE: schema vs. xsd:schema
Not to be a pedant, but I'm correcting a minor typo in Simon's response
so Jarmo does not get confused:
On 7/11/06, Simon Fell <sf...@salesforce.com> wrote:
> It depends on whether the schema namespace has been made the default
> namespace or not.
> <schema xmlns="http://www.w3.org/2001/XMLSchema">
> <element name="foo" />
> </schema>
>
> Is equivilent to
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:element name="foo" />
> </xsd:schema>
Cheers,
- Ian
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: RE: schema vs. xsd:schema
Posted by Ian Brown <ia...@gmail.com>.
Not to be a pedant, but I'm correcting a minor typo in Simon's
response so Jarmo does not get confused:
On 7/11/06, Simon Fell <sf...@salesforce.com> wrote:
> It depends on whether the schema namespace has been made the default
> namespace or not.
> <schema xmlns="http://www.w3.org/2001/XMLSchema">
> <element name="foo" />
> </schema>
>
> Is equivilent to
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <xsd:element name="foo" />
> </xsd:schema>
Cheers,
- Ian
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: schema vs. xsd:schema
Posted by Simon Fell <sf...@salesforce.com>.
It depends on whether the schema namespace has been made the default
namespace or not.
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<element name="foo" />
</schema>
Is equivilent to
<xsd:schema xmlns:xmlns="http://www.w3.org/2001/XMLSchema">
<xsd:element name="foo" />
</xsd:schema>
The vision is that the tools will save you, to date, this has yet to
happen and IMO you need deep knowledge of xml namespace, schema, soap &
WSDL to get fully functioning system up and running.
To answer your rant, Salesforce.com offers Web Services that are
regularly used by Java / .NET / Perl / PHP / Python / Ruby / VB / C++ /
Javascript clients.
Cheers
Simon
-----Original Message-----
From: Jarmo Doc [mailto:jarmod@hotmail.com]
Sent: Tuesday, July 11, 2006 2:02 PM
To: axis-user@ws.apache.org
Subject: RE: schema vs. xsd:schema
Should I just assume that this is a bug in Axis and that schema,
simpleType, complexType and so on should always be qualified by a
namespace, typically "xsd:"?
Or is there some sneaky implicit arrangement whereby xmlns or something
else being indicated means that I don't need qualification.
<rant>Is there actually anyone out there successfully using this
technology with multiple client types (Axis, gSOAP, WebSphere, .NET)? I
don't see how it's possible for anything more complex than a stock quote
lookup service.</rant>
>From: "Jarmo Doc" <ja...@hotmail.com>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: schema vs. xsd:schema
>Date: Tue, 11 Jul 2006 09:21:28 -0700
>
>Axis 1.3 java2wsdl generates 'schema' tags but most WSDL that I see
>contains 'xsd:schema' tags. The WSDL spec. also seems to suggest that
>'xsd:schema' is the only legal option.
>
>What is the difference between these two tags and why does Axis
>generate the former?
>
>Thanks.
>
>_________________________________________________________________
>Express yourself instantly with MSN Messenger! Download today - it's
FREE!
>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how
to get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
RE: schema vs. xsd:schema
Posted by Jarmo Doc <ja...@hotmail.com>.
Should I just assume that this is a bug in Axis and that schema, simpleType,
complexType and so on should always be qualified by a namespace, typically
"xsd:"?
Or is there some sneaky implicit arrangement whereby xmlns or something else
being indicated means that I don't need qualification.
<rant>Is there actually anyone out there successfully using this technology
with multiple client types (Axis, gSOAP, WebSphere, .NET)? I don't see how
it's possible for anything more complex than a stock quote lookup
service.</rant>
>From: "Jarmo Doc" <ja...@hotmail.com>
>Reply-To: axis-user@ws.apache.org
>To: axis-user@ws.apache.org
>Subject: schema vs. xsd:schema
>Date: Tue, 11 Jul 2006 09:21:28 -0700
>
>Axis 1.3 java2wsdl generates 'schema' tags but most WSDL that I see
>contains 'xsd:schema' tags. The WSDL spec. also seems to suggest that
>'xsd:schema' is the only legal option.
>
>What is the difference between these two tags and why does Axis generate
>the former?
>
>Thanks.
>
>_________________________________________________________________
>Express yourself instantly with MSN Messenger! Download today - it's FREE!
>http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
>For additional commands, e-mail: axis-user-help@ws.apache.org
>
_________________________________________________________________
On the road to retirement? Check out MSN Life Events for advice on how to
get there! http://lifeevents.msn.com/category.aspx?cid=Retirement
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org