cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Burton" <>
Subject Re: 1.1 vs 1.2 - possible Collections problem
Date Wed, 05 Apr 2000 17:05:52 GMT

> I've just been looking at the 1.1 Collections README:
> "Since these classes are direct copies of their 1.2 counterparts with the
> package names changed, the API's are 100% identical with the one
> exception that since they are in different packages they are distinct Java
> types and cannot be cast/assigned between each other."
> There is thus one possible problem. Any communication between Cocoon and
> web-applications (for example, webapp calling a Cocoon utility method),
> which uses collections (if any), must use the same collection import
> statements as Cocoon. Is this going to be a problem?

Personally, I doubt it.  Most webapps (etc) only directly call the engine,
or really a wrapper class around the engine (such as ServletCocoon). These
interfaces are defined and do not need to use Collections.


View raw message