I hunted through the code myself for this. As it turns out, Magnolia does not hard code the use of magnoliaAuthor or magnoliaPublic for composing links. They make standard Servlet 2.4 API calls to get the context name and other info for composing urls and links. And that may be the issue you're running into. The urls generated aren't relative. Most are absolute (ie http://my.server.com/myContext/myPage.html).
--David Michael Aemisegger wrote: > anthony rogers wrote: > >> Well yes it seems u will be in for some pain. Tomcat5 and Apache2 is a >> nightmare and I am surprised there isn't a 'how to get it working nice' >> paper online- all the docs seem to gloss over the topic... I have it >> sort of >> working but the /magnoliaPublic/ is still in the URL so I guess its >> really >> doesn't work and I have no idea if it's an Apache thing or a >> Tomcat/Magnolia >> thing... > > > So, there must be some configuration parameter somewhere still set to > '/magnoliaPublic' ( web.xml, magnolia config repository, httpd.conf or > similar). > > Or maybe a caching issue? > > -- > Cheers > Michael > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- -- ======================================= David Smith Network Operations Supervisor Department of Entomology College of Agriculture & Life Sciences Cornell University 2132 Comstock Hall Ithaca, NY 14853 Phone: 607.255.9571 Fax: 607.255.0939 ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
