Ant
This seems fine.. I guess you will work on the required modifications
for this.
asankha
ant elder wrote:
I'm not looking to be able to use alternative impls so I
its fine for Synapse to be tightly bound with Axis2. I'm just looking
for a Synapse method to create a new MessageContext for me, the thing
it returned would still be an o.a.synapse.axis2.Axis2MessageContext.
Its no biggie if no one likes it on the SynapseEnvironment i'll just
keep it in my own code, just seemed a bit cleaner that way.
Your other question about how Tuscany sends messages, if Tuscany had a
Synapse binding then Synapse would do it. Tuscany would create a new
Synpase messageContext (hopefully with
SynapseEnvironment.createMessageContext :) ), set the soap body payload
and then call SynapseEnvironment.injectMessage and Synapse would run
the configured mediators and send the message.
...ant
On 11/8/06, Asankha C. Perera <[EMAIL PROTECTED]> wrote:
Ant
I think Synapse is right now quite tightly bound in with Axis2,
especially on sending the messages out.. I am not much familiar with
Tuscany, but how does it handle sending messages?
asankha
ant elder wrote:
> I've been having a look at how to use Synapse in another project
> (Tuscany) and I think there could be some changes to make doing
this
> easier.
>
> One problem is Synapse doesn't provide any way to easily create a
new
> Synapse MessageContext as currently it assumes request come from
the
> Axis2 MessageReceiver and therefore have an existing Axis2
> MessageContext. I could just new one of these up, get it
initialized
> correctly and then use the classes in the o.a.synapse.core.axis2
> package to create a Synapse MessageContext but that doesn't seem
> right. How about adding a createMessageContext() method to the
> SynapseEnvironment interface so Synapse embedders don't need to
mess
> with the Axis2 internals of Synapse?
>
> ...ant
>
> PS. Anyone interested in helping with a Tuscany WS binding based
on
> Synapse?
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
|
