You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by is...@cocoondev.org on 2004/04/26 23:13:19 UTC

[issues] Updated: (FOR-133) Cocoon.xconf is misconfigured in WAR

The following issue has been updated:

    Updater: Juan Jose Pablos (mailto:cheche@che-che.com)
       Date: Mon, 26 Apr 2004 11:13 PM
    Comment:
Target to be fixed on that release
    Changes:
[Fix For] set to [0.6]

---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-133&page=history

---------------------------------------------------------------------
View the issue:

  http://issues.cocoondev.org/jira//secure/ViewIssue.jspa?key=FOR-133


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-133
    Summary: Cocoon.xconf is misconfigured in WAR
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Forrest
  Component: Building Forrest
    Fix For: 0.6
   Versions:
             HEAD

   Assignee: 
   Reporter: Sjur N. Moshagen

    Created: Tue, 20 Apr 2004 3:36 PM
    Updated: Mon, 26 Apr 2004 11:13 PM
Environment: MacOS X 10.2.8, latest forrest

Description:
When building a war file, the generated WEB-INF/cocoon.xconf file contains absolute paths to the resources, content, catalogs etc of the webapp as found on the development computer. This brakes the war when installed in a servlet container. Manually editing cocoon.xconf after installing the war fixes the issue.

[While I wrote this bug report, nicolaken wrote an UPDATE about what looks like the same issue. But since I could not find a bug report covering it, I found it better to file the report as not to forget to test against it later on.]


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org/jira//Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira