You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Alex Shneyderman <a....@gmail.com> on 2008/03/18 12:05:12 UTC
More WebLogic troubles.
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: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: More WebLogic troubles.
Posted by Randy Burgess <RB...@nuvox.com>.
On 9.2.1 and 9.2.2 I use
<param-value>classpath:applicationContext.xml
/WEB-INF/spring/otherAppContext.xml</param-value>
That is a space between the context file names. I don't use wildcards
because I have contexts that I don't want loaded in WL.
Regards,
Randy Burgess
Sr. Web Applications Developer
Nuvox Communications
> From: Alex Shneyderman <a....@gmail.com>
> Reply-To: Struts Users Mailing List <us...@struts.apache.org>
> Date: Tue, 18 Mar 2008 12:58:13 +0100
> To: Struts Users Mailing List <us...@struts.apache.org>
> Subject: Re: More WebLogic troubles.
>
> 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</listene
> r-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</listene
> r-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
> <a....@gmail.com> 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: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
This email and any attachments ("Message") may contain legally privileged and/or confidential information. If you are not the addressee, or if this Message has been addressed to you in error, you are not authorized to read, copy, or distribute it, and we ask that you please delete it (including all copies) and notify the sender by return email. Delivery of this Message to any person other than the intended recipient(s) shall not be deemed a waiver of confidentiality and/or a privilege.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: More WebLogic troubles.
Posted by Alex Shneyderman <a....@gmail.com>.
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
<a....@gmail.com> 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: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org