You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@geronimo.apache.org by pa...@targetgroup.net on 2005/09/21 12:52:13 UTC
Possible class path class loader problem when using Spring
ClassPathXmlApplicationContext class
I have an application that uses Spring to interface with Hibernate, which
in turn accesses data via JDBC.
In Spring you can define a configuration file (applicationContext.xm) and
embed it in your class structure, at the package level, like so
net/targetgroup/broker/hibernate/applicationContext.xml
I have a class that loads up this configuration file, using the Spring
ClassPathXmlApplicationContext class:
static final ApplicationContext springApplicationContext = new
ClassPathXmlApplicationContext(
"net/targetgroup/broker/hibernate/applicationContext.xml");
This code effectivley loads the application context from the classpath,
and as my class that calls the above line of code is in the package
net.targetgroup.broker.hibernate
then by rights the applicationContext.xml should be in the classpath as
well, as its at the same level in the package hierarchy as the class
trying to load it.
The javadoc for the Spring class is here
http://www.springframework.org/docs/api/org/springframework/context/support/ClassPathXmlApplicationContext.html
This all works fine in Websphere 5.1. When I export my EAR from WSAD and
try and deploy it into Geronimo I get the stack trace below. This implies
to me that the classpath is somehow different to what it shuld be, but how
can this be ? If the class running is
net.targetgroup.broker.hibernate.HibernateAttributes
then how come it cannot find the resource
net/targetgroup/broker/hibernate/applicationContext.xml
in the class path ? Is there some difference in how classpaths or
classlaoding is handled between Websphere 5.1 and Geronimo ?
Caused by: org.springframework.beans.factory.BeanDefinitionStoreException:
IOException parsing XML document from class path resource
[net/targetgroup/broker/hibernate/applicationContext.xml]; nested
exception is java.io.FileNotFoundException: class path resource
[net/targetgroup/broker/hibernate/applicationContext.xml] cannot be opened
because it does not exist
at
org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:176)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:125)
at
org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:141)
at
org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:113)
at
org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:81)
at
org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:89)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:268)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:81)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:66)
at
org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:57)
at
net.targetgroup.broker.hibernate.HibernateAttributes.<clinit>(HibernateAttributes.java:26)
... 7
Paul Newport
Systems Consultant
Tel: +44 (0) 117 917 0600
Fax: +44 (0) 117 917 0660
Target
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.
**********************************************************************
_____________________________________________________________________
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
Re: Possible class path class loader problem when using Spring
ClassPathXmlApplicationContext class
Posted by pa...@targetgroup.net.
It was M4 not the head, and I didn't see anythign extra in the log.....
Target
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.
**********************************************************************
_____________________________________________________________________
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
Re: Possible class path class loader problem when using Spring ClassPathXmlApplicationContext class
Posted by Kevan Miller <ke...@gmail.com>.
Hi Paul,
Thanks for doing all that! Now if only it had identified your problem... Are
you running on M4 or have you built from HEAD? Do you see anything in the
log?
I don't have any suggestions at the moment for gathering additional
information, but will look into it...
--kevan
On 9/23/05, paul.newport@targetgroup.net <pa...@targetgroup.net>
wrote:
>
>
> Just an update on this:
>
> 1) some test code where a servlet tries to load the initial context works
> 2) some test code where a servlet calls an EJB which tries to load the
> initial context works
> 3) My application EAR still has the original problem
> 4) I cannot provide the EAR I'm afraid (too big to send, company rules
> etc).
>
> Has anyone any suggestions for adding any logging code to see what is
> going on ? In particular I am mightily confused how a class in a particular
> package can be running (and therefore that class and package must surely be
> in the classpath) cannot load a resource at the same level in the package
> hierarchy as the class running.
>
> Target 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.
> **********************************************************************
> _____________________________________________________________________
> 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
>
--
--kevan
Re: Possible class path class loader problem when using Spring ClassPathXmlApplicationContext class
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I guess one of the questions is, where's the Spring code? Are you packaging
Spring in your EAR or using the Spring features in Geronimo or what?
Aaron
On 9/21/05, Aaron Mulder <am...@alumni.princeton.edu> wrote:
>
>
>
> On 9/21/05, Gianny Damour <gi...@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
> > > <ma...@targetgroup.net>* <paul.newport@targetgroup.net
> > > <ma...@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
> > > <ma...@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
> > >
> > >
> >
> >
> >
>
Re: Possible class path class loader problem when using Spring ClassPathXmlApplicationContext class
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On 9/21/05, Gianny Damour <gi...@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
> > <ma...@targetgroup.net>* <paul.newport@targetgroup.net
> > <ma...@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
> > <ma...@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
> >
> >
>
>
>
Re: Possible class path class loader problem when using Spring
ClassPathXmlApplicationContext class
Posted by pa...@targetgroup.net.
Just an update on this:
1) some test code where a servlet tries to load the initial context works
2) some test code where a servlet calls an EJB which tries to load the
initial context works
3) My application EAR still has the original problem
4) I cannot provide the EAR I'm afraid (too big to send, company rules
etc).
Has anyone any suggestions for adding any logging code to see what is
going on ? In particular I am mightily confused how a class in a
particular package can be running (and therefore that class and package
must surely be in the classpath) cannot load a resource at the same level
in the package hierarchy as the class running.
Target
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.
**********************************************************************
_____________________________________________________________________
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
Re: Possible class path class loader problem when using Spring
ClassPathXmlApplicationContext class
Posted by pa...@targetgroup.net.
I can't supply the EAR due to the product being commerical, but will
attempt to knock up a test EAR.
Your example is a bit different to mine, in that in yours the path is web
app class calls Spring, and mine is web app calls EJB calls Spring
Thanks for your help.
Target
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.
**********************************************************************
_____________________________________________________________________
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
Re: Possible class path class loader problem when using Spring ClassPathXmlApplicationContext
class
Posted by Gianny Damour <gi...@optusnet.com.au>.
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
> <ma...@targetgroup.net>* <paul.newport@targetgroup.net
> <ma...@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>
> **********************************************************************
> 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
> <ma...@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
>
>
Re: Possible class path class loader problem when using Spring ClassPathXmlApplicationContext class
Posted by Kevan Miller <ke...@gmail.com>.
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 <pa...@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>**********************************************************************
> 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.
> **********************************************************************
> _____________________________________________________________________
> 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
>
Re: Possible class path class loader problem when using Spring
ClassPathXmlApplicationContext class
Posted by pa...@targetgroup.net.
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
**********************************************************************
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.
**********************************************************************
_____________________________________________________________________
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
Re: Possible class path class loader problem when using Spring ClassPathXmlApplicationContext class
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
How have you packaged the Spring libraries and config file and
application code within the EAR/JAR/WAR or the repository? That
definitely affects the class loaders used in Geronimo.
Aaron
On 9/21/05, paul.newport@targetgroup.net <pa...@targetgroup.net> wrote:
>
> I have an application that uses Spring to interface with Hibernate, which in
> turn accesses data via JDBC.
>
> In Spring you can define a configuration file (applicationContext.xm) and
> embed it in your class structure, at the package level, like so
>
> net/targetgroup/broker/hibernate/applicationContext.xml
>
> I have a class that loads up this configuration file, using the Spring
> ClassPathXmlApplicationContext class:
>
> static final ApplicationContext springApplicationContext = new
> ClassPathXmlApplicationContext("net/targetgroup/broker/hibernate/applicationContext.xml");
>
> This code effectivley loads the application context from the classpath, and
> as my class that calls the above line of code is in the package
>
> net.targetgroup.broker.hibernate
>
> then by rights the applicationContext.xml should be in the classpath as
> well, as its at the same level in the package hierarchy as the class trying
> to load it.
>
> The javadoc for the Spring class is here
>
> http://www.springframework.org/docs/api/org/springframework/context/support/ClassPathXmlApplicationContext.html
>
>
> This all works fine in Websphere 5.1. When I export my EAR from WSAD and try
> and deploy it into Geronimo I get the stack trace below. This implies to me
> that the classpath is somehow different to what it shuld be, but how can
> this be ? If the class running is
>
> net.targetgroup.broker.hibernate.HibernateAttributes
>
> then how come it cannot find the resource
>
> net/targetgroup/broker/hibernate/applicationContext.xml
>
> in the class path ? Is there some difference in how classpaths or
> classlaoding is handled between Websphere 5.1 and Geronimo ?
>
>
> Caused by:
> org.springframework.beans.factory.BeanDefinitionStoreException:
> IOException parsing XML document from class path resource
> [net/targetgroup/broker/hibernate/applicationContext.xml];
> nested exception is java.io.FileNotFoundException: class path resource
> [net/targetgroup/broker/hibernate/applicationContext.xml]
> cannot be opened because it does not exist
> at
> org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:176)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:125)
> at
> org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:141)
> at
> org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:113)
> at
> org.springframework.context.support.AbstractXmlApplicationContext.loadBeanDefinitions(AbstractXmlApplicationContext.java:81)
> at
> org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:89)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:268)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:81)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:66)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:57)
> at
> net.targetgroup.broker.hibernate.HibernateAttributes.<clinit>(HibernateAttributes.java:26)
> ... 7
>
> Paul Newport
> Systems Consultant
> Tel: +44 (0) 117 917 0600
> Fax: +44 (0) 117 917 0660 Target 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.
> **********************************************************************
> _____________________________________________________________________
> 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
>