[wildfly-dev] Concurrency tests are failing

[Eduardo Martins]

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.

—E

On 27 Nov 2013, at 16:40, Arun Gupta <arun.gupta at gmail.com> wrote:

> https://github.com/arun-gupta/javaee7-samples/tree/master/concurrency/managedexecutor
> 
> On Wed, Nov 27, 2013 at 8:28 AM, Eduardo Martins <emartins at redhat.com> wrote:
>> Where are the test sources so I can have a look?
>> 
>> —E
>> 
>> On 26 Nov 2013, at 23:57, Arun Gupta <arun.gupta at 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.
>>> 
>>> https://arungupta.ci.cloudbees.com/job/Java%20EE%207%20Samples%20on%20WildFly-cb/lastCompletedBuild/testReport/
>>> 
>>> Suggestions ?
>>> 
>>> Thanks
>>> Arun
>>> 
>>> --
>>> http://blog.arungupta.me
>>> http://twitter.com/arungupta
>>> _______________________________________________
>>> wildfly-dev mailing list
>>> wildfly-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>> 
> 
> 
> 
> -- 
> http://blog.arungupta.me
> http://twitter.com/arungupta