taskWithTransaction is null
On 27 Nov 2013, at 17:32, Arun Gupta <arun.gupta(a)gmail.com> wrote:
Seems like it was a test configuration issue and Aslak helped me fix
it. Most of the errors are now gone in the latest test run at:
However there is one that is still failing. Can you take a look on that one ?
On Wed, Nov 27, 2013 at 8:56 AM, Eduardo Martins <emartins(a)redhat.com> wrote:
> All these tests are failing because you are using directly the executor in the
arquillian test class code. I mean, there is no EE component information set in the
invocation context when you use the executor, so the executor is not able to identify what
is the related EE component and know what state it should save, for instance what is are
the java:comp or java:module jndi contexts.
> We could make this work, but I’m not sure it would be correct, maybe someone else can
help clarify that.
> If you use an EE component to invoke the EE concurrency utilities, as the TCK does,
then it should work.
> On 27 Nov 2013, at 16:40, Arun Gupta <arun.gupta(a)gmail.com> wrote:
>> On Wed, Nov 27, 2013 at 8:28 AM, Eduardo Martins <emartins(a)redhat.com>
>>> Where are the test sources so I can have a look?
>>> On 26 Nov 2013, at 23:57, Arun Gupta <arun.gupta(a)gmail.com> wrote:
>>>> I added a few new tests to Java EE 7 samples to test for JSR
>>>> 236/Concurrency Utilities. All the tests are failing because they are
>>>> not able to either inject or JNDI resolve a ManagedExecutor.
>>>> Suggestions ?
>>>> wildfly-dev mailing list