Am I right in saying security-role-ref tag can be there only for entity and session beans and NOT for MDB?
SInce it is used by bean provider to specify any roles that he might have used in context.isCallerInRole("XXX") In place of XXX. And MDBs can not call isCallerInRole.
Having the tag for MDB doesn't make any sense. Some verifiers may complain. Some do not. Also, because the DTD is common for all the bean types, even XML parsers ignore them when specified for MDB. All we need to make sure is that there is no isCallerInRole("XYZ") call in our MDBs.
Both should not because the DTD is common for all the bean types
But then I was just trying to understand why is that the point of not having Unchecked element for MDB is specified in HFEJB where as The point of not having security-role-ref for MDB is not specified anywhere.
So I thought one causes error at vaerifier level and other does not.
However if both dont, then my understanding is right.
Being too much watchful is dangerous as far as this exam is concerned because then you may get bogged down into unnecessary 'inferences' from simple questions. Just my $0.02
Just keep in mind that security-role-ref does not make any sense for MDB and you generally won't specify it. The exam will not test you with questions like 'What error occurs when security-role-ref is specified as XYZ for a MDB?' Most of the gray areas from the spec are carefully avoided/questioned in the exam. So don't worry.
Post by:autobot
We noticed he had no friends. So we gave him this tiny ad:
a bit of art, as a gift, the permaculture playing cards