JBoss Messaging->HornetQ: @RunAs now ignored?

[kennardconsulting]

Hi guys,

I am migrating our JBoss Messaging (AS 5.1.0.GA) app to HornetQ (AS 6.0.0.Final).

We have some stateless EJBs whose methods are protected by @RolesAllowed annotations, and some MDBs that use @RunAs to enable them to call those methods. However this idiom doesn't appear to work under JBoss AS 6's HornetQ integration?

I've searched all over, but there doesn't seem to be an example in the HornetQ docs/distribution of using HornetQ MDBs together with @RunAs and EE security roles? Is this still expected to work?

Regards,

Richard.

[clebert.suconic]

MDBs are not really part of HornetQ. That's more a question for EJB guys.

[kennardconsulting]

Clebert,

Thanks for your response!

I realize my question lies at the 'boundary' between HornetQ and EJB. However I believe it falls slightly on the HornetQ side, seeing as it worked with JBoss Messaging in JBoss 5.1.0.GA.

There are already several MDB examples under /hornetq-2.2.2.Final/examples/javaee/mdb-* but none of them showcase (or test) @RunAs annotations (or <run-as> in ejb-jar.xml) functionality. Do I take it therefore this has not been tested?

Regards,

Richard.

[clebert.suconic]

We don't do anything with these annotations. They are exclusively features of the application server / MDBs. There should be tests on the application server for this (I believe there are).

If you find issues around this, you should provide a test and raise the issue to the AS team. (Unless you prove the issue is on the resource adapter, which I don't think it will be the case).

[kennardconsulting]

Clebert,

Okay - I put together a standalone, comprehensive test case to reproduce the problem and... the problem disappeared. So either a) there is something else wrong in my production code or b) I scared it away.

I am choosing to believe b) for now

Thanks again!

Regards,

Richard.

[ataylor]

I am choosing to believe b) for now

Its defo B, one thing ive learnt from my years of developing is that 'its never my fault'

[kennardconsulting]

Actually for once it may not be me after all! I have reproduced the problem and opened a JIRA: https://issues.jboss.org/browse/EJBTHREE-2254

It looks like it is an EJB issue though, not a HornetQ one, just as Clebert surmised.

Regards,

Richard.

[clebert.suconic]

What is cool about your test is that you are using Quartz (not even HornetQ) what really isolates the problem as not being HornetQ.

Thank you.