My question below has been answered. I should have done more digging first before submitting it to the list. I even made a wrong statement in my original post. The statement below about "URI_CURRENT_SOAP_ENV" and "URIS_SOAP_ENV" not being used in the AXIS sourcecode is not true. My apologies to anyone I may have mislead. :(
It appears AXIS does handle SOAP versioning properly. The problem was in my own code. Next time I won't pull the trigger so quickly. Steve Pannier Jacada, Inc. (763) 201-0002 Ext. 219 [EMAIL PROTECTED] http://www.jacada.com > Hello. The AXIS User Guide states the following in the "What's in this > release" section: > > This release includes the following features: > SOAP 1.1 compliant engine (with some SOAP 1.2 support as well) > > My question is this: What does this mean as far as SOAP versioning in AXIS? > That is, > in what situations (if any) will AXIS generate a SOAP VersionMismatch > fault? If I send a > SOAP 1.2 envelope to my AXIS server, should I expect to see a > VersionMismatch fault? > > I know what the SOAP 1.2 spec says in the "Version Transition from SOAP/1.1 > to SOAP > Version 1.2" section. But I need to know exactly what AXIS supports (or > intends to support) > in this area. Is this something that is intended to be supported, but > hasn't yet been > implemented? (I see that Constants.java defines "URI_CURRENT_SOAP_ENV" and > "URIS_SOAP_ENV", but neither of these are used anywhere throughout the AXIS > sourcecode.) > > Any info on this issue would be greatly appreciated! Thanks in advance. > > > > Steve Pannier > Jacada, Inc. > (763) 201-0002 Ext. 219 > [EMAIL PROTECTED] > http://www.jacada.com > > >
