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 20934 - IllegalArgumentException after set incorrect value to Direction(BorderLayout)
Summary: IllegalArgumentException after set incorrect value to Direction(BorderLayout)
Status: CLOSED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: -FFJ-
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-02-27 11:27 UTC by Marian Mirilovic
Modified: 2003-06-30 18:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IllegalArgumentException (1.64 KB, text/plain)
2002-02-27 11:28 UTC, Marian Mirilovic 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marian Mirilovic 2002-02-27 11:27:08 UTC 
[ffj40_ea](20020225), [jdk1.4](92)

Steps to reproduce:
- open/create JFrame (layout = BorderLayout)
- add JLabel 
- invoke custom editor for JLabel property Direction
- change editor to "StringEditor", push Ok
- type value "east" (incorrect => correct is "East")
- Enter
-> IllegalArgumentException arise (see attachment) 

This exception should be annotated with information " Invalid value ...."
Comment 1 Marian Mirilovic 2002-02-27 11:28:26 UTC 
Created attachment 4838 [details]
IllegalArgumentException
Comment 2 Richard Malaschitz 2002-05-07 12:25:04 UTC 
I think that exception is proper behaviour - but better possibily is allow 
only BorderDirectionEditor at this place.
Comment 3 Tomas Pavek 2002-06-07 11:35:45 UTC 
Custom property editor for Direction property (layout 
constraint) was disabled (already some time ago). So I 
think this can be marked as fixed.
Comment 4 Marian Mirilovic 2002-06-10 12:54:45 UTC 
verified in [nb_dev](20020610)
Comment 5 Quality Engineering 2003-06-30 18:29:43 UTC 
Resolved for 3.3.x or earlier, no new info since then -> closing.