You would have to deploy the mdb in a seperate jar within the ear
that does not have a security-domain specified in 2.2.x. In 2.4 you
can specify the principal name to use for anonymous access.
----- Original Message -----
From: "Brian Sondergaard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: "Brian Sondergaard" <[EMAIL PROTECTED]>
Sent: Wednesday, July 18, 2001 8:38 PM
Subject: [JBoss-user] Re: MDB Security: authentication exception on container call to
onMessage()?
>
> As far as our security requirements on the MDB, I was going to start with
> using run-as to specify a particular role in order to allow the MDB to
> execute business logic encapsulated entirely in session beans. Going
> forward, I'd like to explore programmatically setting the principal. The
> latter is not an immediate requirement.
>
> The trouble I've run into is that I can't get the MDB to run at all when
> it's deployed within an application that has security enabled. I've tried
> every combination of method permissions and such that I can think of, but to
> no avail. Right now, I'll be happy if I can have declarative security on all
> the session beans but disable all security on the MDBs. Any thoughts on how
> to get around this?
>
> Thanks!
>
> Brian
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
