Re: [DISCUSS] Migration to Axis2 1.4.1

Thu, 18 Sep 2008 09:25:10 -0700 

+1 to go ahead with this migration including the dependencies.

Yours,  Mike.

Raymond Feng wrote:

+1 for the corresponding dependency upgrade.
I also suggest that you check in the changes as soon as most of the test cases are passing. We can add @Ignore("TUSCANY-xxxx") to failing test cases with JIRAs. This way, other people can help too. 

Thanks,
Raymond

From: Ramkumar R
Sent: Thursday, September 18, 2008 4:26 AM
To: [email protected]
Subject: Re: [DISCUSS] Migration to Axis2 1.4.1


Hi All,
As part of this migration from Axis2 1.3 to 1.4.1. Here are the list of dependency that needs an upgrade in Tuscany as recommended by Axis 1.4.1... 

org.apache.ws.commons.axiom - axiom-api - 1.2.5 to 1.2.7
org.apache.ws.commons.axiom - axiom-impl - 1.2.5 to 1.2.7
commons-logging - 1.1 to 1.1.1
commons.httpclient - 3.0.1 to 3.1
org.apache.neethi - neethi - 2.0.2 to 2.0.4
org.apache.ws.commons.schema - XmlSchema - 1.3 to 1.4.2
org.codehaus.woodstox - wstx-asl - 3.2.1 to 3.2.4
I believe, we can go ahead with upgrade of these dependencies where ever applicable in Tuscany modules. 
Please let me know if any one has concerns in doing so.
NOTE: As part of XmlSchema upgrade to 1.4.2, I faced few problems in Tuscany modules like xsd-xml and binding-ws-axis2 for the below reason. In XmlSchema 1.4.x, the schema collection can only have a single schema instance for a sysid+ns combination. 1.3.x used to not care and would create multiple schemas with the same id+ns.
Though in tuscany, I have not come across any multiple instance of the schema with the same sysid+ns combination in the same contribution. Here are few instance which had problems...
In xsd-xml module, as part of the junit test in XSDDocumentProcessorTestCase linenumber 80, this throws an error as we are trying to resolve the same schema instance more than once.
In databindings-jaxb-top-down itest fails, as the standard-types-service.wsdl file has 2 inline schema with the same namespace as shown below 
        <xs:schema targetNamespace="http://jaxb.dev.java.net/array";
           version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema";>

       </xs:schema>
       <xs:schema targetNamespace="http://jaxb.dev.java.net/array";
           version="1.0" xmlns:xs="http://www.w3.org/2001/XMLSchema";>
       </xs:schema>

Apart from the Schema errors, I am another strange issue as shown below...
testHelloWorld(org.apache.tuscany.sca.binding.ws.axis2.itests.policy.mixed.WSSecurityMixedTestCase) Time elapsed: 3.094 
sec  <<< ERROR!
org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.interfacedef.util.FaultException: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd : Security 
Sep 16, 2008 5:28:01 PM org.apache.tuscany.sca.node.impl.NodeImpl <init>
INFO: Creating node: org/apache/tuscany/sca/binding/ws/axis2/itests/soap12/questionmark-wsdl.composite at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:136) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154) 
       at $Proxy77.getGreetings(Unknown Source)
at org.apache.tuscany.sca.binding.ws.axis2.itests.HelloWorldOMComponent.getGreetings(HelloWorldOMComponent.java:=31) 
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
       at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:132) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:112) at org.apache.tuscany.sca.binding.sca.impl.SCABindingInvoker.invoke(SCABindingInvoker.java:61) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:112) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:154)
I am working on to resolve these issues, In the mean time if some one has some knowledge on these issue please share with me. Thanks. 



On Wed, Sep 17, 2008 at 2:40 PM, Ramkumar R <[EMAIL PROTECTED]> wrote:

Thanks All, I have opened a JIRA TUSCANY-2606 for the same.
On Tue, Sep 16, 2008 at 11:27 PM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: 

Ramkumar R wrote:

Hi All,
Tuscany currently uses Axis2 1.3.

How about migrating to Axis2 1.4.1 to take advantage of the latest changes?

Major Changes in Axis2 1.4 release:
- Support for JAXWS and JSR 181 Annotations (See 7 samples in the binary distribution) 
- Experimental CORBA Support
- Fixed tons of small and not-so-small bugs (See list in release-notes.html in the binary distribution)
Apache Axis2 1.4.1 fixes a security vulnerability present in Apache Axis2 1.4 policy processing. 

Please let me know your comments on the same. Thanks.

Reply via email to