RE: ... again multiRef problem with .Net client

2002-06-10 Thread blake biesecker
This looks like bug 9637 - it should be fixed in the current cvs source (but not in beta 2). What version are you using? Blake > -Original Message- > From: Kai Steven Kunze [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 10, 2002 11:26 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Sub

RE: C# client, java server

2002-06-10 Thread blake biesecker
Pop,   Visual Studio .NET should build up the client side stubs for you when you import the WSDL as a Web Reference. Then it is just about using the generated C# classes to make your calls to the server.   We ran into a slight problem with the href/id mechanism when interoperating with Ax

RE: Deserialization in axis beta 2

2002-06-05 Thread blake biesecker
none > of the existing tests are not broken. Also, If you REALLY, > REALLY want to make sure that no one > trips on this fix then you should send in a test case for > this "functionality/feature/patch". > > Thanks, > dims > > --- blake biesecker <[EMAI

RE: Deserialization in axis beta 2

2002-06-04 Thread blake biesecker
> -Original Message- > From: Vidyanand Murunikkara [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, June 04, 2002 5:23 PM > To: [EMAIL PROTECTED] > Subject: Deserialization in axis beta 2 > > > > Hi > > Please refer to > http://marc.theaimsgroup.com/?l=axis-dev&m=102027493116786&w=2 > >

hrefs where SOAP-ENC:root is not supplied - interop issue with .NET

2002-05-30 Thread blake biesecker
We have run into this same issue and I agree with Jason that it would be best if Axis handled body elements that are not root elements but have the soapenc:root="0" tag omitted. Is there consensus in the Axis community on this? If so, I or one of my colleagues can suggest an Axis code change, b