CSS Links and request forwarding

2008-07-08 Thread Miguel Paraz
Hi,
I have a servlet on /site. Depending on the User-Agent, it will use
the RequestDispatcher and forward to /site1 or /site2.
/site1 is mapped to the Wicket filter, /site2 is another plain servlet.

When I open site1 directly, the CSS link is alright.

In the original html:

link href=site1/styles/site.css rel=stylesheet type=text/css /

In the processed html:

link href=../site1/styles/site.css rel=stylesheet type=text/css/


But, when I open this through /site and it passes through the
RequestDispatcher, the processed html becomes:

link href=../../site1/styles/site.css rel=stylesheet type=text/css/


How did the base URL change?
Thanks.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: CSS Links and request forwarding

2008-07-08 Thread Miguel Paraz
On Tue, Jul 8, 2008 at 8:37 PM, James Carman [EMAIL PROTECTED] wrote:
 Try redirecting rather than forwarding

I'm trying to avoid redirecting.

Do you mean, forwarding cannot retain the correct URL?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



WebApplication-level styles?

2008-07-03 Thread Miguel Paraz
Hi,
Is it possible to set the style once, at the WebApplication, instead
of getting the Session in every Page, and calling setStyle() ?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



UTF-8 Byte Order Marks in .html files

2008-06-25 Thread Miguel Paraz
Hi,
I found out - through a lot of trial and error - that if your .html
file has a Byte Order Mark, the ?xml encoding=utf-8 ? at the top
of the document is ignored.
The document is treated as something else - I'm not sure what.

The effect is that the special output characters become the ?
unknown characters.

Is this a known issue?
Thanks.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: UTF-8 Byte Order Marks in .html files

2008-06-25 Thread Miguel Paraz
On Wed, Jun 25, 2008 at 9:51 PM, Brill Pappin [EMAIL PROTECTED] wrote:
 I think it might be your browser that is not displaying the unicode chars.
 That you see the odd symbols at all means that the made it to the client
 side.

 Are you on a Mac?

Hi! Thanks for the reply.

No, I'm on Firefox 3 on Windows.

Do you have an idea why removing the BOM fixes it?

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]