All servers have application server specific jar files that clients need
to use. J2EE is just a collection of interfaces for the most part which
means there has to be an implementation provided and this means
jars in addition to those that contain the J2EE interfaces.
----- Original Message -----
From: "Christofer Jennings" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 06, 2001 11:16 AM
Subject: Re: [JBoss-user] ejb client classpath
> I think you may have missed my point. I figured out what was needed
> (though it is nice to know all the jars are in
> $JBOSS_DIST/jboss/client/ ... thanks)(and yes, shame on me for not
> searching first) but maybe my question is as much an EJB question as a
> JBoss question.
>
> That is, why do I need all those jars? Seems to me that a client should
> need to know nothing but how to look up the server (i.e., the jndi
> properties) and have the home and remote interfaces in its classpath.
>
> Is that not right?
>
> Is it required of all EJB containers that similar jars be in the
> classpath, or is this just a JBoss thing?
>
> This leads me to another point though. I get the impression that the
> example is not generic enough. Call it constructive criticism or the
> babbling of the uninformed, but I wanted that example to primarily teach
> me how to build and deploy a stateless session bean and secondarily how
> to optimize it for JBoss. Maybe that's beyond the scope of the manual,
> but that's what I was hoping.
>
> Thanks,
> boz
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
