Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (herse.apache.org: domain of davanum@gmail.com designates
 66.249.92.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=ovxRqJm6n2LU4ubbofji2PPDjJOKfMOPjaJ/UGwdwuNsc4I5AqMQwWbyxCJRaDQaIGgOWyzB9EDhlg5OMWxynGGbfagibK1WgEbbPc9qu/agJ+SZDClhqdJR9hVWQeu5njuKyxU6p1Th+2q6fHBJHGtcEW2x3RruXwbwqR59ITM=
Message-ID: <19e0530f0703061235q7ecc9b73if5a3589e43709945@mail.gmail.com>
Date: Tue, 6 Mar 2007 15:35:26 -0500
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: dev@geronimo.apache.org
Subject: Re: SAAJ integration help
In-Reply-To: <5eb405c70703061113h919107cte2be5e6adf3b98c1@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <5eb405c70703061113h919107cte2be5e6adf3b98c1@mail.gmail.com>

Axis1 will not work with an external SAAJ implementation or API. Not
sure if we can update the API in Axis1 because then it will fail the
jax-rpc signature tests.

thanks,
dims

On 3/6/07, Jarek Gawor <jgawor@gmail.com> wrote:
> I started looking into SAAJ integration. And that appears to be a much
> more work than I initially thought. Here's the background info. In
> Java EE 5 we have to support both JAX-RPC and JAX-WS web services
> (both might be deployed in the same module). Right now JAX-RPC support
> is provided by Axis1 and JAX-WS support is provided by either Axis2 or
> CXF. Both JAX-RPC and JAX-WS endpoints must support SAAJ.  Both Axis1
> and Axis2 have their own implementations of the SAAJ API. Axis1
> implements SAAJ 1.1/1.2 and Axis2 implements SAAJ 1.3. CXF uses
> Glassfish 1.3 implementation.
> My initial idea was to use Axis2 SAAJ for Axis2/Axis1 assembly and
> Glassfish SAAJ for CXF/Axis1 assembly. However, I'm not sure what
> would be the effects on Axis1 when Axis2 or Glassfish SAAJ
> implementation is used because I think Axis1 expects its own SAAJ
> implementation. So things might just blow up in this case.  I also
> assume that we will need to update Axis1 code to implement the SAAJ
> 1.3 API (e.g. to throw OperationUnsupportedException(), etc.)
>
> Assuming things do blow up what are our options for supporting two
> different SAAJ implementations? Or do we need one common SAAJ
> implementation?
>
> I have an idea how maybe we can support two different SAAJ
> implementations by setting a context classloader to force a given
> implementation to be used but I'm not sure how reliable it will be.
>
> Jarek
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers