Hi Martin
We did try setting the cache headers but it didnt work. Moreover this
application works fine when accessed directly. The problem comes only when
the application is accessed via proxy server. Thats the reason i have
suspected the URL.
We did a workaround at proxy server setting level so
Hi Felix
Even in our application which is built using Tapestry 5, we are facing the
same issue. This problem occurs when we access our app via a proxy server.
we tried setting appropriate cache-headers but still no luck. Even am
looking out for a way to change all url's to have a dynamic value but
Wow, This is the day I've waiting for.
Nice :)
Howard Lewis Ship wrote:
>
>
> - Keep backwards compatibility to Tapestry 5.2
> What I'm proposing is a gradual transition, over Tapestry 5.3 and 5.4,
> where new, documented, stable JavaScript APIs are introduced. and
> Tapestry and 3rd party lib
Thanks a lot, I will try it, I looks Tapestry's component's relationship is
build by component class rather than component template.
So, are there some dos about this?
On Sat, Mar 19, 2011 at 9:37 PM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Sat, 19 Mar 2011 01:16:21 -0300,
I've been organizing my common code into libraries and when it makes
sense hosting then at https://github.com/trsvax/
This project builds upon tapestry-aws-core which just exposes the
Amazon libraries as Tapestry services. I started using AWS when the
only service was S3.
Tapestry-aws will contai
Great News.
2011/3/18 jqzone
> That great!
>
> On Thu, Mar 17, 2011 at 8:17 AM, Howard wrote:
>
> > I've always had a love/hate relationship with JavaScript; some of the
> > earliest motivations for Tapestry was to "encapsulate that ugly
> > JavaScript stuff so I don't have to worry about it ag
