I concur entirely!
________________________________
From: Dhanji R. Prasanna [mailto:dhanji_at_gmail.com]
Sent: Fri 7/13/2007 4:33 AM
To: dev_at_jsr311.dev.java.net
Subject: Re: Re: Re: Re: API feedback
Larry, while I agree with you in principle I think you will find that JSR-299 is a big driver of the IoC standard and is going to try to be the de-facto across several EE use cases (JSF2, Servlet, possibly even jsr311, and other components like EJB, WS etc.). The EE JSR has got legitimate means to reign in all the fledgling recalcitrant IoCs and standardize across the board (whether on 299 or 314's framework) because many of its components are diving them.
By the time we get something to the SE profile we will have all these disparate prodigal IoCs sitting off in their own spaces making future standardization even more difficult. I think in the interest of pragmatism we ought to try to tackle this early and across the board ( i.e. in EE6).
Dhanji.
On 7/13/07, Larry Cable <lcable_at_bea.com> wrote:
Actually I think the right place to do (at least part of this) might be in SE not EE ...
:-)
________________________________
From: Dhanji R. Prasanna [mailto:dhanji_at_gmail.com]
Sent: Thursday, July 12, 2007 3:35 PM
To: dev_at_jsr311.dev.java.net
Subject: Re: Re: Re: API feedback
Probably not thru JavaBeans, but I think it's worth bringing up to the EE6 JSR.
On 7/13/07, Larry Cable < lcable_at_bea.com <mailto:lcable_at_bea.com> > wrote:
I wonder if such a thing is doable/achievable, or has Pandora already opened the box?
________________________________
From: Dhanji R. Prasanna [mailto: dhanji_at_gmail.com]
Sent: Thursday, July 12, 2007 12:30 PM
To: dev_at_jsr311.dev.java.net
Subject: Re: Re: API feedback
On 7/13/07, Larry Cable < lcable_at_bea.com <mailto:lcable_at_bea.com> > wrote:
perhaps a revision of the JavaBeans specification is called for to define a common IoC model for Java?
Atleast that. I'm hearing this all over the shop (JSF2, EE6, JSR-299), each one wants DI their way. I would *strongly* support your suggestion.
Dhanji.
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.