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.

We need a working solution for this. Currently, it are hassles like
those which alienate even the good-will developers which actually *do*
try to write good API documentation (it are way too few). If we're
serious about our API, we shouldn't impose such artificial restrictions
on ourselves.

Ciao
Frank

-- 
- Frank Schönheit, Software Engineer         [EMAIL PROTECTED] -
- Sun Microsystems                      http://www.sun.com/staroffice -
- OpenOffice.org Base                       http://dba.openoffice.org -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to