RE: .NET client

nutes. -Original Message-From: bethana kumar [mailto:[EMAIL PROTECTED]Sent: Friday, December 17, 2004 10:36 AMTo: [EMAIL PROTECTED]Subject: RE: .NET client Hi   Does anybody have an idea,how to access  Webservices (java) from C#, I would like to know how it works. Does any

RE: .NET client

Hi   Does anybody have an idea,how to access  Webservices (java) from C#, I would like to know how it works. Does any body help for getting an overview(i.e white paper)  on this.   If anybody provide me some sample sites where i can get more info.   Thanks shanta.BSagar Pidaparth

RE: .NET client

oc"; /> From: Lyndon Tiu [mailto:[EMAIL PROTECTED] Sent: Tue 12/14/2004 8:04 AM To: [EMAIL PROTECTED] Subject: Re: .NET client Sagar Pidaparthi wrote: >Hi, > >I wrote a simple .NET client and it does not work. I

Re: .NET client

Sagar Pidaparthi wrote: Hi, I wrote a simple .NET client and it does not work. I would appreciate any help. Here are my steps on AXIS 1.1 1. I write a simple class called SecurityMgr and publish as wrapped literal Without sending us the Java web service code and the Java web service wsdl, it

RE: .NET client accessing multiple Axis WSDLs

ronously using an event-based programming pattern. - Arent-Jan -Original Message- From: Anand Natrajan [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 30, 2004 3:48 PM To: [EMAIL PROTECTED] Subject: RE: .NET client accessing multiple Axis WSDLs : Re

RE: .NET client accessing multiple Axis WSDLs

e types between services. Sadly, that's not possible... I do want some complex types to be used by multiple services. Thanks! Anand : - Arent-Jan : : -Original Message- : From: Anand Natrajan [mailto:[EMAIL PROTECTED] : Sent: Tuesday, June 29, 2004 7:14 PM : To: [EMAIL PROTECTED] : Sub

RE: .NET client accessing multiple Axis WSDLs

-Original Message- From: Anand Natrajan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 29, 2004 7:14 PM To: [EMAIL PROTECTED] Subject: Re: .NET client accessing multiple Axis WSDLs Re: specify the same namespace, do you mean within the WSDLs itself? I already do specify the same na

Re: .NET client accessing multiple Axis WSDLs

Re: specify the same namespace, do you mean within the WSDLs itself? I already do specify the same namespace for the common data structure, and it doesn't work. Re: specify the same namespace, do you mean within VB? Tried that, but VB won't let you do it. It's sort of like trying to specify two va

Re: .NET client accessing multiple Axis WSDLs

Is it possible to merge all your wsdls into a same wsdl file? Or specify a same namespace for all of them? Anand Natrajan wrote: Hello! As part of my .NET and Axis interoperability work, I am facing a piquant situation. I have written multiple web services using Axis. Each of these web services

RE: .NET Client -> Axis Web service -Issue with "anyType"

: [EMAIL PROTECTED] Subject: RE: .NET Client -> Axis Web service -Issue with "anyType" If you desire a Java XML type (org.w3c.dom.*), you should investigate the message oriented web services examples. For example, /samples/message /Chris -- Ori

RE: .NET Client -> Axis Web service -Issue with "anyType"

pe should I use if my parameter and return type are >w3c.org.dom.document? > >Thanks, >Ranjith Pillai. > >-Original Message- >From: Chris Haddad [mailto:[EMAIL PROTECTED] >Sent: Friday, April 02, 2004 7:05 PM >To: [EMAIL PROTECTED] >Subject: Re: .NET Client -&g

RE: .NET Client -> Axis Web service -Issue with "anyType"

pe should I use if my parameter and return type are >w3c.org.dom.document? > >Thanks, >Ranjith Pillai. > >-Original Message- >From: Chris Haddad [mailto:[EMAIL PROTECTED] >Sent: Friday, April 02, 2004 7:05 PM >To: [EMAIL PROTECTED] >Subject: Re: .NET Client -&g

RE: .NET Client -> Axis Web service -Issue with "anyType"

w3c.org.dom.document? Thanks, Ranjith Pillai. -Original Message- From: Chris Haddad [mailto:[EMAIL PROTECTED] Sent: Friday, April 02, 2004 7:05 PM To: [EMAIL PROTECTED] Subject: Re: .NET Client -> Axis Web service -Issue with "anyType" if the XML document conforms to a XML Schema def

Re: .NET Client -> Axis Web service -Issue with "anyType"

if the XML document conforms to a XML Schema definition, just replace the anyType reference in the WSDL with the schema element reference. /Chris -- Original Message -- From: "Pillai, Ranjith" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Fri, 2 A

Re: .Net Client/Axis Server & MultiDim Arrays -- I GIVE

Cory Wilkerson wrote: > From what I can tell, .Net web services implementations do not support > multidimensional arrays. This sucks. Anyone have a good way to marshall a > key/value set across the wire? Convert it into an xml string, turn it into a byte array, send that to the .net client

RE: .Net Client/Axis Server & MultiDim Arrays -- I GIVE

ry Wilkerson > Sent: Thursday, February 27, 2003 10:13 PM > To: [EMAIL PROTECTED] > Subject: RE: .Net Client/Axis Server & MultiDim Arrays > > > When wsdl.exe is generated agains the WSDL, you'll see that: > > string[] rulesElements > > is created as

RE: .Net Client/Axis Server & MultiDim Arrays

ECTED] Subject: RE: .Net Client/Axis Server & MultiDim Arrays Does this happen as a result of running wsdl.exe on the generated WSDL file? Harry J. Kobetitsch UBS Warburg One North Wacker Drive Chicago, Illinois 60606-2809 312-525-5866 [EMAIL PROTECTED]

RE: .Net Client/Axis Server & MultiDim Arrays

Does this happen as a result of running wsdl.exe on the generated WSDL file? Harry J. Kobetitsch UBS Warburg One North Wacker Drive Chicago, Illinois 60606-2809 312-525-5866 [EMAIL PROTECTED] -Original Message- From: Cory Wilkerson [mailto:[EMAIL PROTECTED

RE: .NET client and nested arrays

Thanks, Dan. This worked. I have added an empty check to my get-array methods: if (things.length == 0) return null; return things; At 08:23 2003.01.07 -0800, you wrote: I have noticed that a c# .net client does not handle the deserialization of empty arrays very well. You may be able to 'sid

RE: .NET client and nested arrays

I have noticed that a c# .net client does not handle the deserialization of empty arrays very well. You may be able to 'sidestep' this issue not sending empty arrays. I have been setting the array to null within a bean instead of sending an empty array : Example: Hope this helps. Dan Stone

RE: .NET Client does not deserialize typed Array

- > From: Christian Schmitz [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 24, 2002 7:18 AM > To: '[EMAIL PROTECTED]' > Subject: RE: .NET Client does not deserialize typed Array > > > I´ve attached the SOAP Message and the WSDL file. WSDL is so > lar

RE: .NET Client does not deserialize typed Array

27; Subject: RE: .NET Client does not deserialize typed Array Christian, It would be helpful to also see the soap message returned to the client and your wsdl. Blake > -Original Message- > From: Christian Schmitz [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 24, 2002

RE: .NET Client does not deserialize typed Array

Christian, It would be helpful to also see the soap message returned to the client and your wsdl. Blake > -Original Message- > From: Christian Schmitz [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 24, 2002 3:10 AM > To: '[EMAIL PROTECTED]' > Subject: .NET Client does not deserialize t

RE: .Net Client for Axis Service

thenticate", "Basic realm=\"mydomain.com\"");    throw new AxisFault(..);}   .     -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, June 12, 2002 3:06 PMTo: [EMAIL PROTECTED]Subject: RE: .Net Client for Axis

RE: .Net Client for Axis Service

Title: RE: .Net Client for Axis Service You can also try to confirm what I experienced if you do not do something like service.PreAuthenticate = true. Without doing the PreAuthenticate, every request from the client will first do a request without the auth header, get a 401 and then send the

RE: .Net Client for Axis Service

Title: RE: .Net Client for Axis Service Hi all, I have got the servlet solution to work :-).  I made a servlet that checks if there is any auth information in the request.  If there is not it responds with a 401 and the WWW-Authenticate header.  If there is auth information, it forwards the

RE: .Net Client for Axis Service

: Jones, Rhys [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 1:40 PMTo: '[EMAIL PROTECTED]'Subject: RE: .Net Client for Axis Service Thanks Vidyanand, I can't get the method of sending the WWW-Authenticate header back to the client to work.  I am curious of

RE: .Net Client for Axis Service

Title: RE: .Net Client for Axis Service Thanks Vidyanand, I can't get the method of sending the WWW-Authenticate header back to the client to work.  I am curious of how you changed the GetWebRequest() method to send the correct headers.  It does seem like the hard way to do it, b

RE: .Net Client for Axis Service

Title: RE: .Net Client for Axis Service That should be fine. Thanks for the pointers, which is all I really needed. Thomas -Original Message- From: Vidyanand Murunikkara [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 7:08 PM To: [EMAIL PROTECTED] Subject: RE: .Net Client

RE: .Net Client for Axis Service

really are interested in seeing what i exactly did, I can look it up for you when I find sometime. Vidyanand. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 3:09 PM To: [EMAIL PROTECTED] Subject: RE: .Net Client for Axis Service I

RE: .Net Client for Axis Service

Title: RE: .Net Client for Axis Service I think that returning 401 is not enough. You need to return 401 and the WWW-Authenticate header so the .NET client understands that it has to retry by sending authentication information. Vidyanand, I will be interested to understand what you mean by

RE: .Net Client for Axis Service

Hi Rhys check this out http://marc.theaimsgroup.com/?l=axis-user &m=102224516027914&w=2 . Similar problem But there is no good solution to it. But there is one way you can make it send the required headers. But it involves chan

RE: .NET Client calling Axis service with Bean Datatype returned

Sorry, didn't include the WSDL and TCPMonitor Message Trace on the first email. - steve === TCPMon TRACE: === Listen Port: 8080 Target Host: localhost Target Port: 100 Request POST /axis/services/PapService HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Clien