• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

what is difference in access jstl and jsf tags!

 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi

we use ${} to get any variable in jstl tags but in jsf we use #{}

what is specific difference in using this ???
 
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Moved to the JSF forum.
 
Author
Posts: 12617
IntelliJ IDE Ruby
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
One's for JSF, one's for JSP. The UEL is supposed to remove the disparity, but since I don't know anything about JSF (that I admit to), I can't really speak to that.
 
Bear Bibeault
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In my opinion, moving the EL information out of the JSP Specification, and into its own mixed up with the JSF stuff was a big mistake. It's completely confusing for anyone not interested in the JSF aspects of the EL.
 
Bear Bibeault
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Oh, and to clarify: this has nothing to do with the JSTL, or with tags. The EL is not the JSTL, and EL expressions are not tags.

 
Saloon Keeper
Posts: 27762
196
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Acutally, what they did was get rid of the idosyncratic per-framework expression languages and merge them all into a Unified Expression Language (UEL). Makes the rules more consistent and voids the need for separate parsing, interpreting and support facilities.

The primary difference between the "$" and "#" indicators is that "#" indicates a reference and "$" indicates a value. Specifically, since "#" is a reference, it can be used in situations where an lvalue expression is required.

The JSTL/jsp tags retrieved only values, so they use ""$". However, JSF often updates the references, as for example in the "inputText" controls.

I think in JSF pre-historic times, the use of one or the other might have been briefly mandatory. These days, the "#" notation works for most everything JSF. JSP items, on the other hand, aren't prepared to receive input on their EL properties, so they continue to use the (read-only) "$" notation.
 
Bear Bibeault
Sheriff
Posts: 67746
173
Mac Mac OS X IntelliJ IDE jQuery TypeScript Java iOS
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Right, Tim. I understand why they did it -- I just think it was done in a ham-handed way that makes it confusing for people who just want to know how to use the EL in JSP.
 
reply
    Bookmark Topic Watch Topic
  • New Topic