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 30257

Summary: IndexOutOfBound exception when right clicking on jwsdp-services:8081 node
Product: javaee Reporter: Jason Rush <jrush>
Component: CodeAssignee: Milan Kuchtiak <mkuchtiak>
Status: VERIFIED FIXED    
Severity: blocker    
Priority: P2    
Version: -S1S-   
Hardware: All   
OS: All   
Issue Type: DEFECT Exception Reporter:

Description Jason Rush 2003-01-22 00:11:36 UTC
Description: 
S1S:  Sierra RC5 build

I've downloaded the Java  Web Services Developer Pack 1.0 from:
  http://java.sun.com/webservices/downloads/install_windows.html

1) in S1S, at the runtime tab -> Server Registry -> Installed Servers ->
    Tomcat 4.0
     select "Add Tomcat 4.0 installation"
    jwsdp-1_0_01 is added  (see attached jpg picture)
2) Select jwsdp-services:8081 and right click 
    results the following exceptions:

Fri Oct 25 11:25:44 PDT 2002: java.lang.IndexOutOfBoundsException: Index: -1, 
Size: 0
Annotation: Invalid value. The property Default Connector could not be set. 
Reason:
Index: -1, Size: 0
java.lang.IndexOutOfBoundsException: Index: -1, Size: 0
        at java.util.ArrayList.RangeCheck(ArrayList.java:508)
        at java.util.ArrayList.get(ArrayList.java:320)
        at org.netbeans.modules.schema2beans.BeanProp.getAttributeValue
(BeanProp.java:1262)
        at org.netbeans.modules.schema2beans.BaseBean.getAttributeValue
(BaseBean.java:643)
        at org.netbeans.modules.tomcat.tomcat40.nodes.HostNode.getHostName
(HostNode.java:252)
        at 
org.netbeans.modules.tomcat.tomcat40.nodes.HostNode.getDefaultConnector
(HostNode.java:263)
        at org.netbeans.modules.tomcat.tomcat40.nodes.HostNode.access$000
(HostNode.java:39)
        at org.netbeans.modules.tomcat.tomcat40.nodes.HostNode$7.getValue
(HostNode.java:542)
        at org.openide.explorer.propertysheet.PropertyPanel$SimpleModel.getValue
(PropertyPanel.java:1356)
[catch] at org.openide.explorer.propertysheet.PropertyPanel.updateEditor
(PropertyPanel.java:622)
        at org.openide.explorer.propertysheet.PropertyPanel.<init>
(PropertyPanel.java:259)
        at org.openide.explorer.propertysheet.PropertyPanel.<init>
(PropertyPanel.java:265)
        at org.openide.explorer.propertysheet.PropertySheetTab.fillProperties
(PropertySheetTab.java:359)
        at org.openide.explorer.propertysheet.PropertySheetTab.createPane
(PropertySheetTab.java:310)
        at org.openide.explorer.propertysheet.PropertySheetTab.<init>
(PropertySheetTab.java:175)
        at org.openide.explorer.propertysheet.PropertySheet.refreshPropertySheet
(PropertySheet.java:463)
        at org.openide.explorer.propertysheet.PropertySheet.access$1100
(PropertySheet.java:52)
        at org.openide.explorer.propertysheet.PropertySheet$3.run
(PropertySheet.java:638)
        at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
        at java.awt.EventQueue.dispatchEvent(EventQueue.java:443)
        at java.awt.EventDispatchThread.pumpOneEventForHierarchy
(EventDispatchThread.java:191)
        at java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:144)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
        at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:130)
        at java.awt.EventDispatchThread.run(EventDispatchThread.java:98)

When I install jwsdp the first time, I didn't encountered this problem within 
S1S.
I uninstall jwsdp and reinstall jwsdp, restart the system, then this problem
occurs.

(see attached jpg file, and ide.log)

Evaluation: 

Lark Fitzgerald 2002-10-25: rico, I can't reproduce this so I'm not sure what's 
going on.

I'm not using the jwsdp version bundle with the S1S. I don't problem with this 
bundled version. However download an external version from the web will cause
this problem.
Joanne Lau 2002-10-29

Lark Fitzgerald 2003-01-21: Nevada will bundle the jwsdp version of tomcat so 
the user will not have to use an external jwsdp so the priority of this may 
drop some more BUT it is still a problem that needs to be fixed but I don't 
believe it is a web services issue.

A comment.
Comment 1 Jason Rush 2003-01-22 00:13:44 UTC
Transferred from BugTraq issue #4769056.
Comment 2 akemr 2003-02-04 09:44:40 UTC
Cannot reproduce on current Nevada build and JWSDP 1_0_01 (now
available version on java.sun.com), so I'm marking as fixed.
Comment 3 Jason Rush 2003-02-04 13:03:31 UTC
Verified in NetBeans dev build 200302040100.