if you are using the latest snapshot then i would file this as a bug, this
should work out of the box the way you have it.
-igor
On 5/17/07, Matt Welch [EMAIL PROTECTED] wrote:
Putting shared css and javascript resource into the java package hierarchy
would seem to eliminate one of the
It would appear that someone has already submitted an issue:
https://issues.apache.org/jira/browse/WICKET-567
Int he mean time, I'll use the technique suggested above to load the css
files from my java package. Thanks for all of the help, folks.
Matt
On 5/18/07, Matt Welch [EMAIL PROTECTED]
On 5/18/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
if you are using the latest snapshot then i would file this as a bug, this
should work out of the box the way you have it.
-igor
I'll be happy to do that. Are there any instructions or guidelines available
anywhere about the right way to
Putting shared css and javascript resource into the java package hierarchy
would seem to eliminate one of the advantages of using a framework like
Wicket; the clean separation of responsibilities between HTML page
developers and java developers. Of course, I'm probably already long past
the
Hello Matt,
I'd suggest you put the CSS in the same package as your (base) page.
Then you can do the following in the constructor:
add(HeaderContributor.forCss(new
CompressedResourceReference(MyPage.class, style.css)));
Is it possible to use this method to add a .css that isn't in the
I have a stylesheet called base.css that sits in a directory called styles
that is in my base webapp directory. I have the following stylesheet
reference in an HTML template called Login.html:
link rel=stylesheet type=text/css href=styles/base.css
media=screen /
When I go to the login page,
what version are you using? if you are using a recent trunk (1 day old)
please report this as a bug.
-igor
On 5/15/07, Matt Welch [EMAIL PROTECTED] wrote:
I have a stylesheet called base.css that sits in a directory called
styles that is in my base webapp directory. I have the following
