Re: 4.1.1 (or 4.1.2) Dojo Dialog escaping pageBeginRender

Jesse, It is my own application code that I want to avoid. The ResponseBuilder solution works great. Thanks. Jesse Kuhnert wrote: You can inject the ResponseBuilder service and call ResponseBuilder.isDynamic() to avoid doing things you don't want to have happen in one vs. another instance.

Re: 4.1.1 upgrade to 4.1.2 async listener no longer works

Thanks for the jira issue. Sorry I've been really busy trying to get some normal contact stuff completed. On 7/4/07, Paul Stanton <[EMAIL PROTECTED]> wrote: I've figured out why the exception is being thrown: my formSubmit method requires the submission control (Submit or LinkSubmit) to have s

Re: 4.1.1 (or 4.1.2) Dojo Dialog escaping pageBeginRender

You can inject the ResponseBuilder service and call ResponseBuilder.isDynamic() to avoid doing things you don't want to have happen in one vs. another instance. To be clear, ~everything~ that happens in a dynamic request should be the same as what happens in a normal request. (except maybe for js

Re: 4.1.1 Session issue

great :) On 7/5/07, Paolo Scopa <[EMAIL PROTECTED]> wrote: Ok, I eventually did it. I mached your solution with the post in http://www.nabble.com/How-to-inject-ASO-in-service--tf1518378.html#a4141166 and it works fine Thanks a lot Paolo Paolo Scopa wrote: > > Thanks for replying, > I trie

Re: 4.1.1 Session issue

Ok, I eventually did it. I mached your solution with the post in http://www.nabble.com/How-to-inject-ASO-in-service--tf1518378.html#a4141166 and it works fine Thanks a lot Paolo Paolo Scopa wrote: > > Thanks for replying, > I tried my best to understand what i should do, but im afraid i cant

Re: 4.1.1 Session issue

Thanks for replying, I tried my best to understand what i should do, but im afraid i cant follow you. I never used ApplicationStateManager directly and i dont know where to find an example. Also i don't know where the lines you posted should be added. What i started from is something like

Re: 4.1.1 Session issue

Hi, you can inject the ApplicationStateManager in your DAO and access your ASO by using it. http://tapestry.apache.org/tapestry4.1/apidocs/org/apache/tapestry/engine/state/ApplicationStateManager.html http://tapestry.apache.org/tapestry4.1/tapestry-framework/hivedoc/service/tapestry.state.Applic

Re: 4.1.1 upgrade to 4.1.2 async listener no longer works

I've figured out why the exception is being thrown: my formSubmit method requires the submission control (Submit or LinkSubmit) to have set the tag and selected attributes/parameters. Now, my async button comes in without those set and the null pointer is thrown. So I've added an "if null retu

Re: 4.1.1 Dialog disappears without request

Turns out this is fixed in 4.1.2. I had to do some funky stuff to get 4.1.2 working and it's not 100% yet, but I can't reproduce this particular issue in 4.1.2. So thanks for the suggestion, it did help me figure out another problem ;) Igor Drobiazko wrote: Hi Paul, just guessing: the might

Re: 4.1.1 Dialog disappears without request

Hi Paul, just guessing: the might be some bug in @EventListener You could try to replace your Buttons by Submit and call your listener methods via action parameter: Why do you prefer the combination of buttons + @EventListener? Your listener methods is triggered by clicking on a button, so you

Re: 4.1.1 (or 4.1.2) Dojo Dialog escaping pageBeginRender

Thanks Renat, unfortunately the dialog needs to be initialised programmatically .. I need to dynamically stuff an object into it. I might be able to use JS for the close operation though. Renat Zubairov wrote: Hi You can show or hide dialog not from the Tapestry (read server-side) but directl

Re: 4.1.1 (or 4.1.2) Dojo Dialog escaping pageBeginRender

Hi You can show or hide dialog not from the Tapestry (read server-side) but directly with Javascript. It's pretty simple, you just need to call method "show" or "hide" on the DoJo dialog: function closeDialog() { dojo.widget.byId('DialogContent').hide(); } Renat On 04/07/07, Pau

Re: 4.1.1 upgrade to 4.1.2 async listener no longer works

Should I log this in Jira Jesse? Paul Stanton wrote: Thanks Jesse, I've changed it to @EventListener(targets = {"myButton"}, events = "onclick", async = true, autoSubmit = false) public void showMyDialog() and the same exception is thrown. Any more info? Paul. Jesse Kuhnert wrote: Co

Re: 4.1.1 upgrade to 4.1.2 async listener no longer works

Thanks Jesse, I've changed it to @EventListener(targets = {"myButton"}, events = "onclick", async = true, autoSubmit = false) public void showMyDialog() and the same exception is thrown. Any more info? Paul. Jesse Kuhnert wrote: Components implementing IFormComponent that are targeted

Re: 4.1.1 upgrade to 4.1.2 async listener no longer works

Components implementing IFormComponent that are targeted with an @EventListener do now have their surrounding forms submitted automatically as part of the async request. If there is something in your logic that doesn't need/want this to happen you can set the autoSubmit = false parameter in the a

RE: 4.1.1

Great Scott, that fixed it! Thank you very very much Justin! > -Original Message- > From: Justin Walsh [mailto:[EMAIL PROTECTED] > Sent: Monday, March 12, 2007 2:29 PM > To: Tapestry users > Subject: Re: 4.1.1 > > Put the backport-util-concurrent jar (for jdk 5)

Re: 4.1.1

ge- >> From: Justin Walsh [mailto:[EMAIL PROTECTED] >> Sent: Monday, March 12, 2007 2:06 PM >> To: Tapestry users >> Subject: Re: 4.1.1 >> >> What version of the jdk are you using? >> >> Damian Sobieralski wrote: >> >>> Correc

RE: 4.1.1

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03) > -Original Message- > From: Justin Walsh [mailto:[EMAIL PROTECTED] > Sent: Monday, March 12, 2007 2:06 PM > To: Tapestry users > Subject: Re: 4.1.1 > > What version of the jdk are you using? &g

Re: 4.1.1

What version of the jdk are you using? Damian Sobieralski wrote: > Correction - I WAS running successfully 4.0.1 from the Maven2 repo (not > 4.0.2 like I was saying). > > >> -Original Message- >> From: Damian Sobieralski >> Sent: Monday, March 12, 2007 1:12 PM >> To: 'Tapestry users' >>

RE: 4.1.1

Correction - I WAS running successfully 4.0.1 from the Maven2 repo (not 4.0.2 like I was saying). > -Original Message- > From: Damian Sobieralski > Sent: Monday, March 12, 2007 1:12 PM > To: 'Tapestry users' > Subject: 4.1.1 > > I'm hoping someone can assist me. Okay, I'm doing more than

Re: [4.1.1] ajax update problem

May be the returned XML is not correct - not well formed or not valid. Check it with any available HTTP request tracer. I know there is one for IE, for firefox there are quite some also. Renat On 19/11/06, Norbert Sándor <[EMAIL PROTECTED]> wrote: In IE I get the given message in the dojo conso

Re: [4.1.1] ajax update problem

In IE I get the given message in the dojo console, and the page is not updated. In FF, I get no error (neither on the dojo or the javascript console) but the page is not updated. It seems that I have to debug the javascript code, where should I start? Thanks: Norbi Jesse Kuhnert írta: If you

Re: [4.1.1] ajax update problem

If you have "FireBug" installed on firefox you should be able to click on any of those [foo] objects to see the complete contents of the objects they represent. On 11/19/06, Sándor Norbert <[EMAIL PROTECTED]> wrote: Hello, Clicking on an async DirectLink the following message is displayed: ER

Re: 4.1.1 performance issues

It's an IE bug. I've filed a JIRA issue with a workaround to fix this..I'll probably do it in the next snapshot build. https://issues.apache.org/jira/browse/TAPESTRY-1115 On 10/11/06, Christian Dutaret <[EMAIL PROTECTED]> wrote: Hi all, I am facing some performance issues with my application