On 2/27/06, David Leangen <[EMAIL PROTECTED]> wrote:
could you replicate this in a quickstart project and post that. i would need to walk through it to see what is going wrong.
yep. youd have to append it manually if you dont want to use packaged resources. i would create a reusable subclass of attribute modifier that does this.
-Igor
> hrm, maybe its a problem with our prepender. it does look like its
> prepending the / but nothing after that, maybe the "." that is
> screwing it up. try calling getApplicationSettings().setContextPath
> ("/.temp/www") in your application.init() method. if that works then i
> will assume its a problem in our prepender and see if i can fix it.
Unfortunately, still the same thing... :-(
could you replicate this in a quickstart project and post that. i would need to walk through it to see what is going wrong.
> as far as the css links go wicket will only prepend static markup in
> the .html file, not the one you generate, so there you have to do it
> manually. to put it another way, currently it is a preprocessor not a
> postprocessor.
So I'd need to mount this like I would with my class pages? Is that what
you're saying?
Or I'd have to manually write in the context path as part of the link?
yep. youd have to append it manually if you dont want to use packaged resources. i would create a reusable subclass of attribute modifier that does this.
-Igor
