geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <ammul...@alumni.princeton.edu>
Subject Re: Possible class path class loader problem when using Spring ClassPathXmlApplicationContext class
Date Wed, 21 Sep 2005 15:13:41 GMT
On 9/21/05, Gianny Damour <gianny.damour@optusnet.com.au> wrote:
>
> I just gave a quick try to the following packaging and it works:
>
> minimal.ear
> `-- external.jar
> `-- example/applicationContext.xml
> `-- minimal.war
> `-- META-INF/MANIFEST.MF: Class-Path: external.jar
> `-- WEB-INF/classes/example/ExampleController.class: which defines:
>
> static final ApplicationContext context = new
> ClassPathXmlApplicationContext("example/applicationContext.xml");
>
> As pointed out by Kevan, it would be great to have the EAR to debug this
> problem.
>
> Thanks,
> Gianny
>
> On 22/09/2005 12:20 AM, Kevan Miller wrote:
>
> > Hi Paul,
> > Please excuse the basic question -- are you positive the xml file is
> > in the jar with identical spelling/capitilization?
> >
> > In answer to your previous question -- yes, the WAS 5.1 and Geronimo
> > classloaders are certainly different. They should be both conforming
> > the the J2EE spec, of course...
> >
> > Is it possible for you to share your EAR? Or, (better yet?) can you
> > generate a simple test that illustrates the problem? I'm afraid the
> > exception stack trace isn't very helpful... The "Caused By" exception
> > itself has a "Caused By" exception. Others might be able to intuit the
> > root problem, but not me...
> >
> > --kevan
> >
> > On 9/21/05, *paul.newport@targetgroup.net
> > <mailto:paul.newport@targetgroup.net>* <paul.newport@targetgroup.net
> > <mailto:paul.newport@targetgroup.net>> wrote:
> >
> >
> > The EAR file is packaged up so that all, what we call "utility
> > jars" are present in the root of the main EAR project folder, and
> > projects that use them have a manifest class path pointing to these.
> >
> > In theory the whole thing is self contained so we don't have to
> > mess around with manually putting shared jars into a repository or
> > equivalent of (this just makes deployment easier for us - you just
> > install the EAR). Target www.targetgroup.net<http://www.targetgroup.net>
> > <http://www.targetgroup.net>
> > **********************************************************************
> > DISCLAIMER. This message is intended only for the use of the
> > Addressee and may contain information that is PRIVILEGED and
> > CONFIDENTIAL. If you are not the intended recipient you must not
> > copy, distribute or take any action or reliance upon it. The
> > content of this message may also contain personal views of an
> > employee of this company and does not necessarily represent the
> > view of the company.
> > **********************************************************************
> > This message has been scanned by Norton Anti-Virus. It has also
> > been scanned by MAILsweeper to enforce our e-mail policy. If you
> > have any concerns or comments about the content of this message,
> > please e-mail support@targetgroup.net
> > <mailto:support@targetgroup.net>.
> > **********************************************************************
> >
> >
> > _____________________________________________________________________
> > This email has been scanned for all viruses by the MessageLabs Email
> > Security System. For more information on a proactive email security
> > service working around the clock, around the globe, visit
> > http://www.messagelabs.com
> >
> >
>
>
>

Mime
View raw message