This is a classloader bug. We just don't mount the WEB-INF/lib and WEB-INF/classes during deployment, so we can't verify anything that depends on those classes.

-dain

--
Dain Sundstrom
Chief Architect
Gluecode Software
310.536.8355, ext. 26

On Sep 15, 2004, at 6:37 PM, [EMAIL PROTECTED] wrote:

The following comment has been added to this issue:

Author: David Jencks
Created: Wed, 15 Sep 2004 6:36 PM
Body:
In my experience the ejb interfaces can't be found from a war even if they are elsewhere in an ear such as in the ejb jar file.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/GERONIMO-289? page=comments#action_53118


---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/GERONIMO-289

Here is an overview of the issue:
---------------------------------------------------------------------
Key: GERONIMO-289
Summary: Interface classes for an ejb-ref in a war cannot be loaded from war libs or classes
Type: Bug


     Status: Unassigned
   Priority: Major

    Project: Apache Geronimo
 Components:
             web
   Versions:
             1.0-M2

   Assignee:
   Reporter: Dain Sundstrom

    Created: Wed, 8 Sep 2004 11:46 AM
    Updated: Wed, 15 Sep 2004 6:36 PM

Description:
The libraries contained in a war WEB-INF/lib and classes in the WEB-INF/classes directories are not added to the configuration classloader. This is an problem since this class loader is used to resolve ejb-refs. This means that war ejb-refs can only be used when deploying an ear and the interface classes are available from another module in the ear. We could simply add libs and classes to the configuration class loader, but it would make it impossible to isolate wars in the same configuration. This should be handled when we rewrite the JettyConfigurationBuilder to add JSR 77 objects.



--------------------------------------------------------------------- JIRA INFORMATION: This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



Reply via email to