I know this has changed recently, but better even would be an optional
'light' client jar that could use the HTTP classloader to load the
required implementation classes as needed. Not so good for clients over
slow links (i.e., applets, etc.), but great for collaborating services
within a LAN. A problem I've had before is when my client jars get out of
'version sync' with the server -- this would at least slow down that
problem...
-Jason
Burkhard Vogel <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/06/2001 02:23 PM
Please respond to jboss-user
To: [EMAIL PROTECTED]
cc:
Subject: Re: [JBoss-user] ejb client classpath
Hmm,
why can't we pack the whole bunch of jars into one?
from developing view I can understand that its far easier to have multiple
jars, but seeing the load of mail regarding client problems with CNFE,
wouldn't it be kinda user-friendly only to have to include one
jboss-client.jar?
Burkhard
----- Original Message -----
From: "Scott M Stark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 06, 2001 8:56 PM
Subject: Re: [JBoss-user] ejb client classpath
> 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
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
