Re: wicket conversation scope - weld integration
Hi again, finally i found the last problem bei incident: I had the beans.xml under WEB-INF and WEB-INF/META-INF as described in the docs and user forums. But actually it turned out that i had to put it under classes/META-INF or whatever the class folder is named. But nevertheless your hints were very valuable. Thank you! -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662228.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
Hi, you need to use compatible dependencies run the 6.11 examples with these dependencies dependency groupIdorg.apache.wicket/groupId artifactIdwicket-core/artifactId version6.11.0/version /dependency dependency groupIdorg.apache.wicket/groupId artifactIdwicket-cdi/artifactId version6.11.0/version /dependency dependency groupIdjavax.enterprise/groupId artifactIdcdi-api/artifactId version1.0-SP4/version /dependency dependency groupIdorg.jboss.seam.conversation/groupId artifactIdseam-conversation-spi/artifactId version3.0.0.Final/version /dependency François François Meillet Formation Wicket - Développement Wicket Le 30 oct. 2013 à 16:10, brazz alexander.li...@man.eu a écrit : Hi Martin, thanks for your answer! With the dependencies from your link i now can see log entries of weld. So now it seems to initialize correctly. But i have to run it with wicket version 1.5.10 from the examples page? When i run the examples with wicket 6.11, i get the compile error that method get() of Class CdiConfiguration does not exist. When i run the old examples with wicket 6.11, i get the following (now well known error): WELD-001408 Unsatisfied dependencies for type [ApplicationCounter] with qualifiers [@Default] at injection point [[field] @Inject net.ftlines.wicket.cdi.examples.InjectionPage.counter] this seems to be the main default error of weld. 30.10.2013 15:16:30 org.jboss.weld.bootstrap.WeldBootstrap clinit INFO: WELD-000900 1.1.9 (Final) 30.10.2013 15:16:30 org.jboss.weld.bootstrap.WeldBootstrap startContainer INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously. 30.10.2013 15:16:31 org.jboss.weld.environment.tomcat7.Tomcat7Container initialize INFO: Tomcat 7 detected, CDI injection will be available in Servlets and Filters. Injection into Listeners is not supported 30.10.2013 15:16:31 org.jboss.weld.interceptor.util.InterceptionTypeRegistry clinit WARNUNG: Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled 30.10.2013 15:16:31 org.jboss.weld.interceptor.util.InterceptionTypeRegistry clinit WARNUNG: Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662049.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
Hello François, thanks for your reply. yes that are exactly the dependencies that i use. I found out, that api changed between 1.5 and 1.6.. I checked out wicket examples 1.6 from wicket homepage and now it compiles. But still I get: WELD-001408 Unsatisfied dependencies for type [ApplicationCounter] with qualifiers [@Default] at injection point [[field] @Inject org.apache.wicket.examples.cdi.InjectionPage.counter] I got this exception with several different examples i tried (including the ftlines example) and different classpath dependencies. Althougt weld seems to start up according to the log files, something must go wrong during initialization. But weld doesn't output any details. As now i should have the same configuration as in wicket examples 6.x, i think it just doesn't work with tomcat 7. Thanks anyway. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662059.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
seam-wicket is outdated and has been replaced by wicket-cdi if I’m not mistaken. Also, this series of blog post probably contains all you need for setting up CDI in Wicket. It helped me: https://www.42lines.net/category/blog/software-engineering/full-stack-implementation/ Am 29.10.2013 um 16:53 schrieb brazz alexander.li...@man.eu: Hi, after fighting for several days with integrating cdi with wicket (i am interseted in this conversation scope thing). I ended up with the following stack trace: java.lang.IllegalStateException: Context is already active at org.jboss.weld.context.AbstractConversationContext.activate(AbstractConversationContext.java:245) This is the configuration: tomcat apache-tomcat-7.0.6 or apache-tomcat-7.0.47 seam-conversation-spi-3.0.0.Final.jar seam-wicket.jar weld-servlet.jar cdi-api.jar seam-conversation-weld-3.0.0.Final.jar wicket-cdi-6.11.0.jar wicket version is wicket-6.11.0 cdi version is weld-2.1.0 i think i tried every possible configuration and proposed solution on the internet. Of course i read every article about wicket- cdi, conversation scope, ftlines As it has to run although on WAS7, i'm not very optimistic. Has anyone tried that? Thanks for any suggestions. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org signature.asc Description: Message signed with OpenPGP using GPGMail
Re: wicket conversation scope - weld integration
Hi heapifyman, thanks for your reply. Yes i read it all. But the blog is from 2011 and is based on wicket 1.5. I downloaded the libs with maven, but it didn't work with wicket 6.11. I wanted to use the latest wicket for the new project. I also tried without seam-wicket in the classpath, but it also didn't help I feel like having tried all possible classpath combinations but none of them worked. I also debugged the initialization of weld at startup but couldn't detect the problem. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662036.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
It seems that you have more than one copy of weld in your claspath. Try with that : wicket-core cdi-api seam-conversation-spi wicket-cdi François On Wed, Oct 30, 2013 at 9:07 AM, brazz alexander.li...@man.eu wrote: Hi heapifyman, thanks for your reply. Yes i read it all. But the blog is from 2011 and is based on wicket 1.5. I downloaded the libs with maven, but it didn't work with wicket 6.11. I wanted to use the latest wicket for the new project. I also tried without seam-wicket in the classpath, but it also didn't help I feel like having tried all possible classpath combinations but none of them worked. I also debugged the initialization of weld at startup but couldn't detect the problem. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662036.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
Hi, wicket-examples module comes with CDI demo application. wicket-examples module is part of every Wicket release. You can see the demo at http://www.wicket-library.com/wicket-examples-6.0.x/cdi/ And the code at https://github.com/apache/wicket/tree/master/wicket-examples/src/main/java/org/apache/wicket/examples/cdi On Wed, Oct 30, 2013 at 11:25 AM, francois meillet francois.meil...@gmail.com wrote: It seems that you have more than one copy of weld in your claspath. Try with that : wicket-core cdi-api seam-conversation-spi wicket-cdi François On Wed, Oct 30, 2013 at 9:07 AM, brazz alexander.li...@man.eu wrote: Hi heapifyman, thanks for your reply. Yes i read it all. But the blog is from 2011 and is based on wicket 1.5. I downloaded the libs with maven, but it didn't work with wicket 6.11. I wanted to use the latest wicket for the new project. I also tried without seam-wicket in the classpath, but it also didn't help I feel like having tried all possible classpath combinations but none of them worked. I also debugged the initialization of weld at startup but couldn't detect the problem. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662036.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
Hello François, thanks for your reply! I double checked this. I have weld-servlet.jar in my classpath. According to the documentation this is the ueber-jar that contains all classes of other jar files. I belive so because otherwise i get NoClassDef-Errors. i changed my classpath and removed wicket-weld according to heapifyman. No my weld related jars in classpath are: weld-servlet.jar seam-conversation-spi-3.0.0.Final.jar seam-conversation-weld-3.0.0.Final.jar wicket-cdi-6.11.0.jar i cannot imagine where a second weld implemention could reside? the rest of my configuration: web.xml: listener listener-classorg.jboss.weld.environment.servlet.Listener/listener-class /listener beans.xml (in WEB-INF- Folder): and my context.xml looks like this: Context path=/sandbox reloadable=true docBase=C:\develop\workspaces\1H_ASPWicketSandbox\ASPWicketSandbox\WebContent workDir=C:\develop\workspaces\1H_ASPWicketSandbox\ASPWicketSandbox\work Logger className=org.apache.catalina.logger.SystemOutLogger verbosity=4 timestamp=true/ Loader className=org.apache.catalina.loader.DevLoader reloadable=true debug=1 useSystemClassLoaderAsParent=false / Resource name=BeanManager auth=Container type=javax.enterprise.inject.spi.BeanManager factory=org.jboss.weld.resources.ManagerObjectFactory/ /Context -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662046.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
your weld related jars in classpath should be: wicket-core cdi-api seam-conversation-spi wicket-cdi François On Wed, Oct 30, 2013 at 10:50 AM, brazz alexander.li...@man.eu wrote: Hello François, thanks for your reply! I double checked this. I have weld-servlet.jar in my classpath. According to the documentation this is the ueber-jar that contains all classes of other jar files. I belive so because otherwise i get NoClassDef-Errors. i changed my classpath and removed wicket-weld according to heapifyman. No my weld related jars in classpath are: weld-servlet.jar seam-conversation-spi-3.0.0.Final.jar seam-conversation-weld-3.0.0.Final.jar wicket-cdi-6.11.0.jar i cannot imagine where a second weld implemention could reside? the rest of my configuration: web.xml: listener listener-classorg.jboss.weld.environment.servlet.Listener/listener-class /listener beans.xml (in WEB-INF- Folder): and my context.xml looks like this: Context path=/sandbox reloadable=true docBase=C:\develop\workspaces\1H_ASPWicketSandbox\ASPWicketSandbox\WebContent workDir=C:\develop\workspaces\1H_ASPWicketSandbox\ASPWicketSandbox\work Logger className=org.apache.catalina.logger.SystemOutLogger verbosity=4 timestamp=true/ Loader className=org.apache.catalina.loader.DevLoader reloadable=true debug=1 useSystemClassLoaderAsParent=false / Resource name=BeanManager auth=Container type=javax.enterprise.inject.spi.BeanManager factory=org.jboss.weld.resources.ManagerObjectFactory/ /Context -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662046.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: wicket conversation scope - weld integration
Hi Martin, thanks for your answer! With the dependencies from your link i now can see log entries of weld. So now it seems to initialize correctly. But i have to run it with wicket version 1.5.10 from the examples page? When i run the examples with wicket 6.11, i get the compile error that method get() of Class CdiConfiguration does not exist. When i run the old examples with wicket 6.11, i get the following (now well known error): WELD-001408 Unsatisfied dependencies for type [ApplicationCounter] with qualifiers [@Default] at injection point [[field] @Inject net.ftlines.wicket.cdi.examples.InjectionPage.counter] this seems to be the main default error of weld. 30.10.2013 15:16:30 org.jboss.weld.bootstrap.WeldBootstrap clinit INFO: WELD-000900 1.1.9 (Final) 30.10.2013 15:16:30 org.jboss.weld.bootstrap.WeldBootstrap startContainer INFO: WELD-000101 Transactional services not available. Injection of @Inject UserTransaction not available. Transactional observers will be invoked synchronously. 30.10.2013 15:16:31 org.jboss.weld.environment.tomcat7.Tomcat7Container initialize INFO: Tomcat 7 detected, CDI injection will be available in Servlets and Filters. Injection into Listeners is not supported 30.10.2013 15:16:31 org.jboss.weld.interceptor.util.InterceptionTypeRegistry clinit WARNUNG: Class 'javax.ejb.PostActivate' not found, interception based on it is not enabled 30.10.2013 15:16:31 org.jboss.weld.interceptor.util.InterceptionTypeRegistry clinit WARNUNG: Class 'javax.ejb.PrePassivate' not found, interception based on it is not enabled -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028p4662049.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
wicket conversation scope - weld integration
Hi, after fighting for several days with integrating cdi with wicket (i am interseted in this conversation scope thing). I ended up with the following stack trace: java.lang.IllegalStateException: Context is already active at org.jboss.weld.context.AbstractConversationContext.activate(AbstractConversationContext.java:245) This is the configuration: tomcat apache-tomcat-7.0.6 or apache-tomcat-7.0.47 seam-conversation-spi-3.0.0.Final.jar seam-wicket.jar weld-servlet.jar cdi-api.jar seam-conversation-weld-3.0.0.Final.jar wicket-cdi-6.11.0.jar wicket version is wicket-6.11.0 cdi version is weld-2.1.0 i think i tried every possible configuration and proposed solution on the internet. Of course i read every article about wicket- cdi, conversation scope, ftlines As it has to run although on WAS7, i'm not very optimistic. Has anyone tried that? Thanks for any suggestions. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/wicket-conversation-scope-weld-integration-tp4662028.html Sent from the Users forum mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
