Bug 1015040 - Cannot set date (deadline expression) in Wait and OnAlarm
Summary: Cannot set date (deadline expression) in Wait and OnAlarm
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: BPEL editor
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 6.1.0
Assignee: Robert (Bob) Brodt
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-03 11:14 UTC by Andrej Podhradsky
Modified: 2016-01-06 12:00 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Users cannot set dates in OnAlarm (Pick) and Wait in the BPEL Editor. This affects both the Date and Duration radio button options.
Clone Of:
Environment:
Last Closed: 2016-01-06 12:00:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Eclipse Project 404117 0 None None None Never

Description Andrej Podhradsky 2013-10-03 11:14:19 UTC 
Description of problem:
It doesn't matter which radio bution (Date or Duration) you select there is still <for> (duration) in bpel process. This is in OnAlarm (Pick) and Wait.

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


How reproducible:
always

Steps to reproduce:
1. Add a Wait activity (or Pick with OnAlarm)
2. In Properties view select Details
3. Try to specify a deadline by choosing Date radio button
4. Save and open the bpel process in a text editor. You will see that there is still <for> tag

Actual results:


Expected results:


Additional info:
Comment 1 Robert (Bob) Brodt 2014-08-08 20:57:39 UTC 
Fixed in version 1.0.4
Paul will make this build available in the next JBTIS stack.
Comment 2 Andrej Podhradsky 2015-03-04 12:02:50 UTC 
Verified with BPEL tooling 1.0.4 which is included in
* JBDS 7.1.1.GA + JBDS-IS 7.1.0.CR1
* JBDS 8.0.2.GA + JBDS-IS 8.0.0.GA
Comment 3 Andrej Podhradsky 2016-01-06 12:00:47 UTC 
Fixed and included in the latest release.
Note You need to log in before you can comment on or make changes to this bug.