Servlet EG Java EE 5 Web Tier Proposed Final Draft
We're pleased to announce the availability of the Public Review of the next versions of the specifications for the Java Web tier. This includes Servlet, JavaServer Pages (JSP), the JSP Standard Tag Library (JSTL) and JavaServer Faces (Faces). Servlet is being developed under JSR-154, JSP 2.1 is developed under JSR-245, JSTL is developed under JSR-052 and Faces 1.2 is developed under JSR-252. The expert groups are working together to improve the alignment between these these powerful web technologies. Building on the work that was accomplished with the Early Draft Review, this Public Review covers two additional areas that required better integration between JSP and Faces: - Tree Creation and Content Interweaving - Deferred expressions nested within iteration tags Please see Appendix E of the JSP spec and the Preface of the Faces spec to see details of what's changed in JSP and Faces. Please see the change-logs for the Servlet and JSTL specs for what's changed in Servlet and JSTL. To access the specifications: JSP 2.1 PR (JSR-245) http://jcp.org/aboutJava/communityprocess/pfd/jsr245/ Faces 1.2 PR (JSR-252) http://jcp.org/aboutJava/communityprocess/pfd/jsr252/ To access the change-logs Servlet 2.5 (JSR-154) http://jcp.org/aboutJava/communityprocess/maintenance/jsr154/index3.html JSTL 1.2 (JSR-052) http://jcp.org/aboutJava/communityprocess/maintenance/jsr052/index2.html Sincerely, The Web Tier Expert Groups! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCE] JSP 2.1 and Faces 1.2 Public Review
We are pleased to announce the availability of the Public Review of the next versions of the specification for JavaServer Pages (JSP) and JavaServer Faces (Faces). JSP 2.1 is developed under JSR-245 and Faces 1.2 is developed under JSR-252. The two expert groups are working ogether to improve the alignment between these two powerful web presentation technologies. Building on the work that was accomplished with the Early Draft Review, this Public Review covers two additional areas that required better integration between JSP and Faces: - Tree Creation and Content Interweaving - Deferred expressions nested within iteration tags Please see Appendix E of the JSP spec and the Preface of the Faces spec to see details of what's changed. To access the specifications: JSP 2.1 PR (JSR-245) http://jcp.org/aboutJava/communityprocess/pr/jsr245/ Faces 1.2 PR (JSR-252) http://jcp.org/aboutJava/communityprocess/pr/jsr252/ Sincerely, The JSR-245 and JSR-252 Expert Groups - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANNOUNCE] JSP 2.1 and Faces 1.2 Early Draft Review
We're pleased to announce the availability of the Early Draft Review of the next versions of the specification for JavaServer Pages and Faces. JavaServer Pages (JSP) 2.1 is developed under JSR-245 and JavaServer Faces (Faces) 1.2 is developed under JSR-252. The two expert groups are working together to improve the alignment between these two powerful web presentation technologies. The foremost such alignment issue is the Expression Language, as stated in both JSRs. JSP 2.1 exports the Expression Language (EL) into its own separate document; technically a sub-document of the JSP specification. The Unified EL spec defines a new top level java package, javax.el. This package is completely independent of the technology using it and allows the using technology to plug itself into the EL resolution process. The bulk of the changes in the JSP spec itself follow from how it uses the Unified EL. As mentioned in the original JSR-252, this spec is not a new feature release. Faces 1.2 contains the work for it to leverage the new Unified EL, as well as a few spec related bug fixes. The alignment of Faces and JSP in these JSRs enables some new capabilities and provides a solid foundation for future growth. For example, in a web application that uses both Faces and JSP, it is possible for pages that only use JSP (without any faces content) to access managed beans. Please see Appendix E of the JSP spec and the preface of the Faces spec to see details of what's changed! To access the specifications: JSP 2.1 EDR (JSR-245) http://jcp.org/aboutJava/communityprocess/edr/jsr245/ Faces 1.2 EDR (JSR-252) http://jcp.org/aboutJava/communityprocess/edr/jsr252/ Sincerely, Ed Burns, Pierre Delisle, Roger Kitain, Mark Roth and the JSR-245 and JSR-252 Expert Groups. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Fwd: <%@page isThreadSafe="false" %> does not work]
> I compared two servlets' source code compiled from JSPs, > at the beginning of one jsp I add page directive: > <[EMAIL PROTECTED] isThreadSafe="false" %> > and the other, <[EMAIL PROTECTED] isThreadSafe="true" %>. > > But the two servlet are the same , I had thought the first > servlet will implement interface SingleThreadModel, but it > didn't. Could anyone give me a hint? This must be a bug in Lomboz. I verified this works as expected in Tomcat 5, i.e., specifying <[EMAIL PROTECTED] isThreadSafe="false" %> will cause the generated servlet to implement SingleThreadModel. Jan > BTW, jsp compiler (Lomboz) says SingleThreadModel > is deprecated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jasper complains when parsing valid TLD (was: Can't deploy Custom Tag Library ... )
Mark,
> So, on 4.1.* with logging cranked way up, I've been seeing errors that
> Jasper encountered a TEI class when the tld already has a variable? Very
> wierd error. Here's an example of a tag in my taglib, if anyone sees
> anything wrong with this please let me know, it is still valid against
> the dtd. (again this was a tld generated by Forte4J).
I believe the warning you are getting is based on JSP 1.2, JSP.C
("DTD for TagLibrary Descriptor, JSP 1.2"), p.231:
It is a (translation time) error for an action that
has one or more variable subelements to have a TagExtraInfo
class that returns a non-null object.
Jan
--
To unsubscribe, e-mail:
For additional commands, e-mail:
