Details
-
Type:
Task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.0
-
Fix Version/s: 1.0
-
Component/s: Configuration, Development, Documentation
-
Labels:None
Description
There are a couple of issues here:
1. Why is a sample version of rice-config.xml not included in the non-sample app distribution of the standalone server? I cannot think of a good reason to exclude it.
2. Among the currently included parameters, which are specific to KFS/IU and which are kruft?
Plan is to take the wsa131 copy of the file, put it in the web module, and use maven to filter it on a per-profile basis such that the standalone gets a generic version, the sample app gets a sample-app version and the wsa131 profile creates a flavor for the IU environment.
Attachments
Issue Links
- is related to
-
KULRICE-2934 Verify that Rice Config is as streamlined as possible and that the usage of common-config-defaults.xml is working properly
-
- Closed
-
- relates to
-
KRDOC-20 Create a list of Configuration Parameters available in Rice so that we can document them
-
- Resolved
-
Hey Casey... just had a couple notes below for your questions. I wasn't sure if you were speaking for the was131 server specifically or just speaking in general terms. In terms of the wsa131 rice-config.xml file i think it needs to be reset. The actual rice-config.xml file that needs to be set now for 1.0 can be much smaller than the file that's attached to this issue. We now use the common-config-defaults.xml file to default a lot of these. The wsa131 file should use the existing rice-config.xml template file (see the question 1 comment below) and then we should probably build it up based on some of the paramters that the wsa131 server builds specifically need.
Question 1:
I think there is a rice-config.xml sample file in the rice source code in /web/src/main/config/example-config. I believe the intention is to have it there in the source code and then in the documentation we'll be delivering with 1.0 about how to configure a standalone server and what properties can go in which files and also where Rice looks for config files external to the war file for the standalone server.
Question 2:
My assumption here is that you're talking specifically about the wsa131 server file so you might need some assistance that i can't give to figure those out. As for what's in the rice-config.xml file inside the source code of rice in the web module, there shouldn't be any KFS/IU specific pieces there. =o)