Resource Caching in 1.5.

2012-02-24 Thread Jürgen Lind

Hi,

my migration to Wicket 1.5. is progressing, but there are still some unresolved 
issues. Currently, I
am trying to prevent wicket from adding antiCache-Information to a 
PackageResourceReference. I am
using a subclassed LabelIconPanel to have my own icons in a Tree component. 
However, all icons are
loaded freshly when doing an update due to the antiCache Part that gets added 
to the URL

I have already search the documentation and various forums but I have not been 
able to find a way
to prevent the described behavior. The best think (I thought) was to disable anti-caching 
altogether, so I added


getResourceSettings().setCachingStrategy(NoOpResourceCachingStrategy.INSTANCE);

to my application's init method. Unfortunately, that did not work either. Any 
suggestions how to
get around this problem?


J.

--
Dr. Jürgen Lind
iteratec GmbHFon: +49 (0)89 614551-44
Inselkammerstrasse 4 Fax: +49 (0)89 614551-10
82008 Unterhaching   Web: www.iteratec.de

Sitz und Registergericht der iteratec GmbH: München HRB 113 519
Geschäftsführer: Klaus Eberhardt, Mark Goerke, Inge Hanschke, Ralf Menzel

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Resource Caching in 1.5.

2012-02-24 Thread Igor Vaynberg
package resource references should not have anticache appended, please
create a quickstart.

-igor

On Fri, Feb 24, 2012 at 6:39 AM, Jürgen Lind juergen.l...@iteratec.de wrote:
 Hi,

 my migration to Wicket 1.5. is progressing, but there are still some
 unresolved issues. Currently, I
 am trying to prevent wicket from adding antiCache-Information to a
 PackageResourceReference. I am
 using a subclassed LabelIconPanel to have my own icons in a Tree component.
 However, all icons are
 loaded freshly when doing an update due to the antiCache Part that gets
 added to the URL

 I have already search the documentation and various forums but I have not
 been able to find a way
 to prevent the described behavior. The best think (I thought) was to disable
 anti-caching altogether, so I added

 getResourceSettings().setCachingStrategy(NoOpResourceCachingStrategy.INSTANCE);

 to my application's init method. Unfortunately, that did not work either.
 Any suggestions how to
 get around this problem?


 J.

 --
 Dr. Jürgen Lind
 iteratec GmbH                Fon: +49 (0)89 614551-44
 Inselkammerstrasse 4         Fax: +49 (0)89 614551-10
 82008 Unterhaching           Web: www.iteratec.de

 Sitz und Registergericht der iteratec GmbH: München HRB 113 519
 Geschäftsführer: Klaus Eberhardt, Mark Goerke, Inge Hanschke, Ralf Menzel

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Resource Caching in 1.5.

2012-02-24 Thread Igor Vaynberg
actually, did you override LabelIconPanel#newImageComponent()? in
there i see code to prevent anticache...

return new Image(componentId)
{
@Override
protected boolean shouldAddAntiCacheParameter()
{
return false;
}
};
}

-igor

On Fri, Feb 24, 2012 at 8:02 AM, Igor Vaynberg igor.vaynb...@gmail.com wrote:
 package resource references should not have anticache appended, please
 create a quickstart.

 -igor

 On Fri, Feb 24, 2012 at 6:39 AM, Jürgen Lind juergen.l...@iteratec.de wrote:
 Hi,

 my migration to Wicket 1.5. is progressing, but there are still some
 unresolved issues. Currently, I
 am trying to prevent wicket from adding antiCache-Information to a
 PackageResourceReference. I am
 using a subclassed LabelIconPanel to have my own icons in a Tree component.
 However, all icons are
 loaded freshly when doing an update due to the antiCache Part that gets
 added to the URL

 I have already search the documentation and various forums but I have not
 been able to find a way
 to prevent the described behavior. The best think (I thought) was to disable
 anti-caching altogether, so I added

 getResourceSettings().setCachingStrategy(NoOpResourceCachingStrategy.INSTANCE);

 to my application's init method. Unfortunately, that did not work either.
 Any suggestions how to
 get around this problem?


 J.

 --
 Dr. Jürgen Lind
 iteratec GmbH                Fon: +49 (0)89 614551-44
 Inselkammerstrasse 4         Fax: +49 (0)89 614551-10
 82008 Unterhaching           Web: www.iteratec.de

 Sitz und Registergericht der iteratec GmbH: München HRB 113 519
 Geschäftsführer: Klaus Eberhardt, Mark Goerke, Inge Hanschke, Ralf Menzel

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Resource Caching in 1.5.

2012-02-24 Thread Jürgen Lind

Thx Igor, that was indeed the right call... Not it works as expected...

J.


On 24.02.2012 17:03, Igor Vaynberg wrote:

actually, did you override LabelIconPanel#newImageComponent()? in
there i see code to prevent anticache...

return new Image(componentId)
{
@Override
protected boolean shouldAddAntiCacheParameter()
{
return false;
}
};
}

-igor

On Fri, Feb 24, 2012 at 8:02 AM, Igor Vaynbergigor.vaynb...@gmail.com  wrote:

package resource references should not have anticache appended, please
create a quickstart.

-igor

On Fri, Feb 24, 2012 at 6:39 AM, Jürgen Lindjuergen.l...@iteratec.de  wrote:

Hi,

my migration to Wicket 1.5. is progressing, but there are still some
unresolved issues. Currently, I
am trying to prevent wicket from adding antiCache-Information to a
PackageResourceReference. I am
using a subclassed LabelIconPanel to have my own icons in a Tree component.
However, all icons are
loaded freshly when doing an update due to the antiCache Part that gets
added to the URL

I have already search the documentation and various forums but I have not
been able to find a way
to prevent the described behavior. The best think (I thought) was to disable
anti-caching altogether, so I added

getResourceSettings().setCachingStrategy(NoOpResourceCachingStrategy.INSTANCE);

to my application's init method. Unfortunately, that did not work either.
Any suggestions how to
get around this problem?


J.

--
Dr. Jürgen Lind
iteratec GmbHFon: +49 (0)89 614551-44
Inselkammerstrasse 4 Fax: +49 (0)89 614551-10
82008 Unterhaching   Web: www.iteratec.de

Sitz und Registergericht der iteratec GmbH: München HRB 113 519
Geschäftsführer: Klaus Eberhardt, Mark Goerke, Inge Hanschke, Ralf Menzel

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




--
Mit freundlichen Grüßen,

Jürgen Lind

--
Dr. Jürgen Lind
iteratec GmbHFon: +49 (0)89 614551-44
Inselkammerstrasse 4 Fax: +49 (0)89 614551-10
82008 Unterhaching   Web: www.iteratec.de

Sitz und Registergericht der iteratec GmbH: München HRB 113 519
Geschäftsführer: Klaus Eberhardt, Mark Goerke, Inge Hanschke, Ralf Menzel

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org