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 55965 - Evolution improvements in API before it gets more stable
Summary: Evolution improvements in API before it gets more stable
Status: RESOLVED WORKSFORME
Alias: None
Product: javaee
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: Other Linux
: P4 blocker (vote)
Assignee: martin_adamek
URL:
Keywords:
Depends on:
Blocks: 52155 89013
  Show dependency tree
 
Reported: 2005-03-04 13:39 UTC by Jaroslav Tulach
Modified: 2008-09-19 10:15 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2005-03-04 13:39:37 UTC 
EjbReference in j2ee.api.ejbjar is an interface. 
Do you really believe that you get the set of 
methods right? I doubt you do (especially if you 
are still using org.openide.src hieararchy). 
Split this interface into API and SPI part. In 
API make final class where you will be able to 
add and deprecate methods and in SPI just create 
new and new interfaces. Btw. this class is not 
used in the API at all! Btw2. also 
EnterpriseReferenceContainer? is a candidate for 
API and SPI split.  
 
 
All good points, but IMO good enough for 4.1. 
Can be fixed before this is made stable > friend
Comment 1 Petr Blaha 2006-03-13 13:47:55 UTC 
TM 5.0 -> TBD
Comment 2 pslechta 2008-09-19 10:15:09 UTC 
I believe that this problem was already solved. I see packages org.netbeans.modules.j2ee.api.ejbjar and
org.netbeans.modules.j2ee.spi.ejbjar, so it seems to me that the functionality was split into API and SPI part.

Closing this issue as WORKSFORME. Reporter, please reopen if you still see some problem.