finally got time to test it and it works wonder
thanks
On Fri, May 17, 2013 at 4:09 PM, Steven Yang wrote:
> Thanks will do asap
>
>
> On Fri, May 17, 2013 at 2:39 PM, Lukasz Lenart wrote:
>
>> Committed, please check with the latest snapshot.
>>
>>
>> Regards
>> --
>> Łukasz
>> + 48 606 323 12
Thanks will do asap
On Fri, May 17, 2013 at 2:39 PM, Lukasz Lenart wrote:
> Committed, please check with the latest snapshot.
>
>
> Regards
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
>
> 2013/5/17 Steven Yang :
> > Wow that's fast
> >
> > here it is
> > https://issues.apache.or
Committed, please check with the latest snapshot.
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/5/17 Steven Yang :
> Wow that's fast
>
> here it is
> https://issues.apache.org/jira/browse/WW-4067
>
> thanks
>
>
> On Fri, May 17, 2013 at 3:42 AM, Lukasz Lenart wrote:
>
>> Fi
Wow that's fast
here it is
https://issues.apache.org/jira/browse/WW-4067
thanks
On Fri, May 17, 2013 at 3:42 AM, Lukasz Lenart wrote:
> Fix is ready, I just need a JIRA task :-)
>
> 2013/5/16 Lukasz Lenart :
> > I have been looking into that and I am sure that's the problem, could
> > you regi
Fix is ready, I just need a JIRA task :-)
2013/5/16 Lukasz Lenart :
> I have been looking into that and I am sure that's the problem, could
> you register an issue with JIRA?
>
>
> Thanks in advance
> --
> Łukasz
> + 48 606 323 122 http://www.lenart.org.pl/
>
> 2013/5/16 Lukasz Lenart :
>> Maybe y
I have been looking into that and I am sure that's the problem, could
you register an issue with JIRA?
Thanks in advance
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/5/16 Lukasz Lenart :
> Maybe your problem is related to:
>
> https://issues.apache.org/jira/browse/WW-3870
>
>
> Reg
Maybe your problem is related to:
https://issues.apache.org/jira/browse/WW-3870
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
2013/5/9 Steven Yang :
> thanks good to know i am not being forgotten :)
>
>
> On Thu, May 9, 2013 at 12:51 PM, Lukasz Lenart wrote:
>
>> It's on my ToD
thanks good to know i am not being forgotten :)
On Thu, May 9, 2013 at 12:51 PM, Lukasz Lenart wrote:
> It's on my ToDo list ;-)
>
> 2013/5/9 Steven Yang :
> > Hi just wondering is anyone as any insight on this? Or do I need to
> provide
> > more information?
> >
> > thanks
> >
> >
> > On Fri, A
It's on my ToDo list ;-)
2013/5/9 Steven Yang :
> Hi just wondering is anyone as any insight on this? Or do I need to provide
> more information?
>
> thanks
>
>
> On Fri, Apr 26, 2013 at 3:37 PM, Steven Yang wrote:
>
>> same behavior for devMode=true and false
>>
>> i am not sure what you mean, s
Hi just wondering is anyone as any insight on this? Or do I need to provide
more information?
thanks
On Fri, Apr 26, 2013 at 3:37 PM, Steven Yang wrote:
> same behavior for devMode=true and false
>
> i am not sure what you mean, shouldnt init only be called during
> initialization?
> or do you
same behavior for devMode=true and false
i am not sure what you mean, shouldnt init only be called during
initialization?
or do you want to confirm that when I run my app after initialization, the
init method wont be called again?
so far the observation is that this only happen during initializati
2013/4/25 Felipe Lorenz :
> with version 2.3.12, same behavior.
Is this happen only during initialisation? in devMode?
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: user-unsubscr...@str
2013/4/25 Steven Yang :
> And sorry this behavior started on 2.3.7 and 2.3.4.1 does not have this
> behavior
I would said, it isn't expected behavior ;-)
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubs
@Maurizio sorry in the sample app I do not using Spring. I am using Spring
in my projects, sorry for the confusion
And sorry this behavior started on 2.3.7 and 2.3.4.1 does not have this
behavior
On Thu, Apr 25, 2013 at 9:13 AM, Steven Yang wrote:
> @Maurizio I am indeed using Spring, I will t
@Maurizio I am indeed using Spring, I will try without Spring.
@Dave what i mean by "include" is that I use the tag
I do understand that Interceptor is singleton-ish. And I do understand if I
defined the same interceptor in two different stacks there should be two
different instances.
However the
Yep, it makes sense definitely, otherwise there would not be way to share a
single instance with different params.
Il giorno 24/apr/2013 15:31, "Dave Newton" ha
scritto:
> Definitely singleton-ish, although i thought there was an
> instance-per-package--I thought I had packages with the same inte
Definitely singleton-ish, although i thought there was an
instance-per-package--I thought I had packages with the same interceptor
configured in different ways, but I can't check at the moment.
Dave
On Wed, Apr 24, 2013 at 9:28 AM, Maurizio Cucchiara
wrote:
> @Dave, I also could be wrong, but
@Dave, I also could be wrong, but I remember that interceptors are
singletone (maybe there is a single instance per package).
@Steven looks like you're using Spring, if yes, could you check if you
experience the same behavior w/o it?
Il giorno 24/apr/2013 14:04, "Dave Newton" ha
scritto:
> I'm no
I'm not sure I understand what you mean regarding using the "include"
element (i.e., precisely what you're doing) but I thought that each package
would have its own set of interceptors, meaning there would be two
instances, hence init would be called twice.
This would be trivial to determine by ch
I was using 2.1.8 and recently upgraded to 2.3.14.
And I realized that my interceptor got initialized twice and it didnt
happen before.
This happens when I declare a default package in struts.xml and include
other xml which have packages that extends my default package. But the
thing is no matter
20 matches
Mail list logo
