Deployment of datasource in a different context than root ?

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create testdas.war with datasource
2. Copy to tomcat/webapps
3. start tomcat
4. Browse to: http://localhost/testdas/das

What is the expected output? What do you see instead?

The application reports that the XSL stylesheet is not found, changinging

MydasServerConfig.xml:

<dsn-xslt-url>/xslt/dsn.xsl</dsn-xslt-url>

to

<dsn-xslt-url>xslt/dsn.xsl</dsn-xslt-url>

results in finding the stylesheet, but

http://localhost/testdas/das/dsn

results in the error above.

What version of the product are you using? On what operating system?

V 1.0.2 on Linux, JDK 1.5

Please provide any additional information below.

Original issue reported on code.google.com by we...@web.de on 30 Nov 2007 at 11:41

[GoogleCodeExporter]

Hi,

So, you certainly can deploy a MyDas app to a context other than the root by
deploying using an application context xml file, via the Tomcat manager 
application.
 The problem you have identified with the path to the xslt is a real problem however
and I intend to solve this for version 1.0.3 that I will be releasing soon.

The work-around is to modify the value for <dsn-xslt-url/> (and the other xslt 
paths
as available) to absolute URLs for the location of the xslt, for example:

http://www.yourdomain.com/deployed/path/xslt/dsn.xsl

Hope this helps.  (Reading between the lines, you are clearly familiar with 
Tomcat,
however just in case, you may like to consult
http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html)

Best regards,

Phil.

PS - I am not going to mark this case closed for the moment, until I have fixed 
the
ability to give relative urls in any context.

Original comment by philip.j...@gmail.com on 1 Dec 2007 at 1:32

[GoogleCodeExporter]

Changing status to accepted

Original comment by philip.j...@gmail.com on 1 Dec 2007 at 1:34

• Changed state: Accepted