--
View this message in context:
http://old.nabble.com/Wicket-1.4.5-%3A-Spring-integration-problem--tp27237445p27435266.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsu
quot;>>>"+
> >>> ((NihonBareApplication)getApplication()).getCommonService());
> >>> return
> >>> ((NihonBareApplication)getApplication()).getCommonService();
> >>> }
> >>> }
> >>>
> >>>
>
t; ((NihonBareApplication)getApplication()).getCommonService());
>>> return
>>> ((NihonBareApplication)getApplication()).getCommonService();
>>> }
>>> }
>>>
>>>
>>> But eventhough the bean injected into 'NihonbareApplication' object, the
>>> getCommonService(
Thanks Pierre,
yes,that was a problem with web.xml ,
I forgot to change the filter setting :
applicationFactoryClassName
org.apache.wicket.spring.SpringWebApplicationFactory
Now everything works fine.
Pierre Goupil wrote:
Maybe it comes from the web.xml : can
Maybe it comes from the web.xml : can we ses it, please?
Regards,
Pierre
On Wed, Jan 20, 2010 at 7:41 AM, Ashika Umanga Umagiliya <
auma...@biggjapan.com> wrote:
> Greetings all,
>
> I followed the easy 'Application Object Approach' to integrate Spring with
> my Wicket app. (
> http://cwiki.ap
Greetings all,
I followed the easy 'Application Object Approach' to integrate Spring
with my Wicket app.
(http://cwiki.apache.org/WICKET/spring.html#Spring-ApplicationObjectApproach
)
In my application class :
public class NihonBareApplication extends WebApplication
{
private CommonSe
; };
>
> Alec
>
>
> On Mon, Dec 28, 2009 at 11:01 AM, Alec Swan wrote:
>
>> I just upgraded from Wicket 1.4.2 to Wicket 1.4.5 and started receiving the
>> following exceptions from my Unit test.
>>
>> Is this a known issue or do I need to change my te
() {
addComponentInstantiationListener(new
SpringComponentInjector(this, new AnnotApplicationContextMock(), false));
}
};
Alec
On Mon, Dec 28, 2009 at 11:01 AM, Alec Swan wrote:
> I just upgraded from Wicket 1.4.2 to Wicket 1.4.5 and started receiving the
> following exceptions from my Uni
I just upgraded from Wicket 1.4.2 to Wicket 1.4.5 and started receiving the
following exceptions from my Unit test.
Is this a known issue or do I need to change my test?
Thanks.
org.apache.wicket.WicketRuntimeException: *There is no application attached
to current thread main*
at
regressions are always possible but they should work fine
On Sat, 2009-12-26 at 14:21 -0500, tubin gen wrote:
> I am currently using wicket 1.4 also I use Wicket stuff, wicket
> extensions.Moving to wicket 1.4.5 will it cause any problems with
> wicket-stuff and e
I am currently using wicket 1.4 also I use Wicket stuff, wicket
extensions.Moving to wicket 1.4.5 will it cause any problems with
wicket-stuff and extensions?
The Apache Wicket project is proud to announce the fifth maintenance
release of Apache Wicket 1.4.
Download Apache Wicket 1.4.5
--
You can download the release here:
http://www.apache.org/dyn/closer.cgi/wicket/1.4.5
Or use this in your Maven pom'
12 matches
Mail list logo
