To: 'Tapestry users'
Subject: RE: T5.1.0.2 problem with TestableRequestImpl
Thanks Massimo, I'll probably file a Jira issue about this then. Weird
thing is I don't think all my tests that use PageTester are failing. I
need to investigate it, but so far I've spent a week (@50%) on moving
from
On Tue, Mar 31, 2009 at 3:28 PM, Blower, Andy
andy.blo...@proquest.co.uk wrote:
I'm in the process of migrating from T5.0.18 to T5.1 and I'm using the
T5.1.0.2 release currently being voted on. I've fixed all the compilation
errors and disabled enough of our custom stuff to get pages
know how
much time I'll be able to dedicate to this.
-Original Message-
From: Massimo Lusetti [mailto:mluse...@gmail.com]
Sent: 03 April 2009 10:27
To: Tapestry users
Subject: Re: T5.1.0.2 problem with TestableRequestImpl
On Tue, Mar 31, 2009 at 3:28 PM, Blower, Andy
andy.blo
--
View this message in context:
http://www.nabble.com/T5.1.0.2-problem-with-TestableRequestImpl-tp22805378p22867172.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr
although most of our javascript seems to be broken (I'll be looking into this
issue next)
I had a similar issue and it was caused by Tapestry now including
Javascript in the top (head tag) instead of the end of the body
tag. My Javascript code was referencing some tags by id, but they
weren't
to be defined before
the JS import) is no longer needed with the latest version of the 3rd party
module.
-Original Message-
From: Thiago H. de Paula Figueiredo [mailto:thiag...@gmail.com]
Sent: 03 April 2009 13:18
To: Tapestry users
Subject: Re: T5.1.0.2 problem with TestableRequestImpl
Looking at the stack trace, it appears that there was an exception,
and that the PageTester problem occured while rendering out the
exception report page. We could change getServerName() to just return
localhost rather than throwing an exception.
On Fri, Apr 3, 2009 at 2:26 AM, Massimo Lusetti
I've added TAP5-621.
On Fri, Apr 3, 2009 at 9:14 AM, Howard Lewis Ship hls...@gmail.com wrote:
Looking at the stack trace, it appears that there was an exception,
and that the PageTester problem occured while rendering out the
exception report page. We could change getServerName() to just
On Fri, Apr 3, 2009 at 2:10 PM, Angelo Chen angelochen...@yahoo.com.hk wrote:
Hi Massimo,
What's the Selelium based test? can it replace PageTester? I have tried the
PageTester on the past, and the impression I got is, making it work requires
more effort to write the program itself and test
On Fri, Apr 3, 2009 at 6:23 PM, Howard Lewis Ship hls...@gmail.com wrote:
I've added TAP5-621.
On Fri, Apr 3, 2009 at 9:14 AM, Howard Lewis Ship hls...@gmail.com wrote:
Looking at the stack trace, it appears that there was an exception,
and that the PageTester problem occured while rendering
I'm in the process of migrating from T5.0.18 to T5.1 and I'm using the T5.1.0.2
release currently being voted on. I've fixed all the compilation errors and
disabled enough of our custom stuff to get pages rendering, although most of
our javascript seems to be broken (I'll be looking into this
11 matches
Mail list logo
