You are viewing a plain text version of this content. The canonical link for it is here.
Posted to sandesha-dev@ws.apache.org by "Matt Lovett (JIRA)" <ji...@apache.org> on 2006/09/05 17:02:24 UTC
[jira] Updated: (SANDESHA2-24) Update Sandesha2 to OASIS WS-RM 1.1
Public Review specification
[ http://issues.apache.org/jira/browse/SANDESHA2-24?page=all ]
Matt Lovett updated SANDESHA2-24:
---------------------------------
Attachment: version.patch
Patch that moves the code up to the new namespace
> Update Sandesha2 to OASIS WS-RM 1.1 Public Review specification
> ---------------------------------------------------------------
>
> Key: SANDESHA2-24
> URL: http://issues.apache.org/jira/browse/SANDESHA2-24
> Project: Apache Sandesha2
> Issue Type: Improvement
> Reporter: Matt Lovett
> Priority: Minor
> Attachments: version.patch
>
>
> This patch starts to move the WS-RM 1.1 support in Sandesha2 Java up to the Public Review specification recently published by the OASIS WS-RX Tech Committee. I suggest that we do the work in 2 main stages: bring the namespace up to date, and then implement the new makeConnection operation.
> I'll attach a patch that does the first part shortly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [jira] Updated: (SANDESHA2-24) Update Sandesha2 to OASIS WS-RM 1.1
Public Review specification
Posted by Matthew Lovett <ML...@uk.ibm.com>.
Hi Chamikara,
I've added in a patch to cover the new UsesSequenceSTR element, which
should enable composition with WS-Security (provided you have a
SecurityManager impl).
The next missing piece is composition with SSL (and the UsesSequenceSSL
header). To do that I'll extend the security manager class... I should be
able to get to that in a day or two.
It's good to hear that you are looking at makeConnection :) I'd hope it
isn't too tricky... one way I imagined doing it would be to continue
queueing messages in for the Sender thread in exactly the same way, but
make the Sender smart enough to not attempt transmission of a message that
does not have a 'real' to address. Then for an inbound makeConnection
(either Sequence type, or URI type) all you need to do is search the queue
for a candidate that is due for delivery. This has the neat side-effect
that the re-delivery timers etc all work in the same way too. In
particular, 3 rapid makeConnection attempts might get 3 different
application messages, which could then be acked with a single ack message.
Another nice side-effect is that you can issue a makeConnection for any
sequence, including those that would normally send messages
asynchronously.
Cheers,
Matt
"Chamikara Jayalath" <ch...@gmail.com> wrote on 06/09/2006 03:39:02:
> Hi Matt,
>
> Thanks for the patch.
>
> I'm halfway through in implementing the MakeConnection support. I'll
> commit it soon. Is it possible for you to look into the new Security
> aspects, on which you submitted a patch recently.
>
> Chamikara
>
> On 9/5/06, Matt Lovett (JIRA) <ji...@apache.org> wrote:
> [ http://issues.apache.org/jira/browse/SANDESHA2-24?page=all ]
>
> Matt Lovett updated SANDESHA2-24:
> ---------------------------------
>
> Attachment: version.patch
>
> Patch that moves the code up to the new namespace
>
> > Update Sandesha2 to OASIS WS-RM 1.1 Public Review specification
> > ---------------------------------------------------------------
> >
> > Key: SANDESHA2-24
> > URL: http://issues.apache.org/jira/browse/SANDESHA2-24
> > Project: Apache Sandesha2
> > Issue Type: Improvement
> > Reporter: Matt Lovett
> > Priority: Minor
> > Attachments: version.patch
> >
> >
> > This patch starts to move the WS-RM 1.1 support in Sandesha2 Java
> up to the Public Review specification recently published by the
> OASIS WS-RX Tech Committee. I suggest that we do the work in 2 main
> stages: bring the namespace up to date, and then implement the new
> makeConnection operation.
> > I'll attach a patch that does the first part shortly.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [jira] Updated: (SANDESHA2-24) Update Sandesha2 to OASIS WS-RM 1.1
Public Review specification
Posted by Matthew Lovett <ML...@uk.ibm.com>.
Hi Chamikara,
I've added in a patch to cover the new UsesSequenceSTR element, which
should enable composition with WS-Security (provided you have a
SecurityManager impl).
The next missing piece is composition with SSL (and the UsesSequenceSSL
header). To do that I'll extend the security manager class... I should be
able to get to that in a day or two.
It's good to hear that you are looking at makeConnection :) I'd hope it
isn't too tricky... one way I imagined doing it would be to continue
queueing messages in for the Sender thread in exactly the same way, but
make the Sender smart enough to not attempt transmission of a message that
does not have a 'real' to address. Then for an inbound makeConnection
(either Sequence type, or URI type) all you need to do is search the queue
for a candidate that is due for delivery. This has the neat side-effect
that the re-delivery timers etc all work in the same way too. In
particular, 3 rapid makeConnection attempts might get 3 different
application messages, which could then be acked with a single ack message.
Another nice side-effect is that you can issue a makeConnection for any
sequence, including those that would normally send messages
asynchronously.
Cheers,
Matt
"Chamikara Jayalath" <ch...@gmail.com> wrote on 06/09/2006 03:39:02:
> Hi Matt,
>
> Thanks for the patch.
>
> I'm halfway through in implementing the MakeConnection support. I'll
> commit it soon. Is it possible for you to look into the new Security
> aspects, on which you submitted a patch recently.
>
> Chamikara
>
> On 9/5/06, Matt Lovett (JIRA) <ji...@apache.org> wrote:
> [ http://issues.apache.org/jira/browse/SANDESHA2-24?page=all ]
>
> Matt Lovett updated SANDESHA2-24:
> ---------------------------------
>
> Attachment: version.patch
>
> Patch that moves the code up to the new namespace
>
> > Update Sandesha2 to OASIS WS-RM 1.1 Public Review specification
> > ---------------------------------------------------------------
> >
> > Key: SANDESHA2-24
> > URL: http://issues.apache.org/jira/browse/SANDESHA2-24
> > Project: Apache Sandesha2
> > Issue Type: Improvement
> > Reporter: Matt Lovett
> > Priority: Minor
> > Attachments: version.patch
> >
> >
> > This patch starts to move the WS-RM 1.1 support in Sandesha2 Java
> up to the Public Review specification recently published by the
> OASIS WS-RX Tech Committee. I suggest that we do the work in 2 main
> stages: bring the namespace up to date, and then implement the new
> makeConnection operation.
> > I'll attach a patch that does the first part shortly.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see:
http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [jira] Updated: (SANDESHA2-24) Update Sandesha2 to OASIS WS-RM 1.1 Public Review specification
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Matt,
Thanks for the patch.
I'm halfway through in implementing the MakeConnection support. I'll commit
it soon. Is it possible for you to look into the new Security aspects, on
which you submitted a patch recently.
Chamikara
On 9/5/06, Matt Lovett (JIRA) <ji...@apache.org> wrote:
>
> [ http://issues.apache.org/jira/browse/SANDESHA2-24?page=all ]
>
> Matt Lovett updated SANDESHA2-24:
> ---------------------------------
>
> Attachment: version.patch
>
> Patch that moves the code up to the new namespace
>
> > Update Sandesha2 to OASIS WS-RM 1.1 Public Review specification
> > ---------------------------------------------------------------
> >
> > Key: SANDESHA2-24
> > URL: http://issues.apache.org/jira/browse/SANDESHA2-24
> > Project: Apache Sandesha2
> > Issue Type: Improvement
> > Reporter: Matt Lovett
> > Priority: Minor
> > Attachments: version.patch
> >
> >
> > This patch starts to move the WS-RM 1.1 support in Sandesha2 Java up to
> the Public Review specification recently published by the OASIS WS-RX Tech
> Committee. I suggest that we do the work in 2 main stages: bring the
> namespace up to date, and then implement the new makeConnection operation.
> > I'll attach a patch that does the first part shortly.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: [jira] Updated: (SANDESHA2-24) Update Sandesha2 to OASIS WS-RM 1.1 Public Review specification
Posted by Chamikara Jayalath <ch...@gmail.com>.
Hi Matt,
Thanks for the patch.
I'm halfway through in implementing the MakeConnection support. I'll commit
it soon. Is it possible for you to look into the new Security aspects, on
which you submitted a patch recently.
Chamikara
On 9/5/06, Matt Lovett (JIRA) <ji...@apache.org> wrote:
>
> [ http://issues.apache.org/jira/browse/SANDESHA2-24?page=all ]
>
> Matt Lovett updated SANDESHA2-24:
> ---------------------------------
>
> Attachment: version.patch
>
> Patch that moves the code up to the new namespace
>
> > Update Sandesha2 to OASIS WS-RM 1.1 Public Review specification
> > ---------------------------------------------------------------
> >
> > Key: SANDESHA2-24
> > URL: http://issues.apache.org/jira/browse/SANDESHA2-24
> > Project: Apache Sandesha2
> > Issue Type: Improvement
> > Reporter: Matt Lovett
> > Priority: Minor
> > Attachments: version.patch
> >
> >
> > This patch starts to move the WS-RM 1.1 support in Sandesha2 Java up to
> the Public Review specification recently published by the OASIS WS-RX Tech
> Committee. I suggest that we do the work in 2 main stages: bring the
> namespace up to date, and then implement the new makeConnection operation.
> > I'll attach a patch that does the first part shortly.
>
> --
> This message is automatically generated by JIRA.
> -
> If you think it was sent incorrectly contact one of the administrators:
> http://issues.apache.org/jira/secure/Administrators.jspa
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>