You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Thiago H. de Paula Figueiredo" <th...@gmail.com> on 2009/10/22 22:13:37 UTC

Re: svn commit: r828823 - in /tapestry/tapestry5/trunk/tapestry-beanvalidator: ./ src/ src/main/ src/main/java/ src/main/java/org/ src/main/java/org/apache/ src/main/java/org/apache/tapestry5/ src/main/java/org/apache/tapestry5/beanvalidator/ src/mai

Em Thu, 22 Oct 2009 18:00:49 -0200, Igor Drobiazko  
<ig...@gmail.com> escreveu:

> Well, I actually don't care about names. We can rename it if needed. But
> then we also should rename tapestry-webflow to tapestry-web-flow. ;)

Oops, I forgot about tapestry-webflow, so please ignore this comment. ;)

>> * Why don't we add some object validation service to Tapestry-IoC and  
>> have tapestry-beanvalidator implement it? This way, non-web code can  
>> also use the validation code.
>>
> We can do it in the future if needed.

Ok!

>> * I haven't read almost anything about JSR 303 yet, but does
>> tapestry-beanvalidator implement cross-property validation like  
>> @AssertTrue or @AssertFalse?
> This module doesn't implement any validator yet.

javax.validation.Validator?

>> * Is it the whole code or this commit is just a partial one?
>
> Nope.

I didn't get your answer. I asked an enum question and received a boolean  
response. :P

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Re: svn commit: r828823 - in /tapestry/tapestry5/trunk/tapestry-beanvalidator: ./ src/ src/main/ src/main/java/ src/main/java/org/ src/main/java/org/apache/ src/main/java/org/apache/tapestry5/ src/main/java/org/apache/tapestry5/beanvalidator/ src/mai

Posted by Igor Drobiazko <ig...@gmail.com>.
On Thu, Oct 22, 2009 at 10:13 PM, Thiago H. de Paula Figueiredo <
thiagohp@gmail.com> wrote:

> Em Thu, 22 Oct 2009 18:00:49 -0200, Igor Drobiazko <
> igor.drobiazko@gmail.com> escreveu:
>
>  Well, I actually don't care about names. We can rename it if needed. But
>> then we also should rename tapestry-webflow to tapestry-web-flow. ;)
>>
>
> Oops, I forgot about tapestry-webflow, so please ignore this comment. ;)
>
>  * Why don't we add some object validation service to Tapestry-IoC and have
>>> tapestry-beanvalidator implement it? This way, non-web code can also use the
>>> validation code.
>>>
>>>  We can do it in the future if needed.
>>
>
> Ok!
>
>  * I haven't read almost anything about JSR 303 yet, but does
>>> tapestry-beanvalidator implement cross-property validation like
>>> @AssertTrue or @AssertFalse?
>>>
>> This module doesn't implement any validator yet.
>>
>
> javax.validation.Validator?


By now there is only the integration of Tapestry and JSR-303. Nothing else.
We can add new annotations and ConstraintsValidators if needed. I think of
something like @DependsOn. I have already implemented similar for one of my
non Tapestry projects.

>
>
>  * Is it the whole code or this commit is just a partial one?
>>>
>>
>> Nope.
>>
>
> I didn't get your answer. I asked an enum question and received a boolean
> response. :P


I committed all the code so far. But there are still some issues to do, so
more code still to come.

>
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java consultant, developer, and instructor
> http://www.arsmachina.com.br/thiago
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>


-- 
Best regards,

Igor Drobiazko