[
http://issues.ops4j.org/browse/PAXWICKET-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13798#action_13798
]
Andreas Pieber commented on PAXWICKET-40:
-----------------------------------------
Ok, I've found the real reason for the problem... The pain is that pax-wicket
is not a war... It always registers it's "base" in the root. Now, if you add
something like:
{code}
<head>
<link rel="stylesheet" type="text/css" href="stylesheets/style.css"/>
</head>
{code}
It does fail of cause... Possible options are to use a registration via classes
as described here: https://cwiki.apache.org/WICKET/including-css-resources.html.
As an alternative I can think of e.g. registering a "resource-root-package"
containing the entire root data and mounted always where the app itself is
mounted
> Mounting pax wicket at / breaks css references
> ----------------------------------------------
>
> Key: PAXWICKET-40
> URL: http://issues.ops4j.org/browse/PAXWICKET-40
> Project: Pax Wicket
> Issue Type: Bug
> Environment: Felix, Java 1.6 OSX Snow Leopard
> Reporter: Andrew Williams
> Assignee: Andreas Pieber
> Priority: Critical
> Fix For: 1.0.0.M1, 1.0.0.RELEASE
>
>
> Mounting a pax wicket application at the root breaks the css resource urls -
> they return 404.
> This can be seen in the department store example - change the mount point to
> "/"
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
