Ok I resync'd my ports
The solution to maxformsize was as followqs
set MAVEN_OPTS=-Dorg.mortbay.jetty.Request.maxFormContentSize=-1 -Xms512m
-Xmx1024m -Xss256k
mvn jetty:run
kinda slooowwwwwww but it flies... what is urping me now is the massive content
being churned over the request pipe.. who would have known it takes the whole
entity and processes it over in the first place... well maybe its just the
PHOTO property of the entity ? Are photo images that expensive ? I am inclined
to say that this is the issue...
so I cant just develop a tapestry widget as-is... I need to come up with some
hoakey link ID semantic so-as not to have tapestry serialize the whole ENTITY
over the form request proxy ?
Can someone shed some light here on this ?
Here is my photo logic that operates on a collection of hibernate entities and
renders them in a Gallery widget.
<img
id="ImageWidget" src="${photoLink}" alt="${currentObject}" width="200"
height="160"
title="${currentObject.photo.fileName}"
model="currentObject"
image="${photoLink}"
/>
If you know of a quick way to tell tapestry to just get the photo by ID instead
of the whole thing I would be interested in conforming.
Thanks for your input you can see the gallery widget at
http://psinh.ddns.net:9011/psi/home
and you can login as administrator/administrator
How do I display all these images without clogging up the form content size ?
thanks for your help
Best regards
and thanks... KEN
From: nhhockeypla...@hotmail.com
To: users@tapestry.apache.org
Subject: RE: possible security bug or tapestry bug beta-22
Date: Tue, 2 Dec 2014 02:41:07 -0500
Is this necessary ? Is there a way to resolve ? Cant say I am impressed with
the performance when this thing is fully loaded.
Trying to find a way for this to work.
HTTP ERROR 500
Problem accessing /psi/home.galleryform/player. Reason:
Form too large1051684>200000Caused by:java.lang.IllegalStateException: Form
too large1051684>200000
