Virtualisation Server and context path

[mark_smithson]

We have a dynamic web application which we are managing using Alfresco and have run into an isuse with the virtualisation server.

We have encoded all our urls using the JSTL c:url tag. When viewed through the virtualisation server we get a context path of $-1$site$ROOT added to urls.

I assume this context path is required by the internals of the virtualisation server. However I don't think it should be exposed to the application, as the path is incorrect for the running application. Is there any way I can get rid of this through configuration?

[jcox]

Mark,

I did a checkin today  on  the 2.1 enterprise branch that should
address this problem.   This should make its way to HEAD/community
fairly soon.

The effects of this checkin will make the virt server able to support
sessions (c.f:  JSESSIONID),  as well as make the <c.url> tag happy.

Note:  there is a bug in JSTL 1.1  that causes <c:url>
it to generate "bad" URLs for the default/ROOT webapp:

http://java.sun.com/webservices/docs/1.5/jstl/ReleaseNotes.html
     22860 tag url generate invalid result for root context

The bug in JSTL 1.1 <c:url> is that it fails to remove the name of
the default webapp ("ROOT") from the URL it creates.  However,
JSTL is not alone in problems like this so the virtualization server
automatically accepts "/ROOT" as an alias for "/").  Thus, despite
the problems with JSTL 1.1,  your URLs will work anyhow, once you
upgrade to 2.1E (or some  post-merge version of HEAD).

   I hope this helps,
   -Jon

[mark_smithson]

Thanks Jon,

I look forward to trying it out.

Mark

[sanjay]

I am still facing this problem while using the controller classes.

In case of controller class, it shows "$-1$site$ROOT" as contextPath. Hence, urls generated in controller class are having BAD urls.

I am using latest enterprise 2.1 version.

Appreciate early response.