Bug 819838 - Display appropriate error message when given xml with missing tags
Summary: Display appropriate error message when given xml with missing tags
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: aeolus-conductor
Version: 1.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
Assignee: Angus Thomas
QA Contact: Rehana
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-08 10:39 UTC by Rehana
Modified: 2013-01-25 16:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-25 16:12:10 UTC
Embargoed:


Attachments (Terms of Use)
test (5.60 KB, text/xml)
2012-05-08 10:39 UTC, Rehana
no flags Details

Description Rehana 2012-05-08 10:39:56 UTC
Created attachment 582957 [details]
test

Description of problem:


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


How reproducible:


Steps to Reproduce:
1.PFA the xml(PFA:test)
2.remove ">" of the tag "executable" (ex:<executable)
3.Provide the url from conductor
  
Actual results:
Observed that the error message '1 error prohibited this Application Blueprint from being saved
    seems to be not valid application blueprint XML: Extra content at the end of the document' is displayed

BUT 
when removed the ">" of the tag "deployable" (ex:</deployable)

error message was 
   " 1 error prohibited this Application Blueprint from being saved
    seems to be not valid application blueprint XML: expected '>' "


Expected results:
should display Appropriate error message .

Additional info:
rpm -qa | grep aeolus
aeolus-conductor-0.8.13-1.el6_2.noarch
aeolus-configure-2.5.3-1.el6.noarch
rubygem-aeolus-image-0.3.0-12.el6.noarch
rubygem-aeolus-cli-0.3.1-1.el6.noarch
aeolus-all-0.8.13-1.el6_2.noarch
aeolus-conductor-doc-0.8.13-1.el6_2.noarch
aeolus-conductor-daemons-0.8.13-1.el6_2.noarch

Comment 1 wes hayutin 2012-05-08 13:57:39 UTC
To summarize.. the webui and cli should use the same error message library


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