Re: escape single quote character in parameter

2014-09-15 Thread Chung Khanh Duy
Hi, I think you can escape in Java code and pass value into javascript function params. We have common-lang library to support that. Thanks. On Tue, Sep 16, 2014 at 1:21 PM, Макаров Роман wrote: > How do I escape single quote character in parameter? > I.e. I need something like this ${someFunc

escape single quote character in parameter

2014-09-15 Thread Макаров Роман
How do I escape single quote character in parameter? I.e. I need something like this ${someFunction('\'')}.

Re: Are component parameters shared between sessions?

2014-09-15 Thread Robert Zeigler
No, something else is going on here. @Persist should be specific to the user session by default. Without seeing more of your page and component class code, I can't offer any conjectures. But I've used @Persistany times with no user-bleed over so something else is definitely going on here. Robe

JavaScript and RequireJS

2014-09-15 Thread sshaikh1970
I have the following script in my .tml page $.support.cors = true; $("#refBtn").click(function(){ var myurl = buildURL("${getLegacyUser()}", "${getLegacyCompany()}", "${getLegacyTranId()}") alert(myurl); $.ajax({ url : myurl, type : "GET", success: function(responseData, te

Are component parameters shared between sessions?

2014-09-15 Thread Boris Horvat
Hi all, I have a question and a problem that I was unable to find in tapestry documentation. I have a page that has a filter component. This components basically accepts a filter and then displays is properties. A user can modify those properties and when it presses a button this value is set bac

Re: Tapestry onActivate messes up after submitting a form

2014-09-15 Thread Boris Horvat
Sure I will answer them. Thanks for help in identifying this On Mon, Sep 15, 2014 at 10:18 AM, Lance Java wrote: > I've created an issue here: > https://github.com/uklance/tapestry-cometd/issues/62 > > Not sure of an eta yet. You could help by answering the questions in the > issue. > On 14 Sep

RE: other components inside Dynamic component?

2014-09-15 Thread Lance Java
No, the field is still a Per-Thread value. It will be null for the next request. You've just made it so that the field will be calculated at most once per request. On 15 Sep 2014 14:42, "Макаров Роман" wrote: > Changed to this. Is it ok now? > > ... >private DynamicTemplate dynamicTemplate;

RE: other components inside Dynamic component?

2014-09-15 Thread Макаров Роман
Changed to this. Is it ok now? ... private DynamicTemplate dynamicTemplate; public String getLastModificationDate() { return partnerCodeService.getLastModificationDate().toString(); } @Cached(watch = "LastModificationDate") public DynamicTemplate getDynamicTemplate() {

RE: other components inside Dynamic component?

2014-09-15 Thread Lance Java
I doubt that'll do anything since the field is a per thread value. I meant to add an appropriate hashCode() an equals() method to StringResource. Or perhaps override the DynamicTemplateParser service with a non caching version.

RE: other components inside Dynamic component?

2014-09-15 Thread Макаров Роман
So, if DynamicTemplateParser has a cache by Resource, how is it identifying the resource? Or, just how to avoid the problem? By the way, now my code looks as following, but not sure it changes the cache behavior: public class TrackerDynamic extends Tracker { private DynamicTemplate dynami

Re: other components inside Dynamic component?

2014-09-15 Thread Lance Java
Not sure how to fix your issue but I spot another issue. DynamicTemplateParser has a cache by Resource. It looks like you add to the cache for every render. It's only a question of time before you hit out of memory errors. On 15 Sep 2014 06:32, "Макаров Роман" wrote: > Hi all, > > I have a quest

Re: Tapestry onActivate messes up after submitting a form

2014-09-15 Thread Lance Java
I've created an issue here: https://github.com/uklance/tapestry-cometd/issues/62 Not sure of an eta yet. You could help by answering the questions in the issue. On 14 Sep 2014 23:27, "Boris Horvat" wrote: > Brilliant at least we figured out the issue here :) > > Any eta on the fix? I would be h