All,
The link gives lot of details; I shorten the details to focus on small details first.
The JMS API requires improving ease of
development. The suggested way is to
improve the programming model, introduce
the annotations to define behavior
and JNDI to refer to the resources.
The current API has ambiguities where it is
unclear how a JMS provider should behave
in various cases. The key goal of JMS
was to increase the portability of applications
between the JMS providers. By
hardening the specification and clarifying the ambiguities,
we are not leaving
the detailed behavior up to the vendor to define. It means, user
application written with one provider will work in the same way as with other provider.
The existing JMS specification does not
contain any information on how the JMS API should
be used by applications
running in a Java EE container. The goals should be to make it
easier for both
the user and JSM vendors to understand how the JMS API should be used in
an
application server. It could be defining a new API to allow any JMS provider to
be
integrated with any Java EE application server. Subsequent to the release of
JMS specification,
Java EE architecture has been evolved and developed. Any new
features requires by the
community can be added.
Over the years, different vendors have found
additional features which despite being
non-standard. The newly added similar features can be standardized.
I think, we can discuss how anyone can help
in this proposed specification or the need
of the Java Community.
Anyone can add details or come up with anything different to discuss.
Regards,
Faisal
So, here's the condensed list (from Faisal's + spec) that could be on our
Agenda:
- Enhancing with latest Java (and possibly Java 7) features (Annotations,
cloud etc)
- Addressing API ambiguities
- Introducing Dependency Injection & Context patterns
- Standardizing JMS and JEE interfaces
Does that sound all?
Thanks
Madhu
> Madhusudhan KondaMobile :+44 (0)7803 712271 Home :www.madhusudhan.com
>
>
>
>
> From: mukh...@gmail.com
> Date: Mon, 13 Feb 2012 20:53:54 +0000
> Subject: Re: JSR-343 Progress
> To: ljc-adop...@googlegroups.com
>
>
>
>
> I would prefer after 6 PM as well.
>
> On Mon, Feb 13, 2012 at 7:00 PM, Prasannaa <prasan...@yahoo.com> wrote:
>
>
>
>
>
> I think it would be fine if we meet after 6 PM or we can meet at
> developers session of LJC
>
> I was there last month specifically to meet other JSR members, was not
> able to meet any one from JSR-343.
>
>
>
>
>
>
> Maybe we can plan this time around, anyone for it?
>
> Cheers
> Prasannaa
>
>
>
>
>
> From: Madhusudhan Konda <kn...@hotmail.com>
>
>
>
>
>
> To: ljc-adop...@googlegroups.com
> Sent: Monday, February 13, 2012 6:47 PM
>
>
>
>
>
> Subject: RE: JSR-343 Progress
>
>
>
>
>
>
> I work at Liverpool street, London. Any where in London should be find by
> me.
>
> I would prefer a long lunch session rather than drinks though :)
>
> Regards Madhu
> Madhusudhan Konda
>
>
>
>
> Mobile :+44 (0)7803 712271 Home :www.madhusudhan.com
>
>
>
I am not saying we shouldn't touch them, only cautioning to be more
focussed. I have had experience with JCA and JMS Specs in the past - both,
esp JCA is quite dry!!
One thing I want to understand before we even think of working:
- Are we the only people who are going to work on this spec?
- There's seems to a body on the Spec (Not sure if Nigel is still leading
or not - someone confirm pl)
- What's our input into the Spec body and how are we associated? I mean
are we the development body?
What do you think?
Regarding the code, we need to checkout the JMS RI and start playing
around. Not sure of the home of source code for JMS 2.0 yet :(
So questions..questions..
>
> Thanks, Madhu.
> I'm wondering, how and where to start work for JSR?
> I noticed the _Contributions_ section. It explains;
> The listed documents, specifications or implementation that describe the
> technology are;
> JSR 914: Java Message Service (JMS) API
> http://jcp.org/en/jsr/detail?id=914Java Message Service 1.1 specification:
> http://java.sun.com/products/jms/docs.htmlOpen Message Queue:
> http://mq.java.net/GlasssFish Server, Open Source Edition:
> https://glassfish.dev.java.net/JSR 322: Java EE Connector Architecture
Yes, you've cleared my confusion, I guess :)
With respect to the way we start working, shall we pick up just one simple
task and dwell over it? Once everyone is on the ball and we have gained
enough experience on the task, possibly we could split the tasks between
us. What would you guys say?
Thanks
Madhu
> Hi All
>
> I am happy to see ppl showing some interest in JSR 343 and questions being
> raised.
>
>
>>- Are we the only people who are going to work on this spec?
>
> I guess we are not the only ones, there will be more people working
> (Oracle, IBM, RedHat ... ref :http://jcp.org/en/jsr/detail?id=343 ) on,
> and we are part of this JSR-Spec. If we get more people in this JSR we
> will have more ideas.
>
> http://jcp.org/en/jsr/detail?id=343
>
>>- There's seems to a body on the Spec (Not sure if Nigel is still leading
> or not - someone confirm pl)
>
> Lead for JMS spec is
>
> * Lead:Nigel Deakin (http://java.net/jira/browse/JMS_SPEC)
>
> �Hi Madhu
No preference from my side. Agree that we need to establish current state of the JSR before we try to contribute. My attempt at brainstorming appears to be completely off the mark.
Best regards,
Mikhail Krivoshein
Prasanna, unfortunately I can't commit to be assistant for now (may be in
few months time if one of you gets bored), but would recommend you and
Faisal to take the dual leadership role.
Guys, can we agree on this (unless someone want to be stand up - please
don't feel shy, put your hand up and stand in the election).
Here are the list of candidates - and votes next to them. Please fill in
them when you
1. Prasanna - Madhu
2. Faisal - Mukhan, Madhu
PS: Mukhan - is Faizal your first candidate?, can you spot your second
candidate too)
Thanks
Madhu
> voting for Faizal!
>
> On Fri, Feb 17, 2012 at 4:13 PM, Prasannaa <prasan...@yahoo.com> wrote:
>
>>
>> HI Mikhail
>>
>> i had even posted you brain storming.
>>
>> we will take up your views as well.
>>
>> cheers
>> prasannaa
>> ------------------------------
>> *From:* Mikhail Krivoshein <mikhail.k...@gmail.com>
>> *To:* ljc-adop...@googlegroups.com
>> *Sent:* Friday, February 17, 2012 3:55 PM
>> *Subject:* Re: JSR-343 Progress
>>
>> No preference from my side. Agree that we need to establish current
>> state
>> of the JSR before we try to contribute. My attempt at brainstorming
>> appears
>> to be completely off the mark.
>> Best regards,
>> Mikhail Krivoshein
>> On Feb 17, 2012 3:37 PM, "Prasannaa" <prasan...@yahoo.com> wrote:
>>
>>
>> We are a group of members, we have to decide as a group. We are all part
>> of LJC and each of the members has a right to them.
>>
>> I can take your vote, and i would love to have you assisting me.
>>
>> maybe faizal can vote on this ;)
>>
>> As of now
>>
>> One vote for Prasannaa and one vote for Madhu (although we have
>> exchanged
>> our votes :p)
>>
>> Maybe Trisha can send her views.
>>
>> cheers
>> prasannaa
>>
>>
>>
>> ------------------------------
>> *From:* "madhu...@madhusudhan.com" <madhu...@madhusudhan.com>
>> *To:* ljc-adop...@googlegroups.com
>> *Sent:* Friday, February 17, 2012 3:21 PM
>> *Subject:* Re: JSR-343 Progress
Hard to say. Depends on what we aim to achieve.
What I can propose is - if all agree - let's Prasanna and Faisal (Faisal
hasn't yet confirmed) be the group leaders.
Give them at least three month term - if no one is interested after three
months, let them continue.
Remember, they are not going to carry a briefcase that would destroy the
entire human race with a flick of the switch :)
Agree?
> Hard to say. Depends on what we aim to achieve.
> On Feb 17, 2012 4:53 PM, "Prasannaa" <prasan...@yahoo.com> wrote:
>
>>
>> We can have
>>
>> 1.Prasannaa
>> 2.Faizal
>> 3.Mikhail Krivoshein
>>
>> I remember Mikhail Krivoshein, showed his interest to be as deputy lead.
>>
>> Mikhail Krivoshein are you in?
>>
>> cheers
>> Praannaa
>>
>> ------------------------------
>> *From:* "madhu...@madhusudhan.com" <madhu...@madhusudhan.com>
>> *To:* ljc-adop...@googlegroups.com
>> *Sent:* Friday, February 17, 2012 4:46 PM
Please let's kick-start JMS2.0 JSR - let's not procrastinate any further.
As a gentle rule, do you think it is a good thing to expect mail/feedback
every alternate day at least from each one of us? For example, team
members are expected to work/read/document/analyse/shout/moan/etc atleast
three times a week. Ofcourse, there will be exceptions (you may be really
neck-deep in work, holidaying cruise on the river Nile, (Trying
to)Climbing mount everest or running for a 1000k km run) :)
Can propose a Mon,Wed and Friday email catchup? or at least Tue/Thu?
Thanks
Madhu
Can you please book the meeting? This way we know if all are fine and
happy to come over.
In the mean time, can you pick up a simple task related to the JMS2.0
requirements and circulate please? So we all can butt in.
Thanks
Madhu
>
>
> �Hi Madhu
Hi all,
Sorry, I cannot make it as I will still be out of country.
Best regards,
Mikhail Krivoshein