On 10/17/07, Gary VanMatre <[EMAIL PROTECTED]> wrote:
> >From: "Niall Pemberton" <[EMAIL PROTECTED]>
> >
> > On 10/16/07, Gary VanMatre wrote:
> > > >From: Iain Duncan
> > > >
> > > > Hi Gary,
> > > >
> > > > Thanks a lot for the information! Do you know if the mock implementation
> > > > is going to be extended at any point to include dealing with lists
> > > > reference by expressions like "#{myBean.myList[0]}"?
> > > >
> > >
> > > I'm not sure. The test framework is one of the best parts of Shale but the
> > only problem I see in expanding for more EL support is that it becomes more
> > and
> > more complicated. It's easy to draw the line with the existing mock
> > implementation.
> > >
> > > At one time I added a fix to support scopes like
> > "#{requestScope['xxx.xxx.xx']}" and Craig made a similar comment about
> > keeping
> > the mock implementation simple.
> > >
> > > However, Shale is used by many of the myfaces projects. I think the
> > > community
> > should make the decision providing there is a volunteer to contribute.
> > >
> >
> > I don't know how Shale Test Framework supports EL - but with the new
> > "Unified EL" spec, which is independant of servlet/jsf it might be an
> > idea to plug that into the test framework. Apache Tomcat has released
> > separate jars which are now available in the maven repo.
> >
>
> That sounds like something we should look into. I'm not sure how coupled it
> is with JSP but would be better than building up a mock implementation.
Its not coupled at all - the problem was that jsf and jsp had
different el flavours - the unfied EL was decoupled from JSP and
released as a separate spec. The reason its been labelled "unified"
was because its underpinned the next (can't remember version numbers)
releases of both JSP and JSF:
http://java.sun.com/products/jsp/reference/techart/unifiedEL.html
Niall
> > Niall
> >
>
>
> Gary
>
> > > > Cheers,
> > > >
> > > > Iain
> > > >
> > >
> > >
> > > Gary
> > >
> > >
> > > > ___________________________________________
> > > > Iain Duncan
> > > > MDM Platform Services Development
> > > > IBM UK Limited
> > > > MP 188, Hursley Park, Winchester, Hants, SO21 2JN, UK
> > > > t: +44 (0)1962 816873 / Internal : 7-246873
> > > > e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > > >
> > > > [EMAIL PROTECTED] (Gary VanMatre)
> > > > 16/10/2007 16:27
> > > > Please respond to
> > > > user@shale.apache.org
> > > >
> > > >
> > > > To
> > > > user@shale.apache.org
> > > > cc
> > > >
> > > > Subject
> > > > Re: Using shale-test with ValueBinding lists
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > >From: Iain Duncan
> > > > >
> > > > > Hello All,
> > > > >
> > > > > I've just started using shale-test to test an application using JSF1.1
> > > > so
> > > > > apologies if this is a dumb question and I am doing something obvious
> > > > > wrong! I have been unable to get the getValue() method on a
> > > > > ValueBinding
> > > >
> > > > > that involves a list to work. Does anyone know if this has been
> > > > > implemented?
> > > > >
> > > >
> > > > Simple expressions can be evaluated. The mock implementation tokenizes
> > > > the expression based on the "dot" separator. So, you can evaluate
> > > > expressions like "#{mybean.property}".
> > > >
> > > > You have to programmatically add your beans into scope in your unit
> > > > tests
> > > > or add a few lines of logic to process faces-config's.
> > > >
> > > >
> > > > > Cheers,
> > > > >
> > > > > Iain
> > > > >
> > > >
> > > > Gary
