Hello,
there seems to be some difficulty linking between static and
packages resources, or at least a lot of confusion in forums ;-)
If I refer to a static css from a wicket:link or wicket:head,
the link will be "relativized" automatically, right ?
However, I do have a CSS that is specific to a
> As Andrea mentioned you can use ContextImage which also doesn't use
> IResource and the generated url doesn't depend on the page/component.
>
I think this is the most helpful reply. A static image will be linked
successfully this way.
Thanks for the nice sharing. It helps a l
27;t use
> IResource and the generated url doesn't depend on the page/component.
>
>
> On Tue, Jan 8, 2013 at 12:30 AM, René Vangsgaard
> wrote:
>
> > Hi - I would like to link to a static image, and the link should be
> > stateless.
> >
> > I
use
IResource and the generated url doesn't depend on the page/component.
On Tue, Jan 8, 2013 at 12:30 AM, René Vangsgaard
wrote:
> Hi - I would like to link to a static image, and the link should be
> stateless.
>
> I have tried this (using Scala):
>
> val img = new
Have you tried with ContextImage?
Hi - I would like to link to a static image, and the link should be
stateless.
I have tried this (using Scala):
val img = new Image("img", new ContextRelativeResource("images/img" + imgId
+ ".png"))
But the link becomes stateful
Hi - I would like to link to a static image, and the link should be
stateless.
I have tried this (using Scala):
val img = new Image("img", new ContextRelativeResource("images/img" + imgId
+ ".png"))
But the link becomes stateful.
I just found
My issue appears to be not new...
https://issues.apache.org/jira/browse/WICKET-1889
https://issues.apache.org/jira/browse/WICKET-1700
But the fix is for v1.4.x not v1.3.6
--
View this message in context:
http://www.nabble.com/recommended-static-image-resource-strategy-tp24407111p24415044.html
My issue appears to be not new...
https://issues.apache.org/jira/browse/WICKET-1889
https://issues.apache.org/jira/browse/WICKET-1700
But this only applies to v1.4.
--
View this message in context:
http://www.nabble.com/recommended-static-image-resource-strategy-tp24407111p24415043.html
Sent
I have added a quick start to exemplifies the issue at hand.
Please see https://issues.apache.org/jira/browse/WICKET-2361 for those that
are interested.
Thanks
--
View this message in context:
http://www.nabble.com/recommended-static-image-resource-strategy-tp24407111p24413328.html
Sent
e() method.
From: Igor Vaynberg
To: users@wicket.apache.org; Doug Leeper
Sent: Thursday, July 9, 2009 10:13:05 AM
Subject: Re: recommended static image/resource strategy
it seems like a bug in
ServletWebRequest#getRelativePathPrefixToWicketHandler(), you might
want to subclass that, check for those
it seems like a bug in
ServletWebRequest#getRelativePathPrefixToWicketHandler(), you might
want to subclass that, check for those two params in the url, and add
an additional ../.. as a hack for right now.
also open a jira issue for us to fix it.
-igor
On Wed, Jul 8, 2009 at 2:46 PM, Doug Leeper
Our app has been working great this past year but we recently encountered a
strange behavior and wanted to get the communities input on how to proceed.
Background:
* Wicket 1.3.6
* JDK 1.5
* Jetty (dev) / Apache and Tomcat (prod)
* The URL to our app follows this
map...
add(new PageLink("module-01", Module01.class));
add(new PageLink("module-02", Module02.class));
Thanks for your help,
Cristina
--
View this message in context:
http://www.nabble.com/Using-a-static-ima
Cristina wrote:
> Hello,
>
> I've defined a simple HTML image map from a business process diagram:
>
>
>
>
> href="Module01.html" title="Subprocess 1" />
> href="Module02.html" title="Subprocess 2" />
> href="Module03.html"
t:
http://www.nabble.com/Using-a-static-image-map-tp16656656p16656656.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
15 matches
Mail list logo
