> On Tue, 26 Sep 2000, Rickard Oberg wrote:
> Well, sure, anything's easy if you're using the right tools. But
> I suspect most EJB clients won't be doing that.
> Okay, so if (for a non-reflection situation) the dynamic class
> downloading can't get around the need for having the interfaces on hand,
> what does it get you? I guess you can avoid distributing the JTA JAR, but
> the client still needs the jnp-client.jar and ejb.jar, right?
No, you still need jnp-client.jar unless you use the trick I showed in
posting way back (see archives).
> How about
> jboss-client.jar?
Yes that can also be loaded. So, you don't need any jBoss specific stuff in
your client if you don't want to.
> It seems like it makes things a little better, but
> you've still got to distribute some JARs.
> Now with reflection, I guess you only need jnp-client.jar. Is
> that right? Sure, I could try it myself, but it sounds like you know
> already... :)
Yes, I know everything already, but to try and explain what works/not works
for each and every class/jar is very time consuming. Understand the
principles and go from there. There is no magic involved.
Also, one of the things you could do is add the jBoss dynamic downloading
URL to your Class-Path manifest header if your client is an executable jar.
That way the client can use the interfaces explicitly and still access the
interfaces from jBoss at runtime. Please, don't ask me to explain this
though. Figure out how classloading works, and how dynamic classloading
works, and that is all you need.
/Rickard
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
