You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Paul Fremantle <pz...@gmail.com> on 2006/10/04 10:28:40 UTC
Release plan for 0.90
Guys
I'm just setting up a release plan for 0.90.
We have two choices -
1) release soonish with the asyncweb transport (async server only)
2) wait until Asankha has completed the NIO Axis2 transport (async
server and client)
My preference is to try and stabilize what we have today into a
release and then push out another with the NIO Axis2 transport
afterwards.
My reason is that I think the Axis2 NIO will need lots of testing -
and will probably end up taking longer to complete than we think -
getting full HTTP1.1 support for example. So if the AsyncWeb stuff is
working then we can stabilize all the other good stuff we have put in
and get feedback on it.
For those of you who haven't followed what the async handling is
doing, basically its getting rid of the thread blocks while Synapse is
waiting for a response - even when the HTTP transport is
synchronous/anonymous. The Asyncweb model isn't using an Async sender,
so extra threads are being created and blocking if we are sending to
an async transport.
Thoughts?
Paul
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
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: Release plan for 0.90
Posted by Paul Fremantle <pz...@gmail.com>.
In that case I suggest we hold off doing 0.90 until we have a NIO
solution that doesn't prereq 1.5.
I'm happy to do that - it will push 0.90 out a little, but if 1.4
support is important then lets do that.
Paul
On 10/6/06, Davanum Srinivas <da...@gmail.com> wrote:
> yes please keep 1.4 support.
>
> -- dims
>
> On 10/6/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> > On Wed, 2006-10-04 at 09:37 +0100, Paul Fremantle wrote:
> > > Asankha
> > >
> > > Thanks for letting me know.
> > >
> > > Any objections to a prereq on 1.5? I know I moved to it a while ago.
> >
> > If its a 0.90 situation I'm ok but I'd rather not take a 1.5 prereq yet.
> > Axis2 for example supports 1.4 .. so as long as that's true I'd prefer
> > if we stay at the same level.
> >
> > Sanjiva.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: synapse-dev-help@ws.apache.org
> >
> >
>
>
> --
> Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
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: Release plan for 0.90
Posted by Davanum Srinivas <da...@gmail.com>.
yes please keep 1.4 support.
-- dims
On 10/6/06, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> On Wed, 2006-10-04 at 09:37 +0100, Paul Fremantle wrote:
> > Asankha
> >
> > Thanks for letting me know.
> >
> > Any objections to a prereq on 1.5? I know I moved to it a while ago.
>
> If its a 0.90 situation I'm ok but I'd rather not take a 1.5 prereq yet.
> Axis2 for example supports 1.4 .. so as long as that's true I'd prefer
> if we stay at the same level.
>
> Sanjiva.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Davanum Srinivas : http://www.wso2.net (Oxygen for Web Service Developers)
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Release plan for 0.90
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
On Wed, 2006-10-04 at 09:37 +0100, Paul Fremantle wrote:
> Asankha
>
> Thanks for letting me know.
>
> Any objections to a prereq on 1.5? I know I moved to it a while ago.
If its a 0.90 situation I'm ok but I'd rather not take a 1.5 prereq yet.
Axis2 for example supports 1.4 .. so as long as that's true I'd prefer
if we stay at the same level.
Sanjiva.
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Release plan for 0.90
Posted by Paul Fremantle <pz...@gmail.com>.
Asankha
Thanks for letting me know.
Any objections to a prereq on 1.5? I know I moved to it a while ago.
Paul
On 10/4/06, Asankha C. Perera <as...@wso2.com> wrote:
> Paul
>
> FYI - We currently have a runtime limitation to JDK 1.5 because of the
> use of AsyncWeb.
>
> asankha
>
>
> Paul Fremantle wrote:
> > Guys
> >
> > I'm just setting up a release plan for 0.90.
> >
> > We have two choices -
> >
> > 1) release soonish with the asyncweb transport (async server only)
> > 2) wait until Asankha has completed the NIO Axis2 transport (async
> > server and client)
> >
> > My preference is to try and stabilize what we have today into a
> > release and then push out another with the NIO Axis2 transport
> > afterwards.
> >
> > My reason is that I think the Axis2 NIO will need lots of testing -
> > and will probably end up taking longer to complete than we think -
> > getting full HTTP1.1 support for example. So if the AsyncWeb stuff is
> > working then we can stabilize all the other good stuff we have put in
> > and get feedback on it.
> >
> > For those of you who haven't followed what the async handling is
> > doing, basically its getting rid of the thread blocks while Synapse is
> > waiting for a response - even when the HTTP transport is
> > synchronous/anonymous. The Asyncweb model isn't using an Async sender,
> > so extra threads are being created and blocking if we are sending to
> > an async transport.
> >
> > Thoughts?
> >
> > Paul
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
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: Release plan for 0.90
Posted by "Asankha C. Perera" <as...@wso2.com>.
Paul
FYI - We currently have a runtime limitation to JDK 1.5 because of the
use of AsyncWeb.
asankha
Paul Fremantle wrote:
> Guys
>
> I'm just setting up a release plan for 0.90.
>
> We have two choices -
>
> 1) release soonish with the asyncweb transport (async server only)
> 2) wait until Asankha has completed the NIO Axis2 transport (async
> server and client)
>
> My preference is to try and stabilize what we have today into a
> release and then push out another with the NIO Axis2 transport
> afterwards.
>
> My reason is that I think the Axis2 NIO will need lots of testing -
> and will probably end up taking longer to complete than we think -
> getting full HTTP1.1 support for example. So if the AsyncWeb stuff is
> working then we can stabilize all the other good stuff we have put in
> and get feedback on it.
>
> For those of you who haven't followed what the async handling is
> doing, basically its getting rid of the thread blocks while Synapse is
> waiting for a response - even when the HTTP transport is
> synchronous/anonymous. The Asyncweb model isn't using an Async sender,
> so extra threads are being created and blocking if we are sending to
> an async transport.
>
> Thoughts?
>
> Paul
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Release plan for 0.90
Posted by "Asankha C. Perera" <as...@wso2.com>.
Paul
Yes, we need to spend more time on this, as this is almost the same
example used in the Axis2 Integration test scenario 3 - which works
during an Axis2 build.
The error we encounter at Axis2 is:
java.lang.NullPointerException
at
org.apache.axiom.om.impl.dom.ChildNode.getNextOMSibling(ChildNode.java:45)
at
org.apache.axiom.om.impl.dom.ElementImpl.getNextOMSibling(ElementImpl.java:1355)
at
org.apache.axiom.om.impl.dom.ChildNode.getNextSibling(ChildNode.java:52)
at
org.apache.ws.security.util.WSSecurityUtil.findElementById(WSSecurityUtil.java:299)
at
org.apache.ws.security.util.WSSecurityUtil.getElementByWsuId(WSSecurityUtil.java:439)
at
org.apache.ws.security.message.token.SecurityTokenReference.getTokenElement(SecurityTokenReference.java:176)
at
org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:186)
at
org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:79)
at
org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:279)
at
org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:201)
at org.apache.rampart.RampartEngine.process(RampartEngine.java:62)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:74)
....
And on the Synapse side, we encounter issue
http://issues.apache.org/jira/browse/WSCOMMONS-104 (Caused due to use of
Rampart) while trying to process the above fault message.
thanks
asankha
Paul Fremantle wrote:
> Asankha
>
> With the Signing/Enc am I right in understanding that the target
> service (Axis2) can't understand the messages that Synapse is
> creating?
>
> Paul
>
> Seems like a simple issue (104). Can we get a timeline?
>
>
> On 10/4/06, Asankha C. Perera <as...@wso2.com> wrote:
>> Paul
>>
>> I have just checked in the changes for the new Policy framework with two
>> sample services which could be deployed on an Axis2 instance and a
>> sample Synapse configuration to demonstrate this. Though the first
>> example works, the second example which demonstrates signing and
>> encryption fails on the Axis2 server side currently due to an issue I
>> couldn't figure out yet with help from Ruchith. But it seems like its
>> not on Synapse side, and hence I'm checking in these changes. Also when
>> Rampart is being used, we are hit by
>> http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents
>> Synapse from reading a SOAP fault in an incoming fault message. This
>> again is out of our scope, and should work once Axiom is fixed - though
>> this may take some time.
>>
>> asankha
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Release plan for 0.90
Posted by "Asankha C. Perera" <as...@wso2.com>.
Paul
Yes, we need to spend more time on this, as this is almost the same
example used in the Axis2 Integration test scenario 3 - which works
during an Axis2 build.
The error we encounter at Axis2 is:
java.lang.NullPointerException
at
org.apache.axiom.om.impl.dom.ChildNode.getNextOMSibling(ChildNode.java:45)
at
org.apache.axiom.om.impl.dom.ElementImpl.getNextOMSibling(ElementImpl.java:1355)
at
org.apache.axiom.om.impl.dom.ChildNode.getNextSibling(ChildNode.java:52)
at
org.apache.ws.security.util.WSSecurityUtil.findElementById(WSSecurityUtil.java:299)
at
org.apache.ws.security.util.WSSecurityUtil.getElementByWsuId(WSSecurityUtil.java:439)
at
org.apache.ws.security.message.token.SecurityTokenReference.getTokenElement(SecurityTokenReference.java:176)
at
org.apache.ws.security.processor.SignatureProcessor.verifyXMLSignature(SignatureProcessor.java:186)
at
org.apache.ws.security.processor.SignatureProcessor.handleToken(SignatureProcessor.java:79)
at
org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:279)
at
org.apache.ws.security.WSSecurityEngine.processSecurityHeader(WSSecurityEngine.java:201)
at org.apache.rampart.RampartEngine.process(RampartEngine.java:62)
at
org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:74)
....
And on the Synapse side, we encounter issue
http://issues.apache.org/jira/browse/WSCOMMONS-104 (Caused due to use of
Rampart) while trying to process the above fault message.
thanks
asankha
Paul Fremantle wrote:
> Asankha
>
> With the Signing/Enc am I right in understanding that the target
> service (Axis2) can't understand the messages that Synapse is
> creating?
>
> Paul
>
> Seems like a simple issue (104). Can we get a timeline?
>
>
> On 10/4/06, Asankha C. Perera <as...@wso2.com> wrote:
>> Paul
>>
>> I have just checked in the changes for the new Policy framework with two
>> sample services which could be deployed on an Axis2 instance and a
>> sample Synapse configuration to demonstrate this. Though the first
>> example works, the second example which demonstrates signing and
>> encryption fails on the Axis2 server side currently due to an issue I
>> couldn't figure out yet with help from Ruchith. But it seems like its
>> not on Synapse side, and hence I'm checking in these changes. Also when
>> Rampart is being used, we are hit by
>> http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents
>> Synapse from reading a SOAP fault in an incoming fault message. This
>> again is out of our scope, and should work once Axiom is fixed - though
>> this may take some time.
>>
>> asankha
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Release plan for 0.90
Posted by Paul Fremantle <pz...@gmail.com>.
Asankha
With the Signing/Enc am I right in understanding that the target
service (Axis2) can't understand the messages that Synapse is
creating?
Paul
Seems like a simple issue (104). Can we get a timeline?
On 10/4/06, Asankha C. Perera <as...@wso2.com> wrote:
> Paul
>
> I have just checked in the changes for the new Policy framework with two
> sample services which could be deployed on an Axis2 instance and a
> sample Synapse configuration to demonstrate this. Though the first
> example works, the second example which demonstrates signing and
> encryption fails on the Axis2 server side currently due to an issue I
> couldn't figure out yet with help from Ruchith. But it seems like its
> not on Synapse side, and hence I'm checking in these changes. Also when
> Rampart is being used, we are hit by
> http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents
> Synapse from reading a SOAP fault in an incoming fault message. This
> again is out of our scope, and should work once Axiom is fixed - though
> this may take some time.
>
> asankha
>
> Asankha C. Perera wrote:
> > Paul
> >
> > I'm overall +1 to your plan to release 0.90 now, and I have updated
> > Synapse to be in sync with the recent changes to Policy/neethi. I will
> > check this in ASAP with a few more tests. Then I will work on the
> > documents and prepare for this.
> >
> > asankha
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
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: Release plan for 0.90
Posted by Paul Fremantle <pz...@gmail.com>.
Asankha
With the Signing/Enc am I right in understanding that the target
service (Axis2) can't understand the messages that Synapse is
creating?
Paul
Seems like a simple issue (104). Can we get a timeline?
On 10/4/06, Asankha C. Perera <as...@wso2.com> wrote:
> Paul
>
> I have just checked in the changes for the new Policy framework with two
> sample services which could be deployed on an Axis2 instance and a
> sample Synapse configuration to demonstrate this. Though the first
> example works, the second example which demonstrates signing and
> encryption fails on the Axis2 server side currently due to an issue I
> couldn't figure out yet with help from Ruchith. But it seems like its
> not on Synapse side, and hence I'm checking in these changes. Also when
> Rampart is being used, we are hit by
> http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents
> Synapse from reading a SOAP fault in an incoming fault message. This
> again is out of our scope, and should work once Axiom is fixed - though
> this may take some time.
>
> asankha
>
> Asankha C. Perera wrote:
> > Paul
> >
> > I'm overall +1 to your plan to release 0.90 now, and I have updated
> > Synapse to be in sync with the recent changes to Policy/neethi. I will
> > check this in ASAP with a few more tests. Then I will work on the
> > documents and prepare for this.
> >
> > asankha
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
--
Paul Fremantle
VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
http://bloglines.com/blog/paulfremantle
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Release plan for 0.90
Posted by "Asankha C. Perera" <as...@wso2.com>.
Paul
I have just checked in the changes for the new Policy framework with two
sample services which could be deployed on an Axis2 instance and a
sample Synapse configuration to demonstrate this. Though the first
example works, the second example which demonstrates signing and
encryption fails on the Axis2 server side currently due to an issue I
couldn't figure out yet with help from Ruchith. But it seems like its
not on Synapse side, and hence I'm checking in these changes. Also when
Rampart is being used, we are hit by
http://issues.apache.org/jira/browse/WSCOMMONS-104 which prevents
Synapse from reading a SOAP fault in an incoming fault message. This
again is out of our scope, and should work once Axiom is fixed - though
this may take some time.
asankha
Asankha C. Perera wrote:
> Paul
>
> I'm overall +1 to your plan to release 0.90 now, and I have updated
> Synapse to be in sync with the recent changes to Policy/neethi. I will
> check this in ASAP with a few more tests. Then I will work on the
> documents and prepare for this.
>
> asankha
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org
Re: Release plan for 0.90
Posted by ant elder <an...@gmail.com>.
I'm also +1 to 0.90 now.
I'm also fine with the JDK1.5 prereq but wonder if that should be brought
out into another thread so its clear to anyone who may be not reading every
mail...I'll do that now.
...ant
On 10/4/06, Asankha C. Perera <as...@wso2.com> wrote:
>
> Paul
>
> I'm overall +1 to your plan to release 0.90 now, and I have updated
> Synapse to be in sync with the recent changes to Policy/neethi. I will
> check this in ASAP with a few more tests. Then I will work on the
> documents and prepare for this.
>
> asankha
>
> Paul Fremantle wrote:
> > Guys
> >
> > I'm just setting up a release plan for 0.90.
> >
> > We have two choices -
> >
> > 1) release soonish with the asyncweb transport (async server only)
> > 2) wait until Asankha has completed the NIO Axis2 transport (async
> > server and client)
> >
> > My preference is to try and stabilize what we have today into a
> > release and then push out another with the NIO Axis2 transport
> > afterwards.
> >
> > My reason is that I think the Axis2 NIO will need lots of testing -
> > and will probably end up taking longer to complete than we think -
> > getting full HTTP1.1 support for example. So if the AsyncWeb stuff is
> > working then we can stabilize all the other good stuff we have put in
> > and get feedback on it.
> >
> > For those of you who haven't followed what the async handling is
> > doing, basically its getting rid of the thread blocks while Synapse is
> > waiting for a response - even when the HTTP transport is
> > synchronous/anonymous. The Asyncweb model isn't using an Async sender,
> > so extra threads are being created and blocking if we are sending to
> > an async transport.
> >
> > Thoughts?
> >
> > Paul
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: synapse-dev-help@ws.apache.org
>
>
Re: Release plan for 0.90
Posted by "Asankha C. Perera" <as...@wso2.com>.
Paul
I'm overall +1 to your plan to release 0.90 now, and I have updated
Synapse to be in sync with the recent changes to Policy/neethi. I will
check this in ASAP with a few more tests. Then I will work on the
documents and prepare for this.
asankha
Paul Fremantle wrote:
> Guys
>
> I'm just setting up a release plan for 0.90.
>
> We have two choices -
>
> 1) release soonish with the asyncweb transport (async server only)
> 2) wait until Asankha has completed the NIO Axis2 transport (async
> server and client)
>
> My preference is to try and stabilize what we have today into a
> release and then push out another with the NIO Axis2 transport
> afterwards.
>
> My reason is that I think the Axis2 NIO will need lots of testing -
> and will probably end up taking longer to complete than we think -
> getting full HTTP1.1 support for example. So if the AsyncWeb stuff is
> working then we can stabilize all the other good stuff we have put in
> and get feedback on it.
>
> For those of you who haven't followed what the async handling is
> doing, basically its getting rid of the thread blocks while Synapse is
> waiting for a response - even when the HTTP transport is
> synchronous/anonymous. The Asyncweb model isn't using an Async sender,
> so extra threads are being created and blocking if we are sending to
> an async transport.
>
> Thoughts?
>
> Paul
>
---------------------------------------------------------------------
To unsubscribe, e-mail: synapse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: synapse-dev-help@ws.apache.org