Continuum

General Configuration should be pre-configurable in XML

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1-alpha-1
  • Fix Version/s: 1.2
  • Component/s: Core system
  • Labels:
    None
  • Environment:
    1.1-alpha-1, WinXP
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

It should be possible to pre-configure the items on the General Configuration screen:

  • Working Directory
  • Build Output Directory
  • Deployment Repository Directory:
  • Base URL

Issue Links

is depended upon by

Bug - A problem which impairs or prevents the functions of the product. CONTINUUM-1489 replace use of MungedHttpsURL with apache httpclient (4.0-beta1)

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Wendy Smoak added a comment -

Most likely, this means being able to pre-configure these values in conf/continuum.xml prior to starting the app for the first time.

Show
Wendy Smoak added a comment - Most likely, this means being able to pre-configure these values in conf/continuum.xml prior to starting the app for the first time.
Hide
Permalink
Olivier Lamy added a comment -

looks to be fixed with rev 678639. (I have tested it with success).
Emmanuel do you confirm ?

Show
Olivier Lamy added a comment - looks to be fixed with rev 678639. (I have tested it with success). Emmanuel do you confirm ?
Hide
Permalink
Emmanuel Venisse added a comment -

Done.

Show
Emmanuel Venisse added a comment - Done.
Hide
Permalink
Olivier Lamy added a comment -

I prefer to use modello for configuration instead of commons-configuration.
Which is IMHO more simple to use and the xml file format will be auto documented.
Related thread : http://www.nabble.com/Concerning-continuum-configuration-(commons-configuration-or-modello--)-td19170328.html

Show
Olivier Lamy added a comment - I prefer to use modello for configuration instead of commons-configuration. Which is IMHO more simple to use and the xml file format will be auto documented. Related thread : http://www.nabble.com/Concerning-continuum-configuration-(commons-configuration-or-modello--)-td19170328.html
Hide
Permalink
Olivier Lamy added a comment -

switch to modello in trunk rev 690494.
Leave issue open until configuring xdoc/xsd generation is done.

Show
Olivier Lamy added a comment - switch to modello in trunk rev 690494. Leave issue open until configuring xdoc/xsd generation is done.
Hide
Permalink
Olivier Lamy added a comment -

IMHO this should be merge in 1.2 branch

Show
Olivier Lamy added a comment - IMHO this should be merge in 1.2 branch
Hide
Permalink
Wendy Smoak added a comment -

I see this was merged to the 1.2.x branch, and there seems to be a problem with the Jetty bundle. In continuum.log:

2008-08-30 17:18:54,528 [WrapperSimpleAppMain] INFO org.codehaus.plexus.spring.PlexusApplicationContextDelegate - Registering Plexus to Spring XML translation
2008-08-30 17:18:57,027 [WrapperSimpleAppMain] ERROR org.apache.continuum.configuration.DefaultContinuumConfiguration - Unrecognised tag: 'configuration' (position: START_TAG seen ...missions and limitations\nunder the License.\n-->\n\n<configuration />... @21:18)

I mention it here because it's complaining about a <configuration> element.

I have not actually tried to pre-configure anything since it won't start.

(However, with mvn jetty:run in continuum-webapp, the app starts and runs.)

Show
Wendy Smoak added a comment - I see this was merged to the 1.2.x branch, and there seems to be a problem with the Jetty bundle. In continuum.log: 2008-08-30 17:18:54,528 [WrapperSimpleAppMain] INFO org.codehaus.plexus.spring.PlexusApplicationContextDelegate - Registering Plexus to Spring XML translation 2008-08-30 17:18:57,027 [WrapperSimpleAppMain] ERROR org.apache.continuum.configuration.DefaultContinuumConfiguration - Unrecognised tag: 'configuration' (position: START_TAG seen ...missions and limitations\nunder the License.\n-->\n\n<configuration />... @21:18) I mention it here because it's complaining about a <configuration> element. I have not actually tried to pre-configure anything since it won't start. (However, with mvn jetty:run in continuum-webapp, the app starts and runs.)
Hide
Permalink
Wendy Smoak added a comment -

I see the same problem with the Jetty bundle on trunk.

I tried to revert the 1252-related bits from the branch to confirm that it's really this issue, but they were merged along with changes from 1831 and I'm having trouble identifying what's what.

Olivier, can you take a look?

Show
Wendy Smoak added a comment - I see the same problem with the Jetty bundle on trunk. I tried to revert the 1252-related bits from the branch to confirm that it's really this issue, but they were merged along with changes from 1831 and I'm having trouble identifying what's what. Olivier, can you take a look?
Hide
Permalink
Olivier Lamy added a comment -

fixed in 1.2.x branch rev 690684
merge in trunk rev 690685

Show
Olivier Lamy added a comment - fixed in 1.2.x branch rev 690684 merge in trunk rev 690685
Hide
Permalink
Brent N Atkinson added a comment -

Wendy, I had the same issue (same stack trace, failed to start) when upgrading from 1.1 to 1.2.2. I found that the issue was that 1.1 had an autogenerated $

{appserver.base}

/conf/continuum.xml file and 1.2.2 was trying to parse it and failing. I removed the file and the app started just fine.

Show
Brent N Atkinson added a comment - Wendy, I had the same issue (same stack trace, failed to start) when upgrading from 1.1 to 1.2.2. I found that the issue was that 1.1 had an autogenerated $ {appserver.base} /conf/continuum.xml file and 1.2.2 was trying to parse it and failing. I removed the file and the app started just fine.

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Wendy Smoak
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: