Re: Changes in the JavaPlatform API
Tomas Zezula <[email protected]>
| Newsgroups | gmane.comp.java.netbeans.modules.projects.devel |
|---|---|
| Message-ID | <[email protected]> |
Svata Dedic wrote: > Hi, Tomas, > > I happen to think slowly these days, there's a couple of things, which > I forgot about :-( > > Tomas Zezula wrote: > >> Proposal: 1. Rename the JavaPlatform class to the >> GenericJavaPlatform class and >> remove from it all the J2SE specific methods (getSecificationVersion()) > > > Is the rename necessary if there will be a new specific J2SEPlatform > subtype ? No it is not necessary, it was designed only to point out that new JavaPlatform is no more compatible with old implementation. But the names can stay the same. > > >> 4. Rename the PlatformService into the GenericPlatformService >> without >> any J2SE specific method. > > > [the same question about rename] > >> >> The changes are shown on the attached UML diagram. > > > Would it be possible to have EditionType with no tags defined, and the > tags would be defined on J2SEPlatform, J2MEPlatform and J2EEPlatform, > respectively ? Then adding an edition (not much probable, though) > would not require to change the base API (EditionType). Yes it is possible. The EditionType is not a final class, so it can be extended by any module by other edition types. So adding new edition will not require changes of API, just a platform returns a subclass of EditionType. The question is what to put into base EditionType, according to me it should have at least SE type. > > > Another thought -- what all functions will the tag serve for ? Isn't > "aPlatform instanceof the_edition_specific_subtype" expression > sufficient to lurk for a specific platform edition ? I don't want to have a test of edition type using instanceof, for me it seems better to define an explicit method for that. Tomas > > > Thanks! > -Svata > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >