+1

On Tue, Nov 4, 2008 at 5:15 AM, Simon Kitching <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Currently orchestra-flow 0.0.1 supports JSF1.1. However in order to
> allow pages that declare orchestra flows to be *included* in other pages, eg
>  <ui:include src="somePageThatCallsAFlow">
>    <ui:param name="vname" value="value"/>
>  </ui:include>
> the EL expressions in the included page need to be build using the
> correct ELContext object (otherwise they cannot see the params).
>
> Rather than build some kind of reflection-based solution, it would be
> simpler to just ditch JSF1.1 support for orchestra-flow.
>
> Note that there are no plans to ditch JSF1.1 support for orchestra-core ..
>
> Any objections?
>
> Regards, Simon.
>
> --
> -- Emails in "mixed" posting style will be ignored
> -- (http://en.wikipedia.org/wiki/Posting_style)
>
>



-- 
Kito D. Mann -- Author, JavaServer Faces in Action
http://twitter.com/kito99
http://www.virtua.com - JSF/Java EE consulting, training, and mentoring
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info
+1 203-404-4848 x3

Public JSF Course in NYC: http://www.regonline.com/jsf-course

Reply via email to