Re: T4.1.1 - ComponentClass and Component annotation question

hows the release coming? Jesse Kuhnert wrote: I think I'm going to start a vote to release it this week, so if that goes well possibly this week. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:

Re: T4.1.1 - ComponentClass and Component annotation question

http://jira.opensymphony.com/browse/OGNL-84 2007/5/29, Jesse Kuhnert <[EMAIL PROTECTED]>: 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 t

Re: T4.1.1 - ComponentClass and Component annotation question

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 upgr

Re: T4.1.1 - ComponentClass and Component annotation question

+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

Re: T4.1.1 - ComponentClass and Component annotation question

where do i vote, i need it released desperately. Jesse Kuhnert wrote: I think I'm going to start a vote to release it this week, so if that goes well possibly this week. - To unsubscribe, e-mail: [EMAIL PROTECTED] For addit

Re: T4.1.1 - ComponentClass and Component annotation question

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 alrea

Re: T4.1.1 - ComponentClass and Component annotation question

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)

Re: T4.1.1 - ComponentClass and Component annotation question

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

Re: T4.1.1 - ComponentClass and Component annotation question

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 (/components). A > couple of components had an "empty" component specification file (.jwc) - > so I tried to use @ComponentClass

Re: T4.1.1 - ComponentClass and Component annotation question

Anybody have a clue for me? -J. > First... > > I had some components specified in a directory (/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 cl

T4.1.1 - ComponentClass and Component annotation question

First... I had some components specified in a directory (/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 comp