Hi,
Joe Barefoot wrote:
>
> I'm trying to get dynamic loading of the interface classes using the
> webserver to work also...
>
> Ole, you say that classes in the EJB JAR are not served by the web server?
Sorry, I was wrong here.
> If this is true (I'll take your word for it), dynamic class loading is only
> useful if one
> adopts your approach and just put the interface jars in the class path.
> Unfortunately, there's no way to add
> a JAR to the classpath at runtime (as far as I know), so you would have to
> bounce the server
> or use a custom class loader.
I guess that the interface jar can be
added to the manifest classpath of the
implementation jar and any other bean
jars that use the interface.
> Also, why is there no "sure way" to differentiate between interface classes
> and implementation classes?
> Seems to me that you could just check the type of classes in the JAR and
> only serve those that are of
> type EJBOjbect or EJBHome, which would only be the interface classes.
The home and remote interfaces are easy
to identify as interface. Also primary
key for entities.
But value classes are not handled that
easily: Consider the remote interface
having a method:
void doSomething(Work toDo);
Now, if the bean jar has classes:
class Work { ... }
class ExtWork extends Work { ... }
class IntWork extends Work { ... }
Clearly, class Work belongs in the
interface, but how about the subclasses?
It could be that IntWork is for the
bean to use internally only, while
ExtWork is meant to be used from the
client. But there is not sure mechanical
way of finding out, given an EJB jar
only.
Best Regards,
Ole Husgaard.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
