You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Ken in Nashua <kc...@live.com> on 2012/11/02 05:48:39 UTC
RE: quarky page injection... late allocation
Well i have set all -Dtapestry.production-mode=true (beit true or false) in my eclipse debug configurations, pom.xml's, AppModule.JAVA and web.xml.
The only place that I set this that actually had an effect on how the webapp runs PROD MODE
Application 'app' (version 1.0-SNAPSHOT-1351774079811) startup time: 330 ms to build IoC Registry, 3,082 ms overall.
______ __ ____
/_ __/__ ____ ___ ___ / /_______ __ / __/
/ / / _ `/ _ \/ -_|_-</ __/ __/ // / /__ \
/_/ \_,_/ .__/\__/___/\__/_/ \_, / /____/
/_/ /___/ 5.3.2
2012-11-02 00:35:39.725:INFO::Started SelectChannelConnector@0.0.0.0:8080
or DEV MODE
Application 'app' (version 1.0-SNAPSHOT-1351774079811) startup time: 370 ms to build IoC Registry, 3,283 ms overall.
______ __ ____
/_ __/__ ____ ___ ___ / /_______ __ / __/
/ / / _ `/ _ \/ -_|_-</ __/ __/ // / /__ \
/_/ \_,_/ .__/\__/___/\__/_/ \_, / /____/
/_/ /___/ 5.3.2 (development mode)
2012-11-02 00:42:04.796:INFO::Started SelectChannelConnector@0.0.0.0:8080
[INFO] Started Jetty Server
and actually telling me what mode it is running in is
is by setting the default VM Arguments within my eclipse preferences, java, installed jre's definition with -Dtapestry.production-mode=false
But I am seeing the same behavior... parameters (tapestry component parameters and actualy java method parameters) are intermittently null... but mysteriously appear valid when I step into the next method... but the app progressively gets worse as it runs... clicking event handlers and everything starts becoming null
I dont believe this is a prod/dev runtime mode issue.
But would welcome any more suggestions as how to flush this out beyond beginning to take the app apart.
Thanks
Ken
Re: quarky page injection... late allocation
Posted by Howard Lewis Ship <hl...@gmail.com>.
The fields are null because the values are often stored elsewhere;
this is part of the logic that allows a single page instance to be
actively shared across threads.
Its much more likely that your application is at fault. For example,
that "cursor" parameter may be bound to a property that is non-null
when the page renders, but is then null when the associated link is
clicked. The field that the parameter is ultimately bound to should be
persisted in the session, or on the client (using either page
activation context, or the event's context).
On Thu, Nov 1, 2012 at 9:52 PM, Ken in Nashua <kc...@live.com> wrote:
>
> Just another byproduct of things that occur and run amuck within the app at runtime
>
> An unexpected application exception has occurred.Parameter 'cursor' of component Home:gallerywidget is bound to null. This parameter is not allowed to be null.
>
>
>
> I guess I need to review all the code and see whats taking this down and start pulling it apart to try ans flush it out.
> not a fun bug... but I will be happy to find it
>
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
RE: quarky page injection... late allocation
Posted by Ken in Nashua <kc...@live.com>.
Just another byproduct of things that occur and run amuck within the app at runtime
An unexpected application exception has occurred.Parameter 'cursor' of component Home:gallerywidget is bound to null. This parameter is not allowed to be null.
I guess I need to review all the code and see whats taking this down and start pulling it apart to try ans flush it out.
not a fun bug... but I will be happy to find it