Ted Husted wrote:
On Nov 1, 2007 4:10 PM, Brian Pontarelli [EMAIL PROTECTED] wrote:
s:hidden name=[EMAIL PROTECTED] value=EUR/
s:textfield key=child.allowance/
c:hidden name=[EMAIL PROTECTED] value=MM/dd//
s:textfield key=subscription.expireDate/
Is the use case that these facts
On Nov 1, 2007 4:10 PM, Brian Pontarelli [EMAIL PROTECTED] wrote:
s:hidden name=[EMAIL PROTECTED] value=EUR/
s:textfield key=child.allowance/
c:hidden name=[EMAIL PROTECTED] value=MM/dd//
s:textfield key=subscription.expireDate/
Is the use case that these facts are embedded in the page,
So, just wanted to toss this into the mix and see what you all thought.
Here's the issue I had:
Vertigo has a Money object that is a value and currency. I wanted to set
the value from a form. I wanted the currency code to be definable for
that specific form element. Oh, and Money is
I've always wondered why all parameters are not passed to the
converter. There are a lot of cases, (like yours) when the conversion
depends on other parameters. If all parameters were passed to the
converter you wouldn't need this right? I feel kind of uncomfortable
with adding yet another syntax.
True to some degree. You still have the issue that some of the
parameters don't map to properties of the JavaBean. If you did this:
s:hidden name=user.allowance.currencyCode value=USD/
s:textfield key=user.allowance.amount/
You would need to specify that the currencyCode should be excluded,
