springframework-developer

RE: [Springframework-developer] JMS brainstorming

[Dmitriy K. <dko...@ru...>]

Andre,

nice to meet you :-) Can you introduce yourself and may be send your =
work
progress to the list...

Regards,
Dmitriy.

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
Mark Pollack
Sent: Thursday, February 26, 2004 6:08 AM
To: spr...@li...
Cc: spr...@li...; Andre Biryukov
Subject: Re: [Springframework-developer] JMS brainstorming


Hi,
I've been quiet on the lists for while, but JMS is something I work with =
all
the time and I'd be happy to contribute in this area...  Send me an =
e-mail
andre and we can collaborate.... Cheers, Mark


> Rong
>
> JMS support is in the works, and should make 1.1.
>
> Andre Biryukov is currently working on this, and should be joining the =

> Spring team soon.
>
> Andre, if you want to share your work in progress with the Spring dev=20
> list (or with Rong directly), now would be a good time :-)
>
> Regards,
> Rod
>
> ----- Original Message -----
> From: "Ou, Rong" <Ro...@sa...>
> To: <spr...@li...>
> Sent: Tuesday, February 24, 2004 9:44 PM
> Subject: [Springframework-developer] JMS brainstorming
>
>
> Hi all,
>
> We currently have a project that does a lot of JMS messaging, and we=20
> desperately need an API to simplify the interface layer to JMS. I=20
> heard rumors that JMS support will be added to Spring 1.1, but we just =

> can't wait that long. So I am thinking about doing something in the=20
> interim. Who knows,
> if it comes out good, maybe I can contribute the code back.
>
> In Rod's book there is only a couple of pages that briefly touches=20
> upon JMS. I looked at the interface21 code, the JMS portion is also=20
> pretty simplistic.
> I understand Spring has evolved a lot since the interface21 days. So =
to
> all
> you experienced Spring'ers, if you were to add JMS support today, what
> would
> you do? I am still fairly new to Spring, so any suggestions and help =
are
> welcome.
>
> Thanks,
>
> Rong
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and=20
> deploy apps & Web services for Linux with a free DVD software kit from =

> IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and=20
> deploy apps & Web services for Linux with a free DVD software kit from =

> IBM. Click Now! =
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Andre B. <and...@ho...>]

Hi Rod, Hi All,

I've been working on the JMS support for a few weeks now and I think I'm 
ready to go public with it to find out your opinion. So far, I got Mark to 
volunteer to look at the code, make suggestions and possibly contribute some 
code. If anybody is interested to look at it as well, just drop me a mail, 
I'll be happy to forward what I have so far to you.

I'm not only interested in the feedback about the code, but would like to 
hear opinions on what we should include and what not. The API for messaging 
is huge, well, big. The challenge is to try and put as much functionality as 
possible, but at the same token, try not to make it look complex.

Here's the list of things I've implemented:

1. Templates for publish/subscribe and point-to-point messaging. I did 
include support for both durable and non-durable messaging.
2. The consumers will be able to not only create messages, but also will 
have some control over how they will be delivered. I.e. modify default 
delivery mode, priority, time to live.
3. Message listeners will be instrumental in automatically registering beans 
as subscribers to topics and queues.

I left out support for the transacted sessions. Sessions created are all set 
to "no-transaction" and "auto-ACK". Is this something we would like to see 
in the framework or should we just keep it simple for now ? The more 
suggestions I get now, the better, so please open the flood gate. :)

Thanks,

Andre.

>From: "Rod Johnson" <rod...@in...>
>To: <spr...@li...>
>CC: "Andre Biryukov" <and...@ho...>
>Subject: Re: [Springframework-developer] JMS brainstorming
>Date: Thu, 26 Feb 2004 06:35:33 -0000
>
>Rong
>
>JMS support is in the works, and should make 1.1.
>
>Andre Biryukov is currently working on this, and should be joining the
>Spring team soon.
>
>Andre, if you want to share your work in progress with the Spring dev list
>(or with Rong directly), now would be a good time :-)
>
>Regards,
>Rod
>
>----- Original Message -----
>From: "Ou, Rong" <Ro...@sa...>
>To: <spr...@li...>
>Sent: Tuesday, February 24, 2004 9:44 PM
>Subject: [Springframework-developer] JMS brainstorming
>
>
>Hi all,
>
>We currently have a project that does a lot of JMS messaging, and we
>desperately need an API to simplify the interface layer to JMS. I heard
>rumors that JMS support will be added to Spring 1.1, but we just can't wait
>that long. So I am thinking about doing something in the interim. Who 
>knows,
>if it comes out good, maybe I can contribute the code back.
>
>In Rod's book there is only a couple of pages that briefly touches upon 
>JMS.
>I looked at the interface21 code, the JMS portion is also pretty 
>simplistic.
>I understand Spring has evolved a lot since the interface21 days. So to all
>you experienced Spring'ers, if you were to add JMS support today, what 
>would
>you do? I am still fairly new to Spring, so any suggestions and help are
>welcome.
>
>Thanks,
>
>Rong
>
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!
>http://ads.osdn.com/?ad_id56&alloc_id438&op=ick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>

_________________________________________________________________
Stay informed on Election 2004 and the race to Super Tuesday. 
http://special.msn.com/msn/election2004.armx

RE: [Springframework-developer] JMS brainstorming

[Alef A. <al...@jt...>]

I'd be interested in having look...

Maybe it's an idea to publish the code in the sandbox for now?

Alef


> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On =
Behalf
> Of Andre Biryukov
> Sent: Thursday, February 26, 2004 5:46 PM
> To: rod...@in...; springframework-
> dev...@li...
> Subject: Re: [Springframework-developer] JMS brainstorming
>=20
> Hi Rod, Hi All,
>=20
> I've been working on the JMS support for a few weeks now and I think =
I'm
> ready to go public with it to find out your opinion. So far, I got =
Mark to
> volunteer to look at the code, make suggestions and possibly =
contribute
> some
> code. If anybody is interested to look at it as well, just drop me a =
mail,
> I'll be happy to forward what I have so far to you.
>=20
> I'm not only interested in the feedback about the code, but would like =
to
> hear opinions on what we should include and what not. The API for
> messaging
> is huge, well, big. The challenge is to try and put as much =
functionality
> as
> possible, but at the same token, try not to make it look complex.
>=20
> Here's the list of things I've implemented:
>=20
> 1. Templates for publish/subscribe and point-to-point messaging. I did
> include support for both durable and non-durable messaging.
> 2. The consumers will be able to not only create messages, but also =
will
> have some control over how they will be delivered. I.e. modify default
> delivery mode, priority, time to live.
> 3. Message listeners will be instrumental in automatically registering
> beans
> as subscribers to topics and queues.
>=20
> I left out support for the transacted sessions. Sessions created are =
all
> set
> to "no-transaction" and "auto-ACK". Is this something we would like to =
see
> in the framework or should we just keep it simple for now ? The more
> suggestions I get now, the better, so please open the flood gate. :)
>=20
> Thanks,
>=20
> Andre.
>=20
> >From: "Rod Johnson" <rod...@in...>
> >To: <spr...@li...>
> >CC: "Andre Biryukov" <and...@ho...>
> >Subject: Re: [Springframework-developer] JMS brainstorming
> >Date: Thu, 26 Feb 2004 06:35:33 -0000
> >
> >Rong
> >
> >JMS support is in the works, and should make 1.1.
> >
> >Andre Biryukov is currently working on this, and should be joining =
the
> >Spring team soon.
> >
> >Andre, if you want to share your work in progress with the Spring dev
> list
> >(or with Rong directly), now would be a good time :-)
> >
> >Regards,
> >Rod
> >
> >----- Original Message -----
> >From: "Ou, Rong" <Ro...@sa...>
> >To: <spr...@li...>
> >Sent: Tuesday, February 24, 2004 9:44 PM
> >Subject: [Springframework-developer] JMS brainstorming
> >
> >
> >Hi all,
> >
> >We currently have a project that does a lot of JMS messaging, and we
> >desperately need an API to simplify the interface layer to JMS. I =
heard
> >rumors that JMS support will be added to Spring 1.1, but we just =
can't
> wait
> >that long. So I am thinking about doing something in the interim. Who
> >knows,
> >if it comes out good, maybe I can contribute the code back.
> >
> >In Rod's book there is only a couple of pages that briefly touches =
upon
> >JMS.
> >I looked at the interface21 code, the JMS portion is also pretty
> >simplistic.
> >I understand Spring has evolved a lot since the interface21 days. So =
to
> all
> >you experienced Spring'ers, if you were to add JMS support today, =
what
> >would
> >you do? I am still fairly new to Spring, so any suggestions and help =
are
> >welcome.
> >
> >Thanks,
> >
> >Rong
> >
> >
> >-------------------------------------------------------
> >SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> >Build and deploy apps & Web services for Linux with
> >a free DVD software kit from IBM. Click Now!
> >http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> =
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
>=20
> _________________________________________________________________
> Stay informed on Election 2004 and the race to Super Tuesday.
> http://special.msn.com/msn/election2004.armx
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Mark P. <Mar...@Co...>]

Hi everyone,

I'll look over the code this weekend...on a little vacation now.
Anyway, sounds good so far.  I'm in the middle of discussing donating JMS
code we developed at our company...

Some of the larger items are:

1. A very efficient implementation of the JMS selector for use on
MapMessages, or really anything else you like, hashtables, even text
messages.  Based on JavaCC. This externalized the ugly switch statements
that you typically have to do in the main callback function.

2. We have a 'standalone' jms application, not in an appserver.  We added
some server like infrastructure classes to spring start up the
connections, sessions, etc., after all the bean initialization.  There are
corresponding classes to handle setting up all the JMS specific stuff...tx
session, what ack mode, etc.  Vendors also make extensions to the standard
modes that we should account for...

3. Much like the templates for jdbc etc. there is a bunch of surrounding
code to handle exceptions correctly, also having a seperate method for
"onDuplicate" based on the JMSHeader value is nice.

4. A 'pipe and filters' style processing framwork.  Similar to what you
might see in apache axis, but not specific to soap or jms.  It it based on
the reactor design pattern to pick off the appropriate processing chain to
execute based on the evaluation of a JMS selector string that applies to
the message body (not the header).  It then iterates through various
'process' template methods of modules in the chain.. exceptions result in
rolling back, that is calling 'rollback' up the chain and finally to a
exceptionhandler.  This is all externalized in a config file.  I'm sure
there might be temptations to compare to other workflow like projects...
but this codebase is really pretty simple and has been extremely useful to
us for a number of years....  It really also apply outside the messaging
area...

5. Some pretty print utilities for messages, xml marhsaller/unmarshaller. 
This is part of my conversion/rewrite/refactoring of 'rvtest.sf.net (JUnit
for TIBCO Rendezvous to JMS) I'll be releasing that code on sf but we can
pick and choose little things that might be useful...

I'm pretty sure most I can integrate most of the items on this list to the
effort.


Cheers,
Mark



> Hi Rod, Hi All,
>
> I've been working on the JMS support for a few weeks now and I think I'm
> ready to go public with it to find out your opinion. So far, I got Mark to
> volunteer to look at the code, make suggestions and possibly contribute
> some
> code. If anybody is interested to look at it as well, just drop me a mail,
> I'll be happy to forward what I have so far to you.
>
> I'm not only interested in the feedback about the code, but would like to
> hear opinions on what we should include and what not. The API for
> messaging
> is huge, well, big. The challenge is to try and put as much functionality
> as
> possible, but at the same token, try not to make it look complex.
>
> Here's the list of things I've implemented:
>
> 1. Templates for publish/subscribe and point-to-point messaging. I did
> include support for both durable and non-durable messaging.
> 2. The consumers will be able to not only create messages, but also will
> have some control over how they will be delivered. I.e. modify default
> delivery mode, priority, time to live.
> 3. Message listeners will be instrumental in automatically registering
> beans
> as subscribers to topics and queues.
>
> I left out support for the transacted sessions. Sessions created are all
> set
> to "no-transaction" and "auto-ACK". Is this something we would like to see
> in the framework or should we just keep it simple for now ? The more
> suggestions I get now, the better, so please open the flood gate. :)
>
> Thanks,
>
> Andre.
>
>>From: "Rod Johnson" <rod...@in...>
>>To: <spr...@li...>
>>CC: "Andre Biryukov" <and...@ho...>
>>Subject: Re: [Springframework-developer] JMS brainstorming
>>Date: Thu, 26 Feb 2004 06:35:33 -0000
>>
>>Rong
>>
>>JMS support is in the works, and should make 1.1.
>>
>>Andre Biryukov is currently working on this, and should be joining the
>>Spring team soon.
>>
>>Andre, if you want to share your work in progress with the Spring dev
>> list
>>(or with Rong directly), now would be a good time :-)
>>
>>Regards,
>>Rod
>>
>>----- Original Message -----
>>From: "Ou, Rong" <Ro...@sa...>
>>To: <spr...@li...>
>>Sent: Tuesday, February 24, 2004 9:44 PM
>>Subject: [Springframework-developer] JMS brainstorming
>>
>>
>>Hi all,
>>
>>We currently have a project that does a lot of JMS messaging, and we
>>desperately need an API to simplify the interface layer to JMS. I heard
>>rumors that JMS support will be added to Spring 1.1, but we just can't
>> wait
>>that long. So I am thinking about doing something in the interim. Who
>>knows,
>>if it comes out good, maybe I can contribute the code back.
>>
>>In Rod's book there is only a couple of pages that briefly touches upon
>>JMS.
>>I looked at the interface21 code, the JMS portion is also pretty
>>simplistic.
>>I understand Spring has evolved a lot since the interface21 days. So to
>> all
>>you experienced Spring'ers, if you were to add JMS support today, what
>>would
>>you do? I am still fairly new to Spring, so any suggestions and help are
>>welcome.
>>
>>Thanks,
>>
>>Rong
>>
>>
>>-------------------------------------------------------
>>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>>Build and deploy apps & Web services for Linux with
>>a free DVD software kit from IBM. Click Now!
>>http://ads.osdn.com/?ad_id56&alloc_id438&op=ick
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>
>>
>
> _________________________________________________________________
> Stay informed on Election 2004 and the race to Super Tuesday.
> http://special.msn.com/msn/election2004.armx
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>

RE: [Springframework-developer] JMS brainstorming

[Mark P. <mar...@co...>]

Hi,

I've added Andre's code into the sandbox. =20

I'd like to get some input on the following.... Can we count on using
the JMS 1.1 API or should we be compatible with the JMS 1.0.2 API? The
reason is that JMS 1.1 introduced "domain unification", meaning that
there the classes are no longer split into "Queue" and "Topic" class
hierarchies.  The code can now refer to a "ConnectionFactory" instead of
it being a "QueueConnectionFactory" or a "TopicConnectionFactory".  This
applies up and down the class hierarchy since the split is rather high
level.  The end result is that using the JMS 1.1 api makes the client
code much easier to use since there is less obvious duplication.  Other
advantages can be read in the spec...such as being able to use  queues
and topics in the same transaction (probably since they now can share
the same Session object).

The templates now are written using the 1.0.2 style classes, which I
haven't used in a long time....but I'd like to hear what people are
using considering how much it will affect the shape of the code...  I'd
vote for dropping 1.0.2 support.

Cheers,
Mark



-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Andre Biryukov
Sent: Thursday, February 26, 2004 11:46 AM
To: rod...@in...;
spr...@li...
Subject: Re: [Springframework-developer] JMS brainstorming


Hi Rod, Hi All,

I've been working on the JMS support for a few weeks now and I think I'm

ready to go public with it to find out your opinion. So far, I got Mark
to=20
volunteer to look at the code, make suggestions and possibly contribute
some=20
code. If anybody is interested to look at it as well, just drop me a
mail,=20
I'll be happy to forward what I have so far to you.

I'm not only interested in the feedback about the code, but would like
to=20
hear opinions on what we should include and what not. The API for
messaging=20
is huge, well, big. The challenge is to try and put as much
functionality as=20
possible, but at the same token, try not to make it look complex.

Here's the list of things I've implemented:

1. Templates for publish/subscribe and point-to-point messaging. I did=20
include support for both durable and non-durable messaging.
2. The consumers will be able to not only create messages, but also will

have some control over how they will be delivered. I.e. modify default=20
delivery mode, priority, time to live.
3. Message listeners will be instrumental in automatically registering
beans=20
as subscribers to topics and queues.

I left out support for the transacted sessions. Sessions created are all
set=20
to "no-transaction" and "auto-ACK". Is this something we would like to
see=20
in the framework or should we just keep it simple for now ? The more=20
suggestions I get now, the better, so please open the flood gate. :)

Thanks,

Andre.

>From: "Rod Johnson" <rod...@in...>
>To: <spr...@li...>
>CC: "Andre Biryukov" <and...@ho...>
>Subject: Re: [Springframework-developer] JMS brainstorming
>Date: Thu, 26 Feb 2004 06:35:33 -0000
>
>Rong
>
>JMS support is in the works, and should make 1.1.
>
>Andre Biryukov is currently working on this, and should be joining the=20
>Spring team soon.
>
>Andre, if you want to share your work in progress with the Spring dev=20
>list (or with Rong directly), now would be a good time :-)
>
>Regards,
>Rod
>
>----- Original Message -----
>From: "Ou, Rong" <Ro...@sa...>
>To: <spr...@li...>
>Sent: Tuesday, February 24, 2004 9:44 PM
>Subject: [Springframework-developer] JMS brainstorming
>
>
>Hi all,
>
>We currently have a project that does a lot of JMS messaging, and we=20
>desperately need an API to simplify the interface layer to JMS. I heard

>rumors that JMS support will be added to Spring 1.1, but we just can't=20
>wait that long. So I am thinking about doing something in the interim.=20
>Who knows, if it comes out good, maybe I can contribute the code back.
>
>In Rod's book there is only a couple of pages that briefly touches upon
>JMS.
>I looked at the interface21 code, the JMS portion is also pretty=20
>simplistic.
>I understand Spring has evolved a lot since the interface21 days. So to
all
>you experienced Spring'ers, if you were to add JMS support today, what=20
>would
>you do? I am still fairly new to Spring, so any suggestions and help
are
>welcome.
>
>Thanks,
>
>Rong
>
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!=20
>http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
>_______________________________________________
>Springframework-developer mailing list=20
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>

_________________________________________________________________
Stay informed on Election 2004 and the race to Super Tuesday.=20
http://special.msn.com/msn/election2004.armx



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Rod J. <rod...@in...>]

What are the release levels of the major services (WLS, WS, JB etc.) to
support 1.1?

----- Original Message -----
From: "Mark Pollack" <mar...@co...>
To: <spr...@li...>
Sent: Tuesday, March 02, 2004 12:02 AM
Subject: RE: [Springframework-developer] JMS brainstorming


Hi,

I've added Andre's code into the sandbox.

I'd like to get some input on the following.... Can we count on using
the JMS 1.1 API or should we be compatible with the JMS 1.0.2 API? The
reason is that JMS 1.1 introduced "domain unification", meaning that
there the classes are no longer split into "Queue" and "Topic" class
hierarchies.  The code can now refer to a "ConnectionFactory" instead of
it being a "QueueConnectionFactory" or a "TopicConnectionFactory".  This
applies up and down the class hierarchy since the split is rather high
level.  The end result is that using the JMS 1.1 api makes the client
code much easier to use since there is less obvious duplication.  Other
advantages can be read in the spec...such as being able to use  queues
and topics in the same transaction (probably since they now can share
the same Session object).

The templates now are written using the 1.0.2 style classes, which I
haven't used in a long time....but I'd like to hear what people are
using considering how much it will affect the shape of the code...  I'd
vote for dropping 1.0.2 support.

Cheers,
Mark



-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Andre Biryukov
Sent: Thursday, February 26, 2004 11:46 AM
To: rod...@in...;
spr...@li...
Subject: Re: [Springframework-developer] JMS brainstorming


Hi Rod, Hi All,

I've been working on the JMS support for a few weeks now and I think I'm

ready to go public with it to find out your opinion. So far, I got Mark
to
volunteer to look at the code, make suggestions and possibly contribute
some
code. If anybody is interested to look at it as well, just drop me a
mail,
I'll be happy to forward what I have so far to you.

I'm not only interested in the feedback about the code, but would like
to
hear opinions on what we should include and what not. The API for
messaging
is huge, well, big. The challenge is to try and put as much
functionality as
possible, but at the same token, try not to make it look complex.

Here's the list of things I've implemented:

1. Templates for publish/subscribe and point-to-point messaging. I did
include support for both durable and non-durable messaging.
2. The consumers will be able to not only create messages, but also will

have some control over how they will be delivered. I.e. modify default
delivery mode, priority, time to live.
3. Message listeners will be instrumental in automatically registering
beans
as subscribers to topics and queues.

I left out support for the transacted sessions. Sessions created are all
set
to "no-transaction" and "auto-ACK". Is this something we would like to
see
in the framework or should we just keep it simple for now ? The more
suggestions I get now, the better, so please open the flood gate. :)

Thanks,

Andre.

>From: "Rod Johnson" <rod...@in...>
>To: <spr...@li...>
>CC: "Andre Biryukov" <and...@ho...>
>Subject: Re: [Springframework-developer] JMS brainstorming
>Date: Thu, 26 Feb 2004 06:35:33 -0000
>
>Rong
>
>JMS support is in the works, and should make 1.1.
>
>Andre Biryukov is currently working on this, and should be joining the
>Spring team soon.
>
>Andre, if you want to share your work in progress with the Spring dev
>list (or with Rong directly), now would be a good time :-)
>
>Regards,
>Rod
>
>----- Original Message -----
>From: "Ou, Rong" <Ro...@sa...>
>To: <spr...@li...>
>Sent: Tuesday, February 24, 2004 9:44 PM
>Subject: [Springframework-developer] JMS brainstorming
>
>
>Hi all,
>
>We currently have a project that does a lot of JMS messaging, and we
>desperately need an API to simplify the interface layer to JMS. I heard

>rumors that JMS support will be added to Spring 1.1, but we just can't
>wait that long. So I am thinking about doing something in the interim.
>Who knows, if it comes out good, maybe I can contribute the code back.
>
>In Rod's book there is only a couple of pages that briefly touches upon
>JMS.
>I looked at the interface21 code, the JMS portion is also pretty
>simplistic.
>I understand Spring has evolved a lot since the interface21 days. So to
all
>you experienced Spring'ers, if you were to add JMS support today, what
>would
>you do? I am still fairly new to Spring, so any suggestions and help
are
>welcome.
>
>Thanks,
>
>Rong
>
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!
>http://ads.osdn.com/?ad_id56&alloc_id438&op=ick
>_______________________________________________
>Springframework-developer mailing list
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>

_________________________________________________________________
Stay informed on Election 2004 and the race to Super Tuesday.
http://special.msn.com/msn/election2004.armx



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=ick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] JMS brainstorming

[Mark P. <mar...@co...>]

Hi,

Here is what I dug up.

J2EE 1.4 specifies JMS 1.1, J2EE 1.3 specifies JMS 1.0.2.


WebLogic 8.1 - 1.1 support
WebLogic 7.0 - hard to tell...doesn't seem to from the docs but Tom
Barnes of BEA claims it is there.
See http://www.theserverside.com/news/thread.jsp?thread_id=3D20400#89550

Anyone with experience using JMS 1.1 with WL 7.0..if not I'll try it out
myself.

WebSphere 'App Server for Developers' Version 6 - 1.1=20
WebSphere Version 5 				      - 1.0.2=20

Jboss 3.2.3 - 1.0.2
Jboss 4 - 1.1

Maybe the slowness of releasing J2EE specs is the reason for what I
think is a rather odd situation, that the JMS 1.1 spec has been out for
almost 2 years, April 2002, but you have to basically go to the latest
app server versions to get support.  Meanwhile, every "independent" JMS
vendor has provided 1.1 support for quite a while... =20

In anycase, hiding the differences in client code between queues/topics
is still a good idea... This is one of the main selling points of the
commons messenger, http://jakarta.apache.org/commons/sandbox/messenger/
How do people feel about a similar approach on top of 1.0, maybe even
wrapping a 1.1 API on top of a 1.0.2 implementation....that might
actually be possible from the API point of view.

Cheers,
Mark





-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Rod Johnson
Sent: Tuesday, March 02, 2004 2:04 AM
To: spr...@li...
Subject: Re: [Springframework-developer] JMS brainstorming


What are the release levels of the major services (WLS, WS, JB etc.) to
support 1.1?

----- Original Message -----
From: "Mark Pollack" <mar...@co...>
To: <spr...@li...>
Sent: Tuesday, March 02, 2004 12:02 AM
Subject: RE: [Springframework-developer] JMS brainstorming


Hi,

I've added Andre's code into the sandbox.

I'd like to get some input on the following.... Can we count on using
the JMS 1.1 API or should we be compatible with the JMS 1.0.2 API? The
reason is that JMS 1.1 introduced "domain unification", meaning that
there the classes are no longer split into "Queue" and "Topic" class
hierarchies.  The code can now refer to a "ConnectionFactory" instead of
it being a "QueueConnectionFactory" or a "TopicConnectionFactory".  This
applies up and down the class hierarchy since the split is rather high
level.  The end result is that using the JMS 1.1 api makes the client
code much easier to use since there is less obvious duplication.  Other
advantages can be read in the spec...such as being able to use  queues
and topics in the same transaction (probably since they now can share
the same Session object).

The templates now are written using the 1.0.2 style classes, which I
haven't used in a long time....but I'd like to hear what people are
using considering how much it will affect the shape of the code...  I'd
vote for dropping 1.0.2 support.

Cheers,
Mark



-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf
Of Andre Biryukov
Sent: Thursday, February 26, 2004 11:46 AM
To: rod...@in...;
spr...@li...
Subject: Re: [Springframework-developer] JMS brainstorming


Hi Rod, Hi All,

I've been working on the JMS support for a few weeks now and I think I'm

ready to go public with it to find out your opinion. So far, I got Mark
to volunteer to look at the code, make suggestions and possibly
contribute some code. If anybody is interested to look at it as well,
just drop me a mail, I'll be happy to forward what I have so far to you.

I'm not only interested in the feedback about the code, but would like
to hear opinions on what we should include and what not. The API for
messaging is huge, well, big. The challenge is to try and put as much
functionality as possible, but at the same token, try not to make it
look complex.

Here's the list of things I've implemented:

1. Templates for publish/subscribe and point-to-point messaging. I did
include support for both durable and non-durable messaging. 2. The
consumers will be able to not only create messages, but also will

have some control over how they will be delivered. I.e. modify default
delivery mode, priority, time to live. 3. Message listeners will be
instrumental in automatically registering beans as subscribers to topics
and queues.

I left out support for the transacted sessions. Sessions created are all
set to "no-transaction" and "auto-ACK". Is this something we would like
to see in the framework or should we just keep it simple for now ? The
more suggestions I get now, the better, so please open the flood gate.
:)

Thanks,

Andre.

>From: "Rod Johnson" <rod...@in...>
>To: <spr...@li...>
>CC: "Andre Biryukov" <and...@ho...>
>Subject: Re: [Springframework-developer] JMS brainstorming
>Date: Thu, 26 Feb 2004 06:35:33 -0000
>
>Rong
>
>JMS support is in the works, and should make 1.1.
>
>Andre Biryukov is currently working on this, and should be joining the=20
>Spring team soon.
>
>Andre, if you want to share your work in progress with the Spring dev=20
>list (or with Rong directly), now would be a good time :-)
>
>Regards,
>Rod
>
>----- Original Message -----
>From: "Ou, Rong" <Ro...@sa...>
>To: <spr...@li...>
>Sent: Tuesday, February 24, 2004 9:44 PM
>Subject: [Springframework-developer] JMS brainstorming
>
>
>Hi all,
>
>We currently have a project that does a lot of JMS messaging, and we=20
>desperately need an API to simplify the interface layer to JMS. I heard

>rumors that JMS support will be added to Spring 1.1, but we just can't=20
>wait that long. So I am thinking about doing something in the interim.=20
>Who knows, if it comes out good, maybe I can contribute the code back.
>
>In Rod's book there is only a couple of pages that briefly touches upon

>JMS. I looked at the interface21 code, the JMS portion is also pretty
>simplistic.
>I understand Spring has evolved a lot since the interface21 days. So to
all
>you experienced Spring'ers, if you were to add JMS support today, what=20
>would you do? I am still fairly new to Spring, so any suggestions and=20
>help
are
>welcome.
>
>Thanks,
>
>Rong
>
>
>-------------------------------------------------------
>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
>Build and deploy apps & Web services for Linux with
>a free DVD software kit from IBM. Click Now!=20
>http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
>_______________________________________________
>Springframework-developer mailing list=20
>Spr...@li...
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>

_________________________________________________________________
Stay informed on Election 2004 and the race to Super Tuesday.
http://special.msn.com/msn/election2004.armx



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Darren D. <da...@da...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 02 March 2004 17:49, Mark Pollack wrote:

> In anycase, hiding the differences in client code between queues/topics
> is still a good idea... This is one of the main selling points of the
> commons messenger, http://jakarta.apache.org/commons/sandbox/messenger/
> How do people feel about a similar approach on top of 1.0, maybe even
> wrapping a 1.1 API on top of a 1.0.2 implementation....that might
> actually be possible from the API point of view.

+1

I think that would be the right direction to try to go.

=2D --=20

Darren Davison
Public Key: http://www.davison.uk.net/key.jsp
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFARNwgKLMLAN01aw0RAk9pAJ0Q0WofYiz9C+vZkWzS8dAeiYUwCgCfcfjC
L4eHSeDymliBBCIZfrE/OFM=3D
=3D3Eqo
=2D----END PGP SIGNATURE-----

Re: [Springframework-developer] JMS brainstorming

[Rod J. <rod...@in...>]

+1, i think this is a nice idea, and consistent with the Spring value
proposition
----- Original Message -----
From: "Darren Davison" <da...@da...>
To: <spr...@li...>
Sent: Tuesday, March 02, 2004 7:10 PM
Subject: Re: [Springframework-developer] JMS brainstorming


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 02 March 2004 17:49, Mark Pollack wrote:

> In anycase, hiding the differences in client code between queues/topics
> is still a good idea... This is one of the main selling points of the
> commons messenger, http://jakarta.apache.org/commons/sandbox/messenger/
> How do people feel about a similar approach on top of 1.0, maybe even
> wrapping a 1.1 API on top of a 1.0.2 implementation....that might
> actually be possible from the API point of view.

+1

I think that would be the right direction to try to go.

- --

Darren Davison
Public Key: http://www.davison.uk.net/key.jsp
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFARNwgKLMLAN01aw0RAk9pAJ0Q0WofYiz9C+vZkWzS8dAeiYUwCgCfcfjC
L4eHSeDymliBBCIZfrE/OFM=
=3Eqo
-----END PGP SIGNATURE-----


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id56&alloc_id438&op=ick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] JMS brainstorming

[Dmitriy K. <dko...@ru...>]

+1 for sandbox

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
Alef Arendsen
Sent: Thursday, February 26, 2004 12:07 PM
To: spr...@li...;
rod...@in...
Subject: RE: [Springframework-developer] JMS brainstorming


I'd be interested in having look...

Maybe it's an idea to publish the code in the sandbox for now?

Alef


> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On=20
> Behalf Of Andre Biryukov
> Sent: Thursday, February 26, 2004 5:46 PM
> To: rod...@in...; springframework-=20
> dev...@li...
> Subject: Re: [Springframework-developer] JMS brainstorming
>=20
> Hi Rod, Hi All,
>=20
> I've been working on the JMS support for a few weeks now and I think=20
> I'm ready to go public with it to find out your opinion. So far, I got =

> Mark to volunteer to look at the code, make suggestions and possibly=20
> contribute some code. If anybody is interested to look at it as well,=20
> just drop me a mail, I'll be happy to forward what I have so far to=20
> you.
>=20
> I'm not only interested in the feedback about the code, but would like =

> to hear opinions on what we should include and what not. The API for=20
> messaging is huge, well, big. The challenge is to try and put as much=20
> functionality as
> possible, but at the same token, try not to make it look complex.
>=20
> Here's the list of things I've implemented:
>=20
> 1. Templates for publish/subscribe and point-to-point messaging. I did =

> include support for both durable and non-durable messaging. 2. The=20
> consumers will be able to not only create messages, but also will have =

> some control over how they will be delivered. I.e. modify default=20
> delivery mode, priority, time to live. 3. Message listeners will be=20
> instrumental in automatically registering beans
> as subscribers to topics and queues.
>=20
> I left out support for the transacted sessions. Sessions created are=20
> all set to "no-transaction" and "auto-ACK". Is this something we would =

> like to see in the framework or should we just keep it simple for now=20
> ? The more suggestions I get now, the better, so please open the flood =

> gate. :)
>=20
> Thanks,
>=20
> Andre.
>=20
> >From: "Rod Johnson" <rod...@in...>
> >To: <spr...@li...>
> >CC: "Andre Biryukov" <and...@ho...>
> >Subject: Re: [Springframework-developer] JMS brainstorming
> >Date: Thu, 26 Feb 2004 06:35:33 -0000
> >
> >Rong
> >
> >JMS support is in the works, and should make 1.1.
> >
> >Andre Biryukov is currently working on this, and should be joining=20
> >the Spring team soon.
> >
> >Andre, if you want to share your work in progress with the Spring dev
> list
> >(or with Rong directly), now would be a good time :-)
> >
> >Regards,
> >Rod
> >
> >----- Original Message -----
> >From: "Ou, Rong" <Ro...@sa...>
> >To: <spr...@li...>
> >Sent: Tuesday, February 24, 2004 9:44 PM
> >Subject: [Springframework-developer] JMS brainstorming
> >
> >
> >Hi all,
> >
> >We currently have a project that does a lot of JMS messaging, and we=20
> >desperately need an API to simplify the interface layer to JMS. I=20
> >heard rumors that JMS support will be added to Spring 1.1, but we=20
> >just can't
> wait
> >that long. So I am thinking about doing something in the interim. Who =

> >knows, if it comes out good, maybe I can contribute the code back.
> >
> >In Rod's book there is only a couple of pages that briefly touches=20
> >upon JMS. I looked at the interface21 code, the JMS portion is also=20
> >pretty simplistic.
> >I understand Spring has evolved a lot since the interface21 days. So =
to
> all
> >you experienced Spring'ers, if you were to add JMS support today,=20
> >what would you do? I am still fairly new to Spring, so any=20
> >suggestions and help are welcome.
> >
> >Thanks,
> >
> >Rong
> >
> >
> >-------------------------------------------------------
> >SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and=20
> >deploy apps & Web services for Linux with a free DVD software kit=20
> >from IBM. Click Now! =
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> =
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
>=20
> _________________________________________________________________
> Stay informed on Election 2004 and the race to Super Tuesday.=20
> http://special.msn.com/msn/election2004.armx
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and=20
> deploy apps & Web services for Linux with a free DVD software kit from =

> IBM. Click Now! =
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] JMS brainstorming

[Ou, R. <Ro...@sa...>]

+1 for sandbox



> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
> On Behalf
> Of Dmitriy Kopylenko
> Sent: Thursday, February 26, 2004 11:23 AM
> To: spr...@li...
> Subject: RE: [Springframework-developer] JMS brainstorming
>=20
>=20
> +1 for sandbox
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
>  On Behalf Of
> Alef Arendsen
> Sent: Thursday, February 26, 2004 12:07 PM
> To: spr...@li...;
> rod...@in...
> Subject: RE: [Springframework-developer] JMS brainstorming
>=20
>=20
> I'd be interested in having look...
>=20
> Maybe it's an idea to publish the code in the sandbox for now?
>=20
> Alef
>=20
>=20
> > -----Original Message-----
> > From: spr...@li...
> > [mailto:spr...@li...] On=20
> > Behalf Of Andre Biryukov
> > Sent: Thursday, February 26, 2004 5:46 PM
> > To: rod...@in...; springframework-=20
> > dev...@li...
> > Subject: Re: [Springframework-developer] JMS brainstorming
> >=20
> > Hi Rod, Hi All,
> >=20
> > I've been working on the JMS support for a few weeks now=20
> and I think=20
> > I'm ready to go public with it to find out your opinion. So=20
> far, I got=20
> > Mark to volunteer to look at the code, make suggestions and=20
> possibly=20
> > contribute some code. If anybody is interested to look at=20
> it as well,=20
> > just drop me a mail, I'll be happy to forward what I have so far to=20
> > you.
> >=20
> > I'm not only interested in the feedback about the code, but=20
> would like=20
> > to hear opinions on what we should include and what not.=20
> The API for=20
> > messaging is huge, well, big. The challenge is to try and=20
> put as much=20
> > functionality as
> > possible, but at the same token, try not to make it look complex.
> >=20
> > Here's the list of things I've implemented:
> >=20
> > 1. Templates for publish/subscribe and point-to-point=20
> messaging. I did=20
> > include support for both durable and non-durable messaging. 2. The=20
> > consumers will be able to not only create messages, but=20
> also will have=20
> > some control over how they will be delivered. I.e. modify default=20
> > delivery mode, priority, time to live. 3. Message listeners will be=20
> > instrumental in automatically registering beans
> > as subscribers to topics and queues.
> >=20
> > I left out support for the transacted sessions. Sessions=20
> created are=20
> > all set to "no-transaction" and "auto-ACK". Is this=20
> something we would=20
> > like to see in the framework or should we just keep it=20
> simple for now=20
> > ? The more suggestions I get now, the better, so please=20
> open the flood=20
> > gate. :)
> >=20
> > Thanks,
> >=20
> > Andre.
> >=20
> > >From: "Rod Johnson" <rod...@in...>
> > >To: <spr...@li...>
> > >CC: "Andre Biryukov" <and...@ho...>
> > >Subject: Re: [Springframework-developer] JMS brainstorming
> > >Date: Thu, 26 Feb 2004 06:35:33 -0000
> > >
> > >Rong
> > >
> > >JMS support is in the works, and should make 1.1.
> > >
> > >Andre Biryukov is currently working on this, and should be joining=20
> > >the Spring team soon.
> > >
> > >Andre, if you want to share your work in progress with the=20
> Spring dev
> > list
> > >(or with Rong directly), now would be a good time :-)
> > >
> > >Regards,
> > >Rod
> > >
> > >----- Original Message -----
> > >From: "Ou, Rong" <Ro...@sa...>
> > >To: <spr...@li...>
> > >Sent: Tuesday, February 24, 2004 9:44 PM
> > >Subject: [Springframework-developer] JMS brainstorming
> > >
> > >
> > >Hi all,
> > >
> > >We currently have a project that does a lot of JMS=20
> messaging, and we=20
> > >desperately need an API to simplify the interface layer to JMS. I=20
> > >heard rumors that JMS support will be added to Spring 1.1, but we=20
> > >just can't
> > wait
> > >that long. So I am thinking about doing something in the=20
> interim. Who=20
> > >knows, if it comes out good, maybe I can contribute the code back.
> > >
> > >In Rod's book there is only a couple of pages that briefly touches=20
> > >upon JMS. I looked at the interface21 code, the JMS=20
> portion is also=20
> > >pretty simplistic.
> > >I understand Spring has evolved a lot since the=20
> interface21 days. So to
> > all
> > >you experienced Spring'ers, if you were to add JMS support today,=20
> > >what would you do? I am still fairly new to Spring, so any=20
> > >suggestions and help are welcome.
> > >
> > >Thanks,
> > >
> > >Rong
> > >
> > >
> > >-------------------------------------------------------
> > >SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and=20
> > >deploy apps & Web services for Linux with a free DVD software kit=20
> > >from IBM. Click Now!=20
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> =
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
>=20
> _________________________________________________________________
> Stay informed on Election 2004 and the race to Super Tuesday.=20
> http://special.msn.com/msn/election2004.armx
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and=20
> deploy apps & Web services for Linux with a free DVD software kit from =

> IBM. Click Now! =
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[<jue...@we...>]

+1 for sandbox too, already using org.springframework.jms as package =
name. I generally recommend putting code contributions to the sandbox =
for the time being, moving them to the main Spring source tree when the =
time is right.
=20
Juergen
=20

________________________________

Von: spr...@li... im Auftrag =
von Dmitriy Kopylenko
Gesendet: Do 26.02.2004 18:22
An: spr...@li...
Betreff: RE: [Springframework-developer] JMS brainstorming



+1 for sandbox

-----Original Message-----
From: spr...@li...
[mailto:spr...@li...] On Behalf =
Of
Alef Arendsen
Sent: Thursday, February 26, 2004 12:07 PM
To: spr...@li...;
rod...@in...
Subject: RE: [Springframework-developer] JMS brainstorming


I'd be interested in having look...

Maybe it's an idea to publish the code in the sandbox for now?

Alef


> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On
> Behalf Of Andre Biryukov
> Sent: Thursday, February 26, 2004 5:46 PM
> To: rod...@in...; springframework-
> dev...@li...
> Subject: Re: [Springframework-developer] JMS brainstorming
>
> Hi Rod, Hi All,
>
> I've been working on the JMS support for a few weeks now and I think
> I'm ready to go public with it to find out your opinion. So far, I got
> Mark to volunteer to look at the code, make suggestions and possibly
> contribute some code. If anybody is interested to look at it as well,
> just drop me a mail, I'll be happy to forward what I have so far to
> you.
>
> I'm not only interested in the feedback about the code, but would like
> to hear opinions on what we should include and what not. The API for
> messaging is huge, well, big. The challenge is to try and put as much
> functionality as
> possible, but at the same token, try not to make it look complex.
>
> Here's the list of things I've implemented:
>
> 1. Templates for publish/subscribe and point-to-point messaging. I did
> include support for both durable and non-durable messaging. 2. The
> consumers will be able to not only create messages, but also will have
> some control over how they will be delivered. I.e. modify default
> delivery mode, priority, time to live. 3. Message listeners will be
> instrumental in automatically registering beans
> as subscribers to topics and queues.
>
> I left out support for the transacted sessions. Sessions created are
> all set to "no-transaction" and "auto-ACK". Is this something we would
> like to see in the framework or should we just keep it simple for now
> ? The more suggestions I get now, the better, so please open the flood
> gate. :)
>
> Thanks,
>
> Andre.
>
> >From: "Rod Johnson" <rod...@in...>
> >To: <spr...@li...>
> >CC: "Andre Biryukov" <and...@ho...>
> >Subject: Re: [Springframework-developer] JMS brainstorming
> >Date: Thu, 26 Feb 2004 06:35:33 -0000
> >
> >Rong
> >
> >JMS support is in the works, and should make 1.1.
> >
> >Andre Biryukov is currently working on this, and should be joining
> >the Spring team soon.
> >
> >Andre, if you want to share your work in progress with the Spring dev
> list
> >(or with Rong directly), now would be a good time :-)
> >
> >Regards,
> >Rod
> >
> >----- Original Message -----
> >From: "Ou, Rong" <Ro...@sa...>
> >To: <spr...@li...>
> >Sent: Tuesday, February 24, 2004 9:44 PM
> >Subject: [Springframework-developer] JMS brainstorming
> >
> >
> >Hi all,
> >
> >We currently have a project that does a lot of JMS messaging, and we
> >desperately need an API to simplify the interface layer to JMS. I
> >heard rumors that JMS support will be added to Spring 1.1, but we
> >just can't
> wait
> >that long. So I am thinking about doing something in the interim. Who
> >knows, if it comes out good, maybe I can contribute the code back.
> >
> >In Rod's book there is only a couple of pages that briefly touches
> >upon JMS. I looked at the interface21 code, the JMS portion is also
> >pretty simplistic.
> >I understand Spring has evolved a lot since the interface21 days. So =
to
> all
> >you experienced Spring'ers, if you were to add JMS support today,
> >what would you do? I am still fairly new to Spring, so any
> >suggestions and help are welcome.
> >
> >Thanks,
> >
> >Rong
> >
> >
> >-------------------------------------------------------
> >SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and
> >deploy apps & Web services for Linux with a free DVD software kit
> >from IBM. Click Now! =
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> >_______________________________________________
> >Springframework-developer mailing list
> >Spr...@li...
> =
>https://lists.sourceforge.net/lists/listinfo/springframework-developer
> >
> >
>
> _________________________________________________________________
> Stay informed on Election 2004 and the race to Super Tuesday.
> http://special.msn.com/msn/election2004.armx
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and
> deploy apps & Web services for Linux with a free DVD software kit from
> IBM. Click Now! =
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Ross M. <ro...@at...>]

+1
I've done a lot of work in the past with messaging (my previous employer=20
was a Jms Provider) I would be interested in seeing the code and helping=20
out.

j=FCrgen h=F6ller [werk3AT] wrote:

> +1 for sandbox too, already using org.springframework.jms as package na=
me. I generally recommend putting code contributions to the sandbox for t=
he time being, moving them to the main Spring source tree when the time i=
s right.
> =20
> Juergen
> =20
>=20
> ________________________________
>=20
> Von: spr...@li... im Auftrag v=
on Dmitriy Kopylenko
> Gesendet: Do 26.02.2004 18:22
> An: spr...@li...
> Betreff: RE: [Springframework-developer] JMS brainstorming
>=20
>=20
>=20
> +1 for sandbox
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...] On Behal=
f Of
> Alef Arendsen
> Sent: Thursday, February 26, 2004 12:07 PM
> To: spr...@li...;
> rod...@in...
> Subject: RE: [Springframework-developer] JMS brainstorming
>=20
>=20
> I'd be interested in having look...
>=20
> Maybe it's an idea to publish the code in the sandbox for now?
>=20
> Alef
>=20
>=20
>=20
>>-----Original Message-----
>>From: spr...@li...
>>[mailto:spr...@li...] On
>>Behalf Of Andre Biryukov
>>Sent: Thursday, February 26, 2004 5:46 PM
>>To: rod...@in...; springframework-
>>dev...@li...
>>Subject: Re: [Springframework-developer] JMS brainstorming
>>
>>Hi Rod, Hi All,
>>
>>I've been working on the JMS support for a few weeks now and I think
>>I'm ready to go public with it to find out your opinion. So far, I got
>>Mark to volunteer to look at the code, make suggestions and possibly
>>contribute some code. If anybody is interested to look at it as well,
>>just drop me a mail, I'll be happy to forward what I have so far to
>>you.
>>
>>I'm not only interested in the feedback about the code, but would like
>>to hear opinions on what we should include and what not. The API for
>>messaging is huge, well, big. The challenge is to try and put as much
>>functionality as
>>possible, but at the same token, try not to make it look complex.
>>
>>Here's the list of things I've implemented:
>>
>>1. Templates for publish/subscribe and point-to-point messaging. I did
>>include support for both durable and non-durable messaging. 2. The
>>consumers will be able to not only create messages, but also will have
>>some control over how they will be delivered. I.e. modify default
>>delivery mode, priority, time to live. 3. Message listeners will be
>>instrumental in automatically registering beans
>>as subscribers to topics and queues.
>>
>>I left out support for the transacted sessions. Sessions created are
>>all set to "no-transaction" and "auto-ACK". Is this something we would
>>like to see in the framework or should we just keep it simple for now
>>? The more suggestions I get now, the better, so please open the flood
>>gate. :)
>>
>>Thanks,
>>
>>Andre.
>>
>>
>>>From: "Rod Johnson" <rod...@in...>
>>>To: <spr...@li...>
>>>CC: "Andre Biryukov" <and...@ho...>
>>>Subject: Re: [Springframework-developer] JMS brainstorming
>>>Date: Thu, 26 Feb 2004 06:35:33 -0000
>>>
>>>Rong
>>>
>>>JMS support is in the works, and should make 1.1.
>>>
>>>Andre Biryukov is currently working on this, and should be joining
>>>the Spring team soon.
>>>
>>>Andre, if you want to share your work in progress with the Spring dev
>>
>>list
>>
>>>(or with Rong directly), now would be a good time :-)
>>>
>>>Regards,
>>>Rod
>>>
>>>----- Original Message -----
>>>From: "Ou, Rong" <Ro...@sa...>
>>>To: <spr...@li...>
>>>Sent: Tuesday, February 24, 2004 9:44 PM
>>>Subject: [Springframework-developer] JMS brainstorming
>>>
>>>
>>>Hi all,
>>>
>>>We currently have a project that does a lot of JMS messaging, and we
>>>desperately need an API to simplify the interface layer to JMS. I
>>>heard rumors that JMS support will be added to Spring 1.1, but we
>>>just can't
>>
>>wait
>>
>>>that long. So I am thinking about doing something in the interim. Who
>>>knows, if it comes out good, maybe I can contribute the code back.
>>>
>>>In Rod's book there is only a couple of pages that briefly touches
>>>upon JMS. I looked at the interface21 code, the JMS portion is also
>>>pretty simplistic.
>>>I understand Spring has evolved a lot since the interface21 days. So t=
o
>>
>>all
>>
>>>you experienced Spring'ers, if you were to add JMS support today,
>>>what would you do? I am still fairly new to Spring, so any
>>>suggestions and help are welcome.
>>>
>>>Thanks,
>>>
>>>Rong
>>>
>>>
>>>-------------------------------------------------------
>>>SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and
>>>deploy apps & Web services for Linux with a free DVD software kit
>>
>>>from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3D=
ick
>>
>>>_______________________________________________
>>>Springframework-developer mailing list
>>>Spr...@li...
>>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>>>
>>>
>>
>>_________________________________________________________________
>>Stay informed on Election 2004 and the race to Super Tuesday.
>>http://special.msn.com/msn/election2004.armx
>>
>>
>>
>>-------------------------------------------------------
>>SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and
>>deploy apps & Web services for Linux with a free DVD software kit from
>>IBM. Click Now! http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3D=
click
>>_______________________________________________
>>Springframework-developer mailing list
>>Spr...@li...
>>https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=CCk
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20

RE: [Springframework-developer] JMS brainstorming

[Ou, R. <Ro...@sa...>]

That sounds great! We also have need to support stanadalone jms =
applications. Other items on your list would be of interest to us too.=20

Is there any chance we can see the code?

Thanks,

Rong

> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
> On Behalf
> Of Mark Pollack
> Sent: Friday, February 27, 2004 5:12 AM
> To: spr...@li...
> Subject: Re: [Springframework-developer] JMS brainstorming
>=20
>=20
> Hi everyone,
>=20
> I'll look over the code this weekend...on a little vacation now.
> Anyway, sounds good so far.  I'm in the middle of discussing=20
> donating JMS
> code we developed at our company...
>=20
> Some of the larger items are:
>=20
> 1. A very efficient implementation of the JMS selector for use on
> MapMessages, or really anything else you like, hashtables, even text
> messages.  Based on JavaCC. This externalized the ugly switch=20
> statements
> that you typically have to do in the main callback function.
>=20
> 2. We have a 'standalone' jms application, not in an=20
> appserver.  We added
> some server like infrastructure classes to spring start up the
> connections, sessions, etc., after all the bean=20
> initialization.  There are
> corresponding classes to handle setting up all the JMS=20
> specific stuff...tx
> session, what ack mode, etc.  Vendors also make extensions to=20
> the standard
> modes that we should account for...
>=20
> 3. Much like the templates for jdbc etc. there is a bunch of=20
> surrounding
> code to handle exceptions correctly, also having a seperate method for
> "onDuplicate" based on the JMSHeader value is nice.
>=20
> 4. A 'pipe and filters' style processing framwork.  Similar=20
> to what you
> might see in apache axis, but not specific to soap or jms. =20
> It it based on
> the reactor design pattern to pick off the appropriate=20
> processing chain to
> execute based on the evaluation of a JMS selector string that=20
> applies to
> the message body (not the header).  It then iterates through various
> 'process' template methods of modules in the chain..=20
> exceptions result in
> rolling back, that is calling 'rollback' up the chain and finally to a
> exceptionhandler.  This is all externalized in a config file.=20
>  I'm sure
> there might be temptations to compare to other workflow like=20
> projects...
> but this codebase is really pretty simple and has been=20
> extremely useful to
> us for a number of years....  It really also apply outside=20
> the messaging
> area...
>=20
> 5. Some pretty print utilities for messages, xml=20
> marhsaller/unmarshaller.=20
> This is part of my conversion/rewrite/refactoring of=20
> 'rvtest.sf.net (JUnit
> for TIBCO Rendezvous to JMS) I'll be releasing that code on=20
> sf but we can
> pick and choose little things that might be useful...
>=20
> I'm pretty sure most I can integrate most of the items on=20
> this list to the
> effort.
>=20
>=20
> Cheers,
> Mark
>=20
>=20
>=20
> > Hi Rod, Hi All,
> >
> > I've been working on the JMS support for a few weeks now=20
> and I think I'm
> > ready to go public with it to find out your opinion. So=20
> far, I got Mark to
> > volunteer to look at the code, make suggestions and=20
> possibly contribute
> > some
> > code. If anybody is interested to look at it as well, just=20
> drop me a mail,
> > I'll be happy to forward what I have so far to you.
> >
> > I'm not only interested in the feedback about the code, but=20
> would like to
> > hear opinions on what we should include and what not. The API for
> > messaging
> > is huge, well, big. The challenge is to try and put as much=20
> functionality
> > as
> > possible, but at the same token, try not to make it look complex.
> >
> > Here's the list of things I've implemented:
> >
> > 1. Templates for publish/subscribe and point-to-point=20
> messaging. I did
> > include support for both durable and non-durable messaging.
> > 2. The consumers will be able to not only create messages,=20
> but also will
> > have some control over how they will be delivered. I.e.=20
> modify default
> > delivery mode, priority, time to live.
> > 3. Message listeners will be instrumental in automatically=20
> registering
> > beans
> > as subscribers to topics and queues.
> >
> > I left out support for the transacted sessions. Sessions=20
> created are all
> > set
> > to "no-transaction" and "auto-ACK". Is this something we=20
> would like to see
> > in the framework or should we just keep it simple for now ? The more
> > suggestions I get now, the better, so please open the flood gate. :)
> >
> > Thanks,
> >
> > Andre.
> >
> >>From: "Rod Johnson" <rod...@in...>
> >>To: <spr...@li...>
> >>CC: "Andre Biryukov" <and...@ho...>
> >>Subject: Re: [Springframework-developer] JMS brainstorming
> >>Date: Thu, 26 Feb 2004 06:35:33 -0000
> >>
> >>Rong
> >>
> >>JMS support is in the works, and should make 1.1.
> >>
> >>Andre Biryukov is currently working on this, and should be=20
> joining the
> >>Spring team soon.
> >>
> >>Andre, if you want to share your work in progress with the=20
> Spring dev
> >> list
> >>(or with Rong directly), now would be a good time :-)
> >>
> >>Regards,
> >>Rod
> >>
> >>----- Original Message -----
> >>From: "Ou, Rong" <Ro...@sa...>
> >>To: <spr...@li...>
> >>Sent: Tuesday, February 24, 2004 9:44 PM
> >>Subject: [Springframework-developer] JMS brainstorming
> >>
> >>
> >>Hi all,
> >>
> >>We currently have a project that does a lot of JMS messaging, and we
> >>desperately need an API to simplify the interface layer to=20
> JMS. I heard
> >>rumors that JMS support will be added to Spring 1.1, but we=20
> just can't
> >> wait
> >>that long. So I am thinking about doing something in the=20
> interim. Who
> >>knows,
> >>if it comes out good, maybe I can contribute the code back.
> >>
> >>In Rod's book there is only a couple of pages that briefly=20
> touches upon
> >>JMS.
> >>I looked at the interface21 code, the JMS portion is also pretty
> >>simplistic.
> >>I understand Spring has evolved a lot since the interface21=20
> days. So to
> >> all
> >>you experienced Spring'ers, if you were to add JMS support=20
> today, what
> >>would
> >>you do? I am still fairly new to Spring, so any suggestions=20
> and help are
> >>welcome.
> >>
> >>Thanks,
> >>
> >>Rong
> >>
> >>
> >>-------------------------------------------------------
> >>SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> >>Build and deploy apps & Web services for Linux with
> >>a free DVD software kit from IBM. Click Now!
> >>http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> >>_______________________________________________
> >>Springframework-developer mailing list
> >>Spr...@li...
> >>https://lists.sourceforge.net/lists/listinfo/springframework
-developer
>>
>>
>
> _________________________________________________________________
> Stay informed on Election 2004 and the race to Super Tuesday.
> http://special.msn.com/msn/election2004.armx
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

RE: [Springframework-developer] JMS brainstorming

[Ou, R. <Ro...@sa...>]

As far as I know, JBoss 3.x.x is still on JMS 1.0.2. Since JBoss is our =
current development platform, I'd have to vote against dropping JMS =
1.0.2 support.

Rong

> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
> On Behalf
> Of Mark Pollack
> Sent: Monday, March 01, 2004 6:03 PM
> To: spr...@li...
> Subject: RE: [Springframework-developer] JMS brainstorming
>=20
>=20
> Hi,
>=20
> I've added Andre's code into the sandbox. =20
>=20
> I'd like to get some input on the following.... Can we count on using
> the JMS 1.1 API or should we be compatible with the JMS 1.0.2 API? The
> reason is that JMS 1.1 introduced "domain unification", meaning that
> there the classes are no longer split into "Queue" and "Topic" class
> hierarchies.  The code can now refer to a "ConnectionFactory"=20
> instead of
> it being a "QueueConnectionFactory" or a=20
> "TopicConnectionFactory".  This
> applies up and down the class hierarchy since the split is rather high
> level.  The end result is that using the JMS 1.1 api makes the client
> code much easier to use since there is less obvious=20
> duplication.  Other
> advantages can be read in the spec...such as being able to use  queues
> and topics in the same transaction (probably since they now can share
> the same Session object).
>=20
> The templates now are written using the 1.0.2 style classes, which I
> haven't used in a long time....but I'd like to hear what people are
> using considering how much it will affect the shape of the=20
> code...  I'd
> vote for dropping 1.0.2 support.
>=20
> Cheers,
> Mark
>=20
>=20
>=20
> -----Original Message-----
> From: spr...@li...
> [mailto:spr...@li...]
>  On Behalf
> Of Andre Biryukov
> Sent: Thursday, February 26, 2004 11:46 AM
> To: rod...@in...;
> spr...@li...
> Subject: Re: [Springframework-developer] JMS brainstorming
>=20
>=20
> Hi Rod, Hi All,
>=20
> I've been working on the JMS support for a few weeks now and=20
> I think I'm
>=20
> ready to go public with it to find out your opinion. So far,=20
> I got Mark
> to=20
> volunteer to look at the code, make suggestions and possibly=20
> contribute
> some=20
> code. If anybody is interested to look at it as well, just drop me a
> mail,=20
> I'll be happy to forward what I have so far to you.
>=20
> I'm not only interested in the feedback about the code, but would like
> to=20
> hear opinions on what we should include and what not. The API for
> messaging=20
> is huge, well, big. The challenge is to try and put as much
> functionality as=20
> possible, but at the same token, try not to make it look complex.
>=20
> Here's the list of things I've implemented:
>=20
> 1. Templates for publish/subscribe and point-to-point=20
> messaging. I did=20
> include support for both durable and non-durable messaging.
> 2. The consumers will be able to not only create messages,=20
> but also will
>=20
> have some control over how they will be delivered. I.e.=20
> modify default=20
> delivery mode, priority, time to live.
> 3. Message listeners will be instrumental in automatically registering
> beans=20
> as subscribers to topics and queues.
>=20
> I left out support for the transacted sessions. Sessions=20
> created are all
> set=20
> to "no-transaction" and "auto-ACK". Is this something we would like to
> see=20
> in the framework or should we just keep it simple for now ? The more=20
> suggestions I get now, the better, so please open the flood gate. :)
>=20
> Thanks,
>=20
> Andre.
>=20
> >From: "Rod Johnson" <rod...@in...>
> >To: <spr...@li...>
> >CC: "Andre Biryukov" <and...@ho...>
> >Subject: Re: [Springframework-developer] JMS brainstorming
> >Date: Thu, 26 Feb 2004 06:35:33 -0000
> >
> >Rong
> >
> >JMS support is in the works, and should make 1.1.
> >
> >Andre Biryukov is currently working on this, and should be=20
> joining the=20
> >Spring team soon.
> >
> >Andre, if you want to share your work in progress with the=20
> Spring dev=20
> >list (or with Rong directly), now would be a good time :-)
> >
> >Regards,
> >Rod
> >
> >----- Original Message -----
> >From: "Ou, Rong" <Ro...@sa...>
> >To: <spr...@li...>
> >Sent: Tuesday, February 24, 2004 9:44 PM
> >Subject: [Springframework-developer] JMS brainstorming
> >
> >
> >Hi all,
> >
> >We currently have a project that does a lot of JMS messaging, and we=20
> >desperately need an API to simplify the interface layer to=20
> JMS. I heard
>=20
> >rumors that JMS support will be added to Spring 1.1, but we=20
> just can't=20
> >wait that long. So I am thinking about doing something in=20
> the interim.=20
> >Who knows, if it comes out good, maybe I can contribute the=20
> code back.
> >
> >In Rod's book there is only a couple of pages that briefly=20
> touches upon
> >JMS.
> >I looked at the interface21 code, the JMS portion is also pretty=20
> >simplistic.
> >I understand Spring has evolved a lot since the interface21=20
> days. So to
> all
> >you experienced Spring'ers, if you were to add JMS support=20
> today, what=20
> >would
> >you do? I am still fairly new to Spring, so any suggestions and help
> are
> >welcome.
> >
> >Thanks,
> >
> >Rong
> >
> >
> >-------------------------------------------------------
> >SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> >Build and deploy apps & Web services for Linux with
> >a free DVD software kit from IBM. Click Now!=20
> >http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> >_______________________________________________
> >Springframework-developer mailing list=20
> >Spr...@li...
> >https://lists.sourceforge.net/lists/listinfo/springframework-
developer
>
>

_________________________________________________________________
Stay informed on Election 2004 and the race to Super Tuesday.=20
http://special.msn.com/msn/election2004.armx



-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
_______________________________________________
Springframework-developer mailing list
Spr...@li...
https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Daniel P. <po...@ci...>]

We're still using JMS 1.0.2 (Websphere 4.0.6).  I'd vote against
dropping 1.0.2 support as well.

Daniel

On Tue, Mar 02, 2004 at 10:38:53AM -0600, Ou, Rong wrote:
> As far as I know, JBoss 3.x.x is still on JMS 1.0.2. Since JBoss is our c=
urrent development platform, I'd have to vote against dropping JMS 1.0.2 su=
pport.
>=20
> Rong
>=20
> > -----Original Message-----
> > From: spr...@li...
> > [mailto:spr...@li...]
> > On Behalf
> > Of Mark Pollack
> > Sent: Monday, March 01, 2004 6:03 PM
> > To: spr...@li...
> > Subject: RE: [Springframework-developer] JMS brainstorming
> >=20
> >=20
> > Hi,
> >=20
> > I've added Andre's code into the sandbox. =20
> >=20
> > I'd like to get some input on the following.... Can we count on using
> > the JMS 1.1 API or should we be compatible with the JMS 1.0.2 API? The
> > reason is that JMS 1.1 introduced "domain unification", meaning that
> > there the classes are no longer split into "Queue" and "Topic" class
> > hierarchies.  The code can now refer to a "ConnectionFactory"=20
> > instead of
> > it being a "QueueConnectionFactory" or a=20
> > "TopicConnectionFactory".  This
> > applies up and down the class hierarchy since the split is rather high
> > level.  The end result is that using the JMS 1.1 api makes the client
> > code much easier to use since there is less obvious=20
> > duplication.  Other
> > advantages can be read in the spec...such as being able to use  queues
> > and topics in the same transaction (probably since they now can share
> > the same Session object).
> >=20
> > The templates now are written using the 1.0.2 style classes, which I
> > haven't used in a long time....but I'd like to hear what people are
> > using considering how much it will affect the shape of the=20
> > code...  I'd
> > vote for dropping 1.0.2 support.
> >=20
> > Cheers,
> > Mark
> >=20
> >=20
> >=20
> > -----Original Message-----
> > From: spr...@li...
> > [mailto:spr...@li...]
> >  On Behalf
> > Of Andre Biryukov
> > Sent: Thursday, February 26, 2004 11:46 AM
> > To: rod...@in...;
> > spr...@li...
> > Subject: Re: [Springframework-developer] JMS brainstorming
> >=20
> >=20
> > Hi Rod, Hi All,
> >=20
> > I've been working on the JMS support for a few weeks now and=20
> > I think I'm
> >=20
> > ready to go public with it to find out your opinion. So far,=20
> > I got Mark
> > to=20
> > volunteer to look at the code, make suggestions and possibly=20
> > contribute
> > some=20
> > code. If anybody is interested to look at it as well, just drop me a
> > mail,=20
> > I'll be happy to forward what I have so far to you.
> >=20
> > I'm not only interested in the feedback about the code, but would like
> > to=20
> > hear opinions on what we should include and what not. The API for
> > messaging=20
> > is huge, well, big. The challenge is to try and put as much
> > functionality as=20
> > possible, but at the same token, try not to make it look complex.
> >=20
> > Here's the list of things I've implemented:
> >=20
> > 1. Templates for publish/subscribe and point-to-point=20
> > messaging. I did=20
> > include support for both durable and non-durable messaging.
> > 2. The consumers will be able to not only create messages,=20
> > but also will
> >=20
> > have some control over how they will be delivered. I.e.=20
> > modify default=20
> > delivery mode, priority, time to live.
> > 3. Message listeners will be instrumental in automatically registering
> > beans=20
> > as subscribers to topics and queues.
> >=20
> > I left out support for the transacted sessions. Sessions=20
> > created are all
> > set=20
> > to "no-transaction" and "auto-ACK". Is this something we would like to
> > see=20
> > in the framework or should we just keep it simple for now ? The more=20
> > suggestions I get now, the better, so please open the flood gate. :)
> >=20
> > Thanks,
> >=20
> > Andre.
> >=20
> > >From: "Rod Johnson" <rod...@in...>
> > >To: <spr...@li...>
> > >CC: "Andre Biryukov" <and...@ho...>
> > >Subject: Re: [Springframework-developer] JMS brainstorming
> > >Date: Thu, 26 Feb 2004 06:35:33 -0000
> > >
> > >Rong
> > >
> > >JMS support is in the works, and should make 1.1.
> > >
> > >Andre Biryukov is currently working on this, and should be=20
> > joining the=20
> > >Spring team soon.
> > >
> > >Andre, if you want to share your work in progress with the=20
> > Spring dev=20
> > >list (or with Rong directly), now would be a good time :-)
> > >
> > >Regards,
> > >Rod
> > >
> > >----- Original Message -----
> > >From: "Ou, Rong" <Ro...@sa...>
> > >To: <spr...@li...>
> > >Sent: Tuesday, February 24, 2004 9:44 PM
> > >Subject: [Springframework-developer] JMS brainstorming
> > >
> > >
> > >Hi all,
> > >
> > >We currently have a project that does a lot of JMS messaging, and we=
=20
> > >desperately need an API to simplify the interface layer to=20
> > JMS. I heard
> >=20
> > >rumors that JMS support will be added to Spring 1.1, but we=20
> > just can't=20
> > >wait that long. So I am thinking about doing something in=20
> > the interim.=20
> > >Who knows, if it comes out good, maybe I can contribute the=20
> > code back.
> > >
> > >In Rod's book there is only a couple of pages that briefly=20
> > touches upon
> > >JMS.
> > >I looked at the interface21 code, the JMS portion is also pretty=20
> > >simplistic.
> > >I understand Spring has evolved a lot since the interface21=20
> > days. So to
> > all
> > >you experienced Spring'ers, if you were to add JMS support=20
> > today, what=20
> > >would
> > >you do? I am still fairly new to Spring, so any suggestions and help
> > are
> > >welcome.
> > >
> > >Thanks,
> > >
> > >Rong
> > >
> > >
> > >-------------------------------------------------------
> > >SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> > >Build and deploy apps & Web services for Linux with
> > >a free DVD software kit from IBM. Click Now!=20
> > >http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> > >_______________________________________________
> > >Springframework-developer mailing list=20
> > >Spr...@li...
> > >https://lists.sourceforge.net/lists/listinfo/springframework-
> developer
> >
> >
>=20
> _________________________________________________________________
> Stay informed on Election 2004 and the race to Super Tuesday.=20
> http://special.msn.com/msn/election2004.armx
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=3D1356&alloc_id=3D3438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>=20
>=20
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=3Dclick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Darren D. <da...@da...>]

=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 02 March 2004 18:18, Daniel Potter wrote:
> We're still using JMS 1.0.2 (Websphere 4.0.6).  I'd vote against
> dropping 1.0.2 support as well.

blimey, another poor soul still having to cope with WAS 4.x!  I thought we=
=20
were the only ones :)

=2D --=20

Darren Davison
Public Key: http://www.davison.uk.net/key.jsp
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFARNuOKLMLAN01aw0RAhDyAJ42K4RFwAzKnNHOcQPIL1PnMRsDuACcDSYm
TqXBZ/1sTGaBt1rCv43HNAA=3D
=3DMCQt
=2D----END PGP SIGNATURE-----

Re: [Springframework-developer] JMS brainstorming

[<nem...@cm...>]

You are not the "only", we`re still have to deal with WAS 4.0.5 (used in
PROD in 17 major banks at latin America)

+1 against dropping 1.0.2 support too.


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 02 March 2004 18:18, Daniel Potter wrote:
>> We're still using JMS 1.0.2 (Websphere 4.0.6).  I'd vote against
>> dropping 1.0.2 support as well.
>
> blimey, another poor soul still having to cope with WAS 4.x!  I thought
> we  were the only ones :)
>
> - --
>
> Darren Davison
> Public Key: http://www.davison.uk.net/key.jsp
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
>
> iD8DBQFARNuOKLMLAN01aw0RAhDyAJ42K4RFwAzKnNHOcQPIL1PnMRsDuACcDSYm
> TqXBZ/1sTGaBt1rCv43HNAA=3DMCQt
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id438&op=BFick
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer

Re: [Springframework-developer] JMS brainstorming

[Lars H. <ho...@ar...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> You are not the "only", we`re still have to deal with WAS 4.0.5 (used 
> in
> PROD in 17 major banks at latin America)

Same for a major German insurer.

+1 agains dropping 1.0.2

Yours,
Lars


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQEUSOLcyzbDWnRDCEQIQ7QCgg2CG4KHx11ZfrEpiwRxycS41RqsAoJ85
SKUkDJffTAkcp53ELTa2R+AM
=TVYd
-----END PGP SIGNATURE-----

Re: [Springframework-developer] JMS brainstorming

[Lars H. <ho...@ar...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> blimey, another poor soul still having to cope with WAS 4.x!  I 
> thought we
> were the only ones :)

Nope ;-)
Welcome to the dark side :-))

Yours,
Lars


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0.3

iQA/AwUBQEUR0LcyzbDWnRDCEQKw/ACgnrSxeGirTeLRS41dxuVqz6+B6gcAn15g
2mOQA+X7Eg5aGjN/2PvKZFHf
=aHVp
-----END PGP SIGNATURE-----

RE: [Springframework-developer] JMS brainstorming

[Ou, R. <Ro...@sa...>]

+1

If you can hide the differences between 1.0.2 and 1.1 so that we can =
later upgrade to 1.1 without any code changes, that would be great!

Rong

>=20
> In anycase, hiding the differences in client code between=20
> queues/topics
> is still a good idea... This is one of the main selling points of the
> commons messenger,=20
> http://jakarta.apache.org/commons/sandbox/messenger/
> How do people feel about a similar approach on top of 1.0, maybe even
> wrapping a 1.1 API on top of a 1.0.2 implementation....that might
> actually be possible from the API point of view.
>=20
> Cheers,
> Mark
>=20