tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Quintin Beukes <>
Subject Re: EJB classpath problem in eclipse3.5
Date Mon, 14 Sep 2009 13:16:07 GMT
Every item on the classpath can be seen as a classpath unit, whether
it's a directory item or a JAR archive. The physical storage of it is
abstracted away from the classloader, for example the URL classloader,
or JAR classloader, filesystem classloader, etc. They all inherit from
the main classloader and implement the listing/loading functionality.

So if you have a META-INF/ejb-jar.xml in a classpath item, that
classpath item will be scanned. Each classpath item you wish to scan
has to have it's own ejb-jar.xml, whether it's a filesystem item or a
JAR or a location specified via URL.


On Mon, Sep 14, 2009 at 4:36 AM, sL07 <> wrote:
> Quintin Beukes-2 wrote:
>> Try the following.
>> 1. Check that the following files exist:
>> a. c:\src\seamitp\classes\hot\META-INF\ejb-jar.xml
>>   -> And then in the same directory, ie. "hot", it's EJB classes
>> b. c:\src\seamitp\classes\main\META-INF\ejb-jar.xml
>>   -> And then in the same directory, ie. "main", it's EJB classes
> there is no META-INF directory in either directory.
> from reading the openEJB docs i thought by having a a single
> META-INF/ejb-jar.xml on classpath containing <ejb-jar/> allowed the
> classloader to find classes on classpath.
> i dont follow why a jar directory structure is required?
> -lp
> --
> View this message in context:
> Sent from the OpenEJB User mailing list archive at

Quintin Beukes

View raw message