A problem with the Spring approach is that parameter names are not accessible
by reflection.
The consequence is that if you have method like
public void substract(int param1, int param2)
It will be difficult to pass the parameters in the right order. You will need
either the source code to find t
Are you sure? I think that if you compile with debug info turned
on, and your request parameters are named param1 and param2,
they will be bound correctly without the need for the annotations.
Or is that what you meant by "you will need the source code"?
Cheers,
Freddy
On Tue, 5 Oct 2010 08:36:4
It's a problem that we faced in MyBatis when dealing with multiple parameters.
We went with the annotation approach.
I guess there are many workarounds for that and Spring is probably using one.
Debug seems like a good workaround.
Christian
-Message d'origine-
De : Freddy Daoud [mailto:
Looks like some folks have gone to great lengths to add access to parameter
names, eg: http://paranamer.codehaus.org/
On Oct 5, 2010, at 6:48 AM, Poitras Christian wrote:
> It's a problem that we faced in MyBatis when dealing with multiple
> parameters. We went with the annotation approach.
>
Here's an interesting approach from the waffle framework. It uses annotations,
but lists all the parameter names in a single annotation.
@ActionMethod(parameters = {"firstNumber", "secondNumber"})
Evan
On Oct 5, 2010, at 6:48 AM, Poitras Christian wrote:
> It's a problem that we faced in M
Evan / Christian / Remi et al.
This thread is very interesting and I am enjoying it... and hope it
continues...
However, can we rename this thread to something more aligned to the
discussion?
If no one minds I have taken the liberty to rename it to the above ;-)
Regards,
--Nikolaos
Evan L
Certainly!
I started doing a little prototyping with this today while waiting for another
build to finish. I'm trying the approach of having one annotation on the method
like this:
@ParamBinding({"aString", "aNumber"})
public Resolution myAction(String aString, int aNumber) { ... }
The qu
The downside of using 2 binders is that it's difficult to mix both approach.
Still, it would seem bizarre to have both approach in the same program...
-Message d'origine-
De : Evan Leonard [mailto:evan.leon...@gmail.com]
Envoyé : October-05-10 3:31 PM
À : nikol...@brightminds.org; Stripe
I was thinking it would be possible to use both. Either by adding a second type
of binder to the configuration, so they both run, or potentially by subclassing
the existing binder to overlay the functionality.
On Oct 5, 2010, at 2:36 PM, Poitras Christian wrote:
> The downside of using 2 bind
On 29 Sep 2010, at 20:40, Ben Gunter wrote:
> I believe I finally have the streaming layout code working. I'm asking *all*
> of you to get the latest snapshot from the Sonatype snapshots repo and try it
> out. If you see any problems with what it outputs, please let me know on this
> thread. T
Hello!
Would love to help test, but first what are Streaming Layouts?
Joaquin
On Oct 5, 2010, at 3:11 PM, Stephen Nelson wrote:
>
> On 29 Sep 2010, at 20:40, Ben Gunter wrote:
>
>> I believe I finally have the streaming layout code working. I'm asking *all*
>> of you to get the latest snap
The layout tags in 1.5.3 and earlier buffer virtually everything in memory
before dumping it all out at once. I've modified the tags to stream directly
to output instead, but it required a major overhaul so I'd like to have it
tested thoroughly before I release 1.5.4. From the perspective of the
St
Thank you for the great explanation. I will run a few tested tonight.
On Oct 5, 2010, at 5:28 PM, Ben Gunter wrote:
> The layout tags in 1.5.3 and earlier buffer virtually everything in memory
> before dumping it all out at once. I've modified the tags to stream directly
> to output instead, b
13 matches
Mail list logo
