I'm not sure if it's legal to map the "html" extension to two different
encoders. Try using a different extension for the external pages.
-Steve
Peter Stavrinides wrote:
Does anyone have any ideas?
Peter Stavrinides wrote:
Hi everyone
I am having some trouble with friendly URL's. Getting them to work
is not the problem, but getting two page service encoders to work
together seems unlikely. Maybe there is a better way to do this... I
don't know. I basically want an encoder that will generate friendly
URL's for html pages that use either the external or page services
(PageLink of ExternalLink components).
This is what my encoders look like, both work ok but when used in
tandem, they fight.
<contribution configuration-id="tapestry.url.ServiceEncoders">
<page-service-encoder id="external" extension="html"
service="external"/>
<page-service-encoder id="page" extension="html" service="page"/>
</contribution>
Any ideas?
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
