Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of xhhsld@gmail.com designates
 209.85.214.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=vW7ISy+ciFTcliwXn/MPMRaV70Ct+R6yeyP8rGrR5vq4MA8ByxYqESJvKgJXUug8/2
         isUFAOFJyyrNv5YNLxD1jQAPSzW1wdG/uvmUh64n5IiUkzL65baI5BXcAUSFTA3MpsEw
         Qo6OygLv0DqenQRDkHGOiQxineNpyM80ZWYOE=
MIME-Version: 1.0
Date: Wed, 15 Sep 2010 07:58:44 +0800
Message-ID: <AANLkTi=K3q2VbyaiW5OHx0RtOSEfjF2T6kZ-yYWC-AmU@mail.gmail.com>
Subject: Do we need to support ManagedBean annotation ?
From: Ivan <xhhsld@gmail.com>
To: dev@geronimo.apache.org
Content-Type: multipart/alternative; boundary=000325575e5241daf9049040fe5c

--000325575e5241daf9049040fe5c
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi,
    Currently, all the annotation scan is done by Myfaces while starting th=
e
application, which means those managed bean with any naming injection will
not work.  The interesting thing is that there is no word for the
ManagedBean annotation in the jsf spec and we pass all the jsf tck cases,
after googled, got some history info for that anntation class, also find
some descriptions from the api doc below :
--->

These javadoc files constitute the =93Faces Managed Bean Annotation
Specification for Containers Conforming to Servlet 2.5 and Beyond=94

At the time of this writing, a forthcoming JCP effort is being planned to
extract the specification for managed beans from JSF and place it into its
own specification. To account for this effort and to avoid introducing
classes into JSF 2.0 that would have to be deprecated when this effort is
complete, implementations of JSF 2.0 are not required to implement the
=93Faces Managed Bean Annotation Specification for Containers Conforming to
Servlet 2.5=94. However, JSF implementations are strongly encouraged to
implement this specification, as it provides significant improvements in
ease of use.

The annotations must be processed as specified in section JSF.11.5.1.

<---
It seems that it is not required to support ManagedBean annotation in the
impl, and guess that is why we did not get any error in the jsf tck :-)
So I am thinking whether we need to support this in Geronimo, and actually,
once we integrated the web beans, it should be able to use web bean
annotations.
Thoughts ?

--=20
Ivan

--000325575e5241daf9049040fe5c
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

Hi, <br>=A0=A0=A0 Currently, all the annotation scan is done by Myfaces whi=
le starting the application, which means those managed bean with any naming=
 injection will not work.=A0 The interesting thing is that there is no word=
 for the <br clear=3D"all">


ManagedBean annotation in the jsf spec and we pass all the jsf tck cases, a=
fter googled, got some history info for that anntation class, also find som=
e descriptions from the api doc below :<br>---&gt;<br><p>
These javadoc files constitute the =93Faces Managed=20
Bean Annotation Specification for Containers Conforming to Servlet 2.5 and=
=20
Beyond=94</p>
<div>
<p>At the time of this writing, a forthcoming JCP effort is being planned t=
o=20
extract the specification for managed beans from JSF and place it into its =
own=20
specification. To account for this effort and to avoid introducing classes =
into=20
JSF 2.0 that would have to be deprecated when this effort is complete,=20
implementations of JSF 2.0 are not required to implement the =93Faces Manag=
ed Bean=20
Annotation Specification for Containers Conforming to Servlet 2.5=94. Howev=
er, JSF=20
implementations are strongly encouraged to implement this specification, as=
 it=20
provides significant improvements in ease of use.</p>
<p>The annotations must be processed as specified in section=20
JSF.11.5.1.</p><p>&lt;---<br></p></div>It seems that it is not required to =
support ManagedBean annotation in the impl, and guess that is why we did no=
t get any error in the jsf tck :-)<br>So I am thinking whether we need to s=
upport this in Geronimo, and actually, once we integrated the web beans, it=
 should be able to use web bean annotations.<br>
Thoughts ?<br><br>-- <br>Ivan<br>


--000325575e5241daf9049040fe5c--