AW: Problem sending data from a JS Element back to Tapestry

2016-07-21 Thread Jochimsen, Janko
Hi Chris, Thank you very much. I solve the problem for me and your advice definitely pointed me into the right direction. For everyone following this I may add that we seem to work in different environments. I tried your (function(){ define(["jquery", "t5/core/ajax", "t5/core/utils",

Re: Problem sending data from a JS Element back to Tapestry

2016-07-21 Thread Chris Poulsen
Hi, Utils and ajax are injected using requirejs, the top of the module file looks like this... (function(){ define(["jquery", "t5/core/ajax", "t5/core/utils", "components/editor/inline-toolbar" ], function ($, ajax, utils, toolbar) { On Thu, Jul 21, 2016 at 10:42 PM, Jochimsen,

AW: Problem sending data from a JS Element back to Tapestry

2016-07-21 Thread Jochimsen, Janko
Hi Chris, thanks for your sift answer I think this is the right direction. I am just stuck with a very – probably stupid – problem. I included all relevant paths that I can think of with: define([ "jquery", "t5/core/dom", "t5/core/ajax", "t5/core/utils" ] the function looks like this: var

Re: Problem sending data from a JS Element back to Tapestry

2016-07-21 Thread Chris Poulsen
you cannot expect that your parameters end up as event context (unless you encode them into your url in that way). I've had success using: var url = buildUrl( setupDialogLink, params ); ajax( url, { success: function(){ ... } }); var buildUrl = function( link, params ) { return

Problem sending data from a JS Element back to Tapestry

2016-07-21 Thread Jochimsen, Janko
Hello Everybody, I do have a problem with the communication between tapestry and java Script or to be more precise a JQuery Script. As a background Information I am using JQPlot Graphs that work quiet good and I can start them from tapestry without problems. Now I would like to increase the

TLS termination proxy and Tapestry

2016-07-21 Thread Svein-Erik Løken
Using HAProxy or Apache HTTP Server as a TLS termination proxy I found that setting X-Forwarded-Proto="https" in the header on the proxy org.apache.tapestry5.services.Request::isSecure returns true . That's good! In tapestry.production-mode=true I am getting absolute URLs. E.g.