Hello, Steve,
yes the answer for "why native?" is portability, indeed.
Could you please enlighten me, what the "enhanced" generators
precisely are and why they would fix my problem? At least, I don't
find the term "enhanced" in the IdentifierGeneratorFactory and neither
of the classes implementin
http://in.relation.to/Bloggers/New323HibernateIdentifierGenerators
On Sun, 2009-12-06 at 14:53 +0100, Jochen Wiedmann wrote:
> Hello, Steve,
>
> yes the answer for "why native?" is portability, indeed.
>
> Could you please enlighten me, what the "enhanced" generators
> precisely are and why they
1) http://repository.jboss.com/maven2 is not a SNAPSHOT repo, it only
serves releases. You need http://snapshots.jboss.org/maven2/ as you see
certainly does contain that SNAPSHOT:
http://snapshots.jboss.org/maven2/org/jboss/javaee/jboss-jacc-api/1.1.1-SNAPSHOT/
2) Do you use jacc in conjunction w
Thanks Steve.
As for the the POM, perhaps it should also be given
true? You're right; I don't use JACC. I don't
always run in a JBoss container so it wouldn't be very valuable like in
Tomcat, for example.
Paul
On 12/6/2009 9:29 AM, Steve Ebersole wrote:
> 1) http://repository.jboss.com/maven2
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
On Sun, 2009-12-06 at 09:37 -0600, Paul Benedict wrote:
> Thanks Steve.
>
> As for the the POM, perhaps it should also be given
> true? You're right; I don't use JACC. I don't
> always run in
2009/12/4 Emmanuel Bernard
>
> On 3 déc. 09, at 23:09, Gunnar Morling wrote:
>
> 2009/12/3 Emmanuel Bernard
>
>> For sole determination of allowed types for constraint annotations you
>> wouldn't need any validator implementations (or HV core) on the AP classpath
>> when working with the mirror
