<br><font size=2 face="sans-serif">http://jcp.org/en/eg/download/jsr-277-service-provider-strawman-05222007.pdf?id=277&fileId=3438</font>
<br><font size=2 face="sans-serif"><br>
Glyn</font>
<br>
<br><font size=1 face="sans-serif"><b>Andy Piper <andyp@BEA.COM></b></font><tt><font size=2>
wrote on 14/06/2007 12:43:45 PM:<br>
<br>
> I share Glyn's concerns, but can someone remind me where the strawman
is?!<br>
> <br>
> Thanks!<br>
> <br>
> andy<br>
> <br>
> At 11:07 AM 6/14/2007, Glyn Normington wrote:<br>
> <br>
> >"Stanley M. Ho" <Stanley.Ho@SUN.COM> wrote on
13/06/2007 07:19:10 PM:<br>
> ><br>
> > > Since I have not heard any further input on the services
and<br>
> > > service-providers strawman, I suppose the EG is fine with
the strawman<br>
> > > overall except the issue raised by Richard. Unless I hear
any objection,<br>
> > > I will incorporate the appropriate portion of the strawman
based on the<br>
> > > feedback you have provided into the next revision of the
specification.<br>
> ><br>
> >I am very concerned that the scope of JSR 277 is being expanded<br>
> >considerably without much attention being paid to the state of
the<br>
> >art (particularly Spring-OSGi and Declarative Services). If we
could<br>
> >implement good interoperation with JSR 291, we could delegate
the<br>
> >complexities of supporting services to JSR 291 and technologies
like<br>
> >Spring-OSGi that layer nicely on top of JSR 291.<br>
> ><br>
> >Apart from that, the support for services in the strawman has
some<br>
> >obvious holes, so I don't think it is ready to be incorporated
into<br>
> >the JSR 277 specification:<br>
> ><br>
> >1. It seems to be lacking any form of dependency injection.<br>
> ><br>
> >2. The namespace of services is global, but not partitioned by<br>
> >service interface version. The effect of this is that a module
could<br>
> >import v1 of a service interface class and obtain an instance
of the<br>
> >service that implements v2 of the service interface and get a
class<br>
> >cast exception.<br>
> ><br>
> >3. There is no support for dynamic updates of service providers
and<br>
> >notification of service updates to service consumers. (This is<br>
> >consistent with JSR 277's static nature, but I point it out as
this<br>
> >is an obvious future requirement based on our experience in OSGi.)<br>
> ><br>
> >4. There seems to be some confusion in the strawman between loading<br>
> >of service interfaces/implementations and construction and<br>
> >publication of service instances.<br>
> ><br>
> >I wonder what other Expert Group members think of this strawman.<br>
> >Silence does not necessarily indicate happiness, so it would be
good<br>
> >to have more feedback.<br>
> ><br>
> >Glyn<br>
> ><br>
> ><br>
> ><br>
> >----------<br>
> ><br>
> ><br>
> >Unless stated otherwise above:<br>
> >IBM United Kingdom Limited - Registered in England and Wales with<br>
> >number 741598.<br>
> >Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU<br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> <br>
> <br>
> <br>
> Notice: This email message, together with any attachments, may
<br>
> contain information of BEA Systems, Inc., its
subsidiaries and <br>
> affiliated entities, that may be confidential, proprietary,
<br>
> copyrighted and/or legally privileged, and is intended solely
for <br>
> the use of the individual or entity named in this message. If you
<br>
> are not the intended recipient, and have received this message in
<br>
> error, please immediately return this by email and then delete it.<br>
</font></tt><font size=3 face="sans-serif"><br>
</font>
<br><font size=3 face="sans-serif"><br>
</font>
<hr><font size=2 face="sans-serif"><br>
<i><br>
</i></font>
<p><font size=2 face="sans-serif"><i>Unless stated otherwise above:<br>
IBM United Kingdom Limited - Registered in England and Wales with number
741598. <br>
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU</i></font>
<p><font size=2 face="sans-serif"><br>
</font><font size=3 face="sans-serif"><br>
</font>
<br>
<br><font size=3 face="sans-serif"><br>
</font>