Re: Content is not allowed in prolog

Yuval wrote: Should I change something in my attachment or just in the client code? Do you know how to change the encoding of the request to utf-16? Yuval, I will just point you to this JIRA enhancement request I ran across a few weeks back, for changing the encoding for the SOAP messag

RE: Content is not allowed in prolog

On September 14, 2005, [EMAIL PROTECTED] wrote: >But when I'm running it under Tomcat 5.0 (The axis client is always running >from >the same place), I get the following exception: >org.xml.sax.SAXParseException: Content is not allowed in prolog Yuval, I don't have experience with the problem i

Re: Field with second letter capitalized problem

Mike, I didn't see any responses to your question about how to get Axis to map from Java bean property names to the XML element names. I ran into what may be the same problem a couple of weeks ago; from reading the Axis documentation, I found that the generated classes should have type-mapping

RE: changing the reponse character encoding

Rob, I ran across this JIRA issues a few days ago while looking into UTF-16 encoding. The discussion here may help answer your questions: http://issues.apache.org/jira/browse/AXIS-1682 The upshot is, it looks like the Axis service will respond in whatever encoding the client sends in. I am us

RE: AW: Axis on IBM websphere5.0

Just to clarify-- We have not removed a "webservices.jar" file or made any modifications to our WebSphere install. You haven't described what problems you ran into; perhaps one of the circumstances of my setup is protecting us from the error--the fact that we don't use HTTP/HTTPS, or that we a

RE: AW: Axis on IBM websphere5.0

I, also am running Axis 1.2.1 on WebSphere 5.1. In my case, however, we're using a custom transport for JMS because the existing one didn't support our needs--so if there are conflicts with the HTTP/HTTPS handling, I wouldn't run into them. WSDL2Java generation worked great once I got the WSA

RE: Disable creation of "encoding="UTF-8"

I'll reply to my own message in case someone in the future needs this answer... I tracked the code snippet down to org.apache.axis.encoding.SerializationContext, in the writeXMLDeclaration() method. The method itself is fairly simple, and it's very obvious that there's no way to turn off the e

Disable creation of "encoding="UTF-8"

I'll start searching the mail archives and JIRAs, but if anyone can short-cut my search by telling me this, I'd be grateful! Apparently, even though it outputs xml containing the encoding="UTF-8" text, the Siebel web service we are accessing cannot stand receiving it. I think I remember that t

Re: encodingStyle attribute location

Ah. I hadn't backed up in the WS-I BP to see R1005, although I knew that WS-I didn't allow rpc/encoded and that should have told me right there. :) Well, unreasonable or not, they've already got a .NET client working on it and now they want my Java webapp to access the services, so I'll have t

encodingStyle attribute location

I am using Axis 1.2.1, for rpc/encoded, as a Java client talking to a Siebel SOAP service over JMS. Siebel insists that the encodingStyle attribute be in the soap Body or soap Envelope elements. W3C SOAP standards state that the attribute can be in any element in the message, but I did find th

Re: stumped on deserializer problem

Sounds great, Thad! I'm currently stuggling with the custom (de)serialization-within-custom-(de)serialization problem, so I'll appreciate your writeup if I don't get it working first! Meghan Pietila Granite Consulting On Tuesday 08 August 2005 17:49, [EMAIL PROTECTED] wrote: >Bingo! I've cra

RE: Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons???

Don, The JAR file names in your classpath don't match up to the names in my 1.2.1 download of Axis; I had the same problem when I copied a classpath setup script from the wiki (but had forgotten until Tim mentioned it). You'll want to go through and compare each JAR name against the real JAR in

Exception in thread "main" java.lang.NoClassDefFoundError: org.apache.commons???

Don, >From your copy and paste below, it appears that you put the AXISCLASSPATH >variable in quotation marks. Don't do that; you want the shell to fill in the >actual value--that's what the percent signs are for. Meghan Pietila Granite Consulting On a Win box, I followed the Axis 1.2 “Inst

RE: "Invalid element" error - Lower-case property name

All right, I've discovered that those classes I originally generated using WSDL2Java--with the missing meta-data--looked so odd because when I installed WebSphere Application Developer, it had WSDL2Java on the classpath. And it was earlier in the classpath than my Axis 1.2.1 jar. So I've been

RE: "Invalid element" error - Lower-case property name

I think I've made some progress; I found this archived mail: http://marc.theaimsgroup.com/?l=axis-user&m=102260719826152&w=2 It seems to indicate that when I ran WSDL2Java on the Siebel WSDL, some static code _should_ have been generated in my bean classes, to set up the XML -> Java mapping with

"Invalid element" error - Lower-case property name

I was encountering an "Invalid element" error when I attempted to receive a response message with my Axis client (Siebel service). I found this error mentioned many times in the axis-user mailing list archives, but was unable to find anyone listing an explanation or a solution. I debugged thro

stumped on deserializer problem

Thad, I didn't see any answers to your question, so I'll add what I know, having just run into the same exception myself. When I went to add the typeMapping into my .wsdd file, I found that adding the element qname didn't resolve anything--what I needed to do, was add the _complexType_ qname.