You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tiles.apache.org by Mck <mc...@apache.org> on 2013/11/01 13:49:03 UTC
Re: Infinite loop when using completeAutoLoad=true & Tiles 3.0.1
> I don't think there is anything specifically special in this
> configuration, so am not sure why I get into an infinite loop. If I
> replace the CompleteAutoTilesInitializer class with the
> BasicTilesInitializerClass and use Wildcards (ie: */*) instead and
> replace {1} with {1}/{2}, then the view loads properly (no infinite loop).
This problem was fixed by making the REGEXP pattern less greedy correct?
~mck
Re: Infinite loop when using completeAutoLoad=true & Tiles 3.0.1
Posted by Paul Benedict <pb...@apache.org>.
Jinal,
You'll have to unsubscribe yourself:
http://struts.apache.org/mail.html
-- Paul
On Tue, Nov 5, 2013 at 3:33 PM, Jinal Patel <pa...@gmail.com> wrote:
> can you please remove me from the mailing list? I am not sure why I am
> getting these emails. Thank you
>
>
> On Tue, Nov 5, 2013 at 2:49 PM, Eric B <eb...@hotmail.com> wrote:
>
> > On 13-11-01 8:49 AM, Mck wrote:
> >
> >>
> >> I don't think there is anything specifically special in this
> >>> configuration, so am not sure why I get into an infinite loop. If I
> >>> replace the CompleteAutoTilesInitializer class with the
> >>> BasicTilesInitializerClass and use Wildcards (ie: */*) instead and
> >>> replace {1} with {1}/{2}, then the view loads properly (no infinite
> >>> loop).
> >>>
> >>
> >>
> >> This problem was fixed by making the REGEXP pattern less greedy correct?
> >>
> >
> > Yes - a less greedy regexp fixed this problem. I had not realized that
> > every template name would be tested against the definition names/patterns
> > as well, and therefore cause an infinite loop with a greedy regex.
> >
> >
> >
>
--
Cheers,
Paul
Re: Infinite loop when using completeAutoLoad=true & Tiles 3.0.1
Posted by Jinal Patel <pa...@gmail.com>.
can you please remove me from the mailing list? I am not sure why I am
getting these emails. Thank you
On Tue, Nov 5, 2013 at 2:49 PM, Eric B <eb...@hotmail.com> wrote:
> On 13-11-01 8:49 AM, Mck wrote:
>
>>
>> I don't think there is anything specifically special in this
>>> configuration, so am not sure why I get into an infinite loop. If I
>>> replace the CompleteAutoTilesInitializer class with the
>>> BasicTilesInitializerClass and use Wildcards (ie: */*) instead and
>>> replace {1} with {1}/{2}, then the view loads properly (no infinite
>>> loop).
>>>
>>
>>
>> This problem was fixed by making the REGEXP pattern less greedy correct?
>>
>
> Yes - a less greedy regexp fixed this problem. I had not realized that
> every template name would be tested against the definition names/patterns
> as well, and therefore cause an infinite loop with a greedy regex.
>
>
>
Re: Infinite loop when using completeAutoLoad=true & Tiles 3.0.1
Posted by Eric B <eb...@hotmail.com>.
On 13-11-01 8:49 AM, Mck wrote:
>
>> I don't think there is anything specifically special in this
>> configuration, so am not sure why I get into an infinite loop. If I
>> replace the CompleteAutoTilesInitializer class with the
>> BasicTilesInitializerClass and use Wildcards (ie: */*) instead and
>> replace {1} with {1}/{2}, then the view loads properly (no infinite loop).
>
>
> This problem was fixed by making the REGEXP pattern less greedy correct?
Yes - a less greedy regexp fixed this problem. I had not realized that every template name would be tested against the definition names/patterns as
well, and therefore cause an infinite loop with a greedy regex.