You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Ralf E. Stranzenbach" <mo...@reswi.de> on 2005/08/13 23:44:52 UTC
Boxing / Unboxing in Tapestry 4B4
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
AW: Boxing / Unboxing in Tapestry 4B4
Posted by "Ralf E. Stranzenbach" <ra...@reswi.de>.
Hi,
I had the time to check this and it seems that this "misbehaviour" was an
outcome of my problems related to my use of "default-binding".
I'm not sure what happened but midway of the migration from beta3 to beta4
Tapestry/My Application disliked a long parameter and complained about
converting some Long value.
After a clean build now everything is gone...
Sorry for the inconvenience,
- Ralf
-----Ursprüngliche Nachricht-----
Von: Ralf E. Stranzenbach [mailto:ralf@reswi.de]
Gesendet: Sonntag, 14. August 2005 22:34
An: 'Tapestry users'
Betreff: AW: Boxing / Unboxing in Tapestry 4B4
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:hlship@gmail.com]
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 <mo...@reswi.de> 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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
AW: Boxing / Unboxing in Tapestry 4B4
Posted by "Ralf E. Stranzenbach" <ra...@reswi.de>.
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:hlship@gmail.com]
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 <mo...@reswi.de> 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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Boxing / Unboxing in Tapestry 4B4
Posted by Howard Lewis Ship <hl...@gmail.com>.
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 <mo...@reswi.de> 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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org
Re: Boxing / Unboxing in Tapestry 4B4
Posted by Howard Lewis Ship <hl...@gmail.com>.
Very odd; no changes in the code, this should work. You would get
tripped up if the parameter was null (null can't be expressed as a
long, just as a Long, and would likely cause a runtime error).
On 8/13/05, Ralf E. Stranzenbach <mo...@reswi.de> 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: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org