Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of chathurah@gmail.com designates
 66.249.92.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=PUfvqbd1kH/wmBZWJRjGLKMNm5XyINpwHQGMbhqHas1NopzRHpnVgTNrL+R+HPw1ZjvIDi8Wgx4vwH4dIs+8Xyv+jAdRzgGj9gIrPGmjHWAdQcfctJOov2FNIJV+P11Q0ZUAq7L7tW3ej5eA9ng9t4WQKxeiAujWa0Jts842KiM=
Message-ID: <3ce57c850606062037u7e220e21y6b9b79880823e4ce@mail.gmail.com>
Date: Tue, 6 Jun 2006 22:37:03 -0500
From: "Chathura Herath" <chathurah@gmail.com>
To: axis-dev@ws.apache.org, woden-dev@ws.apache.org, dims@apache.org
Subject: Re: [axis2] woden/axis2 interop
In-Reply-To: <19e0530f0606061647m1cc45cb3h67b2d20962531198@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: 
 <OFDDF4A08F.297AB051-ON80257185.004B1803-80257185.004D2515@uk.ibm.com>
	 <OFFA1A9511.969F16C3-ON85257185.00504280-85257185.00513645@ca.ibm.com>
	 <4c2ae8f80606060941w58cd0d0di6cba8b5a3e21dc56@mail.gmail.com>
	 <a477174c0606061533m1777bf6cy636b839a3a0a8b7a@mail.gmail.com>
	 <19e0530f0606061647m1cc45cb3h67b2d20962531198@mail.gmail.com>

Hi,

So here is where we stand. Basic skeleton of the integration is
there.I called it skeleton because it need to handle the rpc case and
not so urgent but eventually need to handle the policy stuff. you can
run WSDL2Jave with -wv 2 which will engage the woden. It will not
codegen successfully, there is a schema compilation issue and have to
fix it. I am concentrating on the xmlbeans databinding right now.

The two Scenarios given above are the classic interop test and would
be great to have. My guess is within two weeks we should be able to
get the run time up and them we could see how the clients and servers
generated with the isomorphic but two WSDL versions would interop. So
i would say we will be able to have at least one interop scenario for
the interop.

John you could see the WSDL20ToAxisServiceBuilder which is the center
of the integration work.
Oshini please send your patches often and do have a look at the latest
code. I should commit more often cos you are working on it as well. I
have changed it to work with the component model, i belive you
followed that thread.
Thanks
Chathura


On 6/6/06, Davanum Srinivas <davanum@gmail.com> wrote:
> Oshani,
>
> can you please open a JIRA issue and keep uploading diff's as you progress?
>
> thanks,
> dims
>
> On 6/6/06, Oshani Seneviratne <oshanis@gmail.com> wrote:
> > Hi,
> >
> > With the help of the core Axis2 dev team, I'm also in the process of
> > implementing the Axis2/Woden integration. At the moment, my efforts are on
> > populating the AxisService once a WSDL2.0 is bundled in a service archive
> > file and deployed on Axis2.
> >
> >
> > >
> > > There's a class called WSDL20ToAxisServiceBuilder in Axis2. I haven't
> > looked at it yet, but is this the 'layer' between Woden and Axis2?
> >
> >
> > AFAIK, yes. And I am using this class to populate the AxisService from the
> > Woden components.
> >
> > Hopefully I should be able to finish this by July 5th, so that the scenarios
> > mentioned earlier can be tested with Axis2.
> >
> > Oshani
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>


-- 
Chathura Herath
http://people.apache.org/~chathura/
http://chathurah.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org