On Feb 13, 2006, at 10:14 PM, Jeremy Boynes wrote:
ant elder wrote:
I'm all for more explanations of whats going on with the contexts
so go for
it.
Jim, I think more explanation here would be useful, especially on how
the binding and wiring framework can be extended. If you can provide
information on the essential interfaces and integration points,
perhaps
that would be a good starting point that would allow Ant and others to
start work on integrating Axis2.
Yes, will do.
What are you proposing though - converting the existing Axis1
based WS
binding to the new contexts first? I'm fine with that if it
doesn't take to
long, can I help or is this something you and Jeremy need to do?
I'd really
would like to get started on the Axis 2 work soon though.
My first reaction would be to forget about the existing Axis1
implementation, look at the interfaces Jim has to the wiring/binding
infrastructure and start implementing them with Axis2.
Agree on "forgetting" about Axis1 and moving straight to Axis 2
I think starting as you suggested with support for external services
using the Axis2 client model would be the easier way to get going.
--
Jeremy
...ant
On 2/13/06, Jim Marino <[EMAIL PROTECTED]> wrote:
I think we should begin with the changes to the contexts that Jeremy
and myself are working on; otherwise, we risk having to redo this
shortly. I propose we explain the changes better and agree on API
with those interested in working on the integration so that work and
the changes can be done in parallel. How does this sound?
Jim
On Feb 13, 2006, at 4:24 AM, ant elder wrote:
I'd like to start on the migration from Axis 1 to Axis2 now so I'm
wondering
whats the best way to do it. The current WS binding is in
binding.axis so I
guess i need a new binding.axis2, and as there's some others who've
expressed interest in helping it would be good if that could go
in the
Tuscany sandbox or trunk. The easiest approach seems to me to be
copy all
the existing binding.axis code to binding.axis2 and then change
everything
that uses Axis to use Axis2, and probably starting with the
externalService
code, and once thats going do the entryPoint code. I know this
doesn't
include all the context and sdo and other changes which are going
on or
being proposed, but its not real clear what all those require so it
seems
easiest to stick with whats already there for now. How does all
this sound?
...ant
