Well upon further investigation ... the following does not work on WL
but works on jetty
<!-- Listeners -->
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>classpath*:applicationContext*.xml</param-value>
</context-param>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
WL becomes happy if this is specified:
<!-- Listeners -->
<context-param>
<param-name>contextConfigLocation</param-name>
<param-value>/WEB-INF/applicationContext.xml</param-value>
</context-param>
<listener>
<listener-class>org.springframework.web.context.ContextLoaderListener</listener-class>
</listener>
The first is the sample from archetype. So, does anyone know why WL is
this retarded and how to make it load ctx from the classpath ?
Alex.
On Tue, Mar 18, 2008 at 12:05 PM, Alex Shneyderman
<[EMAIL PROTECTED]> wrote:
> It seems that anything I do today with WL and struts 2 does not seem
> to be working :-(
>
> So, now I have an interceptor (S2 interceptor). I would like to wire a
> spring managed service on it. So, I use spring plugin + autowire by
> name convention. There is nothing fancy really just a declaration.
> but when I run the application in my local jetty setup everything
> works normally. I deploy to local WLS (but I do not think this would
> be anything different if I deployed remotely) The service does not get
> autowired.
>
> Anyone has a clue as to what's wrong with this?
>
> I setup my WL server to prefer classes and libs in WEB-INF so the
> classloading issues that might be should not be a problem. There is
> something that WL does that seems unconventional I wonder if anyone
> had similar experiences and what you guys were doing to tame the beast
> ?
>
> Thanks,
> Alex.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
