Hi, because i'm in the midst of the migration of my application from beta3 to beta4 (it hit me hard) i was very puzzeled about this thing and tried to get an idea on what changed in this case.
I'll try to drill down to that problem (first workaround was to migrate from long to Long) and drop a notice afterwards. - Ralf -----Ursprüngliche Nachricht----- Von: Howard Lewis Ship [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 14. August 2005 14:02 An: Tapestry users Betreff: Re: Boxing / Unboxing in Tapestry 4B4 And, as usual, you MUST QUALIFY WHAT "STOPPED WORKING" MEANS? Generally, a stack trace is the MINIMUM amount of information we need. On 8/13/05, Ralf E. Stranzenbach <[EMAIL PROTECTED]> wrote: > Hi, > > I noticed that since Tapestry 4-beta4 my listeners and parameters stoped > working with "long" values. I'm now enforced to using "Long" instead. > > Is this a planned behaviour ? > > > Regards, > Ralf Edmund Stranzenbach > > > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.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]
