i believe this is a websphere bug. we had users report this already, search the archives if you want more info.
-igor On 8/5/07, junqing chen <[EMAIL PROTECTED]> wrote: > > I am sure all the classes needed are in the war . the sticking point is : > > in websphere app server , user filter model , i get the error, in > servlet model , it runs ok . > > > Eelco Hillenius <[EMAIL PROTECTED]> wrote: > On 8/5/07, junqing chen wrote: > > I am using wicket 1.3 beta2 in myproject ,and the application server is > websphere 6.0.2. when I config wicket in websphere using filter mode, > cant't load class org.apche.wicket.spring.SpringWebApplicationFactory > > [07-8-3 10:25:25:202 CST] 0000002a WicketFilter W try to use > classloarder : [EMAIL PROTECTED] > > [07-8-3 10:25:25:623 CST] 0000002a WebApp E SRVE0026E: £ÛServlet > ´íÎó£Ý££ÛFilter [STPMainApp]: could not be initialized£Ý > rg.apache.wicket.protocol.http.WebApplicationFactoryCreationException: > Unable to create application factory of class > org.apache.wicket.spring.SpringWebApplicationFactory > > Caused by: java.lang.ClassNotFoundException: > org.apache.wicket.spring.SpringWebApplicationFactory > > Immediately above is the relevant bit: the class > SpringWebApplicationFactory couldn't be found in your class path. You > should check whether you have all the dependencies you need in your > war (wicket, wicket-spring, etc). > > Eelco > > > > --------------------------------- > > Real people. Real questions. Real answers. Share what you know.
