Hensley, Richard wrote: > If you have a method called currentRepository.getAllFacilities, you will use > currentRepository.allFacilities in your ognl. > > For Tapestry 3.0, you page class will need a getCurrentFacility() and > setCurrentFacility(Object value) abstract methods. Along with a property > called currentFacility.
Actually, you only need the abstract accessors in 3.0 if you need to access the property in your java code. :) If you don't need to access the currentRepository object in code, then you don't need the abstract accessors. There is also a way to get and set object properties without using abstract accessors (but it isn't typesafe) Robert > > For Tapesestry 4.0, all you need is the currentFacility and > currentFacilityIndex properties defined in the .page file > > -----Original Message----- > From: Edward Scanzano [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 25, 2005 10:32 AM > To: tapestry-user > Subject: Is this the right syntax > > <span jwcid="@Foreach" > source="ognl:currentRepository.getAllFacilities" > value="ognl:currentFacility" > index="ognl:currentFacilityIndex"> > > I have an object called currentRepository that has a > method called getAllFacilities and it returns a > Collection object. > > I have nothing defined in the .page file. Do I need > support for these variables as a > property-specification? > > The error I get > > > ognl.NoSuchPropertyException > com.intaglio.client.api.impl.RepositoryImpl.getAllFacilities > > > > > > > --------------------------------------------------------------------- > 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]
