Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 81131 invoked by uid 500); 19 Feb 2002 19:24:56 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 81121 invoked from network); 19 Feb 2002 19:24:55 -0000 Message-ID: From: Tom Jordahl To: "'axis-dev@xml.apache.org'" Subject: RE: EJB Provider - IllegalAccessException Date: Tue, 19 Feb 2002 14:33:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N David, I made the changes to use the EJBMetaData API to get the interface class. I tested with Macromedia JRun. >From my (limited) understanding, EJBMetaData is an interface that the weblogic class should be implementing, and it shouldn't have access restrictions on it. Does Weblogic document some other way to get the interface class? -- Tom Jordahl Macromedia -----Original Message----- From: David L. Cole [mailto:DLCole@cmsenergy.com] Sent: Tuesday, February 19, 2002 2:10 PM To: axis-dev@xml.apache.org Subject: EJB Provider - IllegalAccessException I have been trying to use the default EJBProvider class to access an EJB object through a service. I am getting an IllegalAccessException in the EJBProvider class when testing in the getServiceClass() method at the line: Class interfaceClass = (Class) getRemoteInterfaceClass.invoke(metaData, empty_object_array); After some research, I found that the metaData object is actually a "weblogic.ejb20.internal.EJBMetaDataImpl" object. (I am using Weblogic 6.1) This poses a problem in the Weblogic 6.1 implementation as the EJBMetaDataImpl class has only package access. Could there be a better way to do this, or another approach to take to get around this limitation? Thanks, David Cole