Client Side Jar

Question

Hi folks,
in the days of the good old 5.1 release there where rumors and promises
about a as-thin-as-possible-jar-file for client side usage containing
just the classes a swing client would need. I did not find this magic
jar in 6.0 and 6.1. Is there being worked on? Is there a list of
packages I can safely remove from the giant weblogic.jar in order to cut
it to a WebStart-with-dialup compatible size of let's say 2-5mb? Please
don't point me to verbose2zip, I won't spend weeks on finding every
possible way through WebLogic code ... :-)
Thanks for any insight!
Daniel

Answer 1

That's an easy one ;-). Include the original MANIFEST.MF in the
generated jar.
Daniel
-----Original Message-----
From: Nick Minnutello
[mailto:[email protected]]
Posted At: Friday, August 31, 2001 3:04 AM
Posted To: misc
Conversation: Client Side Jar
Subject: Re: Client Side Jar
Please let me know how you get on.
You can email me if you like.
We too are deploying our apps via JWS, and a 25MB jar will
drive the users
nuts, let alone us when we want to access the server in Hong Kong..!
I had problems with the verboseToZip - I could never get my
client to start
up. Is there some other fancy footwork you have to do apart from
the -verbose and the verboseToZip?
Do you need to exercise every code path in order to create
this file? Once
you have done a JNDI lookip, a few RMI calls, caught an
exception or two,
what else is there ? (I guess that you are using JMS and
FileT3 which makes
it more complicated). However, for straight RMI, is there
that big a risk?
I got a stack trace of:
Any clues anyone?
(I understand that a thin-client jar is on its way soon)
--------stack trace-------------------
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:85)
at
weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitial
ContextFactory
Delegate.java:161)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Unknown Source)
at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInit
ialContextFact
ory.java:119)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at
com.bnpparibas.eqd.stingray.mantaray.servercontext.AbstractSer
verContext.<in
it>(AbstractServerContext.java:65)
at
com.bnpparibas.eqd.stingray.mantaray.servercontext.WebLogicCon
text.<init>(We
bLogicContext.java:35)
at
com.bnpparibas.eqd.stingray.mantaray.servercontext.ServerConte
xtFactory.crea
te(ServerContextFactory.java:34)
at
com.bnpparibas.eqd.stingray.mantaray.beans.ViewFactory.getCurr
encies(ViewFac
tory.java:247)
at
com.bnpparibas.eqd.stingray.mantaray.beans.ViewFactory.createT
ree(ViewFactor
y.java:206)
at
com.bnpparibas.eqd.stingray.mantaray.beans.ViewFactory.<init>(
ViewFactory.ja
va:61)
at
com.bnpparibas.eqd.stingray.mantaray.MantaViewManager.initaliz
e(MantaViewMan
ager.java:24)
at
com.bnpparibas.eqd.stingray.mantaray.MantaMainFrame.initialise
(MantaMainFram
e.java:114)
at
com.bnpparibas.eqd.stingray.mantaray.MantaMainFrame.<init>(Man
taMainFrame.ja
va:56)
at
com.bnpparibas.eqd.stingray.mantaray.MantaMainFrame.getInstanc
e(MantaMainFra
me.java:63)
at com.bnpparibas.eqd.stingray.mantaray.Manta.main(Manta.java:61)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.javaws.Launcher.executeApplication(Launcher.java:701)
at com.sun.javaws.Launcher.executeMainClass(Launcher.java:663)
at com.sun.javaws.Launcher.continueLaunch(Launcher.java:546)
at com.sun.javaws.Launcher.handleApplicationDesc(Launcher.java:334)
at com.sun.javaws.Launcher.handleLaunchFile(Launcher.java:151)
at com.sun.javaws.Launcher.<init>(Launcher.java:113)
at com.sun.javaws.Main.main(Main.java:153)
"Daniel Hoppe" <[email protected]> wrote in message
news:[email protected]...
Thanks for the tip. Actually I have a fat swing-gui client which uses
quite a lot of features, T3 File Systems, EJB Calls, JMS etc.. I'm
afraid the Web Services client jar won't help me here.
I need to distribute it via WebStart, that's why the whole weblogic.jar
is just not acceptable. I used to use java -verbose and verboseToZip,
but that's a quite dangerous strategy, I can never be sure that I really
covered every codepath. I guess I will open a case and see if that
helps. Maybe I can at least get a change request for a future version...
Daniel
-----Original Message-----
From: Dimitri Rakitine [mailto:[email protected]]
Posted At: Monday, August 27, 2001 10:09 PM
Posted To: misc
Conversation: Client Side Jar
Subject: Re: Client Side Jar
6.1 does create small client jar if you use web services :
http://e-docs.bea.com/wls/docs61/webServices/client.html#1036653
Daniel Hoppe <[email protected]> wrote:
Hi folks,
in the days of the good old 5.1 release there where rumorsand promises
about a as-thin-as-possible-jar-file for client side usagecontaining
just the classes a swing client would need. I did not findthis magic
jar in 6.0 and 6.1. Is there being worked on? Is there a list of
packages I can safely remove from the giant weblogic.jar inorder to cut
it to a WebStart-with-dialup compatible size of let's say2-5mb? Please
don't point me to verbose2zip, I won't spend weeks on
finding every
possible way through WebLogic code ... :-)
Thanks for any insight!
Daniel--
Dimitri