Maybe a much more moderate proposal than jelly-api.jar, e.g., one or two classes that encompass most common usages and are recommended officially would do the trick and avoid this ?
paul
Le 20 sept. 04, à 01:37, Hans Gilde a écrit :
Maybe the public API task should also be put off for 1.1. It seems to me that any of the suggestions would result in somewhat significant API changes. We could make it clear in the 1.0 release that the Java API will change but the Tag libs form a stable XML API.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
