This content has been marked as final.
Show 3 replies
-
1. Re: Seam Remoting: How to do HTTPS on some calls
rituraj_tiwari Aug 15, 2008 9:33 PM (in response to rituraj_tiwari)Any takers?
-
2. Re: Seam Remoting: How to do HTTPS on some calls
shane.bryzak Aug 15, 2008 11:37 PM (in response to rituraj_tiwari)For the server side I recommend going the Apache/mod_jk route, in my opinion it's easier to configure.
Client side, you're possibly going to have to hack remote.js to get the kind of functionality that you're describing. What may work as a bandaid solution is setting the value of Seam.Remoting.resourcePath before each request. Say for example the default is this:
Seam.Remoting.resourcePath = "/myapp/seam/resource/remoting";
When sending a secure request, you would have to override it temporarily:
var oldPath = Seam.Remoting.resourcePath; try { Seam.Remoting.resourcePath = "https://myhost.com:443/myapp/seam/resource/remoting"; // execute remoting call here } finally { Seam.Remoting.resourcePath = oldPath; }
This is not the most elegant solution, but at least it's a starting point.
-
3. Re: Seam Remoting: How to do HTTPS on some calls
rituraj_tiwari Sep 5, 2008 10:52 PM (in response to rituraj_tiwari)Shane thanks for the tip. It turns out, however, that XmlHttpRequest sandboxig rules will not allow this to happen. I am forced to do this in a separate page or iframe.
-Raj