On Oct 19, 2010, at 11:26 AM, Steve Ebersole wrote:
> On Tuesday, October 19, 2010, at 11:07 am, John Verhaeg wrote:
>> I'm currently going through the codebase trying to convert our use of slf4j
>> for logging to jboss-logging. In doing so, I've noticed that all of the
>> current loggers are na
On Tuesday, October 19, 2010, at 11:07 am, John Verhaeg wrote:
> I'm currently going through the codebase trying to convert our use of slf4j
> for logging to jboss-logging. In doing so, I've noticed that all of the
> current loggers are named using the package-qualified name of the
> enclosing cla
I'm currently going through the codebase trying to convert our use of slf4j for
logging to jboss-logging. In doing so, I've noticed that all of the current
loggers are named using the package-qualified name of the enclosing class that
define them. JBoss-logging offers a similar concept in that
Den 19.10.2010 10:06, skrev Emmanuel Bernard:
> Cross validation marker annotations like @ExactlyOneNull are not really
> actual constraints (ie annotated with @Constraint) because somehow they must
> carry two logic:
> - the property checking logic
> - the "aggregation" logic
> Besides the
Cross validation marker annotations like @ExactlyOneNull are not really actual
constraints (ie annotated with @Constraint) because somehow they must carry two
logic:
- the property checking logic
- the "aggregation" logic
Besides these markers should be ignored by the rest of the Bean Validatio
