Comments for Jeroen's blog

Comment on Ajaxifying a Grails Webflow by Manoj singh

Manoj singh — Tue, 28 Feb 2012 12:57:16 +0000

Eric,

I am struggling with the same problem as yours .. can you please re-post the changes you made to the _ajaxflow.gsp.

Thanks
Manoj

Comment on Ajaxifying a Grails Webflow by Manoj Singh

Manoj Singh — Mon, 27 Feb 2012 13:02:00 +0000

Hi Eric,

I am also struggling with submitting request params with the … can you please again paste the example you mention in this post .. it seems it didn’t show up.

Thanks
Manoj

Comment on Creating dependent selects in Grails by Jeroen

Jeroen — Wed, 15 Feb 2012 12:14:59 +0000

Hi Eduardo,

Instead, try: Category.findById(params.id)

Cheers, Jeroen

Comment on Creating dependent selects in Grails by eduardo

eduardo — Tue, 14 Feb 2012 20:39:55 +0000

I’ve got the following error while running my code with this example

in this line :
def category = Category.get(params.id)

Error 2012-02-14 18:28:02,513 ["http-bio-8080"-exec-5] ERROR errors.GrailsExceptionResolver – MissingMethodException occurred when processing request: [POST] /Intranet/redirectSummary/ajaxGetProviderByCategory – parameters:
id: 4
No signature of method: static groovy.lang.Category.get() is applicable for argument types: (java.lang.Integer) values: [4]
Possible solutions: grep(), getAt(java.lang.String), grep(java.lang.Object), wait(), any(), wait(long). Stacktrace follows:
Message: No signature of method: static groovy.lang.Category.get() is applicable for argument types: (java.lang.Integer) values: [4]
Possible solutions: grep(), getAt(java.lang.String), grep(java.lang.Object), wait(), any(), wait(long)

Comment on Lampen by Jeroen

Jeroen — Wed, 01 Feb 2012 15:07:59 +0000

Ik heb er nog geen nee. € 1200,- is ook wel een beetje aan de prijs, maar goed: blijft een mooie lamp

Comment on Lampen by jeroen

jeroen — Sun, 29 Jan 2012 11:55:57 +0000

Hier:
http://www.hilldesign.nl/winkel/winkel/hanglampen.html

Zie lamp ‘cup’

Kleinste versie is wel 1200 euro

Comment on Lampen by jeroen

jeroen — Sun, 29 Jan 2012 11:46:37 +0000

Heb je misschien al een kleinere versie gevonden? Ik ben er ook naar op zoek.

Comment on Ajaxifying a Grails Webflow by Jeroen

Jeroen — Thu, 12 Jan 2012 12:41:18 +0000

Hi Eric,

Sorry for not noticing your posts sooner than just now. Unfortunately my cable provider blocks smtp, so my blog is unable to send out notification emails when someone posts comments Perhaps I should move the blog out of my meter box onto an external server

But I see you already found the solution to your question? So, if I understand correctly you are using a flow to edit the properties of one particular domain object?

It’s indeed possible to add the id to the hidden field in the form specification, however as this id is being used throughout the whole web flow / wizard, I would probably store it in the flow scope instead of passing it along every time in a hidden post variable.

The flow scope is available throughout the lifetime of the web flow. So I would probably either store the id in the flowscope, or instantiate the domain object by id and store that in the flowscope so you can use and modify that object throughout the web flow.

I hope this answer is of help? Let me know if you got things working

Cheers, Jeroen

Comment on Ajaxifying a Grails Webflow by Eric

Eric — Thu, 12 Jan 2012 00:23:18 +0000

After a short while of digging into the plugin code I realized my problem is account for it the design and very easy to accomplish. My original _ajaxflow.gsp, as generated from the example wizard flow, was:

You can pass additional form parameters to the initial webflow by adding hidden input parameters within the body of your af:flow element. The example that worked for me is:

Excellent work Jeroen!

Comment on Ajaxifying a Grails Webflow by Eric

Eric — Wed, 11 Jan 2012 20:59:08 +0000

On the other hand, the information in http://grails.1312388.n4.nabble.com/how-to-pass-an-id-to-ajaxFlow-td3220999.html appears to center on the use of the ajaxButton tag. My particular requirements mandate that I pass the id on the initial ajaxified-webflow such as from the initial triggerEvent.

Am I on the right track? Is this currently supported, is there some work around, or would this be considered a future enhancement?