Bug 1160601 - Exception in error log when editing start/end time in quartz binding
Summary: Exception in error log when editing start/end time in quartz binding
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard Editor, Tooling
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: DR4
: ---
Assignee: Brian Fitzpatrick
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-05 08:51 UTC by Andrej Podhradsky
Modified: 2016-01-06 11:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-06 11:49:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-2440 0 Minor Closed Exception in error log when editing time in quartz, atom and rss binding 2016-02-18 15:50:55 UTC

Description Andrej Podhradsky 2014-11-05 08:51:37 UTC 
Description of problem:
The following exception in error log when editing start/end time in quartz binding

Unhandled exception: Start time must match the format yyyy-MM-ddTHH:mm:ss

See the full stack trace in the attachment. Note that the start / end time is saved correctly in switchyard.xml.


Version-Release number of selected component (if applicable):
JBDS 8.0.0.GA with + JBDS-IS 8.0.0.Beta1 (SwitchYard 2.0.0.v20141011-0508-H499-Alpha3)
OpenJDK 1.7 

How reproducible:
always

Steps to Reproduce:
1. Add quartz binding
2. Start typing into Start / End time field
3. Open Error log, there are lots of runtime exceptions


Actual results:


Expected results:


Additional info:
Comment 1 JBoss JIRA Server 2015-01-13 13:51:31 UTC 
Andrej Podhradsky <apodhrad> updated the status of jira SWITCHYARD-2440 to Closed
Comment 2 Andrej Podhradsky 2015-01-13 13:52:30 UTC 
Verified with JBDS 8.0.1.GA + JBDSIS 8.0.0.Beta2a (contains SwitchYard 2.0.0.v20141219-2309-H527-Beta1)

There is a delay 500ms which reduces the number of errors in Error Log.
Comment 5 Andrej Podhradsky 2016-01-06 11:49: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.