Frank Schönheit - Sun Microsystems Germany schrieb: > Hi Mathias, > >> The only way would be to make the service itself "unpublished" what of >> course is not allowed also. Perhaps we could allow it for this service >> as it is an "old style service" and these services never have been used >> for anything else than documentation. So making it "unpublished" won't >> break any code. But I assume that this would create some hassle. >> >> Alternatively you could remove your new interface from the IDL file >> again (as I said: old style services are documentation only) or you can >> design a new, unpublished service and deprecate the old one. This would >> be a good opportunity to make this service a "new style" one. :-) > > Sorry, but as even the inventors of new style-services say, they aren't > the final solution to every problem, and they cannot be applied to each > and everything. So, what you suggest is not a viable option, as there > are enough old-style services around which cannot be reasonably > converted to new-style ones.
What in "this would be a good opportunity to make this service a "new style one" makes you believe that I proposed this as the *solution* of the problem? For me it's just a *side effect* of the replacement of the old service by a new one. So *if* a new service needs to be changed for whatever reason it *should* be considered to also make it a "new style" service. You see the difference? I just asked for checking *if* a new service that should replace or complement an old one also could be a "new style" service. Alternatively the new service derived from the old (and "old style") service could also be extended and converted to a multiple inheritance interface as IMHO this is the better alternative and covers everything you can get from an "old style" service except the service name. I don't see any "old style" service that can't be converted to a multiple inheritance interface. In case it still should be made available as a service so that it can be instantiated by a service provider it can also become a "new style" service. In case you still need an "old style" service (for what?) it also can be based on the multiple inheritance interface. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
