Hi Daniele, On [Tue, 26.04.2011 17:24], Daniele Dellafiore wrote: > Hey Eike. > > Yes, creating a wicket-stuff project for that is the best solution. But > first I want to make sure that everything really works in OSGi and Wicket. > > This morning I succeeded in installing my first complete app on Karaf, with > wicket-spring (and aslo spring-security, mongodb etc...) > > But there is a problem. When I reinstall the bundle, I get this kind of > exception: > > java.lang.IllegalArgumentException: Can not set > org.fenotipi.services.StudiService field > org.fenotipi.web.general.HomePage.studiService to > org.apache.wicket.proxy.$Proxy40 > > Now this only happens from the second time I install the module or just > after the first install, i refresh the module from the karaf console. > Have you ever experienced something like this? > > All the packages are in the same bundle.
I have separate wicket bundle(s) and one war bundle and I have the same problem when I update the main wicket bundle as you describe. But in my case it only occurs when I _update_ the wicket bundle. If I stop and start (not update) the wicket bundle, it works here. I don't know why this happens, seems like some classloader issue to me. For some reason the proxy does not pass the test !field.getType().isAssignableFrom(value.getClass()) anymore (field is the field to be injected and value the proxy which was loaded from the wicket bundle that has been updated.) regards Eike > On Tue, Apr 26, 2011 at 11:37 AM, Eike Kettner <[email protected]> wrote: > > > hi > > > > this might be also interesting. I once started a thread in wicket-user > > mailing list about this problem. (the thread is > > > > http://apache-wicket.1842946.n4.nabble.com/wicket-1-5-rc2-and-aggregate-jar-for-osgi-td3356667.html > > ) > > > > I think the conclusion was to build your own wicket bundle as it was > > distributed with wicket-1.5-rc1. in this release the wicket team created > > one jar out of core, util and request (as i remember). but future > > releases won't distribute this anymore. the idea was then to distribute > > it with the wicket-stuff project... > > > > regards, > > Eike > > > > On [Mon, 25.04.2011 18:13], Daniele Dellafiore wrote: > > > On Mon, Apr 25, 2011 at 5:07 PM, Allen Lau <[email protected]> wrote: > > > > > > > I'm jumping in a bit late, but in order to build our wicket app without > > > > dependencies, we use both the maven-bundle-plugin to generate the > > manifest > > > > file first and then have the maven-war-plugin do the packaging of the > > > > actual > > > > war. > > > > > > > > we use the following lines in the war plugin > > > > > > > > <configuration> > > > > <archive> > > > > > > > > > > > > > > > > <manifestFile>${project.build.outputDirectory}/META-INF/MANIFEST.MF</manifestFile> > > > > </archive> > > > > <packagingExcludes>WEB-INF/spring/**, > > > > WEB-INF/lib/*.jar</packagingExcludes> > > > > </configuration> > > > > > > > > > > > > > > This can works, thanks. > > > Maybe there is no bnd specific solution for this and we have to use a > > > "trick" like this one. > > > > -- > > email: [email protected] https://www.eknet.org pgp: 481161A0 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > -- email: [email protected] https://www.eknet.org pgp: 481161A0 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
