Original status: 1-Dispatched; Suggested Status: NEW
1. install nb5.5 build 200611220100, vwp build 061121_4
2. create a visual web application
3. add a property or class from Outline -> SessionBean1 or ApplicationBean1 or
For instance, add a property to SessionBean1.
Set the Type "a" for instance. That means "a" can be user's class that need to
be imported later.
4. open SessionBean1.java, then save.
5. open another Page1.jsp in another visual application.
6. switch to the first Page1.jsp
SessionBean node disappears from the Outline window. Refer to the screenshot
Closing the project and IDE, and removing the user dir don't make difference.
* This doesn't happen in Leopard.
Can't try out now. There is another issue preventing to add any property into
the beans now.
Currently this issue is blocked by the fact, that the java node misses its sub
nodes with the needed new types (they can't be retrieved now via the current hack).
See blocking issue #96196.
See also issue #90907.
This is not gonna by fixed for 6.0, because of the blocking issues.
*** Issue 98577 has been marked as a duplicate of this issue. ***
Adding 6.0 waiver request.
*** Issue 106148 has been marked as a duplicate of this issue. ***
IMO the issue should be solved a different way. Adding more and more nodes under the Java node just clutters the GUI.
EJB should have extra tab in the navigator which will permit for doing EJB specific operations. (So should do JavaBeans
No objections long time, changing to waiver approved.
*** Issue 111100 has been marked as a duplicate of this issue. ***
*** Issue 111909 has been marked as a duplicate of this issue. ***
Release note added
*** Issue 116443 has been marked as a duplicate of this issue. ***
OK, there are more and more complains about this. I am passing this issue to insync, where it belongs (the node
implementation is there).
The Add Property in Outline window is no longer supported in 6.0 because of removal of underlying beans module support.
Definitley not a P2.
Thirdly the SessionBean1 is disappearing because of the user did not import the "a" which results in the syntax error.
The SessionBean node and the tab does indicate that with a badge. Because of the syntax error Insync cannot model the
SessionBean. Importing the "a" fixes the issue.