1.1 planning

[Paul Fremantle <pz...@gmail.com>]

Time to make a 1.1 plan.

Plenty of good changes have been made, so I think its time to review
what needs to go into 1.1.

I notice we have made an API change (Ruwan I think added a return
value to injectMessage()). We should either figure out another way of
doing this (property), or bite the bullet and declare 1.1 mediators
incompatible with 1.0.

Personally I can see one good reason to break compatibility --- I
added the PayloadHelper class to Synapse, but I think that function
could be exposed directly in the MessageContext -
e.g.
getPayloadAsDOM() , getPayloadAsText(), etc.

I think that would make writing mediators a lot simpler for 80% of usecases.

What else do we need to think about before we cut a 1.1 release?

Paul

-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

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

Re: 1.1 planning

[Ruwan Linton <ru...@gmail.com>]

Paul,

Comments in line,

On 9/10/07, Paul Fremantle <pz...@gmail.com> wrote:
>
> Time to make a 1.1 plan.
>
> Plenty of good changes have been made, so I think its time to review
> what needs to go into 1.1.
>
> I notice we have made an API change (Ruwan I think added a return
> value to injectMessage()). We should either figure out another way of
> doing this (property), or bite the bullet and declare 1.1 mediators
> incompatible with 1.0.
>

I don't think this API change will effect most of the mediators, unless
otherwise a particular mediator digs very deep in to the internals of
Synapse and uses the injectMessage API. (There is no single mediator that is
working in the current head which does not work on 1.0 release)

Personally I can see one good reason to break compatibility --- I
> added the PayloadHelper class to Synapse, but I think that function
> could be exposed directly in the MessageContext -
> e.g.
> getPayloadAsDOM() , getPayloadAsText(), etc.


+1 for this.

I think that would make writing mediators a lot simpler for 80% of usecases.
>
> What else do we need to think about before we cut a 1.1 release?


I think we need to fix the Security and Reliable Messaging functionality. I
think they were broken on the svn head due to the axis2 1.3 migration. (Need
to wait till Sandesha2 1.3)

Thanks,
Ruwan

Paul
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> paul@wso2.com
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>


-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

Re: 1.1 planning

[Ruwan Linton <ru...@gmail.com>]

Ant,

1.0 mediators will not have any problem running on the 1.1 release for
sure....

Thanks,
Ruwan

On 9/10/07, ant elder <an...@gmail.com> wrote:
>
>
>
> On 9/10/07, Paul Fremantle <pzfreo@gmail.com > wrote:
> >
> > Time to make a 1.1 plan.
> >
> > Plenty of good changes have been made, so I think its time to review
> > what needs to go into 1.1.
> >
> > I notice we have made an API change (Ruwan I think added a return
> > value to injectMessage()). We should either figure out another way of
> > doing this (property), or bite the bullet and declare 1.1 mediators
> > incompatible with 1.0.
> >
> > Personally I can see one good reason to break compatibility --- I
> > added the PayloadHelper class to Synapse, but I think that function
> > could be exposed directly in the MessageContext -
> > e.g.
> > getPayloadAsDOM() , getPayloadAsText(), etc.
> >
> > I think that would make writing mediators a lot simpler for 80% of
> > usecases.
> >
> > What else do we need to think about before we cut a 1.1 release?
> >
> > Paul
>
>
> I'd still like to try to get something going with the Synapse-Tuscany
> integration, no time right now as I'm 100% on getting a Tuscany 1.0 out,
> but after then may have time to get at least prototype support of that for
> Synapse 1.1.
>
> +1 to trying really hard to make 1.0 mediator impls compatible with 1.1.
>
>    ...ant
>
>
>


-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

Re: 1.1 planning

[ant elder <an...@gmail.com>]

On 9/10/07, Paul Fremantle <pz...@gmail.com> wrote:
>
> Time to make a 1.1 plan.
>
> Plenty of good changes have been made, so I think its time to review
> what needs to go into 1.1.
>
> I notice we have made an API change (Ruwan I think added a return
> value to injectMessage()). We should either figure out another way of
> doing this (property), or bite the bullet and declare 1.1 mediators
> incompatible with 1.0.
>
> Personally I can see one good reason to break compatibility --- I
> added the PayloadHelper class to Synapse, but I think that function
> could be exposed directly in the MessageContext -
> e.g.
> getPayloadAsDOM() , getPayloadAsText(), etc.
>
> I think that would make writing mediators a lot simpler for 80% of
> usecases.
>
> What else do we need to think about before we cut a 1.1 release?
>
> Paul


I'd still like to try to get something going with the Synapse-Tuscany
integration, no time right now as I'm 100% on getting a Tuscany 1.0 out, but
after then may have time to get at least prototype support of that for
Synapse 1.1.

+1 to trying really hard to make 1.0 mediator impls compatible with 1.1.

   ...ant