Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 48345 invoked from network); 20 Feb 2007 16:54:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Feb 2007 16:54:32 -0000 Received: (qmail 1981 invoked by uid 500); 20 Feb 2007 16:54:36 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 1961 invoked by uid 500); 20 Feb 2007 16:54:36 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 1945 invoked by uid 99); 20 Feb 2007 16:54:36 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Feb 2007 08:54:36 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [64.18.1.185] (HELO exprod6og52.obsmtp.com) (64.18.1.185) by apache.org (qpsmtpd/0.29) with SMTP; Tue, 20 Feb 2007 08:54:24 -0800 Received: from source ([66.46.195.131]) by exprod6ob52.postini.com ([64.18.5.12]) with SMTP; Tue, 20 Feb 2007 08:54:02 PST In-Reply-To: <8BA7150F-ECE8-41BA-B517-A9B5A8C61B1E@yahoo.com> Subject: Re: Message-Driven Beans with run-as Subject To: user@geronimo.apache.org X-Mailer: Lotus Notes Release 7.0 August 18, 2005 Message-ID: From: Aman Nanner/MxI Technologies Date: Tue, 20 Feb 2007 11:54:00 -0500 X-MIMETrack: Serialize by Router on Oceanus/MxI Technologies(Release 7.0|August 18, 2005) at 02/20/2007 11:54:03 AM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Virus-Checked: Checked by ClamAV on apache.org Ok, I had checked out the openejb2 TAG version, not the trunk version of openejb2. I'll try the trunk.... David Jencks wrote on 02-20-2007 11:51:23 AM: > > On Feb 19, 2007, at 9:24 PM, Aman Nanner/MxI Technologies wrote: > > > I checked out the MDB interceptor stack and I do see that the > > EjbRunAsInterceptor is missing. In order for me to add it and test > > it out, > > I'd need to rebuild the openejb-2.2 project. I have this checked > > out but > > am having difficulty building it. Is there an article out there for > > building openejb-2.2? The main page at the openejb.org site has > > instructions on how to build openejb3, but not version 2. I did a > > bit of > > searching but couldn't find it... > > You should have checked out > > https://svn.apache.org/repos/asf/incubator/openejb/trunk/openejb2 > > This project builds with maven 2.0.5, and running > > mvn > > ought to work (after enough tries). > > What problems are you seeing? > > thanks > david jencks > > > > > Thanks, > > Aman > > > > David Jencks wrote on 02-19-2007 01:50:24 PM: > > > >> It looks to me as if the mdb interceptor stack is missing the > >> EJBRunAsInterceptor which would mean that run-as wouldn't work. I'm > >> also not seeing how any Subject such as the default subject is set > >> for an mdb call. So I think there's a bug (would rather check the > >> spec to make sure it's supposed to work before definitely declaring a > >> bug). Since you can't import security with an mdb from the inbound > >> message I'd think you could get almost the same result by making the > >> default subject for the mdb call your run-as subject, and this might > >> work, but I can't figure out if or how that's being set. > >> > >> If you would like to experiment you might compare the ejb containers > >> and modify the mdb one to include the EJBRunAsInterceptor at a likely > >> spot and see if it works. > >> > >> thanks > >> david jencks > >> > >> On Feb 19, 2007, at 9:10 AM, Aman Nanner/MxI Technologies wrote: > >> > >>> > >>> Hi, > >>> > >>> > >>> One Geronimo 1.2-beta, I'm running into a problem where a message- > >>> driven > >>> bean that I have is unable to access a stateless session EJB that I > >>> have, > >>> due to method permission restrictions. This MDB is configured > >>> with a > >>> "run-as" subject in the ejb-jar.xml which is supposed to allow it > >>> to access > >>> this restricted EJB. I have the MDB configured similar to the > >>> following: > >>> > >>> ---- > >>> > >>> TestMDB > >>> TestMDB > >>> com.acme.ejb.TestMDB > >>> Bean > >>> > >>> javax.jms.Topic > >>> > >>> > >>> > >>> acknowledgeMode >>> property-name> > >>> > >>> Auto-acknowledge >>> config-property-value> > >>> > >>> > >>> > >>> messageSelector >>> property-name> > >>> JOB_CODE = > >>> 'FOO' > >>> > >>> > >>> > >>> subscriptionDurability >>> config-property-name> > >>> > >>> NonDurable >>> property-value> > >>> > >>> > >>> > >>> ejb/common/TestEJB > >>> Session > >>> com.acme.ejb.TestHome > >>> com.acme.ejb.TestRemote > >>> TestEJB > >>> > >>> > >>> > >>> TESTROLE > >>> > >>> > >>> > >>> ---- > >>> > >>> Can anybody confirm if the "run-as" functionality for MDBs works as > >>> it's > >>> supposed to in Geronimo 1.2-beta? Am I supposed to make a further > >>> configuration to one of the geronimo or openejb descriptors, in > >>> addition to > >>> the ejb-jar.xml? > >>> > >>> Through some debugging in Eclipse, I've found that the "run-as" > >>> subject > >>> does get loaded into the MDB Deployment Context as described, but I > >>> haven't > >>> confirmed if it actually gets set as the Subject for the context. > >>> > >>> Thanks, > >>> Aman > >>> > >>> ____________________________________________________________________ > >>> __ > >>> ____________ > >>> * This message is intended only for the use of the individual or > >>> entity to which it is addressed, and may contain information that > >>> is privileged, confidential and exempt from disclosure under > >>> applicable law. Unless you are the addressee (or authorized to > >>> receive for the addressee), you may not use, copy or disclose the > >>> message or any information contained in the message. If you have > >>> received this message in error, please advise the sender by reply e- > >>> mail , and delete the message, or call (collect) 001 613 747 4698. * > >>> > >> > > > > ______________________________________________________________________ > > ____________ > > * This message is intended only for the use of the individual or > > entity to which it is addressed, and may contain information that > > is privileged, confidential and exempt from disclosure under > > applicable law. Unless you are the addressee (or authorized to > > receive for the addressee), you may not use, copy or disclose the > > message or any information contained in the message. If you have > > received this message in error, please advise the sender by reply e- > > mail , and delete the message, or call (collect) 001 613 747 4698. * > > > __________________________________________________________________________________ * This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose the message or any information contained in the message. If you have received this message in error, please advise the sender by reply e-mail , and delete the message, or call (collect) 001 613 747 4698. *