1 2 3 Previous Next 34 Replies Latest reply on Nov 25, 2011 1:09 AM by snyder8888 Go to original post
      • 15. Re: Seam Wicket and Servlet
        oranheim

        Hi Dan,


        I agree. In case you want a feature sooner, then one should participate and sumbit patches/contribute.


        I've made a SeamWicketTester and it seems to work out. I'll read through the documentation and will upload my patch. One thing was the tester bean, I also need to write a couple of test cases for NumberGuess so we get it proper shape.


        Cheers,
        Ove

        • 16. Re: Seam Wicket and Servlet
          dan.j.allen

          Excellent! Feel free to stop by seam-dev IRC and chat with the group. We are starting to grow again and if we can't help you, we'll at least make you laugh a few times :)


          seam-dev irc info

          • 17. Re: Seam Wicket and Servlet
            oranheim

            Visited seam-dev and Aslak pointed me to some git reading, so I need to enlighten myself on the diff/patch and do a pull request to the upstream repo.


            I'd like to commit a new sub-module: seam-wicket-mock; to get SeamWicketTester in place. Then write up some NumberGuess tests.


            Secondly, I have written a blog app (very simple example) which for the most part demonstrates CRUD operations using Scala, CDI, Wicket and off course have Arquillian/ShrinkWrap. This might be a nice show off as opposed to LiftWeb.


            Weld and Seam 3 is fun! Scala coding makes it even more fun. Though, Java and Faces is my core focus in my main project.


            The fork I'm working on is checked out by: git clone git://github.com/seam/wicket. It this a right starting point? Should it be forked in a different way, upon making pull request to the upstream repo?

            • 18. Re: Seam Wicket and Servlet
              dan.j.allen

              Ove Ranheim wrote on Jan 11, 2011 19:08:


              Visited seam-dev and Aslak pointed me to some git reading, so I need to enlighten myself on the diff/patch and do a pull request to the upstream repo.


              Excellent! Ah, but did you laugh? :) If not, be sure to come back when lincoln's evil twin is around :)



              I'd like to commit a new sub-module: seam-wicket-mock; to get SeamWicketTester in place. Then write up some NumberGuess tests.


              Great. As you've probably noticed, the Wicket module seem to have left its tests somewhere :) So any test is a good test at this point.



              Secondly, I have written a blog app (very simple example) which for the most part demonstrates CRUD operations using Scala, CDI, Wicket and off course have Arquillian/ShrinkWrap. This might be a nice show off as opposed to LiftWeb.


              Awesome! This would be a great addition to the examples for the Wicket module. I look forward to the pull request.



              The fork I'm working on is checked out by: git clone git://github.com/seam/wicket. It this a right starting point? Should it be forked in a different way, upon making pull request to the upstream repo?


              It's funny you should ask because a guide is currently in the works! In the meantime, checkout the Hacking AS7 guide for a sample workflow.



              Weld and Seam 3 is fun! Scala coding makes it even more fun. Though, Java and Faces is my core focus in my main project.


              We'd love to get your help and/or input on Seam Faces as well!

              • 19. Re: Seam Wicket and Servlet
                kariem

                Kariem, what modifications have you done?

                Our modification were meant to let us use a current version of Hibernate Search and support dependency injection via @Inject. Not a big thing and from what I have seen this should already be done in the current beta.


                On the topic of contributing to the project, I really liked the announcement on Hibernate's move to github: Hibernate moves to Git + Git tips and tricks.

                • 20. Re: Seam Wicket and Servlet
                  oranheim

                  Excellent! Ah, but did you laugh? :) If not, be sure to come back when lincoln's evil twin is around :)


                  Not this time; as I didn't see lincoln's evil twin in there :)


                  What makes me laugh is having a descending dev cycle, so you'd except alpha3 to come after beta1 ;-)



                  Great. As you've probably noticed, the Wicket module seem to have left its tests somewhere :) So any test is a good test at this point.


                  Awesome! :-)



                  It's funny you should ask because a guide is currently in the works! In the meantime, checkout the Hacking AS7 guide for a sample workflow.


                  I got my env set up, which means I might be productive.

                  • 21. Re: Seam Wicket and Servlet
                    dan.j.allen

                    Ove Ranheim wrote on Jan 12, 2011 09:41:



                    Dan Allen wrote:

                    Excellent! Ah, but did you laugh? :) If not, be sure to come back when lincoln's evil twin is around :)


                    Not this time; as I didn't see lincoln's evil twin in there :)


                    Calling Lincoln's evil twin. Come out to play!




                    What makes me laugh is having a descending dev cycle, so you'd except alpha3 to come after beta1 ;-)


                    We like to think outside of the box :)




                    I got my env set up, which means I might be productive.



                    ...and there was much rejoicing!

                    • 22. Re: Seam Wicket and Servlet
                      oranheim

                      Done and committed! Now it is all up to you to consider my contribution :)


                      Have a nice day!


                      -ove-

                      • 23. Re: Seam Wicket and Servlet
                        dan.j.allen

                        Ove,


                        I've committed your changes after some reworking. Trust that all of your changes got applied, they just may look a bit different. You may have to reset hard to HEAD in order to get in sync.


                        I noticed that your XML files had tabs in them. The convention in the Seam project is to expand tabs to spaces. If you could please switch that it will make merges simpler ;)


                        Here are the dev guidelines for Seam: Seam development guidelines


                        Thanks again!

                        • 24. Re: Seam Wicket and Servlet
                          lightguard
                          • 25. Re: Seam Wicket and Servlet
                            Hi Dan,
                            
                            tried the steps above, but get an error starting jetty:
                            
                            INFO: Seam Solder 3.0.0.Beta1 (build id: 20101220-2046)
                            23-jan-2011 23:02:16 org.jboss.weld.environment.servlet.Listener contextInitiali
                            zed
                            INFO: Jetty detected, JSR-299 injection will be available in Servlets and Filter
                            s. Injection into Listeners is not supported.
                            2011-01-23 23:02:16.268::WARN:  failed org.mortbay.jetty.plugin.Jetty6PluginWebA
                            ppContext@6e8504{/seam-wicket-example-numberguess,seam3-wicket
                            wickeumberguessrcmainwebapp}: java.lang.LinkageError: loader con
                            straint violation: loader (instance of org/codehaus/plexus/classworlds/realm/Cla
                            ssRealm) previously initiated loading for a different type with name "javax/el/E
                            xpressionFactory"
                            2011-01-23 23:02:16.268::WARN:  failed ContextHandlerCollection@fe53cf: java.lan
                            g.LinkageError: loader constraint violation: loader (instance of org/codehaus/pl
                            exus/classworlds/realm/ClassRealm) previously initiated loading for a different
                            type with name javax/el/ExpressionFactory
                            2011-01-23 23:02:16.269::WARN:  failed HandlerCollection@130500f: java.lang.Link
                            ageError: loader constraint violation: loader (instance of org/codehaus/plexus/c
                            lassworlds/realm/ClassRealm) previously initiated loading for a different type w
                            ith name "javax/el/ExpressionFactory"
                            2011-01-23 23:02:16.269::WARN:  Error starting handlers
                            java.lang.LinkageError: loader constraint violation: loader (instance of org/cod
                            ehaus/plexus/classworlds/realm/ClassRealm) previously initiated loading for a di
                            fferent type with name "javax/el/ExpressionFactory"
                                    at java.lang.ClassLoader.defineClass1(Native Method)
                                    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
                                    at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
                                    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:14
                            1)
                                    at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
                                    at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
                                    at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
                                    at java.security.AccessController.doPrivileged(Native Method)
                                    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
                                    at org.codehaus.plexus.classworlds.realm.ClassRealm.loadClassFromSelf(Cl
                            assRealm.java:386)
                            
                            I have been trying to get Seam 3, Wicket and RESTeasy to work for a few hours now. Finally decided to use the numberguess example as a reference, so I

                            m eager to get it to work.

                            • 26. Re: Seam Wicket and Servlet
                              dan.j.allen

                              Chances are you are getting this because you have an EL API on the classpath when Jetty is starting. It's likely being pulled in by a Maven dependency. Execute mvn dependency:tree and figure out what needs to be excluded.


                              It would be helpful for others following this discussion if you could post your dependencies. Just the output of dependency:tree would do. Thanks!

                              • 27. Re: Seam Wicket and Servlet

                                Dan,


                                I pulled the numberguess straight from github. I'm now on another machine, I'll try to reproduce the problem.

                                • 28. Re: Seam Wicket and Servlet
                                  mvn dependency:tree

                                  [INFO] ------------------------------------------------------------------------
                                  [INFO] Building Seam Wicket Numberguess example 3.0.0-SNAPSHOT
                                  [INFO] ------------------------------------------------------------------------
                                  [INFO]
                                  [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ seam-wicket-example-
                                  numberguess ---
                                  [INFO] org.jboss.seam.wicket:seam-wicket-example-numberguess:war:3.0.0-SNAPSHOT
                                  [INFO] +- org.jboss.seam.wicket:seam-wicket-api:jar:3.0.0-SNAPSHOT:compile
                                  [INFO] |  \- org.apache.wicket:wicket:jar:1.4.14:compile
                                  [INFO] |     \- org.slf4j:slf4j-api:jar:1.5.10:compile (version managed from 1.5
                                  .8)
                                  [INFO] +- org.jboss.seam.solder:seam-solder-api:jar:3.0.0.Beta1:provided (scope
                                  not updated to compile)
                                  [INFO] +- org.jboss.seam.solder:seam-solder:jar:3.0.0.Beta1:runtime
                                  [INFO] |  \- org.jboss.logging:jboss-logging:jar:3.0.0.Beta4:runtime
                                  [INFO] +- org.jboss.seam.wicket:seam-wicket-mock:jar:3.0.0-SNAPSHOT:test
                                  [INFO] +- javax.enterprise:cdi-api:jar:1.0-SP4:provided
                                  [INFO] |  +- org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.1_spec:ja
                                  r:1.0.0.Final:provided (version managed from 1.0.0.Beta1)
                                  [INFO] |  \- javax.inject:javax.inject:jar:1:provided
                                  [INFO] +- junit:junit:jar:4.8.1:test
                                  [INFO] \- org.jboss.arquillian:arquillian-junit:jar:1.0.0.Alpha4:test
                                  [INFO]    \- org.jboss.arquillian:arquillian-impl-base:jar:1.0.0.Alpha4:test
                                  [INFO]       +- org.jboss.arquillian:arquillian-api:jar:1.0.0.Alpha4:test
                                  [INFO]       |  \- org.jboss.shrinkwrap:shrinkwrap-api:jar:1.0.0-alpha-11:test
                                  [INFO]       +- org.jboss.arquillian:arquillian-spi:jar:1.0.0.Alpha4:test
                                  [INFO]       +- org.jboss.shrinkwrap:shrinkwrap-impl-base:jar:1.0.0-alpha-11:tes
                                  t
                                  [INFO]       \- org.jboss.shrinkwrap:shrinkwrap-spi:jar:1.0.0-alpha-11:test
                                  • 29. Re: Seam Wicket and Servlet
                                    oranheim

                                    I think the reason is because jetty loads the the wrong configuration when you try to start jetty with numberguess.


                                    I had it fixed, but because my files contained tab spaces and not fixed spaces, something went wrong during the pull request.


                                    I'll look into this shortly.


                                    Ove