Thanks alot. That was interceptor problem.
One Question: How can I understand interceptors more. They have certain
stacking otherwise problems. Is there anyway to understand, How to stack
interceptors properly to make things work?
Hope you understand, What I want to ask.
2012/10/15 pirzada rashid :
> One Question: How can I understand interceptors more. They have certain
> stacking otherwise problems. Is there anyway to understand, How to stack
> interceptors properly to make things work?
On the beginning use stacks defined by framework, you can just tweak
them a
Hello Listers,
I have back end website running on Tomcat using struts with the following url
http://local.domain.com/app. External user access the website through apache
proxy with the following url http://www.domain.com/user1 (user1, user2, etc...
It’s uri specific to each user). I want to us
> > ActionSupport#getTextProviderSupport() uses the TextProviderFactory to
> obtain it's instance of a support object. Since it uses the di to inject
> this into
> the factory, my custom version is correctly injected. However, I need to
> initialize my custom support object with a resource that
If you are using the Spring Framework with your App, you should be able to
define your TextProvider, with all it's dependencies, as a Spring Bean,
then when you define the in Struts use the Spring Bean ID instead of
using the full class name. Struts will use that Spring Bean in place of
creating
> If you are using the Spring Framework with your App, you should be able to
> define your TextProvider, with all it's dependencies, as a Spring Bean, then
> when you define the in Struts use the Spring Bean ID instead of using
> the full class name. Struts will use that Spring Bean in place of
With the Spring Plugin, Spring becomes the framework's internal DI.
(*Chris*)
On Mon, Oct 15, 2012 at 8:43 AM, Davis, Chad wrote:
>
>
> > If you are using the Spring Framework with your App, you should be able
> to
> > define your TextProvider, with all it's dependencies, as a Spring Bean,
> t
> If you are using the Spring Framework with your App, you should be able to
> define your TextProvider, with all it's dependencies, as a Spring Bean, then
> when you define the in Struts use the Spring Bean ID instead of using
> the full class name. Struts will use that Spring Bean in place of
Do you have the:
constant defined in your struts.xml? That should be all that's needed.
(*Chris*)
On Mon, Oct 15, 2012 at 2:53 PM, Davis, Chad wrote:
>
>
> > If you are using the Spring Framework with your App, you should be able
> to
> > define your TextProvider, with all it's dependenc
9 matches
Mail list logo