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 30554

Summary:	On Solaris new EJB is not selected properly after creation by wizard
Product:	platform	Reporter:	Unknown <non_migrated_user>
Component:	Explorer	Assignee:	Jiri Rechtacek <jrechtacek>
Status:	VERIFIED DUPLICATE
Severity:	blocker
Priority:	P2
Version:	3.x
Hardware:	Sun
OS:	Solaris
Issue Type:	DEFECT	Exception Reporter:

Description Unknown 2003-01-31 16:10:33 UTC

Description: 
Steps to reproduce:
testing on Dublin build 021025

Create a new Stateful session bean.
In the past, the session bean is selected after creation.
This allows easy creation of business methods etc especially via the keyboard.
On Solaris the newly created nodes are ordered differently and the remote
interface node is selected instead of the (EJB) node.

A comment.

Comment 1 Jiri Rechtacek 2003-01-31 17:41:16 UTC

It seems as duplicate of issue 30274. The defect 30274 was fixed on
Jun31 (either in core and in java) in nb maintrunk , it should work in
next production build.

*** This issue has been marked as a duplicate of 30274 ***

Comment 2 Unknown 2003-07-09 17:36:30 UTC

This is not a duplicate of issue 30274.

Here is additional information. When an EJB is created, several java
files are created as well as the EJB object. If the user specified
that the remote and home interface are to be created for the EJB,
the remote interface java file has the same name as the EJB, for
example, if the EJB is called "Product", then the remote interface
name is Product.java and the generated ejb is Product.ejbdd. In
the explorer, at least on Solaris, the node for Product.java is
always displayed before the one for Product.ejbdd. When the user
selects "Finish" on the wizard, the java files are created and then
the EJB object is created. When the wizard is unmapped, and focus
returns to the explorer, the java node (Product.java) is selected
rather than the EJB node.

I've debugged this a little. After the EJB is created, the
correct OperationEvent is fired with the EJB data object supplied
as the object. But somewhere in the code that selects the node,
the wrong node is selected. I believe it is because in both cases,
both nodes return the same "name" (ie. getName for both nodes
returns "Product"), and since the java node is displayed first,
this one is found first and is selected. But, I've never been able
to prove this theory.

Note that this does not typically happen on Windows because for
some reason there, the EJB node is displayed before the java node
in the explorer, so the EJB node is selected after the wizard 
completes.

Comment 3 Jiri Rechtacek 2003-08-29 18:19:04 UTC

Joe, the decribed behavior is duplicate of genarel problem e.g. issue
22030. It will solved when will be reimplemented parts nodes/views.

*** This issue has been marked as a duplicate of 22030 ***

Comment 4 Marian Mirilovic 2003-09-03 15:25:53 UTC

It's duplicate - verifying (in a fact it's duplicate of issue 21177)