Sorry for not explaining...I don't quite remember if i removed usages of tapestry-prop (i still see that in the pom) but i know that the reason beanform moved into tacos was to make it work for T4.1.2+
So, get versions 0.8 or (even better) 0.9 See http://mirrors.ibiblio.org/pub/mirrors/maven2/net/sf/tacos/beanform-core/ and notice that the groupId has changed! On Jan 5, 2008 8:22 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > I'd be really interested in knowing how :-) > > As far as I know, tapestry-prop 1.0.0 does not work with Tapestry 4.1.2+. I > know I had a heck of a time upgrading Tapestry because of it and had to > track down all of my prop references to change them to ognl (slightly more > fun than when I went from ognl to prop). Indeed, the following JIRA issue > seems to indicate the same: > > https://issues.apache.org/jira/browse/TAPESTRY-1586 > > This is largely why I thought that having a dependency on both > Tapestry-4.1.2 and tapestry-prop-1.0.0 was contradictory. > > Anyway, I did grab the tapestry-prop JAR and throw it on my classpath. I > don't get parse exceptions from Tapestry anymore, but I do get > javassist.NotFoundExceptions much like those described in the aforementiond > JIRA. This is with BeanForm 0.7 on Tapestry 4.1.4-SNAPSHOT, FWIW. > > I'm open to the notion that I'm doing something wrong, so any suggestions > would be appreciated. > > Regards, > Kevin > > > On 1/5/08 12:40 PM, in article > [EMAIL PROTECTED], "Andreas > > Andreou" <[EMAIL PROTECTED]> wrote: > > > I have BeanForm working in a live 4.1.3 app, so it just works... ! > > > > > > On Jan 5, 2008 6:33 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > >> Hi all, > >> > >> Are there any plans to update BeanForm to use OGNL rather than > >> tapestry-prop? Unless I'm mistaken, tapestry-prop doesn't work with 4.1.x > >> anymore, making it impossible to BeanForm. Even if that weren't the case, > >> given the optimizations made in OGNL switching back shouldn't hurt > >> performance but would remove an additional third party dependency. > >> > >> I can put together a patch pretty trivially, but just wanted to make sure > >> it > >> wasn't something being actively worked on. > >> > >> -- > >> Kevin > >> > >> > >> > >> ------------------------------------------------------------------------- > >> This SF.net email is sponsored by: Microsoft > >> Defy all challenges. Microsoft(R) Visual Studio 2005. > >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > >> _______________________________________________ > >> Tacos-devel mailing list > >> Tacos-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/tacos-devel > >> > > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Tacos-devel mailing list > Tacos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tacos-devel > -- Andreas Andreou - [EMAIL PROTECTED] - http://blog.andyhot.gr Tapestry / Tacos developer Open Source / JEE Consulting ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Tacos-devel mailing list Tacos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tacos-devel