This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 80219 - Property 'Year' in Duration dialog should have value validation
Summary: Property 'Year' in Duration dialog should have value validation
Status: CLOSED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: BPEL Mapper (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Joshua Sandusky
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-13 18:43 UTC by bugbridge
Modified: 2006-08-04 02:33 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugbridge 2006-07-13 18:43:42 UTC
Original status: 1-Dispatched; Suggested Status: NEW

Original Target Release: coke_dev; Suggested Target Milestone : 5.5

These items should be added to the Status Whiteboard: EXCEPTION
Original submitter: kaktus

Description:
Steps to reproduce:
- Go to Mapper window.
- Add datetime | duration literal in mapper.
- 'Duration' dialog appears.
- Set year property with value of at least 11 digits and press OK.
- Following exception occurs:

java.lang.NumberFormatException: For input string: "11111111111"
	at java.lang.NumberFormatException.forInputString
(NumberFormatException.java:48)
	at java.lang.Integer.parseInt(Integer.java:459)
	at java.lang.Integer.parseInt(Integer.java:497)
	at 
org.netbeans.modules.bpel.xpath.view.component.StaticDurationPanel.getTimeoutVa
lue(StaticDurationPanel.java:250)
	at 
org.netbeans.modules.bpel.xpath.view.component.StaticDurationDialog.okSelected
(StaticDurationDialog.java:101)
	at 
org.netbeans.modules.bpel.xpath.view.component.StaticDurationDialog.access$000
(StaticDurationDialog.java:33)
	at 
org.netbeans.modules.bpel.xpath.view.component.StaticDurationDialog$1.actionPer
formed(StaticDurationDialog.java:83)
	at javax.swing.AbstractButton.fireActionPerformed
(AbstractButton.java:1849)
	at javax.swing.AbstractButton$Handler.actionPerformed
(AbstractButton.java:2169)
	at javax.swing.DefaultButtonModel.fireActionPerformed
(DefaultButtonModel.java:420)
	at javax.swing.DefaultButtonModel.setPressed
(DefaultButtonModel.java:258)
	at javax.swing.plaf.basic.BasicButtonListener.mouseReleased
(BasicButtonListener.java:234)
	at java.awt.Component.processMouseEvent(Component.java:5488)
	at javax.swing.JComponent.processMouseEvent(JComponent.java:3126)
	at java.awt.Component.processEvent(Component.java:5253)
	at java.awt.Container.processEvent(Container.java:1966)
	at java.awt.Component.dispatchEventImpl(Component.java:3955)
	at java.awt.Container.dispatchEventImpl(Container.java:2024)
	at java.awt.Component.dispatchEvent(Component.java:3803)
	at java.awt.LightweightDispatcher.retargetMouseEvent
(Container.java:4212)
	at java.awt.LightweightDispatcher.processMouseEvent
(Container.java:3892)
	at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3822)
	at java.awt.Container.dispatchEventImpl(Container.java:2010)
	at java.awt.Window.dispatchEventImpl(Window.java:1774)
	at java.awt.Component.dispatchEvent(Component.java:3803)
[catch] at java.awt.EventQueue.dispatchEvent(EventQueue.java:463)
	at java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:242)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:163)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:153)
	at java.awt.Dialog$1.run(Dialog.java:515)
	at java.awt.Dialog.show(Dialog.java:536)
	at java.awt.Component.show(Component.java:1300)
	at java.awt.Component.setVisible(Component.java:1253)
	at 
org.netbeans.modules.bpel.xpath.view.AbstractMapperRule.handleNewOperator
(AbstractMapperRule.java:212)
	at org.netbeans.modules.bpel.xpath.view.AbstractMapperRule.eventInvoked
(AbstractMapperRule.java:108)
	at org.netbeans.modules.mapper.basicmapper.BasicMapperController$1.run
(BasicMapperController.java:430)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
	at java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:242)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:163)
	at java.awt.EventDispatchThread.pumpEvents
(EventDispatchThread.java:157)
	at java.awt.EventDispatchThread.pumpEvents
(EventDispatchThread.java:149)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
Comment 1 Joshua Sandusky 2006-07-21 20:25:52 UTC
proper validation will occur when the duration literal no longer reverse
engineers into the string literal. There will be a duration literal editor that
pops up, and the user will enter in date information into that editor instead of
free-form.

*** This issue has been marked as a duplicate of 80201 ***
Comment 2 Mikhail Kondratyev 2006-07-24 15:04:16 UTC
I don't clearly understand why this is a duplicate.
According to bug description exception occurs when user types incorrect value
_in the duration editor_ , not in the free form way. So this looks like the
duration literal bug
Comment 3 Joshua Sandusky 2006-08-01 20:27:06 UTC
fixed, validation is now performed
Comment 4 lchang 2006-08-04 02:33:55 UTC
Fixed, now it only allows you to put in 10 digits, and then it stops letting 
you enter more.