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 111275 - [ally] - No Accessible Description in new WSDL wizard for JMS
Summary: [ally] - No Accessible Description in new WSDL wizard for JMS
Status: RESOLVED FIXED
Alias: None
Product: soa
Classification: Unclassified
Component: Binding Components (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Shivanand Kini
URL:
Keywords: A11Y
Depends on:
Blocks:
 
Reported: 2007-07-28 00:41 UTC by lchang
Modified: 2007-10-29 22:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
A11Y tester results (1.05 KB, application/octet-stream)
2007-07-28 00:42 UTC, lchang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description lchang 2007-07-28 00:41:35 UTC
When running the A11Y tester tool against the Create new WSDL Wizard (For JMS Binding), the results show that there is 
No Accessible descriptions.

Steps to reproduce:
1.  Create a BPEL Module
2.  Create a new WSDL
3.  On first screen (Name and Location) accept default
4.  On second screen (Abstract Configuration) accept default
5.  On third screen (Concrete configuration) change the binding type to "JMS"
6.  Run the A11Y tester tool on this page

Result (also please see attached for full results)
No Accessible description :
   Class: javax.swing.JComboBox {  Binding Type: |  } 
   Class: javax.swing.JRadioButton {  JMS Transport |  } 
   Class: javax.swing.JTextField {  Binding Name: |  } 
   Class: javax.swing.JTextField {  Port Name: |  } 
   Class: javax.swing.JTextField {  Service Name: |  } 
   Class: org.netbeans.core.windows.services.NbDialog {  New WSDL Document |  }
Comment 1 lchang 2007-07-28 00:42:06 UTC
Created attachment 45851 [details]
A11Y tester results
Comment 2 Jaromir Uhrik 2007-08-06 15:12:42 UTC
Changing the priority to P3 because all components have accessible name that are descriptive enough and their semantic
is obvious from the context. Then the accessible description is not so important.
Comment 3 Sherry Weng 2007-10-26 19:19:29 UTC
This is not a binding component bug, reassigning to the WSDL editor team to be evaluated.
Comment 4 Shivanand Kini 2007-10-29 22:56:20 UTC
I have added the accessible description to all of the items