[prev in list] [next in list] [prev in thread] [next in thread]
List: jacorb-developer
Subject: RE: [jacorb-developer] Problems
From: "Kevin A. Palfreyman" <kap () apama ! com>
Date: 2004-02-25 9:29:27
Message-ID: 7CD4BE0203A91845A17CE0E8BD9A1289AF5F1A () ukcamms002 ! msapama ! apama ! com
[Download RAW message or body]
The jacorb.jar manifest already specifies both avalon and the logkit
jars.
I even tried changing the manifests in avalon and logkit to refer to
each other, but that didn't help either. I also tried directly
referencing all of the jars from the manifest of my test application,
but still no luck.
Any more ideas?
K.
> -----Original Message-----
> From: justfear1-jacorb@yahoo.com [mailto:justfear1-jacorb@yahoo.com]
> Sent: 24 February 2004 22:40
> To: Discussions concerning CORBA development with JacORB
> Subject: Re: [jacorb-developer] Problems
> resolvingorg/apache/log/format/PatternFormatter
>
> Be sure to include avalon.jar as well..
>
>
>
> --- "Kevin A. Palfreyman" <kap@apama.com> wrote:
> > I'm also having a similar issue with the classloader and
> these logging
> > classes.
> > Is there any way to get this working *without* using either the
> > bootclasspath (in JDK 1.3) or the java.endorsed.dirs (in JDK 1.4)?
> >
> > We are considering an upgrade from JacORB 1.3.30, but need
> to be able
> > to cleanly deploy in a wide variety of situations (from
> running nice
> > easy swing clients under 1.4.2, to deploying WARs in customer app
> > servers that we are unable to change startup options for).
> >
> > Previously we have been able to do everything we need simply by
> > including jacorb.jar in the Class-Path: entry of the
> Manifest for our
> > client library jars. We use Lots of JacORB clients to communicate
> > with TAO servers.
> >
> > It seems very odd that the ease of deployment of a corba orb is
> > reduced due to a logging library.
> >
> > Please help - what simple step am I missing?
> > (remember - can't use bootclasspath/endorsed.dir and can't
> put copies
> > in customer lib/ext)
> >
> > Thanks,
> >
> > Kev
> >
> >
> > > Mark,
> > > In your case the logkit jar is NOT visible to the
> > bootstrap
> > classloader which is
> > > what is used to load JacORB. Under JDK 1.3 you
> > need to include all
> > classes
> > > loaded by the bootstrap classloader in the
> > Xbootclasspath. Under JDK
> > 1.4 you can
> > > instead use the 'java.endorsed.dirs' property and
> > then specify the
> > dependencies,
> > > such as the logkit jar, in your classpath (e.g.
> > the manifest's
> > Class-Path).
> > > -Alan
> > >
> > > "Reed, Mark (MREED)" wrote:
> > >
> > > > I have upgraded to v2.0 in the last couple of
> > days and keep getting
> > this
> > > > exception when trying to launch from the command
> > line
> > > > In this particular case I have made sure all the
> > dependencies for
> > v2.0 are
> > > > in my jars manifest Class-Path entry.
> > > > I have also tried explicitly setting it on
> > command line and I am
> > sure that
> > > > the logkit-1.2.jar file is visible to the class
> > loader.
> > > > Seem to be having a lot of trouble loading this
> > class, seems to work
> > ok
> > > > under eclipse but all paths and such are
> > duplicated identically
> > between
> > > > eclipse launch and command line launch. Also
> > getting this when
> > trying to run
> > > > as NT service using service wrapper.
> > > >
> > > > Any ideas?
> > > >
> > > >
> >
> C:\SelfServ\applications\CUSSDemo>c:\jdk1.3.1_06\bin\java
> > > > -Xbootclasspath:"C:/se
> > > >
> >
> lfserv/platform/lib/jacorb.jar;C:\jdk1.3.1_06\jre\lib\rt.jar"
> > > > -Dorg.omg.CORBA.OR
> > > > BClass=org.jacorb.orb.ORB
> > > >
> >
> -Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSi
> > > > ngleton -jar CUSSDemo.jar -config
> > cussdemo.properties
> > > > [configuration loaded from C:\Documents and
> > > > Settings\mreed\jacorb.properties] Exception in thread "main"
> > java.lang.NoClassDefFoundError:
> > > > org/apache/log/format
> > > > /PatternFormatter
> > > > at
> > org.jacorb.util.LogKitLoggerFactory.<clinit>(Unknown
> > Source)
> > > > at java.lang.Class.newInstance0(Native
> > Method)
> > > > at
> > java.lang.Class.newInstance(Class.java:232)
> > > > at
> > org.jacorb.util.Environment.initLogging(Unknown
> > Source)
> > > > at
> > org.jacorb.util.Environment.init(Unknown Source)
> > > > at
> > org.jacorb.util.Environment.<clinit>(Unknown Source)
> > > > at
> > org.jacorb.orb.BufferManager.<clinit>(Unknown
> > Source)
> > > > at org.jacorb.orb.ORB.<init>(Unknown
> > Source)
> > > > at java.lang.Class.newInstance0(Native
> > Method)
> > > > at
> > java.lang.Class.newInstance(Class.java:232)
> > > > at org.omg.CORBA.ORB.create(Unknown
> > Source)
> > > > at org.omg.CORBA.ORB.init(Unknown
> > Source)
> > > > at CUSSDemo.SetORB(CUSSDemo.java:517)
> > > > at CUSSDemo.<init>(CUSSDemo.java:145)
> > > > at CUSSDemo.main(CUSSDemo.java:1656)
> > > > _______________________________________________
> >
> >
> > ---
> > Dr. Kevin Palfreyman
> > Apama (UK) Ltd, Unit 200, Rustat House, 60 Clifton Road,
> Cambridge,
> > CB1 7EG, UK
> > Email: kap@apama.com
> > Mobile: +44 (0)774 876 7109
> > Phone: +44 (0)1223 866290
> > Fax: +44 (0)1223 866222
> >
> > > _______________________________________________
> > jacorb-developer maillist -
> > jacorb-developer@lists.spline.inf.fu-berlin.de
> >
> http://lists.spline.inf.fu-berlin.de/mailman/listinfo/jacorb-developer
> >
>
>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic