The fact that optional parameters worked in the past was unintentional. However it seems like a good idea, I'm just trying to think of the best way to implement it. I'd rather not add another method to the Validator interface, if possible ... in fact, I'm thinking of simplifying it (putting more of the information gathered from the interface into a contribution to the service) ... go ahead, an an issue, but bear in mind that the API will likely change a bit. Viva le Alpha!
On 7/6/07, Dan Adams <[EMAIL PROTECTED]> wrote:
I have a validator that takes one optional constraint. If it's not specified it defaults to something reasonable. But now that I updated to 5.0.5 I don't seem to be able to do this. Should I file a ticket? -- Dan Adams Senior Software Engineer Interactive Factory 617.235.5857 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache 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]
