Hi,
I'm new to axis2 in general, so my apologize in advance if I'm asking trivial question :-) Are there any specific reasons as to why we need to use the same version of axis module to axis2? In other word, is it a 'must' or a 'should' that we use the same version (e.g. rampart-1.4 and axis2-1.4)? The reason I'm asking is that I am falling into this situation: I originally use Axis2 1.3 and Rampart 1.3. It was working perfectly, until we need to upgrade to Axis2 1.4.1 because command line WSDL2Java in Axis2 1.4.1 support http proxy (our new XSD files require import to an external XSD files in other company's website). Having upgraded to Axis2 1.4.1, I upgraded my Rampart module to Rampart 1.4, and it's been painful since then, though perhaps it because of my lack of knowledge. It started that we have custom axis2.xml, we got that fixed, then we got "org.apache.axis2.AxisFault: Error in extracting message properties". the symptoms closely resemble https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jir a.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1262168 5#action_12621685. I'm not sure if this info is any relevant, but we are using xmlbeans (xmlbeans-2.3.0.jar for data binding), tomcat, axis2 1.4.1 I've been putting rampart 1.3 back into picture (so now we have combination of Axis2 1.4.1 and rampart 1.3), and while I will do more testings, so far looks so good. So I wonder if there is any fatal reason if I remain on rampart 1.3 and not upgrading to rampart 1.4 ? Furthermore, a philosophical question, should a module be 'loosely coupled' to axis2's version or in the other hand axis2 should be backward compatible to its old features? For instance, if I'm writing a module, I would hope that my module will work with the future releases of axis2 (except when there's major release of course). Thanks in advance, any advice much appreciated ! cheers, Ave
