...could we please have a warning message logged when the default
application module is not found on startup? Something like,
"Could not find the application module 'com.mycompany.project.WoteverModule'"
Because everytime (and it does seem to be *everytime*!) I start a new
project I miss-type, mi
Oh, nice one!
Cheers!
On 15 October 2011 05:51, Howard Lewis Ship wrote:
> I'm about to commit changes to allow for registry "will" shutdown
> notifications.
>
> On Fri, Oct 14, 2011 at 1:20 PM, Tony Nelson wrote:
>> I have a bunch of threads that I've spawned off that I'd like to shut down
I'm about to commit changes to allow for registry "will" shutdown notifications.
On Fri, Oct 14, 2011 at 1:20 PM, Tony Nelson wrote:
> I have a bunch of threads that I've spawned off that I'd like to shut down
> gracefully.
>
> On Oct 14, 2011, at 4:14 PM, Steve Eynon wrote:
>
>> Alas no, there
On Fri, Oct 14, 2011 at 1:22 PM, Richard Yunhua Sang
wrote:
> Tapestry 5 version: 5.3-beta19
>
> I love the API of tapestry-func, Today when I use tapestry-func to process a
> file with 3 million lines, I get following exception:
>
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap
Tapestry 5 version: 5.3-beta19
I love the API of tapestry-func, Today when I use tapestry-func to process a
file with 3 million lines, I get following exception:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOfRange(Arrays.java:3209)
at java.lang
I have a bunch of threads that I've spawned off that I'd like to shut down
gracefully.
On Oct 14, 2011, at 4:14 PM, Steve Eynon wrote:
> Alas no, there is no other method (I'm aware of) that lets you know
> the registry is "about to shutdown", just the one that tells you it's
> in the process
Alas no, there is no other method (I'm aware of) that lets you know
the registry is "about to shutdown", just the one that tells you it's
in the process of.
There have been a couple of situations when I wished there was though!
(e.g. to log the shutdown event to a database.)
Steve.
On 15 October
I have successfully registered a shutdown listener as described in the document
ion. It seems that registryDidShutdown() is called after the registry is done
shutting down and I no longer have access to any of the services the registry
previously held. Is there another method I can use to be n
Thanks, Wulf, this is an excellent idea.
I wound up doing something similar:
Effect.Highlight.prototype.initialize = function(element) {
this.element = $(element);
if (!this.element) throw(Effect._elementDoesNotExistError);
var options = Object.extend({ startcolor: '%s' }, arguments[1]
On Fri, 14 Oct 2011 11:31:13 -0300, Wechsung, Wulf
wrote:
2) checks all classes in the "managed" package for the class format and
tapestry-required visibility
This is done by the JVM, so I don't know why Tapestry should do that
too.
I specifically mean it should test ( if possible) that
I saw the following notification in my tomcat log after a tomcat:redeploy
SEVERE: The web application [/instihire] registered the JDBC driver
[org.postgresql.Driver] but failed to unregister it when the web application
was stopped. To prevent a memory leak, the JDBC Driver has been forcibly
unr
No idea where "compassion" came from. I meant to say that I noticed
situations where setupRender is never called.
On Fri, Oct 14, 2011 at 9:35 AM, Ray Nicholus wrote:
> We are using T5.3 beta 19. Within the last few days, I
> noticed compassion where setupRender is never called on a rendering
Awesome, thanks! Learning something new every day :)
-Original Message-
From: Steve Eynon [mailto:steve.ey...@alienfactory.co.uk]
Sent: Freitag, 14. Oktober 2011 14:18
To: Tapestry users
Subject: Re: An Appeal To Use the Latest Betas
For point 3, try viewing the new PageCatalog page.
We are using T5.3 beta 19. Within the last few days, I
noticed compassion where setupRender is never called on a rendering
component. This does not happen with all components. It seems like this
happens on the affected components almost every time. Occasionally,
setupRender IS called on these c
On Fri, 14 Oct 2011 08:47:52 -0300, Wechsung, Wulf
wrote:
I've taken 5 minutes to try out the beta with my integration test
project and besides noticing that chenillekit doesn't declare its
dependency on tapestry as "provided" which leads to an
IncompatibleClassChangeError I found the be
For point 3, try viewing the new PageCatalog page.
e.g. http://localhost:8080/PageCatalog
There's a button there to load all pages.
Steve.
On 14 October 2011 19:47, Wechsung, Wulf wrote:
> I've taken 5 minutes to try out the beta with my integration test project and
> besides noticing that c
That occurred to me as well ... if you use a layout, wouldn't it be enough to
run
Effect.prototype.Highlight = function() { }
OnLoad to prevent all highlight effects everywhere in your app ...
-Original Message-
From: Robert Zeigler [mailto:robert.zeig...@roxanemy.com]
Sent: Freitag
You could monkey-patch Effect.Highlight to be a no-op... :)
Robert
On Oct 14, 2011, at 10/145:45 AM , Wechsung, Wulf wrote:
> Hi Lenny,
>
> one way would be to copy the complete datefield component, comment out line
> 121 in datefield js and make a beanblocksource contribution so that the
> b
I've taken 5 minutes to try out the beta with my integration test project and
besides noticing that chenillekit doesn't declare its dependency on tapestry as
"provided" which leads to an IncompatibleClassChangeError I found the beta-21
to be much stricter about the location of non-managed classe
Hi Lenny,
one way would be to copy the complete datefield component, comment out line 121
in datefield js and make a beanblocksource contribution so that the beaneditor
used your datefield instead of the built-in one.
(Can't promise that this is the easiest solution but if you need further
adv
A question I've been meaning to ask for a wee while now...
"How do I find out what updates go into each beta release?"
I've tried poking around JIRA but have not been able to come up with a
successful query. (I also admit my JIRA foo is lacking.)
You mention Twitter but I've resisted that (and m
...using beta-20 and I can't blame you for the bugs in my apps :-)
Am 14.10.2011 um 01:16 schrieb Howard Lewis Ship:
> If you've been following the discussions here and elsewhere, you may
> be aware that Tapestry 5.3 is nearly done, with big improvements to
> every aspect of Tapestry, including
...So that was the cause for my random problems in the other post:
http://tapestry-users.832.n2.nabble.com/SetupRender-not-called-td6854976.html
I had this error for Palette, too! Haven't seen the exception for a few days
now, so I guess your change made it into my branch :-)
Am 04.10.2011 um
23 matches
Mail list logo
