Ed,<br><br>Hmmm., fascinating development. In this bundle, I don't see the "managed-bean-javadocs" directory, nor do I see any changes in section 5.1 of the prose document.<br><br>Have the Java EE folks discussed how managed beans and WebBeans will be reconciled, since they have different XML formats and annotations? For example, in Java EE 6, is @ManagedBean more or less the same as @Named?<br>
<br clear="all">---<br>Kito D. Mann -- Author, JavaServer Faces in Action<br><a href="http://twitter.com/kito99">http://twitter.com/kito99</a> <a href="http://twitter.com/jsfcentral">http://twitter.com/jsfcentral</a><br>
<a href="http://www.virtua.com">http://www.virtua.com</a> - JSF/Java EE consulting, training, and mentoring<br><a href="http://www.JSFCentral.com">http://www.JSFCentral.com</a> - JavaServer Faces FAQ, news, and info<br>+1 203-404-4848 x3<br>
<br>Public JSF Course in NYC (April 21st-24th): <a href="http://www.regonline.com/jsf-course">http://www.regonline.com/jsf-course</a><br><br>
<br><br><div class="gmail_quote">On Wed, Mar 25, 2009 at 7:17 PM, Ed Burns <span dir="ltr"><<a href="mailto:Ed.Burns@sun.com">Ed.Burns@sun.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This is likely new to most of you, but we need to make a small,<br>
non-technical, change to the way we think of our annotations related to<br>
Managed Beans in JSF 2.0. First, some background.<br>
<br>
Fact<br>
<br>
JSF2 will be final several months before Java EE6 becomes final. JSF2<br>
will do a maintenance release to synchronize with EE6.<br>
<br>
Corollary<br>
<br>
JSF2 must not depend on any features defined in Java EE 6.<br>
Thankfully, we have no such features. No, wait a minute...<br>
<br>
Recent development<br>
<br>
A movement is afoot at the EE platform level to extract the concept of<br>
managed beans from JSF and move it into its own specification, which<br>
would be a core part of Java EE 6. EJB, JSF, and Web Beans would then<br>
depend on this concept. This naturally would include the annotations<br>
relating to managed beans which we have in JSF 2.0. The EE Platform<br>
is now directing the JSF EG to make changes to accomodate this recent<br>
development.<br>
<br>
Options<br>
<br>
1. Drop the managed bean annotation feature for JSF2.0, adding it back<br>
for the JSF2 Maintenance Release for EE6.<br>
<br>
2. Find some way to keep the managed bean annotation feature for JSF<br>
2.0 that will be compatible with EE6.<br>
<br>
I've seen the smiles on peoples faces when I present JSF 2.0 and I get<br>
to the @ManagedBean @RequestScoped part. I couldn't bare to disappoint<br>
users that will be using JSF 2.0 outside of JavaEE 6.<br>
<br>
Here is Roberto Chinnici's implementation of option 2 which is specified<br>
in this snapshot [1]. I have modified our code for generating javadocs<br>
to create a separate top level javadoc bundle containing only the<br>
annotations relating to managed beans. JSF 2.0 implementations are<br>
strongly encouraged to implement this additional specification, but it<br>
is optional.<br>
<br>
This is simply a change in how we think about these annotations, not in<br>
the way they are specified or implemented, though they have been moved<br>
to a new package: javax.faces.bean.<br>
<br>
ACTION: I really don't have much leverage here so if you disagree with<br>
this, you'll have to take it up with your organization's JSR-316<br>
representative.<br>
<br>
[1] <a href="https://javaserverfaces-spec-public.dev.java.net/files/documents/1936/130753/jsf-spec-2.0-20090325.zip" target="_blank">https://javaserverfaces-spec-public.dev.java.net/files/documents/1936/130753/jsf-spec-2.0-20090325.zip</a><br>
<font color="#888888"><br>
<br>
--<br>
| <a href="mailto:ed.burns@sun.com">ed.burns@sun.com</a> | office: 408 884 9519 OR x31640<br>
| homepage: | <a href="http://ridingthecrest.com/" target="_blank">http://ridingthecrest.com/</a><br>
</font></blockquote></div><br>