Guys, Im having a really strange problem with the context handling in an app im writing. Essentially, the app is pretty "normal", it goes about its business perfectly well. However, as this will be distributed through different parts of our company, and could be deployed in different contexts, I need a way of handling this. Our usual setup for apps is to have them running as the root context on their own port and then to manage app URIs through a front end proxy (yes, there are pros and cons here, but it is what it is!)
For example, I want to deploy the app to: /mypath/<appurls> whilst the guys in the USA might want to put it at: /another/path/<appurls> This is pretty problematic, as lift doesnt know about this and tries to submit forms from the / context and also references liftAjax.js from the root context too. I've had a play with LiftRules.calculateContextPath but it doesn't appear to do what I want, or im not understand how it should work. Any ideas? Cheers, Tim -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
