ike.wasser...@intelliware.ca]
Sent: Mon 1/12/2009 9:53 AM
To: Tapestry users
Subject: RE: Tapestry Upgrade problem
We believe that we may have found a solution to this problem.
We have placed the call to PageSpecificationResolver.resolve(IRequestCycle
cycle, String prefixedName) in PageSource.makeObject(
9/2009 11:36 AM
To: Tapestry users
Subject: RE: Tapestry Upgrade problem
Done.
If you need any more information please don't hesitate to ask.
Thanks
Mike
From: andre...@gmail.com on behalf of Andreas Andreou
Sent: Thu 1/8/2009 2:23 PM
To: Tapestry users
S
Done.
If you need any more information please don't hesitate to ask.
Thanks
Mike
From: andre...@gmail.com on behalf of Andreas Andreou
Sent: Thu 1/8/2009 2:23 PM
To: Tapestry users
Subject: Re: Tapestry Upgrade problem
Also, add an issue at
to
be in a similar area of the code it isn't the same stack trace that we're
getting.
Mike
From: andre...@gmail.com on behalf of Andreas Andreou
Sent: Thu 1/8/2009 2:03 PM
To: Tapestry users
Subject: Re: Tapestry Upgrade problem
I want to take
at
> they may be clobbering each other when getting loaded.
>
> Is this possible?
>
>
>
> From: Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
> Sent: Thu 1/8/2009 10:15 AM
> To: Tapestry users
> Subject: RE: Tapestry Upgrade prob
our app that are seperate Tapestry pages and we think
>> that they may be clobbering each other when getting loaded.
>>
>> Is this possible?
>>
>>
>>
>> From: Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
>> S
Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
> Sent: Thu 1/8/2009 10:15 AM
> To: Tapestry users
> Subject: RE: Tapestry Upgrade problem
>
>
>
> It now makes sense to me why the _components map is empty when getComponent()
> is called.
> The map is never populated because
From: Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
Sent: Thu 1/8/2009 10:15 AM
To: Tapestry users
Subject: RE: Tapestry Upgrade problem
It now makes sense to me why the _components map is empty when getComponent()
is called.
The map is never populated because no componentIds are found
creation happens is controlled by the
number of componentIds found.
Now to figure out why there are no ids.
Mike
From: Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
Sent: Wed 1/7/2009 3:32 PM
To: Tapestry users
Subject: RE: Tapestry Upgrade problem
he variables in the AbstractComponent class we found that the _components Map
was null, and _active was false.
Thanks
Mike
From: Howard Lewis Ship [mailto:hls...@gmail.com]
Sent: Wed 1/7/2009 2:33 PM
To: Tapestry users
Subject: Re: Tapestry Upgrade problem
stractComponent class we found that the _components Map
was null, and _active was false.
Thanks
Mike
From: Howard Lewis Ship [mailto:hls...@gmail.com]
Sent: Wed 1/7/2009 2:33 PM
To: Tapestry users
Subject: Re: Tapestry Upgrade problem
The _components field shou
; circumstances.
>
> Anyone have any clue why this is happening, or how it is possible for this to
> happen in Tapestry?
>
> Thanks
>
> Mike
>
>
>
>
> From: Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
> Sent: Tue 1/6/20
Wasserman [mailto:mike.wasser...@intelliware.ca]
Sent: Tue 1/6/2009 2:58 PM
To: Tapestry users
Subject: RE: Tapestry Upgrade problem
I've tried a variety of JDKs and the problem happens with all of them.
I've tracked it through the code and what it seems to come down to is that
somet
it's some sort of threading problem within
Tapestry.
Anyone have any ideas on how to fix this problem?
Thanks
Mike
From: Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
Sent: Thu 12/25/2008 1:07 PM
To: Tapestry users
Subject: RE: Tapestry Upgrade p
3:11 PM
To: Tapestry users
Subject: Re: Tapestry Upgrade problem
So, you weren't seeing this problem with 4.1.2 ?
I'd be interesting if you could try with a 1.6 VM, but apart from that
and since you're getting this consistently, i'm wondering if you can try this
(which is ba
p [mailto:hls...@gmail.com]
> Sent: Tuesday, December 23, 2008 2:00 PM
> To: Tapestry users
> Subject: Re: Tapestry Upgrade problem
>
> What JDK are you running on?
>
> On Tue, Dec 23, 2008 at 10:50 AM, Mike Wasserman
> wrote:
>> I am upgrading from Tapestry 4.1.2 t
al Message-
From: Howard Lewis Ship [mailto:hls...@gmail.com]
Sent: Tuesday, December 23, 2008 2:00 PM
To: Tapestry users
Subject: Re: Tapestry Upgrade problem
What JDK are you running on?
On Tue, Dec 23, 2008 at 10:50 AM, Mike Wasserman
wrote:
> I am upgrading from Tapestry 4.1.2 to Tapes
: Tapestry users
Subject: Re: Tapestry Upgrade problem
What JDK are you running on?
On Tue, Dec 23, 2008 at 10:50 AM, Mike Wasserman
wrote:
> I am upgrading from Tapestry 4.1.2 to Tapestry 4.1.6.
> When I run my integration tests (using Selenium) I am get a error
randoml
What JDK are you running on?
On Tue, Dec 23, 2008 at 10:50 AM, Mike Wasserman
wrote:
> I am upgrading from Tapestry 4.1.2 to Tapestry 4.1.6.
> When I run my integration tests (using Selenium) I am get a error randomly.
> I receive a org.apache.hivemind.ApplicationRuntimeException that indicates
19 matches
Mail list logo