OGNL errors? Hmmm. When you do file them the best place is here:
http://jira.opensymphony.com/browse/OGNL Please do file them when you get a chance as I'm not as comfortable making a release knowing they exist. On 5/29/07, Christian Dutaret <[EMAIL PROTECTED]> wrote:
+1 Just tried an upgrade from 4.1.1 (large app) and it went more smoothly than I expected. A few OGNL and EventListener issues here and there, not too difficult to fix. When I have time, I'll post the OGNL issues I noticed (all related to the way expressions like "prop1.prop2[index]" are handled - quick fix replace with "prop1.getProp2(index)") So whenever you start the vote, count me in ;-) 2007/5/28, Jesse Kuhnert <[EMAIL PROTECTED]>: > > I think I'm going to start a vote to release it this week, so if that > goes > well possibly this week. > > On 5/28/07, Jan Vissers <[EMAIL PROTECTED]> wrote: > > > > And... > > any idea when T4.1.2 will be released. I'm currently (re)evaluating > T4.1+ > > as one of our predominant (web)frameworks - currently we already use > > T3/T4.0.2 quite frequently. > > > > -J. > > > > > Ok, thanks.... > > > > > > But what does this mean exactly, in terms of how I specify the > > @Component? > > > Should I (still) use: @Component(type="components/Feedback") > > > or something different? > > > > > > Suppose I would have bundled these components into a Tapestry library > - > > > would that have changed something, or is this not comparable from > using > > a > > > Component as part of your application, so without libraries? > > > > > > This 4.1.2-SNAPSHOT contains a fix, for something I guess - right? > > > Can I use 4.1.2-SNAPSHOT with JDK1.4, provided I decide not to use > > > annotations? > > > > > > Thanks again > > > -J. > > > > > >> Use 4.1.2-SNAPSHOT. > > >> > > >> On 5/28/07, Jan Vissers <[EMAIL PROTECTED]> wrote: > > >>> > > >>> Anybody have a clue for me? > > >>> > > >>> -J. > > >>> > > >>> > First... > > >>> > > > >>> > I had some components specified in a directory > > >>> (<ctxroot>/components). > > >>> A > > >>> > couple of components had an "empty" component specification file > > >>> (.jwc) > > >>> - > > >>> > so I tried to use @ComponentClass on the component so I don't need > > >>> the > > >>> > .jwc file any longer. > > >>> > > > >>> > A page class in my application first used the .jwc'd component > like > > >>> so: > > >>> > > > >>> > @Component(type="components/Feedback") > > >>> > public abstract Feedback getFeedback(); > > >>> > > > >>> > Question: > > >>> > > > >>> > How should I specify @ComponentClass and/or @Component annotation, > > so > > >>> the > > >>> > component is properly spotted when the page loads? - currently I > > have > > >>> been > > >>> > unable to. Remember the <ctxroot>/components folder only contains > > the > > >>> > component's html template. > > >>> > > > >>> > Thanks, > > >>> > -J. > > >>> > > > >>> > > > >>> > > > --------------------------------------------------------------------- > > >>> > To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>> > For additional commands, e-mail: [EMAIL PROTECTED] > > >>> > > > >>> > > > >>> > > >>> > > >>> > > >>> > --------------------------------------------------------------------- > > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > > >>> For additional commands, e-mail: [EMAIL PROTECTED] > > >>> > > >>> > > >> > > >> > > >> -- > > >> Jesse Kuhnert > > >> Tapestry/Dojo team member/developer > > >> > > >> Open source based consulting work centered around > > >> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > >> > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Jesse Kuhnert > Tapestry/Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com >
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
