Yes you can provide the delegate. The delegate is the short circuit. I was referring to the fact that the regular coded part of Tapestry is not configurable.
Geoff On 5/18/06, James Carman <[EMAIL PROTECTED]> wrote:
Or, maybe we should be setting the " org.apache.tapestry.specification-resolver-delegate" key to instantiate our own implementation of " org.apache.tapestry.resolver.ISpecificationResolverDelegate"? On 5/18/06, James Carman <[EMAIL PROTECTED]> wrote: > > Couldn't you override the implementation of the " > tapestry.page.ComponentSpecificationResolver" service point to resolve > specifications elsewhere? You could maybe "borrow" some of your > implementation from the default implementation. If you wanted, you could > change the implementation into a pipeline and put their resolver at the end > and put your custom resolver in front of it so you could only override > certain components' specifications. Just a thought. > > James > > p.s. I didn't exactly dig into the code to see what uses this class, but > from its name and API, it seems that this is the place to do some > customization. Jesse? Howard? Someone? > > > On 5/18/06, ZedroS Schwart <[EMAIL PROTECTED]> wrote: > > > Arg. Quite ironical for something implementing IoS and such of things no > > ? > > Just kidding ! > > > > Would it be a possibility for a change on this point in Tapestry 5 ? :$ > > > > Thanks in advance > > ZedroS > > > > >
-- The Spindle guy. http://spindle.sf.net Blog: http://jroller.com/page/glongman Other interests: http://www.squidoo.com/spaceelevator/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
