Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 67255 - In sun-ejb-jar.xml GUI editor, it fail to check for the dup of Message Destination Jndi Name
In sun-ejb-jar.xml GUI editor, it fail to check for the dup of Message Destin...
Status: NEW
Product: serverplugins
Classification: Unclassified
Component: Sun Appserver 8
All All
: P4 (vote)
: 6.x
Assigned To: Vince Kraemer
: 114366 (view as bug list)
Depends on: 95131
  Show dependency treegraph
Reported: 2005-10-21 02:05 UTC by judytang
Modified: 2010-08-31 20:57 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT


Note You need to log in before you can comment on or make changes to this bug.
Description judytang 2005-10-21 02:05:53 UTC
I am using 10/19 IDE dialy build with JDK 5.0, Appserver 8 UR2 on Win XP

In sun-ejb-jar.xml GUI editor, it fail to check for the dup of Message
Destination Jndi Name.

Steps to recreate:

(1) Create any new J2EE project

(2) EJBModule node -> Configuration Files -> open sun-ejb-jar.xml in GUI mode

(3) Click on Message Generation, enter two entries with the same Jndi Name, it
    did not detect the duplication of Jndi names.
Comment 1 _ pcw 2005-11-04 02:19:46 UTC
We can do some checks for duplication here... not sure how far we should go, but
I guess anything within a single module is acceptable as we can easily have a
per-DeploymentConfiguration registry of what JNDI names have been used and apply
this to anything that is manually entered.

I'm loathe to prevent the user from entering duplicate names but rather would
prefer to simply flag names as conflicting in a warning message.  Additionally,
while I think the zero-config code should not intentionally create a duplicate,
the JNDI names that it generates are synchronized with the various code
generators in the various J2EE project types.  If it doesn't generate the
expected name, then the generated code will be wrong.  There is no practical way
to for the code generators to inspect what JNDI name we generated either (they
work independent of what the selected server is).
Comment 2 Vince Kraemer 2007-02-10 02:15:22 UTC
this would be addressed by the changes for 95131. linking
Comment 3 Vince Kraemer 2007-05-15 17:51:24 UTC
tm change
Comment 4 _ pcw 2007-10-30 00:26:54 UTC
Defer to after NB6.

See also issue 114366.

Comment 5 Vince Kraemer 2007-12-08 03:51:21 UTC
Is it time to work on this now?  Or should we just close this? (and  issue 114366)???
Comment 6 _ pcw 2007-12-08 08:25:04 UTC
Why close them?  They are legitimate requests.  If they are closed, noone will ever look at them again and improvements
in this area will certainly never happen.

I suppose you could make one or both enhancement requests.  It does not matter to me.
Comment 7 Vince Kraemer 2008-10-17 23:36:20 UTC
This did not apply to our 6.5 priorities, since v3 did not really support EJB.  i think that will be different for 7.0...

I guess this should be a p2 issue.

Please be ready to discuss this issue on 2008/10/22
Comment 8 _ pcw 2008-10-22 18:39:55 UTC
--> P4, not easy to fix, mostly relevant to J2EE 1.4
Comment 9 Vince Kraemer 2008-12-24 21:57:04 UTC
not worth worrying about in 7.0 time frame
Comment 10 Vince Kraemer 2010-08-31 20:57:22 UTC
*** Bug 114366 has been marked as a duplicate of this bug. ***

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo