...@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(Object key
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
Subject: Re: Tapestry
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 a look, but got two questions
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 https
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
: 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 when
[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 when
: Tapestry Upgrade problem
Actually I was wrong in what I wrote in my last email.
addComponent() is NOT being called before getComponent() when the problem
arises.
Mike
From: Mike Wasserman [mailto:mike.wasser...@intelliware.ca]
Sent: Wed 1/7/2009 2:47 PM
and we think that
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 problem
It now makes sense
[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
sometimes the _components
it is possible for this to
happen in Tapestry?
Thanks
Mike
From: Mike 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
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 should be populated
: Tapestry Upgrade problem
Multiple pages are afflicted. It appears to happen primarily with the shell
component.
We put logging in the getComponent() and the addComponent() methods of the
AbstractComponent class to output the Thread Id and Component Id since the
adding of components
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 problem
Thanks
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 based on some old reports I
: 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
mike.wasser...@intelliware.ca wrote:
I am upgrading from Tapestry 4.1.2
, 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
mike.wasser...@intelliware.ca wrote:
I am upgrading from Tapestry 4.1.2 to Tapestry 4.1.6.
When I run my integration tests (using
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 that
given component (page) does not contain a component shell.
All of the affected pages
users
Subject: Re: Tapestry Upgrade problem
What JDK are you running on?
On Tue, Dec 23, 2008 at 10:50 AM, Mike Wasserman
mike.wasser...@intelliware.ca 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
19 matches
Mail list logo
