Bug 115809 - 404 error due to wrong web.xml
404 error due to wrong web.xml
Status: CLOSED NOTABUG
Product: Red Hat Web Application Framework
Classification: Retired
Component: installation (Show other bugs)
nightly
All Linux
medium Severity medium
: ---
: ---
Assigned To: ccm-bugs-list
Jon Orris
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-02-16 05:50 EST by Steve Etherington
Modified: 2007-04-18 13:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-02-16 05:56:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Steve Etherington 2004-02-16 05:50:28 EST
Description of problem:

When trying to view the homepage, I get this error.

404 /ccm-cdn-portal/files/ was not found on this server


Going into the root webapp and copy 'web.xml-aplaws' to 'web.xml' 
solved the problem.

Background. Installing APLAWS+ for development, using the aplaws-
standard bundle.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Daniel Berrange 2004-02-16 05:56:27 EST
In a development environment you need to provide your own custom
web.xml containing entries for the aplaws apps & any custom apps
you've written. You specifiy this using the webxml attribute on
ccm:project tag in project.xml. For example:

   webxml="web.xml-mycustom"

Alternatively, (if your app doesn't require custom entries) you can
reference one of the standard APLAWS web.xml files:

   webxml="/usr/share/ccm-tools/bundles/aplaws-standard/web.xml"
Comment 2 Steve Etherington 2004-02-16 06:01:51 EST
Is this documented or clearly referenced in the installation docs? I 
follwed the instructions step by step and ended up with a non-
functional server. :(

Note You need to log in before you can comment on or make changes to this bug.