I think everything I've done is checked in currently. I'll take a look at your patches later and see how things shake out. One thing I noticed was that my beans weren't being picked up from my local project if I didn't include a src/main/resources/META-INF/beans.xml file in there. I guess the classpath scanning looks for all of those resources and scans those locations only or something. Again, thanks for taking a look at what I put together. I plan on doing the conversation stuff very soon, so stay tuned.
On Tue, Mar 30, 2010 at 7:43 AM, Cemal Bayramoglu < jweekend_for...@cabouge.com> wrote: > James, > > I'm pretty sure "mvn test" ran successfully on all your projects once > I patched the POMs. > I ran some (maybe not all) of the demo apps too. > Send me your patches if you like too (they must not have been deployed > yet on Sunday) and I may be able to take another look this evening or > tomorrow PM. > > Regards - Cemal > jWeekend > OO & Java Technologies, Wicket > Consulting, Development, Training > http://jWeekend.com > > On 30 March 2010 12:30, James Carman <jcar...@carmanconsulting.com> wrote: > > I was using M4 of OWB, but I had to patch it. Are you sure it works for > > you? I was getting a NPE. > > > > On Tue, Mar 30, 2010 at 7:22 AM, Cemal Bayramoglu < > > jweekend_for...@cabouge.com> wrote: > > > >> James, > >> > >> See the patch below; please double-check but it should be still valid > >> if you haven't updated your POMs since Sunday AM your time. > >> > >> Regards - Cemal > >> jWeekend > >> OO & Java Technologies, Wicket > >> Consulting, Development, Training > >> http://jWeekend.com > >> > >> ====================== PATCH STARTS BELOW ============================= > >> Index: pom.xml > >> =================================================================== > >> --- pom.xml (revision 78) > >> +++ pom.xml (working copy) > >> @@ -36,4 +36,22 @@ > >> </plugin> > >> </plugins> > >> </build> > >> + > >> + <repositories> > >> + <repository> > >> + <id>JBoss Repo</id> > >> + <url>http://repository.jboss.com/maven2</url> > >> + </repository> > >> + > >> + <repository> > >> + <id>geronimo-snapshots</id> > >> + <name>Apache Nexus Snapshots</name> > >> + > >> <url>https://repository.apache.org/content/groups/snapshots-group</url> > >> + <snapshots> > >> + <enabled>true</enabled> > >> + </snapshots> > >> + </repository> > >> + > >> + </repositories> > >> + > >> </project> > >> \ No newline at end of file > >> Index: owb/pom.xml > >> =================================================================== > >> --- owb/pom.xml (revision 78) > >> +++ owb/pom.xml (working copy) > >> @@ -16,11 +16,12 @@ > >> <artifactId>wicket-cdi</artifactId> > >> <version>${project.version}</version> > >> </dependency> > >> - <dependency> > >> - <groupId>org.apache.openwebbeans</groupId> > >> - <artifactId>openwebbeans-impl</artifactId> > >> - <version>1.0.0-SNAPSHOT</version> > >> - </dependency> > >> +<dependency> > >> + <groupId>org.apache.openwebbeans</groupId> > >> + <artifactId>openwebbeans-impl</artifactId> > >> + <version>1.0.0-M4</version> > >> +</dependency> > >> + > >> <dependency> > >> <groupId>org.apache.geronimo.specs</groupId> > >> <artifactId>geronimo-jcdi_1.0_spec</artifactId> > >> Index: owb-example/pom.xml > >> =================================================================== > >> --- owb-example/pom.xml (revision 78) > >> +++ owb-example/pom.xml (working copy) > >> @@ -62,15 +62,11 @@ > >> <artifactId>wicket-cdi-owb</artifactId> > >> <version>${project.version}</version> > >> </dependency> > >> - <dependency> > >> - <groupId>org.apache.openwebbeans</groupId> > >> - <artifactId>openwebbeans-web</artifactId> > >> - <version>1.0.0-SNAPSHOT</version> > >> - </dependency> > >> + > >> <dependency> > >> <groupId>org.apache.openwebbeans</groupId> > >> <artifactId>openwebbeans-spi</artifactId> > >> - <version>1.0.0-SNAPSHOT</version> > >> + <version>1.0.0-M4</version> > >> </dependency> > >> <dependency> > >> <groupId>org.apache.geronimo.specs</groupId> > >> ====================== END OF PATCH ABOVE ======================== > >> > >> On 30 March 2010 12:09, James Carman <jcar...@carmanconsulting.com> > wrote: > >> > Cemal, > >> > > >> > Please feel free to send me a patch if anything looks crazy. I have > had > >> a > >> > heck of a time getting all this stuff working. It's a delicate > balance > >> > (like herding cats)! :) The OWB folks have checked in my patch to fix > >> one > >> > of the issues, but we're still hammering out another. > >> > > >> > Thanks, > >> > > >> > James > >> > > >> > On Tue, Mar 30, 2010 at 7:05 AM, Cemal Bayramoglu < > >> > jweekend_for...@cabouge.com> wrote: > >> > > >> >> Olivier, > >> >> > >> >> I got Jame's stuff [1] up and running (thanks James) with just a few > >> >> small changes to the POMs - maybe he has stuff already in his local > >> >> Maven repo that is no longer on the main public repos) working with > >> >> little effort. > >> >> > >> >> If you'd like to make (and maintain ;-) an archetype out of those > >> >> (based on Apache implementations), or a Galssfish based one, we > would > >> >> be happy to include those on our LegUp page [2][3]. > >> >> > >> >> Regards - Cemal > >> >> jWeekend > >> >> OO & Java Technologies, Wicket > >> >> Consulting, Development, Training > >> >> http://jWeekend.com > >> >> > >> >> [1] http://svn.carmanconsulting.com/public/wicket-cdi/trunk > >> >> [2] http://jweekend.com/dev/LegUp > >> >> [3] http://code.google.com/p/legup/ > >> >> > >> >> > >> >> On 30 March 2010 10:24, Olivier Bourgeois > >> >> <olivier.bourgeois....@gmail.com> wrote: > >> >> > I do also think that it's because Wicket is not a managed framework > : > >> >> > everything is simple unmanaged POJOs except for your classes > extending > >> >> > WebPage which are "managed". I've juste had a quick look at JSF 2.0 > >> and > >> >> > never worked with it - but I worked with Wicket - so I did not > >> expected > >> >> > Wicket JEE6 integration to be a drop in replacement for JSF. I do > >> think > >> >> > Wicket is an alternative framework for JEE6, not a replacement of > the > >> >> > reference framework. > >> >> > > >> >> > On one hand JSF2 assumes that you are running a JEE6 AS, so it is > >> tightly > >> >> > integrated with CDI, and you got all the cool stuff like injection, > >> >> scopes, > >> >> > bean validation, etc. On the other hand, Wicket doesn't assume > >> anything > >> >> > except a web container implementing the servlet spec, so it can't > have > >> >> all > >> >> > the cool stuff of CDI because it's not built around CDI. > >> >> > > >> >> > I think the next step to make Wicket JEE6 integration going further > is > >> to > >> >> > provide some Maven quickstart archetypes, the Weld team is looking > for > >> >> > contributors : > >> >> http://in.relation.to/Bloggers/WeldArchetypesInTheSpotlight > >> >> > > >> >> > Now that I have something working, and when I will have some spare > >> time, > >> >> my > >> >> > next step is to create an archetype for Glassfish. And if some > people > >> on > >> >> > this list have some time, their help is of course welcome :) > >> >> > > >> >> > >> >> --------------------------------------------------------------------- > >> >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> >> For additional commands, e-mail: users-h...@wicket.apache.org > >> >> > >> >> > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
