When using secured EJB access to the MEJB Proxy, the cargo.jonas.mejb.jaas.entry option as well as the user name and password options are not handled correctly:
If only a file name is set but the entry is missing, all settings are ignored.
The user name is only used for JNDI authentication and InitialContext creation.
Even when all this succeeds, a "LoginException: No handler has been defined." is thrown.