You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Benson Margulies <bi...@basistech.com> on 2007/10/09 15:16:45 UTC
Microsoft interoperability
I pointed the Microsoft visual studio 2005 wsdl.exe tool at a WSDL from
one of my CXF services.
The results are not wonderful. I get warnings like the following. Based
on my reading of the WSDL, the Microsoft tool is just confused, but I
wonder if anyone else has been here?
Schema validation warning: Schema item 'complexType' named
'NameIndexQuery' from namespace 'http://index.rnm.basistech.com' is
invalid. Namespace 'http://rnm.basistech.com' is not available to be
referenced in this schema.
Re: Microsoft interoperability
Posted by Daniel Kulp <dk...@apache.org>.
Lovely. :-(
I'll put fixing that on my todo list for this week. It's definitely
broken and causes too many issues.
Dan
On Tuesday 09 October 2007, Benson Margulies wrote:
> Not happy for a reason related, I think, to one of your favorite
> JIRAs. Which makes it hard to evaluate any other problems.
>
> (benson@sobig)[36] /cygdrive/c/x/rlp54/rlpws/smoketests %
> c:/x/apache-cxf-2.0.2-incubator/bin/wsdlvalidator
> ../../rlpnc/source/ws/xml/rni/NameIndex.wsdl
> WSDLValidator Error : Violate WSI-BP-1.0 R2205: In Message
> {http://ws.index.rnm.basistech.com}NameIndexException, part
> NameIndexException must specify a 'element' attribute
>
>
>
> (benson@sobig)[37] /cygdrive/c/x/rlp54/rlpws/smoketests %
>
> > -----Original Message-----
> > From: Daniel Kulp [mailto:dkulp@apache.org]
> > Sent: Tuesday, October 09, 2007 9:39 AM
> > To: cxf-user@incubator.apache.org
> > Cc: Dave Kallstrom
> > Subject: Re: Microsoft interoperability
> >
> >
> > One more thing...
> >
> > Can you run our own wsdlvalidator (in the bin directory) against the
>
> wsdl
>
> > just to double check that the wsdl looks OK from it's standpoint?
> >
> > Dan
> >
> > On Tuesday 09 October 2007, Dave Kallstrom wrote:
> > > I've seen that warning from .NET's wsdl tool a number of times. It
>
> has
>
> > > never caused any problems though. It sill seems to generate both
> > > Vb and C# code that works just fine. Also we have two clients up
> > > and running on .NET and all are running fine.
> > >
> > > On 10/9/07, Benson Margulies <bi...@basistech.com> wrote:
> > > > I pointed the Microsoft visual studio 2005 wsdl.exe tool at a
> > > > WSDL from one of my CXF services.
> > > >
> > > > The results are not wonderful. I get warnings like the
> > > > following. Based on my reading of the WSDL, the Microsoft tool
> > > > is just confused, but I wonder if anyone else has been here?
> > > >
> > > > Schema validation warning: Schema item 'complexType' named
> > > > 'NameIndexQuery' from namespace 'http://index.rnm.basistech.com'
>
> is
>
> > > > invalid. Namespace 'http://rnm.basistech.com' is not available
> > > > to
>
> be
>
> > > > referenced in this schema.
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer
> > IONA
> > P: 781-902-8727 C: 508-380-7194
> > daniel.kulp@iona.com
> > http://www.dankulp.com/blog
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
RE: Microsoft interoperability
Posted by Benson Margulies <bi...@basistech.com>.
Not happy for a reason related, I think, to one of your favorite JIRAs.
Which makes it hard to evaluate any other problems.
(benson@sobig)[36] /cygdrive/c/x/rlp54/rlpws/smoketests %
c:/x/apache-cxf-2.0.2-incubator/bin/wsdlvalidator
../../rlpnc/source/ws/xml/rni/NameIndex.wsdl
WSDLValidator Error : Violate WSI-BP-1.0 R2205: In Message
{http://ws.index.rnm.basistech.com}NameIndexException, part
NameIndexException must specify a 'element' attribute
(benson@sobig)[37] /cygdrive/c/x/rlp54/rlpws/smoketests %
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: Tuesday, October 09, 2007 9:39 AM
> To: cxf-user@incubator.apache.org
> Cc: Dave Kallstrom
> Subject: Re: Microsoft interoperability
>
>
> One more thing...
>
> Can you run our own wsdlvalidator (in the bin directory) against the
wsdl
> just to double check that the wsdl looks OK from it's standpoint?
>
> Dan
>
>
> On Tuesday 09 October 2007, Dave Kallstrom wrote:
> > I've seen that warning from .NET's wsdl tool a number of times. It
has
> > never caused any problems though. It sill seems to generate both Vb
> > and C# code that works just fine. Also we have two clients up and
> > running on .NET and all are running fine.
> >
> > On 10/9/07, Benson Margulies <bi...@basistech.com> wrote:
> > > I pointed the Microsoft visual studio 2005 wsdl.exe tool at a WSDL
> > > from one of my CXF services.
> > >
> > > The results are not wonderful. I get warnings like the following.
> > > Based on my reading of the WSDL, the Microsoft tool is just
> > > confused, but I wonder if anyone else has been here?
> > >
> > > Schema validation warning: Schema item 'complexType' named
> > > 'NameIndexQuery' from namespace 'http://index.rnm.basistech.com'
is
> > > invalid. Namespace 'http://rnm.basistech.com' is not available to
be
> > > referenced in this schema.
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer
> IONA
> P: 781-902-8727 C: 508-380-7194
> daniel.kulp@iona.com
> http://www.dankulp.com/blog
Re: Microsoft interoperability
Posted by Daniel Kulp <dk...@apache.org>.
One more thing...
Can you run our own wsdlvalidator (in the bin directory) against the wsdl
just to double check that the wsdl looks OK from it's standpoint?
Dan
On Tuesday 09 October 2007, Dave Kallstrom wrote:
> I've seen that warning from .NET's wsdl tool a number of times. It has
> never caused any problems though. It sill seems to generate both Vb
> and C# code that works just fine. Also we have two clients up and
> running on .NET and all are running fine.
>
> On 10/9/07, Benson Margulies <bi...@basistech.com> wrote:
> > I pointed the Microsoft visual studio 2005 wsdl.exe tool at a WSDL
> > from one of my CXF services.
> >
> > The results are not wonderful. I get warnings like the following.
> > Based on my reading of the WSDL, the Microsoft tool is just
> > confused, but I wonder if anyone else has been here?
> >
> > Schema validation warning: Schema item 'complexType' named
> > 'NameIndexQuery' from namespace 'http://index.rnm.basistech.com' is
> > invalid. Namespace 'http://rnm.basistech.com' is not available to be
> > referenced in this schema.
--
J. Daniel Kulp
Principal Engineer
IONA
P: 781-902-8727 C: 508-380-7194
daniel.kulp@iona.com
http://www.dankulp.com/blog
RE: Microsoft interoperability
Posted by Benson Margulies <bi...@basistech.com>.
The cs0030 is this charming bug of Microsoft's:
http://support.microsoft.com/kb/891386
> -----Original Message-----
> From: Benson Margulies [mailto:bim2007@basistech.com]
> Sent: Tuesday, October 09, 2007 9:57 AM
> To: cxf-user@incubator.apache.org
> Subject: RE: Microsoft interoperability
>
> Also, the Mindreef Soapscope tool has complaints about inaccessible
> types that I am harassing their tech support for an explanation of.
>
> > -----Original Message-----
> > From: Benson Margulies [mailto:bim2007@basistech.com]
> > Sent: Tuesday, October 09, 2007 9:55 AM
> > To: cxf-user@incubator.apache.org
> > Subject: RE: Microsoft interoperability
> >
> > So far, not too good.
> >
> > 'Unable to generate a temporary class (result = 1). Error CS0030:
> Cannot
> > convert type BasisTechnology.rnm.ws.Name[] to
> > BasisTechnology.rnm.ws.Name'
> >
> > This is thrown on construction of the proxy class generated by their
> > wsdl tool.
> >
> > I'm also getting all the parameters wrapped up as extra objects, but
I
> > imagine that there's some option on the MS side that I need to
> > rediscover on that front.
> >
RE: Microsoft interoperability
Posted by Benson Margulies <bi...@basistech.com>.
Also, the Mindreef Soapscope tool has complaints about inaccessible
types that I am harassing their tech support for an explanation of.
> -----Original Message-----
> From: Benson Margulies [mailto:bim2007@basistech.com]
> Sent: Tuesday, October 09, 2007 9:55 AM
> To: cxf-user@incubator.apache.org
> Subject: RE: Microsoft interoperability
>
> So far, not too good.
>
> 'Unable to generate a temporary class (result = 1). Error CS0030:
Cannot
> convert type BasisTechnology.rnm.ws.Name[] to
> BasisTechnology.rnm.ws.Name'
>
> This is thrown on construction of the proxy class generated by their
> wsdl tool.
>
> I'm also getting all the parameters wrapped up as extra objects, but I
> imagine that there's some option on the MS side that I need to
> rediscover on that front.
>
RE: Microsoft interoperability
Posted by Benson Margulies <bi...@basistech.com>.
So far, not too good.
'Unable to generate a temporary class (result = 1). Error CS0030: Cannot
convert type BasisTechnology.rnm.ws.Name[] to
BasisTechnology.rnm.ws.Name'
This is thrown on construction of the proxy class generated by their
wsdl tool.
I'm also getting all the parameters wrapped up as extra objects, but I
imagine that there's some option on the MS side that I need to
rediscover on that front.
Re: Microsoft interoperability
Posted by Dave Kallstrom <da...@gmail.com>.
I've seen that warning from .NET's wsdl tool a number of times. It has never
caused any problems though. It sill seems to generate both Vb and C# code
that works just fine. Also we have two clients up and running on .NET and
all are running fine.
On 10/9/07, Benson Margulies <bi...@basistech.com> wrote:
>
> I pointed the Microsoft visual studio 2005 wsdl.exe tool at a WSDL from
> one of my CXF services.
>
> The results are not wonderful. I get warnings like the following. Based
> on my reading of the WSDL, the Microsoft tool is just confused, but I
> wonder if anyone else has been here?
>
> Schema validation warning: Schema item 'complexType' named
> 'NameIndexQuery' from namespace 'http://index.rnm.basistech.com' is
> invalid. Namespace 'http://rnm.basistech.com' is not available to be
> referenced in this schema.
>
--
Dave Kallstrom