You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Krishnendu Kunti <Kr...@infosys.com> on 2004/10/09 09:55:35 UTC
Sandesha-- JDBC based persistent queues will be first
Hi Guys
I was going through the mails and decided that as per the groups (Sanjiva,Jaliya and Davanum) opinion , we will go with implementing JDBC based queues first then move on to JMS based queues.
Hi Sanjiva just got your mail , yes I too agree with you , but tying the config parameters of Sandesha to Axis will couple it more tightly with Axis..well I too agree with about regarding bringing external JARS is bit messy.
So, should we go ahead with config files at server-config.wsdd or some additional config . We will go with the decision of the Axis team of.
Guy's is it okay,
Thanks
Regards
Krishnendu
-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com]
Sent: Friday, October 08, 2004 5:06 PM
To: Krishnendu Kunti
Cc: Sanjiva Weerawarana; fx-dev@ws.apache.org
Subject: Re: Sandesha
Krishnendu,
You can start by contributing code that replaces the in-memory queue
with one based on JMS (say OpenJMS) as per your suggestion in a
previous email.
-- dims
On Fri, 8 Oct 2004 13:39:16 +0530, Krishnendu Kunti
<kr...@infosys.com> wrote:
>
> Hi Sanjiva
>
> Thanks, we would definitely like to contribute to sandesha, please let me know how to get involved in the project more deeply.
>
> In fact we were thinking of donating Syndeo framework or some components of the framework to Apache. We are in the process of consulting our legal experts as to the extent, scope, modus operandi, ramifications of this kind of contribution.
>
> Yes, you are very much correct I felt that tying Sandesha to Axis will limit its' utility in terms of support of RM to the web services deployed in that particular Axis engine. So if Sandesha is made available in terms of a pluggable utility which can be used along with an ESB then it will be possible to extend the RM to web services deployed across multiple web servers across the enterprise.
>
> It will be great if we get an opportunity to contribute to Apache Sandesha.
> Awaiting response from the apache team.
> Thanks
> Regards
> Krishnendu
>
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> Sent: Friday, October 08, 2004 7:41 AM
> To: Krishnendu Kunti; fx-dev@ws.apache.org
> Subject: Re: Sandesha
>
> Hi Krishnendu,
>
> Sounds great! Would your team be willing and interested to join the
> Sandesha project and help move it in the right direction so Syndeo
> for example could build on it? Clearly Sandesha is not an ESB .. its
> only the messaging part of a potential Web services based ESB.
>
> Could you also expand what you mean by "Sandesha impl at middleware
> level"? I thought it was indeed at the middleware level .. all of the
> Axis stuff is in some sense at the middleware level. I guess Sandesha
> could be made Axis independent for other SOAP stacks to be able to
> use it, but I'm not sure whether that's a requirement for us at this
> time. Is that what you're suggesting?
>
> If you need help on how to get started please holler.
>
> Sanjiva.
>
> ----- Original Message -----
> From: Krishnendu Kunti
> To: fx-dev@ws.apache.org
> Sent: Thursday, October 07, 2004 4:33 PM
> Subject: Sandesha
>
> Hi Jaliya
>
> Our team at Infosys have developed a Web services management framework
> "Syndeo" ( AN ESB -Enterprise service bus), the first version is already
> out. We are using open source tools primarily Apache tools. We have built
> the frame work on JMS (open JMS) infrastructure.
>
> Well we can have JMS based queues in axis instead of having in memory
> queues.
>
> Here is the mapping of Syndeo architecture to Sandesha architecture.
> RMSender-à Transporation Handler
> We don't' have a ClientQueue as we are not waiting for
> Acknowledgements...but a Clientqueue can be introduced to store the same.
>
> Senderà don't' have it but can be added to listen to the queue as mentioned
> in the previous step
>
> RMProviderà TopicRequestReceiver
> INQUEUEà RequestQueuePool (used as persistence storage, but does not
> support storage of messages till all the message of a sequence are received)
> RMInvokerà QueueRequest Receiver ( WS Invoker)
> OUTQUEUE à has to be added (we still don't' support a proper order of
> message .I guess this feature needs to be built)
>
> Finally I have two suggestions to make:
> Sandesha Implementation at a middleware level will make more sense as then
> it can support web services deployed across multiple web servers..
> Inference: A pluggable version of Sandesha should be made available which
> can be plugged to ESB like Mule or Syndeo.
>
> We can use JMS based queues in sandesa.
>
> Thanks again for sending the link of present architecture of sandesha.
>
> Included below is architecture diagram (only the message handling part) of
> syndeo:
>
> A man with a dream will not be denied
>
> Krishnendu Kunti
>
> SETLABS, Infosys Technologies LTD
> Bangalore, India
> Fax: +91 80 51102520
> Mobile: 9886375255
>
> URL: http://setlabs/wscoe (Infosys Intranet)
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Sandesha-- JDBC based persistent queues will be first
Posted by Davanum Srinivas <da...@gmail.com>.
don't forget..the deal includes unit tests, system tests (round-trip) etc :)
-- dims
On Sat, 9 Oct 2004 07:24:55 -0400, Davanum Srinivas <da...@gmail.com> wrote:
> let's get the tingy working before worrying about dependencies and
> configuration :)
>
> -- dims
>
> On Sat, 9 Oct 2004 13:25:35 +0530, Krishnendu Kunti
> <kr...@infosys.com> wrote:
> >
> > Hi Guys
>
>
> > I was going through the mails and decided that as per the groups (Sanjiva,Jaliya and Davanum) opinion , we will go with implementing JDBC based queues first then move on to JMS based queues.
> >
> > Hi Sanjiva just got your mail , yes I too agree with you , but tying the config parameters of Sandesha to Axis will couple it more tightly with Axis..well I too agree with about regarding bringing external JARS is bit messy.
> >
> > So, should we go ahead with config files at server-config.wsdd or some additional config . We will go with the decision of the Axis team of.
> >
> > Guy's is it okay,
> > Thanks
> > Regards
> >
> > Krishnendu
> >
> > -----Original Message-----
> > From: Davanum Srinivas [mailto:davanum@gmail.com]
> > Sent: Friday, October 08, 2004 5:06 PM
> > To: Krishnendu Kunti
> > Cc: Sanjiva Weerawarana; fx-dev@ws.apache.org
> > Subject: Re: Sandesha
> >
> > Krishnendu,
> >
> > You can start by contributing code that replaces the in-memory queue
> > with one based on JMS (say OpenJMS) as per your suggestion in a
> > previous email.
> >
> > -- dims
> >
> > On Fri, 8 Oct 2004 13:39:16 +0530, Krishnendu Kunti
> > <kr...@infosys.com> wrote:
> > >
> > > Hi Sanjiva
> > >
> > > Thanks, we would definitely like to contribute to sandesha, please let me know how to get involved in the project more deeply.
> > >
> > > In fact we were thinking of donating Syndeo framework or some components of the framework to Apache. We are in the process of consulting our legal experts as to the extent, scope, modus operandi, ramifications of this kind of contribution.
> > >
> > > Yes, you are very much correct I felt that tying Sandesha to Axis will limit its' utility in terms of support of RM to the web services deployed in that particular Axis engine. So if Sandesha is made available in terms of a pluggable utility which can be used along with an ESB then it will be possible to extend the RM to web services deployed across multiple web servers across the enterprise.
> > >
> > > It will be great if we get an opportunity to contribute to Apache Sandesha.
> > > Awaiting response from the apache team.
> > > Thanks
> > > Regards
> > > Krishnendu
> > >
> > > -----Original Message-----
> > > From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> > > Sent: Friday, October 08, 2004 7:41 AM
> > > To: Krishnendu Kunti; fx-dev@ws.apache.org
> > > Subject: Re: Sandesha
> > >
> > > Hi Krishnendu,
> > >
> > > Sounds great! Would your team be willing and interested to join the
> > > Sandesha project and help move it in the right direction so Syndeo
> > > for example could build on it? Clearly Sandesha is not an ESB .. its
> > > only the messaging part of a potential Web services based ESB.
> > >
> > > Could you also expand what you mean by "Sandesha impl at middleware
> > > level"? I thought it was indeed at the middleware level .. all of the
> > > Axis stuff is in some sense at the middleware level. I guess Sandesha
> > > could be made Axis independent for other SOAP stacks to be able to
> > > use it, but I'm not sure whether that's a requirement for us at this
> > > time. Is that what you're suggesting?
> > >
> > > If you need help on how to get started please holler.
> > >
> > > Sanjiva.
> > >
> > > ----- Original Message -----
> > > From: Krishnendu Kunti
> > > To: fx-dev@ws.apache.org
> > > Sent: Thursday, October 07, 2004 4:33 PM
> > > Subject: Sandesha
> > >
> > > Hi Jaliya
> > >
> > > Our team at Infosys have developed a Web services management framework
> > > "Syndeo" ( AN ESB -Enterprise service bus), the first version is already
> > > out. We are using open source tools primarily Apache tools. We have built
> > > the frame work on JMS (open JMS) infrastructure.
> > >
> > > Well we can have JMS based queues in axis instead of having in memory
> > > queues.
> > >
> > > Here is the mapping of Syndeo architecture to Sandesha architecture.
> > > RMSender-à Transporation Handler
> > > We don't' have a ClientQueue as we are not waiting for
> > > Acknowledgements...but a Clientqueue can be introduced to store the same.
> > >
> > > Senderà don't' have it but can be added to listen to the queue as mentioned
> > > in the previous step
> > >
> > > RMProviderà TopicRequestReceiver
> > > INQUEUEà RequestQueuePool (used as persistence storage, but does not
> > > support storage of messages till all the message of a sequence are received)
> > > RMInvokerà QueueRequest Receiver ( WS Invoker)
> > > OUTQUEUE à has to be added (we still don't' support a proper order of
> > > message .I guess this feature needs to be built)
> > >
> > > Finally I have two suggestions to make:
> > > Sandesha Implementation at a middleware level will make more sense as then
> > > it can support web services deployed across multiple web servers..
> > > Inference: A pluggable version of Sandesha should be made available which
> > > can be plugged to ESB like Mule or Syndeo.
> > >
> > > We can use JMS based queues in sandesa.
> > >
> > > Thanks again for sending the link of present architecture of sandesha.
> > >
> > > Included below is architecture diagram (only the message handling part) of
> > > syndeo:
> > >
> > > A man with a dream will not be denied
> > >
> > > Krishnendu Kunti
> > >
> > > SETLABS, Infosys Technologies LTD
> > > Bangalore, India
> > > Fax: +91 80 51102520
> > > Mobile: 9886375255
> > >
> > > URL: http://setlabs/wscoe (Infosys Intranet)
> > >
> > >
> >
> > --
> > Davanum Srinivas - http://webservices.apache.org/~dims/
> >
>
>
>
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
Re: Sandesha-- JDBC based persistent queues will be first
Posted by Davanum Srinivas <da...@gmail.com>.
let's get the tingy working before worrying about dependencies and
configuration :)
-- dims
On Sat, 9 Oct 2004 13:25:35 +0530, Krishnendu Kunti
<kr...@infosys.com> wrote:
>
> Hi Guys
> I was going through the mails and decided that as per the groups (Sanjiva,Jaliya and Davanum) opinion , we will go with implementing JDBC based queues first then move on to JMS based queues.
>
> Hi Sanjiva just got your mail , yes I too agree with you , but tying the config parameters of Sandesha to Axis will couple it more tightly with Axis..well I too agree with about regarding bringing external JARS is bit messy.
>
> So, should we go ahead with config files at server-config.wsdd or some additional config . We will go with the decision of the Axis team of.
>
> Guy's is it okay,
> Thanks
> Regards
>
> Krishnendu
>
> -----Original Message-----
> From: Davanum Srinivas [mailto:davanum@gmail.com]
> Sent: Friday, October 08, 2004 5:06 PM
> To: Krishnendu Kunti
> Cc: Sanjiva Weerawarana; fx-dev@ws.apache.org
> Subject: Re: Sandesha
>
> Krishnendu,
>
> You can start by contributing code that replaces the in-memory queue
> with one based on JMS (say OpenJMS) as per your suggestion in a
> previous email.
>
> -- dims
>
> On Fri, 8 Oct 2004 13:39:16 +0530, Krishnendu Kunti
> <kr...@infosys.com> wrote:
> >
> > Hi Sanjiva
> >
> > Thanks, we would definitely like to contribute to sandesha, please let me know how to get involved in the project more deeply.
> >
> > In fact we were thinking of donating Syndeo framework or some components of the framework to Apache. We are in the process of consulting our legal experts as to the extent, scope, modus operandi, ramifications of this kind of contribution.
> >
> > Yes, you are very much correct I felt that tying Sandesha to Axis will limit its' utility in terms of support of RM to the web services deployed in that particular Axis engine. So if Sandesha is made available in terms of a pluggable utility which can be used along with an ESB then it will be possible to extend the RM to web services deployed across multiple web servers across the enterprise.
> >
> > It will be great if we get an opportunity to contribute to Apache Sandesha.
> > Awaiting response from the apache team.
> > Thanks
> > Regards
> > Krishnendu
> >
> > -----Original Message-----
> > From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> > Sent: Friday, October 08, 2004 7:41 AM
> > To: Krishnendu Kunti; fx-dev@ws.apache.org
> > Subject: Re: Sandesha
> >
> > Hi Krishnendu,
> >
> > Sounds great! Would your team be willing and interested to join the
> > Sandesha project and help move it in the right direction so Syndeo
> > for example could build on it? Clearly Sandesha is not an ESB .. its
> > only the messaging part of a potential Web services based ESB.
> >
> > Could you also expand what you mean by "Sandesha impl at middleware
> > level"? I thought it was indeed at the middleware level .. all of the
> > Axis stuff is in some sense at the middleware level. I guess Sandesha
> > could be made Axis independent for other SOAP stacks to be able to
> > use it, but I'm not sure whether that's a requirement for us at this
> > time. Is that what you're suggesting?
> >
> > If you need help on how to get started please holler.
> >
> > Sanjiva.
> >
> > ----- Original Message -----
> > From: Krishnendu Kunti
> > To: fx-dev@ws.apache.org
> > Sent: Thursday, October 07, 2004 4:33 PM
> > Subject: Sandesha
> >
> > Hi Jaliya
> >
> > Our team at Infosys have developed a Web services management framework
> > "Syndeo" ( AN ESB -Enterprise service bus), the first version is already
> > out. We are using open source tools primarily Apache tools. We have built
> > the frame work on JMS (open JMS) infrastructure.
> >
> > Well we can have JMS based queues in axis instead of having in memory
> > queues.
> >
> > Here is the mapping of Syndeo architecture to Sandesha architecture.
> > RMSender-à Transporation Handler
> > We don't' have a ClientQueue as we are not waiting for
> > Acknowledgements...but a Clientqueue can be introduced to store the same.
> >
> > Senderà don't' have it but can be added to listen to the queue as mentioned
> > in the previous step
> >
> > RMProviderà TopicRequestReceiver
> > INQUEUEà RequestQueuePool (used as persistence storage, but does not
> > support storage of messages till all the message of a sequence are received)
> > RMInvokerà QueueRequest Receiver ( WS Invoker)
> > OUTQUEUE à has to be added (we still don't' support a proper order of
> > message .I guess this feature needs to be built)
> >
> > Finally I have two suggestions to make:
> > Sandesha Implementation at a middleware level will make more sense as then
> > it can support web services deployed across multiple web servers..
> > Inference: A pluggable version of Sandesha should be made available which
> > can be plugged to ESB like Mule or Syndeo.
> >
> > We can use JMS based queues in sandesa.
> >
> > Thanks again for sending the link of present architecture of sandesha.
> >
> > Included below is architecture diagram (only the message handling part) of
> > syndeo:
> >
> > A man with a dream will not be denied
> >
> > Krishnendu Kunti
> >
> > SETLABS, Infosys Technologies LTD
> > Bangalore, India
> > Fax: +91 80 51102520
> > Mobile: 9886375255
> >
> > URL: http://setlabs/wscoe (Infosys Intranet)
> >
> >
>
> --
> Davanum Srinivas - http://webservices.apache.org/~dims/
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/
RE: Sandesha-- JDBC based persistent queues will be first
Posted by Jaliya Ekanayake <ja...@opensource.lk>.
Hi Krishnendu,
I would like to focus your attention to the followings with respect to jdbc
queues. We have identified these things when we initially implement the
Sandesha with the database support.
If we operates at the transport level we may just store the in and out SOAP
envelops and some transport related properties in the queue.
But since we need to provide the INORDER EXACTLY ONCE quality of service we
need to rearrange the order of the messages depending on their message
numbers.
We can take that decision at the provider level only. However we have to
store the WS-RM specific messages from a handler because these messages
should not pass through the other user defined handlers. We can simply store
the properties of these messages instead of the entire messages.
Since the invocation is done in the correct order we have to store the
service request messages after been processed by all the handler chains and
only at the provider level.
At this stage we can store the message with the operation description in the
database.
Hope to see Sandesha running with jdbc support :)
Thanks,
Jaliya
-----Original Message-----
From: Krishnendu Kunti [mailto:Krishnendu_Kunti@infosys.com]
Sent: Saturday, October 09, 2004 1:56 PM
To: dims@apache.org
Cc: fx-dev@ws.apache.org; Jaliya Ekanayake; Sanjiva Weerawarana
Subject: Sandesha-- JDBC based persistent queues will be first
Hi Guys
I was going through the mails and decided that as per the groups
(Sanjiva,Jaliya and Davanum) opinion , we will go with implementing JDBC
based queues first then move on to JMS based queues.
Hi Sanjiva just got your mail , yes I too agree with you , but tying the
config parameters of Sandesha to Axis will couple it more tightly with
Axis..well I too agree with about regarding bringing external JARS is bit
messy.
So, should we go ahead with config files at server-config.wsdd or some
additional config . We will go with the decision of the Axis team of.
Guy's is it okay,
Thanks
Regards
Krishnendu
-----Original Message-----
From: Davanum Srinivas [mailto:davanum@gmail.com]
Sent: Friday, October 08, 2004 5:06 PM
To: Krishnendu Kunti
Cc: Sanjiva Weerawarana; fx-dev@ws.apache.org
Subject: Re: Sandesha
Krishnendu,
You can start by contributing code that replaces the in-memory queue
with one based on JMS (say OpenJMS) as per your suggestion in a
previous email.
-- dims
On Fri, 8 Oct 2004 13:39:16 +0530, Krishnendu Kunti
<kr...@infosys.com> wrote:
>
> Hi Sanjiva
>
> Thanks, we would definitely like to contribute to sandesha, please let me
know how to get involved in the project more deeply.
>
> In fact we were thinking of donating Syndeo framework or some components
of the framework to Apache. We are in the process of consulting our legal
experts as to the extent, scope, modus operandi, ramifications of this kind
of contribution.
>
> Yes, you are very much correct I felt that tying Sandesha to Axis will
limit its' utility in terms of support of RM to the web services deployed in
that particular Axis engine. So if Sandesha is made available in terms of a
pluggable utility which can be used along with an ESB then it will be
possible to extend the RM to web services deployed across multiple web
servers across the enterprise.
>
> It will be great if we get an opportunity to contribute to Apache
Sandesha.
> Awaiting response from the apache team.
> Thanks
> Regards
> Krishnendu
>
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@opensource.lk]
> Sent: Friday, October 08, 2004 7:41 AM
> To: Krishnendu Kunti; fx-dev@ws.apache.org
> Subject: Re: Sandesha
>
> Hi Krishnendu,
>
> Sounds great! Would your team be willing and interested to join the
> Sandesha project and help move it in the right direction so Syndeo
> for example could build on it? Clearly Sandesha is not an ESB .. its
> only the messaging part of a potential Web services based ESB.
>
> Could you also expand what you mean by "Sandesha impl at middleware
> level"? I thought it was indeed at the middleware level .. all of the
> Axis stuff is in some sense at the middleware level. I guess Sandesha
> could be made Axis independent for other SOAP stacks to be able to
> use it, but I'm not sure whether that's a requirement for us at this
> time. Is that what you're suggesting?
>
> If you need help on how to get started please holler.
>
> Sanjiva.
>
> ----- Original Message -----
> From: Krishnendu Kunti
> To: fx-dev@ws.apache.org
> Sent: Thursday, October 07, 2004 4:33 PM
> Subject: Sandesha
>
> Hi Jaliya
>
> Our team at Infosys have developed a Web services management framework
> "Syndeo" ( AN ESB -Enterprise service bus), the first version is already
> out. We are using open source tools primarily Apache tools. We have built
> the frame work on JMS (open JMS) infrastructure.
>
> Well we can have JMS based queues in axis instead of having in memory
> queues.
>
> Here is the mapping of Syndeo architecture to Sandesha architecture.
> RMSender-à Transporation Handler
> We don't' have a ClientQueue as we are not waiting for
> Acknowledgements...but a Clientqueue can be introduced to store the same.
>
> Senderà don't' have it but can be added to listen to the queue as
mentioned
> in the previous step
>
> RMProviderà TopicRequestReceiver
> INQUEUEà RequestQueuePool (used as persistence storage, but does not
> support storage of messages till all the message of a sequence are
received)
> RMInvokerà QueueRequest Receiver ( WS Invoker)
> OUTQUEUE à has to be added (we still don't' support a proper order of
> message .I guess this feature needs to be built)
>
> Finally I have two suggestions to make:
> Sandesha Implementation at a middleware level will make more sense as then
> it can support web services deployed across multiple web servers..
> Inference: A pluggable version of Sandesha should be made available which
> can be plugged to ESB like Mule or Syndeo.
>
> We can use JMS based queues in sandesa.
>
> Thanks again for sending the link of present architecture of sandesha.
>
> Included below is architecture diagram (only the message handling part) of
> syndeo:
>
> A man with a dream will not be denied
>
> Krishnendu Kunti
>
> SETLABS, Infosys Technologies LTD
> Bangalore, India
> Fax: +91 80 51102520
> Mobile: 9886375255
>
> URL: http://setlabs/wscoe (Infosys Intranet)
>
>
--
Davanum Srinivas - http://webservices.apache.org/~dims/