Re: 5.4-beta-27 rendered unbalanced elements

2015-02-11 Thread Sven Homburg
hey george, yesterday, jochen commits a fix for that problem 2015-02-11 5:44 GMT+01:00 George Christman : > Hi, I just tried upgrading from 5.4-beta-27 and started receiving the > following exception all over my app. > > *Component vehicles/Index:gridlisting.if_5 has rendered unbalanced > elemen

Re: 5.4-beta-27 rendered unbalanced elements

2015-02-11 Thread Thiago H de Paula Figueiredo
On Wed, 11 Feb 2015 11:44:06 -0200, George Christman wrote: great thanks. I'm assuming we'll see this fix released in beta-28? Yes! On Wed, Feb 11, 2015 at 6:34 AM, Bob Harner wrote: This sounds like the bug Jochen just fixed yesterday... https://issues.apache.org/jira/browse/TAP5-24

Re: 5.4-beta-27 rendered unbalanced elements

2015-02-11 Thread George Christman
great thanks. I'm assuming we'll see this fix released in beta-28? On Wed, Feb 11, 2015 at 6:34 AM, Bob Harner wrote: > This sounds like the bug Jochen just fixed yesterday... > > https://issues.apache.org/jira/browse/TAP5-2450 > On Feb 10, 2015 11:45 PM, "George Christman" > wrote: > > > Hi, I

Re: 5.4-beta-27 rendered unbalanced elements

2015-02-11 Thread Bob Harner
This sounds like the bug Jochen just fixed yesterday... https://issues.apache.org/jira/browse/TAP5-2450 On Feb 10, 2015 11:45 PM, "George Christman" wrote: > Hi, I just tried upgrading from 5.4-beta-27 and started receiving the > following exception all over my app. > > *Component vehicles/Index

Re: Access a T5 app through both http (Tomcat) and https (Apache httpd + AJP + Tomcat)

2015-02-11 Thread Martin Nagl
Setting tapestry.secure-enabled to "false" and removing @Secure annotations solved my problem. Internal users can acces Tomcat directly via HTTP. External users can access Apache httpd via HTTPS, which handles SSL and forwards the request to Tomcat (via AJP). Works nicely now when Tapestry does no

Re: Access a T5 app through both http (Tomcat) and https (Apache httpd + AJP + Tomcat)

2015-02-11 Thread Martin Nagl
On Thu, Feb 5, 2015 at 5:01 PM, Martin Nagl wrote: > Aha, sorry for the "hardcoded" part, I can see that the number 80 is only > used to determine whether to include port in URL or not :) Will try to > provide HOSTPORT instead. > > M. > > On Thu, Feb 5, 2015 at 4:53 PM, Martin Nagl wrote: > >> I