Mailing-List: contact woden-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: woden-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of ryman@ca.ibm.com designates
 32.97.182.143 as permitted sender)
In-Reply-To: 
 <OFDDF4A08F.297AB051-ON80257185.004B1803-80257185.004D2515@uk.ibm.com>
To: woden-dev@ws.apache.org
Cc: axis-dev@ws.apache.org, woden-dev@ws.apache.org
Subject: Re: [axis2] woden/axis2 interop
MIME-Version: 1.0
From: Arthur Ryman <ryman@ca.ibm.com>
Message-ID: 
 <OFFA1A9511.969F16C3-ON85257185.00504280-85257185.00513645@ca.ibm.com>
Date: Tue, 6 Jun 2006 10:46:42 -0400
Content-Type: multipart/alternative;
 boundary="=_alternative 0051309985257185_="

--=_alternative 0051309985257185_=
Content-Type: text/plain; charset="US-ASCII"

Graham,

I haven't seen any results yet. We need to make some visible progress asap 
since the event in one month away.

We could start with generating clients for existing Axis2 Webservices, 
e.g.

Scenario 1

1. Create a simple Java class, e.g. echoString, and deploy it as an Axis2 
Web service and generate WSDL 1.1. The service can use SOAP 1.1.
2. Convert the WSDL 1.1 to WSDL 2.0 using the existing converter.
3. Generate a Java client from the WSDL 2.0 using the to-be-written 
WSDL2Java client proxy generator that uses WSDL 2.0.
4. Test the WSDL 2.0 based client agains the deployed service.
5. Validate the SOAP traffic using the WS-I Test Tools available at 
Eclipse. These tools understand WSDL 1.1 and SOAP 1.1 but that's OK since 
we have both a WSDL 1.1 and WSDL 2.0 description and are using SOAP 1.1.

Scenario 2

Same as scenario 1 except we generate a client from WSDL 1.1. and a 
service from the converted WSDL 2.0. This requires a to-be-writen 
WSDLtoJava server skeleton generator.


Arthur Ryman,
IBM Software Group, Rational Division

blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca


Graham Turrell <GTURRELL@uk.ibm.com> 
06/06/2006 10:02 AM
Please respond to
woden-dev@ws.apache.org


To
woden-dev@ws.apache.org, axis-dev@ws.apache.org
cc

Subject
[axis2] woden/axis2 interop


Hi folks,

Just wondering where we are in terms of development on the axis2 / woden
integration for the interop event, and what is there left to do?
I know that one or two contributors are already actively working on this.

I think that a good minimal demonstration for the interop event would be 
to
send a client request to an in-out axis2 service with a wsdl2.0
description,
ensure that the SOAP message is correctly interpreted and the appropriate
response message generated and dispatched.
(Deserialization is a TBD but from earlier discussion on the list doesnt
seem to be specifically needed for the interop demonstration)

To that end, I am keen to help on any aspect of the interop work 
(primarily
from the Woden side), such as architecture, code or test
creation/execution:
Where are the gaps (if any) and how can I help?

Kind Regards,

Graham.
_____________________________________________
Graham C Turrell CEng, MBCS
Chartered IT Practitioner

WebSphere ESB Foundation Technologies
DE3F16 / MP 211
IBM Labs
Hursley Park
Winchester, Hampshire
England.  SO21 2JN

Tel +44-(0)1962-815018
email: gturrell@uk.ibm.com

"No army can withstand the force of an idea whose time
has come.". -Victor Hugo


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


--=_alternative 0051309985257185_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Graham,</font>
<br>
<br><font size=2 face="sans-serif">I haven't seen any results yet. We need
to make some visible progress asap since the event in one month away.</font>
<br>
<br><font size=2 face="sans-serif">We could start with generating clients
for existing Axis2 Webservices, e.g.</font>
<br>
<br><font size=2 face="sans-serif">Scenario 1</font>
<br>
<br><font size=2 face="sans-serif">1. Create a simple Java class, e.g.
echoString, and deploy it as an Axis2 Web service and generate WSDL 1.1.
The service can use SOAP 1.1.</font>
<br><font size=2 face="sans-serif">2. Convert the WSDL 1.1 to WSDL 2.0
using the existing converter.</font>
<br><font size=2 face="sans-serif">3. Generate a Java client from the WSDL
2.0 using the to-be-written WSDL2Java client proxy generator that uses
WSDL 2.0.</font>
<br><font size=2 face="sans-serif">4. Test the WSDL 2.0 based client agains
the deployed service.</font>
<br><font size=2 face="sans-serif">5. Validate the SOAP traffic using the
WS-I Test Tools available at Eclipse. These tools understand WSDL 1.1 and
SOAP 1.1 but that's OK since we have both a WSDL 1.1 and WSDL 2.0 description
and are using SOAP 1.1.</font>
<br>
<br><font size=2 face="sans-serif">Scenario 2</font>
<br>
<br><font size=2 face="sans-serif">Same as scenario 1 except we generate
a client from WSDL 1.1. and a service from the converted WSDL 2.0. This
requires a to-be-writen WSDLtoJava server skeleton generator.</font>
<br>
<br>
<br><font size=2 face="sans-serif"><br>
Arthur Ryman,<br>
IBM Software Group, Rational Division<br>
<br>
blog: http://ryman.eclipsedevelopersjournal.com/<br>
phone: +1-905-413-3077, TL 969-3077<br>
assistant: +1-905-413-2411, TL 969-2411<br>
fax: +1-905-413-4920, TL 969-4920<br>
mobile: +1-416-939-5063, text: 4169395063@fido.ca</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Graham Turrell &lt;GTURRELL@uk.ibm.com&gt;</b>
</font>
<p><font size=1 face="sans-serif">06/06/2006 10:02 AM</font>
<table border>
<tr valign=top>
<td bgcolor=white>
<div align=center><font size=1 face="sans-serif">Please respond to<br>
woden-dev@ws.apache.org</font></div></table>
<br>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">woden-dev@ws.apache.org, axis-dev@ws.apache.org</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">[axis2] woden/axis2 interop</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>Hi folks,<br>
<br>
Just wondering where we are in terms of development on the axis2 / woden<br>
integration for the interop event, and what is there left to do?<br>
I know that one or two contributors are already actively working on this.<br>
<br>
I think that a good minimal demonstration for the interop event would be
to<br>
send a client request to an in-out axis2 service with a wsdl2.0<br>
description,<br>
ensure that the SOAP message is correctly interpreted and the appropriate<br>
response message generated and dispatched.<br>
(Deserialization is a TBD but from earlier discussion on the list doesnt<br>
seem to be specifically needed for the interop demonstration)<br>
<br>
To that end, I am keen to help on any aspect of the interop work (primarily<br>
from the Woden side), such as architecture, code or test<br>
creation/execution:<br>
Where are the gaps (if any) and how can I help?<br>
<br>
Kind Regards,<br>
<br>
Graham.<br>
_____________________________________________<br>
Graham C Turrell CEng, MBCS<br>
Chartered IT Practitioner<br>
<br>
WebSphere ESB Foundation Technologies<br>
DE3F16 / MP 211<br>
IBM Labs<br>
Hursley Park<br>
Winchester, Hampshire<br>
England. &nbsp;SO21 2JN<br>
<br>
Tel +44-(0)1962-815018<br>
email: gturrell@uk.ibm.com<br>
<br>
&quot;No army can withstand the force of an idea whose time<br>
has come.&quot;. -Victor Hugo<br>
<br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org<br>
For additional commands, e-mail: woden-dev-help@ws.apache.org<br>
<br>
</font></tt>
<br>
--=_alternative 0051309985257185_=--