You should do it in the init method before you use the @SpringBean
Mathias P.W Nilsson wrote:
>
> Where should I do that?
>
> I have done this right now and it worked
>
> (Application)Application.get()).getSpringContextLocator().getSpringContext().getBean(
> "setting" )
>
> but it is not pre
Try using InjectorHolder.getInjector().inject(this);
Mathias P.W Nilsson wrote:
>
> Hi!
>
> I have extended the SpringWebApplication and the init method looks like
>
> addComponentInstantiationListener(new SpringComponentInjector(this));
>
>
> I want to access my @SpringBean in the init met
Did you find a solution to this problem? I've got the same problem.
Soniya wrote:
>
> yes I am running it development mode.
>
--
View this message in context:
http://www.nabble.com/Tomcat-Problem-tp15607207p16558427.html
Sent from the Wicket - User mailing list archive at Nabble.com.
When I deploy a new version of a Wicket application without restarting
Tomcat, the new version is not fully used. Java changes are applied
immediately, but html changes are not applied before I restart Tomcat.
I have tried inserting getMarkupSettings().getMarkupCache().clear(); in the
init() meth
No, I hadn't tried that, but that actually solved the problem. :jumping:
igor.vaynberg wrote:
>
> it may very well be. have you tried setting up the context with
> anti-jar locking enabled?
>
> -igor
>
>
--
View this message in context:
http://www.nabble.com/Problem-when-deploying-to-Tomc
IResourceSettings.setDisableGZipCompression() is not available in the version
of Wicket that I'm using (1.2.6).
I will try wireshark. What should I be looking for?
Tormod
Al Maw wrote:
>
> [EMAIL PROTECTED] wrote:
>> Hello.
>>
>> I have a problem with a css file that resides in the classpat
It seems that the server is returning a 304 message (Not Modified). Do you
understand why?
Tormod
Al Maw wrote:
>
> [EMAIL PROTECTED] wrote:
>> Hello.
>>
>> I have a problem with a css file that resides in the classpath along with
>> the Panel-class and being linked to the Panel using this c
I'm injecting a Spring session scoped bean into a Wicket component. No error
messages, but it seems that the changes I make to the bean are not reflected
back to the actual session bean. This is what I do (just a test class):
@SpringBean(name="basket")
private Basket basket;
Thanks for the quick answer.
I already have in the bean. In fact, I get the exact
same result without this tag, because CGLIB is in the classpath.
Do you have any other suggestions?
Tormod
Raffaele Cigni wrote:
>
> put this "" in your beans, like:
>
>
>
>
>
> Spring manages a p
I'm sorry. My mistake... :-$
I was making wrong assumptions about the internal behavior of the
CGLIB-generated object. I assumed I could use the Eclipse debugger and look
at the internal variables of the object, but this is of course wrong, since
it's just a proxy and the data is stored elsewhere
I'm trying to use SSL on certain pages in my application by using the
description for Wicket 1.3 in the wiki. However, when I access a page with
SSL, I'm always redirected to the start page. I see that the respond-method
in my WebRequestCycleProcessor is called 3 times. The first time, it calls
we
ive onces so if you type
>
> https://server/
>
> then that first part https://server will not be changed by wicket
>
>
>
> On Tue, Mar 11, 2008 at 10:15 AM, Tormod Øverlier <[EMAIL PROTECTED]>
> wrote:
>
>>
>> I'm trying to use SSL on
12 matches
Mail list logo