Re: removing :xxxx port requirement in URL [update]

[BuildSmart <bu...@daleenterprise.com>]

I was beginning to be happy with the results of my work and was  
enjoying the ability to have apache serve the .jsp files from any of  
it's virtualhost document roots  and not the Tomcat docroot and only  
having one Tomcat virtualhost defined allowed me to design an admin  
interface on the defined Tomcat port.

I was thinking it was time to start planning out a release package  
when I decided to try using Tomcat 5 instead of Tomcat 4 (which is  
vendor supplied) and I'm disappointed to find out that the changes in  
the class files have combined the docroot, work and scratch dir  
variable initialization so changing docroot dynamically on the fly  
doesn't work cause it then complains about no WEB-INF and no work dir  
and exits with a 500 error msg.

I thought to be safe I'd try Tomcat 6 (forced me to use JSDK 1.5) and  
it exhibits the same issue.

It looks like my current solution only works with Tomcat 4.1 (I  
didn't try anything older).

I'm wondering how to resolve this, I doubt they'd make changes in the  
source to allow the ability to modify the docroot without affecting  
other directory designations because I need it for my module.

Maybe using Tomcat was a poor choice based on the current available  
config state or maybe there is another method in the newer Tomcat's  
to achieve the  docroot change without disrupting the others or maybe  
I should consider dropping it as a possible method of implementation?


-- Dale

Re: removing :xxxx port requirement in URL [update]

[Christopher Schultz <ch...@christopherschultz.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dale,

BuildSmart wrote:
> It looks like my current solution only works with Tomcat 4.1 (I didn't
> try anything older).
> 
> I'm wondering how to resolve this, I doubt they'd make changes in the
> source to allow the ability to modify the docroot without affecting
> other directory designations because I need it for my module.

Maybe they would. Feel free to start another thread (I don't think
anyone else is reading this one anymore) asking that question (maybe
even on the dev list instead of the user list). Another option is to
file a bug report (enhancement request) that asks for a way to do what
you need to do.

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHH0pC9CaO5/Lv0PARAgiUAJ9bHq8a1ZBtl6a18c1c8gdqPTCxUACfXuZd
l+jKiGw06W40nmBkw7Ekvnw=
=sJB4
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org