this is a follow-up to #82987.
the contract for modules implementing J2eeModuleProvider and related classes is
not clearly documented anywhere.
Specific issues I encountered
1. at some point in time getConfigSupport().ensureConfigurationReady() has to be
called, not clear what is the right time.
2. setServerInstanceID(String severInstanceID) is abstract and needs to be
implemented but is never actually called by the infrastructure
3. it generally seems to be a strange mix of api and spi and it's not clear
where is the line of responsibility between the project module, j2eeserver
infrastructure and the server plugins modules.
Changing the issue type to TASK.
I fully agree with the reporter that the API/SPI is not very well designed and
is not easy to use, the lack of documentation makes it even worse. Fixing the
documentation is the least we can do to improve it a little bit.
Setting the TM to DEV and increasing the priority to P1.
Stepan, has any work been done on this with your changes in j2eeserver in NB 6? Thx.
Some of the methods were moved from the J2eeModuleProvider to J2eeModule, where they belong, but there is still a lot of
clean up to do. I started a wiki page where j2eeserver API problems like this should be listed. For NB 6.0 I would like
to improve the javadocs at least.
here is the link http://wiki.netbeans.org/wiki/view/J2EEServerAPIProblems