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 Matt Munz <mm...@apelon.com> on 2003/02/25 20:15:29 UTC
Array Deserialization in .net (was RE: .Net Interop: JavaBean -> WSDL -> c# proxy)
Is there a bug# or RFE for this issue? I'm interested in the workaround. Is there a person I can contact to get more information about it?
- Matt Munz (mmunz@apelon.com)
-----Original Message-----
From: Kellogg, Richard [mailto:RKellogg@MICROS.COM]
Sent: Tuesday, February 25, 2003 11:15 AM
To: axis-user@ws.apache.org
Subject: RE: .Net Interop: JavaBean -> WSDL -> c# proxy
You are correct. This has been fixed in the latest .NET Framework 1.1 Beta. I would suggest you try this. A work around is in progress for Axis. I do not know the status of this correction/patch or whether it will be included in Axis 1.1 RC2.
Refer to the following article for more details:
http://support.microsoft.com/default.aspx?scid=kb;en-us;330065
Take care,
Rick
> -----Original Message-----
> From: Matt Munz [mailto:mmunz@apelon.com]
> Sent: Tuesday, February 25, 2003 11:08 AM
> To: axis-user@ws.apache.org
> Subject: RE: .Net Interop: JavaBean -> WSDL -> c# proxy
>
>
> Paolo & group,
>
> I just caught this in the response.
>
> <fetchedRoles xsi:type="soapenc:Array"
> soapenc:arrayType="ns2:role[0]"/>
>
> Did I read somewhere that .Net can't deserialize an empty
> array? Could this be the problem?
>
> - Matt
>
> -----Original Message-----
> From: Matt Munz
> Sent: Tuesday, February 25, 2003 11:05 AM
> To: axis-user@ws.apache.org
> Subject: RE: .Net Interop: JavaBean -> WSDL -> c# proxy
>
>
> Paolo,
>
> Thanks again for your advice. I'm using wsdl.exe to
> generate the proxy.
>
> What specifically about ConceptBean is "too complex" or
> otherwise non-interoperable?
>
> From my point of view, ConceptBean is an extremely simple
> object. Regarding the "logic" of the class, why does it
> matter? The bean serializer should only serialize state,
> right? Methods that don't start in "get" or "set", or aren't
> public, shouldn't matter.
>
> Basically, I need to know where to draw the line. Is the
> problem the depth of my object graph? Can beans only have
> primitives (and not other beans) as attributes?
>
> In a perfect world, I suppose my web service would only
> deal in primitives. In reality, I have an existing Java API
> that I would like to wrap with a web service. Perhaps I
> should look into custom serializers...
>
> In the meantime, I'll check your theory that the
> ConceptBean object is the problem by creating a new service
> that dispenses Form objects.
>
> - Matt
>
>
> -----Original Message-----
> From: Paolo Paganotto [mailto:paolo.paganotto@txt.it]
> Sent: Tuesday, February 25, 2003 10:40 AM
> To: axis-user@ws.apache.org
> Subject: Re: .Net Interop: JavaBean -> WSDL -> c# proxy
>
>
> Yeah, but doing it has been a right move.
> According to the code, I can say you that, in my experience,
> I've been using
> Web services exchanging beans and array of beans (with
> complex members, too)
> without problems.
> My scenario is: Java classes in an application server, and a
> client Web
> server developed in .NET c#.
> Well, exchanging parameters that are pure JavaBeans (as your
> FormBean),
> without ANY logic inside them, just only members, getters and setters,
> permits you to map the bean with the default
> serializer/deserializer. The
> other bean, called ConceptBean, looks too much complicated to
> exchange:
> better is to say that it is too complicated to be exported in
> a way that
> maximizes interoperability. Maybe Axis can recognize it, but
> .NET, in my
> opinion, absolutelly don't.
> In my project I have complex classes and complex objects, but
> the only way
> to be sure that the WS are really understandable by other platform, is
> definitely to exchange parameters that as simple as you can
> (this may entail
> more services to be invoked by clients).
> And, since you can put array of beans as member variables of
> Beans, this
> means that parameters can be not so simple.
> So, if you are sure that your bean doesn't work, you have to split it
> putting through the wire just only the relevant data your client need.
> One question: what tool do you use to create the C# proxy class?
> ----- Original Message -----
> From: "Matt Munz" <mm...@apelon.com>
> To: <ax...@ws.apache.org>
> Sent: Tuesday, February 25, 2003 4:19 PM
> Subject: RE: .Net Interop: JavaBean -> WSDL -> c# proxy
>
>
> > installing .Net SP2 didn't fix it...
> >
> > - Matt
> >
> > -----Original Message-----
> > From: Matt Munz
> > Sent: Tuesday, February 25, 2003 10:03 AM
> > To: axis-user@ws.apache.org
> > Subject: RE: .Net Interop: JavaBean -> WSDL -> c# proxy
> >
> >
> > Paolo,
> >
> > Thanks for taking an interest in my problem.
> >
> > I am fairly certain that my beans are correct, since the
> java client
> proxy generated by WSDL2Java works just fine.
> >
> > Attached are my WSDD (JBoss) and the source for the bean
> that is being
> returned by the service. Included below is the relevant
> source for the
> webservice object.
> >
> > Next, I'll install SP 2 and see what happens ;)
> >
> > Thanks again.
> >
> > - Matt
> >
> > From ConceptServerWs (superclass of NavServerWs) ...
> >
> > /**
> > * This is the method that I am testing.
> > */
> > public ConceptBean findConceptById(int concept_id)
> > throws Exception
> > {
> > ...
> > }
> >
> > public ConceptBean findConceptById(int concept_id,
> AttributeSetDescriptorBean descriptor)
> > throws Exception
> > {
> > ...
> > }
> >
> > public ConceptBean[] findConceptById(int[] concept_id,
> AttributeSetDescriptorBean descriptor)
> > throws Exception
> > {
> > ...
> > }
> >
> > -----Original Message-----
> > From: Paolo Paganotto [mailto:paolo.paganotto@txt.it]
> > Sent: Tuesday, February 25, 2003 9:37 AM
> > To: axis-user@ws.apache.org
> > Subject: Re: .Net Interop: JavaBean -> WSDL -> c# proxy
> >
> >
> > ==>Hi, Matt
> > is your bean really correct? I mean, do you have a getter
> and a setter for
> > every variable member in the bean? This is very important,
> in fact, even
> > though .NET doesn't throw any error if you don't specify a
> getter or a
> > setter for a variable, you don't get the corresponding type in .NET.
> > Maybe it is better if you post your bean and the WSDD.
> > Ah, download the service pack 2 for .NET. if you didn't
> before; I did, and
> > lots of eerie errors magically disappeared.
> >
> > :P:
> >
> >
> > > Hi again,
> > >
> > > At this point, I am able to get a Bean-based ws to
> work, but not the
> one
> > I am currently working on. I am fairly certain, at this
> point, that my
> wsdd
> > is correct. What else could be the problem? I believe
> that this issue
> has
> > come up before on this list. Does anyone have any useful
> ideas on the
> > subject?
> > >
> > > - Matt Munz (mmunz@apelon.com)
> > >
> > > -----Original Message-----
> > > From: Matt Munz
> > > Sent: Fri 2/21/2003 2:29 PM
> > > To: axis-user@ws.apache.org
> > > Cc:
> > > Subject: .Net Interop: JavaBean -> WSDL -> c# proxy
> > >
> > >
> > > Hi all,
> > >
> > > I am having trouble using the C# proxy I generated from
> the WSDL I got
> > from Axis 1.0 for my JavaBean-based web service. On the wiki, it is
> stated
> > that JavaBeans can be accessed via .Net. Does anyone have
> an example of
> > this? When I try to access the web service using the
> generated proxy, the
> > request works just fine, but the response cannot be parsed
> correctly by
> the
> > proxy, which throws a System.InvalidOperationException.
> > >
> > > After searching the mailing list, I see that this is
> perhaps a common
> > problem, but I am unable to find a solution. If anyone has
> an example
> > laying around, or even any good ideas on where the problem
> may lie, I'd
> love
> > to hear it.
> > >
> > > Thanks,
> > > Matt (mmunz@apelon.com)
> > >
> > >
> > >
> >
> >
> >
>
>
>