<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Bean Validation initial draft released</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Wed, 22 May 2013 11:44:52 -0400</pubDate>


    <item>

        <title>problematic with JSR-303</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[I have a question about JSR-303....]]></description>
        

        <pubDate>Mon, 20 Apr 2009 06:51:53 -0400</pubDate>

        

        <jf:creationDate>Mon, 20 Apr 2009 06:51:53 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 20 Apr 2009 06:51:53 -0400</jf:modificationDate>
        <jf:date>Apr 20, 2009</jf:date>
        <jf:author>Laurent Michenaud</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>costume annotations</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[Good news :) I used to like hibernate validator, nice to have such a standard....]]></description>
        

        <pubDate>Tue, 01 Apr 2008 14:38:27 -0400</pubDate>

        

        <jf:creationDate>Tue, 01 Apr 2008 14:38:27 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 01 Apr 2008 14:38:27 -0400</jf:modificationDate>
        <jf:date>Apr 1, 2008</jf:date>
        <jf:author>Daoud Abdelmonem Faleh</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Making a narrow solution a standard</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote>I expect that, as the spec is fleshed out, we'll get a better idea of its ability to be flexible enough to solve those more difficult, sticky areas (which end up being more common than we hope).</blockquote>...]]></description>
        

        <pubDate>Tue, 01 Apr 2008 10:57:40 -0400</pubDate>

        

        <jf:creationDate>Tue, 01 Apr 2008 10:57:40 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 01 Apr 2008 10:57:40 -0400</jf:modificationDate>
        <jf:date>Apr 1, 2008</jf:date>
        <jf:author>Emmanuel Bernard</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Bean Validation initial draft released</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote>In regards to your last comments, the constraints placed at the bean level are bound to the database. This is perfectly acceptable since it's in the context of data persistence. It just becomes messy when constraints vary based upon context....]]></description>
        

        <pubDate>Tue, 01 Apr 2008 10:34:37 -0400</pubDate>

        

        <jf:creationDate>Tue, 01 Apr 2008 10:34:37 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 01 Apr 2008 10:34:37 -0400</jf:modificationDate>
        <jf:date>Apr 1, 2008</jf:date>
        <jf:author>Emmanuel Bernard</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Some feedback</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote><blockquote>&gt;//and in a properties file<br>specificcase.error.length=Wayyy too long, are you kidding me?!<br><br><br>seem easier to me</blockquote><br>Easy enough on a single- or few developer project, a pain when you have 5+ developers...]]></description>
        

        <pubDate>Tue, 01 Apr 2008 10:22:38 -0400</pubDate>

        

        <jf:creationDate>Tue, 01 Apr 2008 10:22:38 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 01 Apr 2008 10:22:38 -0400</jf:modificationDate>
        <jf:date>Apr 1, 2008</jf:date>
        <jf:author>Emmanuel Bernard</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Making a narrow solution a standard</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote>This looks like an attempt to turn a narrow solution into a standard. In any real world, non trivial example (hint: These are the ones with more than one data source, more than one client for the service layer and so on), validation is so...]]></description>
        

        <pubDate>Tue, 01 Apr 2008 10:18:25 -0400</pubDate>

        

        <jf:creationDate>Tue, 01 Apr 2008 10:18:25 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 01 Apr 2008 10:18:25 -0400</jf:modificationDate>
        <jf:date>Apr 1, 2008</jf:date>
        <jf:author>Emmanuel Bernard</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Attribute with type-safe string-free meta handle</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote>yes both properties and method literal have been proposed. Not sure property will make it in Java 7 though.</blockquote>

Do you aware of the JSR number? I tried to look for any related spec not long ago but don't find any. Thanks]]></description>
        

        <pubDate>Mon, 31 Mar 2008 15:24:01 -0400</pubDate>

        

        <jf:creationDate>Mon, 31 Mar 2008 15:24:01 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 31 Mar 2008 15:24:01 -0400</jf:modificationDate>
        <jf:date>Mar 31, 2008</jf:date>
        <jf:author>hacking bear</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Making a narrow solution a standard</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[I'm unconvinced that a single framework will have the flexibility and power to cross all layers (especially in an AJAX environment) at a deep integration point (i.e. create appropriate javascript, as well as at the web, business, and data tiers), though...]]></description>
        

        <pubDate>Mon, 31 Mar 2008 13:00:54 -0400</pubDate>

        

        <jf:creationDate>Mon, 31 Mar 2008 13:00:54 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 31 Mar 2008 13:00:54 -0400</jf:modificationDate>
        <jf:date>Mar 31, 2008</jf:date>
        <jf:author>Dan Shellman</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Some feedback</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote><blockquote><blockquote>&gt;//and in a properties file<br>specificcase.error.length=Wayyy too long, are you kidding me?!<br><br><br>seem easier to me</blockquote><br>Easy enough on a single- or few developer project, a pain when you have 5+...]]></description>
        

        <pubDate>Mon, 31 Mar 2008 12:10:11 -0400</pubDate>

        

        <jf:creationDate>Mon, 31 Mar 2008 12:10:11 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 31 Mar 2008 12:10:11 -0400</jf:modificationDate>
        <jf:date>Mar 31, 2008</jf:date>
        <jf:author>Richard Burton</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Some feedback</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote><blockquote>&gt;//and in a properties file<br>specificcase.error.length=Wayyy too long, are you kidding me?!<br><br><br>seem easier to me</blockquote><br>Easy enough on a single- or few developer project, a pain when you have 5+ developers...]]></description>
        

        <pubDate>Mon, 31 Mar 2008 12:00:49 -0400</pubDate>

        

        <jf:creationDate>Mon, 31 Mar 2008 12:00:49 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 31 Mar 2008 12:00:49 -0400</jf:modificationDate>
        <jf:date>Mar 31, 2008</jf:date>
        <jf:author>Richard Burton</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Bean Validation initial draft released</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote><blockquote>Can you explain how Grails seems unnatural?<br><br>I bring up Grails to bring in a different view no how other frameworks/languages do similar tasks. How many Ruby, PHP, etc.. developers have loads of XML files to store...]]></description>
        

        <pubDate>Mon, 31 Mar 2008 11:54:22 -0400</pubDate>

        

        <jf:creationDate>Mon, 31 Mar 2008 11:54:22 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 31 Mar 2008 11:54:22 -0400</jf:modificationDate>
        <jf:date>Mar 31, 2008</jf:date>
        <jf:author>Richard Burton</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Some feedback</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote>&gt;//and in a properties file<br>specificcase.error.length=Wayyy too long, are you kidding me?!<br><br><br>seem easier to me</blockquote>...]]></description>
        

        <pubDate>Mon, 31 Mar 2008 07:07:53 -0400</pubDate>

        

        <jf:creationDate>Mon, 31 Mar 2008 07:07:53 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 31 Mar 2008 07:07:53 -0400</jf:modificationDate>
        <jf:date>Mar 31, 2008</jf:date>
        <jf:author>Wille Faler</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Making a narrow solution a standard</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[This looks like an attempt to turn a narrow solution into a standard. In any real world, non trivial example (hint: These are the ones with more than one data source, more than one client for the service layer and so on), validation is so complex that it...]]></description>
        

        <pubDate>Sun, 30 Mar 2008 14:19:02 -0400</pubDate>

        

        <jf:creationDate>Sun, 30 Mar 2008 14:19:02 -0400</jf:creationDate>
        <jf:modificationDate>Sun, 30 Mar 2008 14:19:02 -0400</jf:modificationDate>
        <jf:date>Mar 30, 2008</jf:date>
        <jf:author>Karl Banke</jf:author>
        <jf:replyCount>3</jf:replyCount>
    </item>


    <item>

        <title>Re: DB integration</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[<blockquote>Yes, trans-layer is difficult. But rewrite the same field len attribute in N-layer (db/ejb/jsp/javascript) is redundant.<br><br>A "pragmatic" validation mechanism should allow to acquire some infos from DB(like nullability, length) and add...]]></description>
        

        <pubDate>Sun, 30 Mar 2008 11:39:31 -0400</pubDate>

        

        <jf:creationDate>Sun, 30 Mar 2008 11:39:31 -0400</jf:creationDate>
        <jf:modificationDate>Sun, 30 Mar 2008 11:39:31 -0400</jf:modificationDate>
        <jf:date>Mar 30, 2008</jf:date>
        <jf:author>Emmanuel Bernard</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: DB integration</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=48810</link>

        

        
            <description><![CDATA[Yes, trans-layer is difficult. But rewrite the same field len attribute in N-layer (db/ejb/jsp/javascript) is redundant.

A "pragmatic" validation mechanism should allow to acquire some infos from DB(like nullability, length) and add some other logic.]]></description>
        

        <pubDate>Sun, 30 Mar 2008 06:36:15 -0400</pubDate>

        

        <jf:creationDate>Sun, 30 Mar 2008 06:36:15 -0400</jf:creationDate>
        <jf:modificationDate>Sun, 30 Mar 2008 06:36:15 -0400</jf:modificationDate>
        <jf:date>Mar 30, 2008</jf:date>
        <jf:author>Roberto Colmegna</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>



</channel>
</rss>

