Sure. But why modify Axis when the other framework involved is in error? That's where it gets to be hacking axis up.
He didn't say what the precise usage was, but if the C++ service is to be provided as an open integration point should he then provide 'modified' versions of any library anybody might want to use, simply because this server library decided to be 'simple' to the point of ignoring various XML specs? ----- Original Message ----- From: "Rushikesh Thakkar" <[EMAIL PROTECTED]> To: [email protected] Sent: Saturday, January 12, 2008 12:22:34 PM (GMT-0600) America/Chicago Subject: Re: SOAP-ENV versus soapenv Its not about hacking up Axis, you can modify the code and build it according to your needs. Thats the appealing thing about open source, isn't it? On Jan 12, 2008 5:56 PM, Dan Christopherson < [EMAIL PROTECTED] > wrote: Hack up Axis to make up for a non-compliant server library? ----- Original Message ----- From: "Rushikesh Thakkar" < [EMAIL PROTECTED] > To: [email protected] Sent: Saturday, January 12, 2008 10:08:02 AM (GMT-0600) America/Chicago Subject: Re: SOAP-ENV versus soapenv I think it should be possible if you modify org.apache.axis.Constants.NS_PREFIX_SOAP_ENV value from soapenv to SOAP-ENV org.apache.axis.Constants.NS_PREFIX_SOAP_ENC value from soapenc to SOAP-ENC I dont think you'll need to build axis entirely. Make this change in axis and just replace the class in jar, it should work.. See if it works.. On Jan 11, 2008 8:32 PM, Andrew Wood < [EMAIL PROTECTED] > wrote: When creating SOAP tags is there a choice of using either SOAP-ENV or soapenv? I thought it had to be SOAP-ENV but my Axis client is using soapenv, and I think this is probably the cause for the server moaning that the start or end tags of the SOAP message are missing. For example Axis sends <soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoap.org/soap/ envelope/" xmlns:xsd=" http://www.w3.org/2001/XMLSchema " xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance "> <soapenv:Body>........ And the server (not Axis) says <SOAP-ENV:faultcode>Client.ImproperlyFormattedMessage</SOAP- ENV:faultcode> <SOAP-ENV:faultstring>The message either has no begin tag or is missing the end tag. In either case, the message was not formatted correctly.</SOAP-ENV:faultstring> Am I right or is soapenv perfectly acceptable? Thanks Andrew --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
