Hi,
That feature is far from new. I'm using it on several sites in
production and it works perfectly. :)
-Filip
zack1403 skrev:
Using T5 Components. I was able to get rid of the error when I renamed my
classes back to what they were. I.e: pages.project.ProjectAdd went back to
pages.project
When I renamed my classes the package length didn't throw an oom error. Is
working right now with the same package depth as when it was throwing an
error. Right now I am using:
-vmargs -Xmx1g -XX:PermSize=256M -XX:MaxPermSize=512M
Zack
Sven Homburg wrote:
>
> your package depth is too deep
Using T5 Components. I was able to get rid of the error when I renamed my
classes back to what they were. I.e: pages.project.ProjectAdd went back to
pages.project.Add etc. I know the feature is pretty new, maybe a bug?
Zack
Hi Zack.
By chance are you using any 3rd party component libs?
c
your package depth is too deep
every package URL (not only the classes and files ) are stored by tapestry
in an internal queue
if there are too many packages, java throws an oom excpetion.
try to start your servlet container with more heap memory (eg. -Xms512m)
2008/4/21, Chris Lewis <[EMAIL PROT
Hi Zack.
By chance are you using any 3rd party component libs?
chris
zack1403 wrote:
> I have a very basic project with a few pages just doing basic crud stuff. My
> Tomcat6 (SDK 1.6) server is running just this one tapestry project with
> nothing running of my own during startup. I get this s
