I am answaring your question to the list as it is probably of intrest to
others.
It's in the docs on java.sun.com under the plugin section :-) Well that said
you have to add something like this :
<jsp:param name="cache_option" value="Plugin" />
<jsp:param name="cache_archive"
value="PakkaApplet.jar,padda.jar,pakka.jar,ejb.jar,orion.jar,jndi.jar,exense
.jar,objectfx.jar,parser.jar,mail.jar,jaxp.jar,jdbc.jar,VisualNumerics.jar"/
>
the jsp tags comes from me using jsp to start the applet and setting up
credentials for the user and so forth. If you are using plain html just use
the params direct.
Regards,
Torgeir
-----Original Message-----
From: Frank Eggink [mailto:[EMAIL PROTECTED]]
Sent: 22. august 2000 21:10
To: '[EMAIL PROTECTED]'
Subject: RE: EJB stub classes and stand-alone remote java client
Torgeir,
So far I had not heard from java-plugging cach options. What is that and can
you point me in a direction
for some more info?
Thanks,
Frank
On Tuesday, August 22, 2000 5:43 PM, [EMAIL PROTECTED]
[SMTP:[EMAIL PROTECTED]] wrote:
> As it is at the moment you need make a jar containing remote and home
> interfaces by your self. This needs to be deployed on the client. Also you
> need to make an application-client.xml file in your meta-inf in the client
> jar and have a jndi.properties file in the root catalog.
>
> Since orion has no ligthwight library you must include :
>
> ejb.jar,orion.jar,jndi.jar,parser.jar,mail.jar,jaxp.jar,jdbc.jar
>
> This is a bit anoying as this means that you have to update the client for
> each new release of orion. If you like me are running in applets it means
> lot of files to download for before start (Modem users arn't to happy
:-)).
> This can be partly fixed by using the java-plugging cach options.
>
> As indicated by an e-mail from Karl Alvdal of the Orion team earlier today
> they are working on a lightwight library which will remedy this.
>
> As for makeing jars with home and remote interfaces, it's easy to automate
> this task with a shell-script, bat-file or using ant. The later is what we
> found preferbal.
>
> Regards,
> Torgeir Lerkerod
> -----Original Message-----
> From: Paul Knepper [mailto:[EMAIL PROTECTED]]
> Sent: 22. august 2000 16:37
> To: Orion-Interest
> Subject: EJB stub classes and stand-alone remote java client
>
>
>
>
> I've been trying to get my standalone java client to access EJBs on a
remote
> machine, but with no luck. I've deployed a J2EE application with my EJBs
in
> it. But I can't figure out how to generate the stub classes.
>
> I can't find the Orion tool to generate the stub classes that the client
> would normally reference from the CLASSPATH (as described in "Java 2
> Enterprise Edition Developer's Guide" page 95). How do you generate the
> stub classes that enable the client to communicate with the enterprise
bean?
> This is a simple thing to do with the deploytool that comes with Sun's
J2EE
> Reference Implementation. During deployment you simply select a checkbox
> labelled "Return client Jar" when you deploy the application.
>
> I don't understand how the client can resolve the EJB classes if you don't
> have the client stubs to include in your CLASSPATH. I keep getting a
> java.lang.ClassNotFoundException exception.
>
> Also, what else do I need to deploy to my client machine, just orion.jar?
>
>
> Thanks,
> Paul Knepper
> <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
>
>
>
> << File: ATT00001.html >>
