Bug 860258 - Incomplete output of TroubleTicketExample application
Incomplete output of TroubleTicketExample application
Status: NEW
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Examples (Show other bugs)
BRMS 5.3.1
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Tihomir Surdilovic
Lukáš Petrovický
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-25 08:17 EDT by jgargula
Modified: 2013-01-10 20:36 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
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 jgargula 2012-09-25 08:17:27 EDT
Description of problem:
There are three similar example applications with the name TroubleTicketExample* which should have very similar outputs but the problem is that the application with the exact name TroubleTicketExample is something like the patern of output, the second one with the name TroubleTicketExampleWithDT does not follow the rule that the colon is seperated by spaces on both sides (in case of "New" and "Done") and the last application TroubleTicketExampleWithDSL does not even show all details (for example "New ticket..." without the ticket details). And "Done" is without any additional information too.

Version-Release number of selected component (if applicable):
BRMS 5.3.1.ER1

How reproducible:
Follow next steps.

Steps to Reproduce:
1. Run runExample.sh script.
2. Click on every button with label starting by "TroubleTicketExample".
3. Compare all three outputs.
  
Actual results:
Different output.

Expected results:
Almost the same outputs, the only difference should be in order.

Additional info:
All info is in section "Description". It will be nice for users to have the same output for comparison and it will be easier to test too.

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