Continuum

Configuration page shows en error in the form the first time is accessed

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.1-alpha-1
  • Fix Version/s: 1.1-alpha-1
  • Component/s: Web interface
  • Labels:
    None
  • Environment:
    acegi-branch
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

Now that the configuration step is back in place, when login the first time you get redirected to http://localhost:8080/continuum/configuration!input.action

That page shows "You must define a URL." for the BaseURL, seems that it's doing validation before submit. Also the css is bad and the message is missaligned

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Carlos Sanchez added a comment -

Also, when saving the config "Company URL" is printed correctly, but after coming back to the config page it's empty, seems it's not saved as the top right log does not have a link

Show
Carlos Sanchez added a comment - Also, when saving the config "Company URL" is printed correctly, but after coming back to the config page it's empty, seems it's not saved as the top right log does not have a link
Hide
Permalink
Nap Ramirez added a comment -

Is it ok to just use a default value for the baseUrl to avoid the validation errors before submitting the configuration?

Btw, in the branch, the companyUrl can now be saved.

Show
Nap Ramirez added a comment - Is it ok to just use a default value for the baseUrl to avoid the validation errors before submitting the configuration? Btw, in the branch, the companyUrl can now be saved.
Hide
Permalink
Nap Ramirez added a comment -

Dropped the idea of having the default value for baseUrl.

The validation-before-submit error is now fixed in the branch. As suspected, this undesired behavior was due to the lacking configuration in some interceptors overridden in xwork.xml.

The reason why validation occurs even before submit (as opposed to the default behavior) is because the validation & workflow interceptors were overridden with empty configuration (excluded methods). Reference: http://forums.opensymphony.com/thread.jspa?messageID=27367&#27367

Is there any reason for having a custom interceptor stack aside from the exception logging? If not, maybe we can reuse the defaultStack beside the defaultContinuumStack.

Just a thought...

Show
Nap Ramirez added a comment - Dropped the idea of having the default value for baseUrl. The validation-before-submit error is now fixed in the branch. As suspected, this undesired behavior was due to the lacking configuration in some interceptors overridden in xwork.xml. The reason why validation occurs even before submit (as opposed to the default behavior) is because the validation & workflow interceptors were overridden with empty configuration (excluded methods). Reference: http://forums.opensymphony.com/thread.jspa?messageID=27367&#27367 Is there any reason for having a custom interceptor stack aside from the exception logging? If not, maybe we can reuse the defaultStack beside the defaultContinuumStack. Just a thought...

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.