On Jun 16, 2007, at 3:42 AM, Dhanji R. Prasanna wrote:
>
> Since we're targetting the EE6 release, I think we should consider
> interoperability with JSR-303 (cross-tier validation of beans).
> Atleast the runtimes should have some background coalescence in an
> EE(6) container--has any thought been given to this?
>
No thought so far but I can see that a validation engine could be
useful when processing classes using the jsr 311 annotations.
> I am also curious about the javax.interceptor and javax.annotations
> as regards dependency injection (@Resource), and similar cross-
> cutting concerns. I imagine this would all be container specific
> (JEE containers mainly); but it would be cool if such
> infrastructure were available even in SE environments, which jsr311
> obviously targets (especially declarative bean validation).
We provided limited support for @Resource in the API that shipped
with R2 of the Sun Web Developer Pack. On the one hand I agree that
providing this kind of infrastructure in SE environments is useful
and beneficial when moving applications between containers but on the
other hand, if required, it impacts the level of complexity of an
implementation so its something of a balancing act.
> In any case Im curious as to whose responsibility it is to define
> the behaviors/contracts of interop between the various runtimes
> (311 & 303 for instance)--is it the EE6 JSR's or ours or both?
>
I think its a bit of both.
Marc.
---
Marc Hadley <marc.hadley at sun.com>
CTO Office, Sun Microsystems.
- application/pkcs7-signature attachment: smime.p7s