That sounds like a bug. AssetEncoder should be able to differ between private and context assets.
"Vinicius Carvalho" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] >I found out that the problem was the asset service. I was mapping my > assets to /assets/* as shown in the examples. even though my pages > displayed the assets in a correct way, the Exception page get all > messed up. Removing the asset encoder, got the exception page back on > it's track :) > > Regards > > On 8/23/06, Henri Dupre <[EMAIL PROTECTED]> wrote: >> Hmm looks like somehting is screwed up with the tapestry css include... >> Did you disable the base tag in the @Shell? >> >> >> On 8/23/06, Vinicius Carvalho <[EMAIL PROTECTED]> wrote: >> > >> > Hello there! I've noticed that after defining a friendly url for >> > direct service, I lost all the formatting of the Exception page (the >> > blue headers, and highlight and stuff) >> > >> > Why is that? Am I missing something in my configuration? >> > >> > Regards >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> -- >> Henri Dupre >> Actualis Center >> >> > > --------------------------------------------------------------------- > 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]
