EJBSpecUnitTestCase and the MDB Run As related tests

[anil.saldhana]

The EJBSpecUnitTestCase has a complex setup and the MDB run as related tests have been failing for a long long time. But debugging the issue has been pretty complex for a long long time now because the MDB tests fail arbitrarily. If the other tests are commented out, then the failing test that we are interested starts passing, thereby negating the effort of getting to the root cause.

I am going to spend another 3-4 days on finding out why some of the MDB run as related tests are failing. If I am unable to solve them by then, then I am going to refactor the MDB run as tests into separate tests.

Related: https://jira.jboss.org/jira/browse/JBAS-5054

[anil.saldhana]

The issue with the MDB run as tests was that there was the

 <use-caller-identity/>

tag missing in the Level1CallerBean.

MDB->Level1CallerBean->Level2CallerBean->Level3CallerBean

If Level1CallerBean does not define an explicit run-as or use-caller-principal, the run-as defined by the MDB can never be propagated to Level2CallerBean. Level2CallerBean defines use-caller-identity.

Not sure how this worked in 4.x

In JBAS5, we have clear separation of run as and subject principals. More spec-like behavior.

[starksm64]

There were lots of default behavior spread all over, so we probably just picked up a default of use-caller-identity somewhere.

[anil.saldhana]

The EJBSpecUnitTestCase should be passing in full. JBAS-5054 is resolved.