From: Aplaws D. L. <apl...@li...> - 2009-05-22 08:12:05
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=7404141 By: pboy Hi Terry, I suppose your patch will break a lot of modifications I made to the java code. The rationale of milestone (1) is that all references to files, resources and anything else in APLAWS is strictly made relative to document root rsp. the web application context All modifications / configurations regarding the servlet container and where to install APLAWS (in which context) are the responsibility of the container / the container administrator / the container's webapp installation tool. Nothing at all that APLAWS should care about. In some situations we need the full file system path to a file or resource (esp. during installation / initial configuration and while using the test machinery I suppose), and we need the path to the APLAWS web context. That is ccm.home in the logik of milestone (1). Currently ccm.home is fixed ${app.server.webapp.dir}/ROOT. As soon as I've finished the work on the URL resource: protocol (I suppose I will provide a patch today in the evening) I will start to make APLAWS installable in any arbitrary directory, specified in project.xml webapp tag or during installation time. This involves a massive rewriting of xsl files and a lot of work in web.xml and the dispatcher magic and may take some time. So ccm.home will become: ${app.server.webapp.dir}/${ccm:project.webapp} See milestone (1) and related tickets for details. Well, I suppose I should start to write a new developer guide as soon as possible. In which situations do we need ccm.home pointing to the servlet containers home dir? Peter ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=368401 |