Because there's a lot of sites out there that already use JSPs. Should
they have to rewrite every page in their site to use the Web Profile?
More likely would be that they simply wouldn't adopt the Web Profile.
In general, Java keeps backward compatibility in every way possible, and
our customers tell us, mostly, that that's what they want. They
complain, sometimes, that we keep around old APIs they don't like, but
the suggestion that an old API they use be removed is met with deserved
horror.
Jim
On 4/23/09 9:39 AM, webtier_at_javadesktop.org wrote:
> I was reading the specs of the WebProfile, and looked at the tecnologies that compose it.
>
> • Servlet 3.0
> [b]• JavaServer Pages (JSP) 2.2[/b]
> • Expression Language (EL) 2.2
> • Debugging Support for Other Languages (JSR-45) 1.0
> • Standard Tag Library for JavaServer Pages (JSTL) 1.2
> • JavaServer Faces (JSF) 2.0
> • Common Annotations for Java Platform (JSR-250) 1.1
> • Enterprise JavaBeans (EJB) 3.1 Lite
> • Java Transaction API (JTA) 1.1
> • Java Persistence API (JPA) 2.0
>
> Sorry if it is a really dumb question but... I thought that JSPs are "cientifically" comproved as worse-than-facelets in every situation. Even JSF2 have built-in facelet support. So if the JSF2 is in the WebProfile and have with it the facelets support, why do we have the JSPs in the profile too?
>
> Israel
> [Message sent by forum member 'israelbgf' (israelbgf)]
>
> http://forums.java.net/jive/thread.jspa?messageID=343400
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: webtier-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: webtier-help_at_glassfish.dev.java.net
>