Craig,

I was actually referring to the class names. I was
confused by the use cases app which didn't list
the faces ViewHandler, NavigationHandler, etc.
Is there another working example which could show
me how those work?  I only saw the use case using
the ShaleFilter, not the Shale JSF parts.  As for
why, I was wondering if Shale could work with FaceLets
but after reading the API which suggests using the
ShaleViewHandler, I'm doubting it since I don't
think JSF can use multiple ViewHandlers in one
webapp/JSF-config.

Regards,
David

-----Original Message-----
From: Craig McClanahan [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 20, 2005 4:08 AM
To: Struts Users Mailing List
Subject: Re: [Shale] What's the deal with the dollar signs?


On 8/20/05, David G. Friedman <[EMAIL PROTECTED]> wrote:
> I thought I'd read some Shale documents a while ago mentioning the purpose
> for the dollar signs in the example use cases but while speed-reading
though
> various Shale documents, I'm totally missing that.  Can someone point that
> out to me?
>

I'm not positive what "dollar signs" you are referring to ... but
there are two delimiters for dynamic expressions that might be of
interest:

* "${xxx}" is typically an expression in the syntax/semantics supported
  by the JSP Standard Tag Library (JSTL), as well as that supported by
  JSP 2.0.  These expressions are evaluated as the page is rendered,
  and are dynamically replaced by the result of the expression evaluation.
  Shale is totally agnostic to such expressions, and does not know whether
  or not they exist.

* "#{xxx}" is a JSF 1.0/1.1 expresion.  At rendering time, it has identical
  syntax and semantics to a corresponding "${xxx}" expression as described
  above.  The difference is that a "#{xxx}" expression also has meaning on
the
  subsequent postback caused by a form submit, when the JSP page that
  originally created this view no longer exists.

Can you clarify which usage of expresion syntax you are referring to?

NOTE:  One of the primary objectives of the JSF 1.2 and JSP 2.1 specs
was to resolve the semantic differences between the "${...}" and
"#{...}" expression syntaxes -- but Shale itself doesn't care anything
about this area.  It's more an issue for the underlying JSP pages and
JSF components that you are using.

Craig


> Thanks,
> David
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to