1 of 1 people found this helpful
So what ever is hosted by the professional company would be the gateway in to your web application (the url that everyone sees). Your JBoss instance would be on your server at home (web application) and this would be called by the website (the one hosted by professional hosting). Your web application would be not publicly available so you would run it with authentication against your web site.
The downside to this is that every request that needs some sort of backend processing would need to contact your JBoss server. So depending on the amount of traffic that you are expecting perhaps some sort of load balancer may be needed.
I'm not by any means a web developer nor have I done this myself so I could be completely wrong. It's just my idea
Yes, this approach makes sense. Thx.
I think I will have to verify though -
- that the hosting company can give me a 'site builder' facility that allows the gateway logic. I mean, hits against the http url by any web client will have to be translated to web services call to the host sitting in my home
- which means I have to have a way to generate a web service client (SOAP?) from my web service wsdl and embed that client in the web server hosted by the company. This client then has to trap hits against the web server http url and mediate the web service call.