Alin Dreghiciu wrote:
I may look into it if you can provide a simplified WAR that displays
this problem.
I've prepared simple maven project. (in attachment)
Otherwise do this for a tryout:
make sure that in the WAR you
have: WEB-INF/classes/http-file-provider-application-context.xml
change
I may look into it if you can provide a simplified WAR that displays this
problem.
Otherwise do this for a tryout:
make sure that in the WAR you have:
WEB-INF/classes/http-file-provider-application-context.xml
change this line as follows:
ApplicationContext context = new
ClassPathXmlApplicationCon
I'm out of ideas, so would need to look at the Spring algorithm to figure
out what is going on. And I'm far from a computer to do so now... Maybe in
the weekend.
Alin, do you got any ideas?
-- Niclas
On 9 Dec 2009 22:34, "Pawel Wesolowski" wrote:
Niclas Hedhman wrote: > > > > This should have
Niclas Hedhman wrote:
This should have gone to list.
I am not sure, but GutFeeling says that this is an icky location.
If I were you, I would first try and see what happens if you move to a
more "obvious" place for Spring to find it, like WEB-INF/classes. I
suspect you are touching corner-ca
This should have gone to list.
I am not sure, but GutFeeling says that this is an icky location.
If I were you, I would first try and see what happens if you move to a more
"obvious" place for Spring to find it, like WEB-INF/classes. I suspect you
are touching corner-cases in servlet spec more tha
Hi all,
I have a problem with deploying my war file in FuseESB v4.1.0.2. As you
may know Fuse v4.1.0.2 is distributed with following bundles:
[ 9] [Active ] [ ] [ 8] OPS4J Pax Logging - API (1.3.0)
[ 10] [Active ] [ ] [ 8] OPS4J Pax Logging - Service (1.3.0)
[ 11] [Active ] [ ] [ 5] OPS4J Pax
