Hi Geert, I can see what you mean, absolute paths are fine, as long as there is a possiblility to generate correct urls without to much fuss...;-)
Regards, Edwin 2007/1/3, Geert Bevin <[EMAIL PROTECTED]>:
Hi Edwin, (note, RIFE really generates absolute paths, not absolute URLs since the protocol and the domain name are not included) I think that generating relative paths would actually create more problems and be more confusing. It doesn't mean that absolute paths will not be needed anymore. For example, you should use still be able to easily generate absolute URLs inside REST responses, emails, ... This means that there has to also be a second set of methods to obtain relative paths as opposed to the current absolute ones (getSubmissionQueryUrlRelative or so) and you'll have to still introduce that configuration parameter to have the absolute URLs being generated correctly. I think it's much clearer to generate them with just one approach, ie. absolute paths. Geert On 03 Jan 2007, at 12:46, Edwin Mol wrote: > Hi Geert, > > This would certainly solve my problem, but I think it would be more > appropriate for rife to generate relative urls without the servlet > rootcontext and without > a leading "/". > I think it will than work in all circumstances as long as the base > url is correct(standard servlet context URL or overridden by the > PROXY_ROOTURL parameter). > I think there is no need for the application to be aware of the > servlet context it runs in. > > What do you think? > > Edwin > > 2007/1/3, Geert Bevin <[EMAIL PROTECTED]>:Hi Edwin, > > I see, I misunderstood your problem. There isn't currently anything > in RIFE that does this. > > Would having a PROXY_WEBAPP_CONTEXT configuration parameter do what > you want? Instead of going to the servlet context to obtain the real > path of the web application root URL, it would use the value of this > parameter. You can then set that to an empty string. > > Best regards, > > Geert > > On 03 Jan 2007, at 11:38, Edwin Mol wrote: > > > Hi Geert, > > > > Thanks, but this only solves part of my problem, it does replace > > the WEBAPP:ROOTURL with the value from PROXY_ROOTURL, but the > > form's action url still contains the context root from the servlet > > container, so the servlet container recieves a request to /myapp/ > > myapp/... instead of > > just: /myapp/.... > > > > Regards, > > > > Edwin > > > > > > 2007/1/3, Geert Bevin < [EMAIL PROTECTED]>: Hi Edwin, > > > > I think you can set the PROXY_ROOTURL configuration parameter for > > that. > > > > Hope this helps. > > > > Geert > > > > On 03 Jan 2007, at 11:03, Edwin Mol wrote: > > > > > Hi All, > > > > > > I have a rife application running in a tomcat container behind an > > > apache web server. > > > The applications runs in a specific context for example "/myapp" > > > The public url has no context root, so I have to replace all > > > FORM:SUBMISSION:name values > > > with the correct values otherwise they point to the wrong > location, > > > is there a way to do this in a generic way? > > > I've looked at the Template.getFilteredValues(String filter) > > > method, but I don't succeed in extracting the FORM:SUBMISSION:name > > > values. > > > > > > Any help will be much appreciated. > > > > > > Regards, > > > > > > Edwin -- Geert Bevin Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Music and words - http://gbevin.com _______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
_______________________________________________ Rife-users mailing list [email protected] http://lists.uwyn.com/mailman/listinfo/rife-users
