On 06/16/2011 04:02 AM, Max Rydahl Andersen wrote:
On Jun 15, 2011, at 21:12, Marius Bogoevici wrote:
> As per the discussion that Scott and I had on IRC earlier, I tried to
> summarize the current issues that we encounter outside the confines of
> strict Java EE usage, for non Java EE JPA and native Hibernate
> applications (with Spring apps being a subset of the larger Hibernate
> application set), as well as some possible workarounds and some possible
> solutions - some of these have working prototypes, for some others we
> need to decide the direction in which we want to go (e.g. fail-fast vs.
> more precise validation vs. runtime failures and so on).
>
> It would be ideal if we could address some of these issues pre-7.0, if
> not, then at least we should have a working plan for 7.1.
>
>
http://community.jboss.org/thread/168089
Yikes - that's not an encouraging list of issues ;(
If I read this right that makes almost every spring or Hibernate 3/JPA app impossible to
deploy - is that correct ?
Hibernate 3 without JPA just using hbm.xml seems then to be the most portable option or
will that fail too ? :)
Anything I can do to help solve these ? (and no I can't fix the issue at its core,
but I can help test if needed)
Sounds to me like AS7 should ignore persistence.xml definitions that
have PersistenceUnitTransactionType of RESOURCE_LOCAL. I think we
currently just pass the PU definition to Hibernate, which is wrong.
I created AS7-1034 for this change.
Max, do you have a simple test case archive (representative of the
typical Hibernate 3 native JPA app) that you could attach to AS7-1034?
I'm all ears since if that thread is true then a lot users will have a very hard time
getting started with AS7.
/max
http://about.me/maxandersen
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev