Re: [axis] unexpected element type

2006-01-07 Thread Anne Thomas Manes
My first recommendation is to not using SOAP encoding -- in other words, switch from rpc/encoded to wrapped document/literal. If for some reason that is not an option, then you need to tell Axis to use xsd types rather than soapenc types. You can do that in your WSDD by adding this parameter:

Re: Deserialization(?) Error on String Array

2006-01-07 Thread Anne Thomas Manes
Shelli, Are you using rpc/encoded or rpc/literal? If you are using rpc/encoded, then you need to define the array using soapenc:Array. If you are using rpc/literal, then you need to define the array as a complex type (not an element) with a maxOccurs="unbounded" and reference the type from your m

RE: AXIS, SOAP and cookie based routing

2006-01-07 Thread Jayaraman, Venkatesh
When I used AXIS on tomcat Web Server. I was seeing high session counts. Any help in reducing this high session counts seen on tomcat manager? -Venky -Original Message- From: Keith [mailto:[EMAIL PROTECTED] Sent: Friday, January 06, 2006 5:09 AM To: axis-user@ws.apache.org Subject: R

RE: Indicating filenames during file attach

2006-01-07 Thread Jarmo Doc
Thanks. I looked into this further and it seems that both content-type and content-disposition (but not content-id) can be used to indicate the file name, e.g. Content-type: image/jpeg; name="mypic.jpg" Content-disposition: attachment; filename="mypic.jpg" From: "Liu, Tao" <[EMAIL PROTECTED

Re: Deserialization(?) Error on String Array

2006-01-07 Thread iksrazal
Shelli, I'm not a big fan of soap encoded arrays, but I used to use them alot and I may be able to help. Doc / Lit is the way things are going. Nevertheless, try posting your original wsdl, and mention where you want to put your String array. Chances are though, your wsdl may be fine. Your D