Hi Thomas Good news, upgrading to 1.5.2 changed me from 18 errors and 4 failures to 13 errors (or some number like that).
Hi Mark, Romain, Here's a gist to get you looking https://gist.github.com/johnament/5710627 It looks like OWB isn't happy when you use abstract classes and type hierarchies. not sure if we ever added support for abstract classes for the partial bean feature that Gerhard did. Gerhard? John On Tue, Jun 4, 2013 at 7:33 PM, John D. Ament <[email protected]>wrote: > Hi Thomas, > > Also, Arquillian + TomEE was kinda buggy in 1.5.0. 1.5.1 was better, > 1.5.2 is also good. I'm going to run the tests against 1.5.2. > > John > > > On Tue, Jun 4, 2013 at 7:29 PM, John D. Ament <[email protected]>wrote: > >> Hi Thomas, >> >> Actually, the first issue I see is a common one for arquillian users. >> The no active context issue can be fixed by switching from an embedded to >> managed/remote container. For TomEE it's just as clean, do you mind if I >> try this out locally to see if some of the errors go away? >> >> BTW (from a design standpoint) do you need to bind everything to >> @RequestScoped? What if a user is working on something that isn't request >> scoped? >> >> John >> >> >> On Tue, Jun 4, 2013 at 4:53 PM, Thomas Hug <[email protected]> wrote: >> >>> Hey TomEE experts >>> >>> I'm currently working on getting the CDI query code base ready for import >>> [1] but haven't been successful running it under the TomEE profile (JBoss >>> and Glassfish run both fine). >>> >>> As far as I could drill down to the problems it's >>> - a Maven Aether library conflict with ShrinkWrap (solved by upgrading to >>> ShrinkWrap 2 beta) >>> - some of the partial beans not created (haven't checked all errors but >>> seems mainly related to abstract classes) >>> - JPA metamodel classes not initialized (all null) >>> >>> Haven't run it with the debugger yet, but in case any of those problems >>> ring a bell, a hint is very welcome. >>> >>> [1] https://github.com/ctpconsulting/query/tree/dsimport >>> >> >> >
