cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sylvain Wallez <sylvain.wal...@anyware-tech.com>
Subject Re: POI serialization code committed
Date Thu, 07 Mar 2002 11:21:17 GMT
Nicola Ken Barozzi wrote:

>POI stuff committed with samples.
>
>:-)
>
>Please cross check.
>
That's really cool stuff, however I have some wonders about the source 
code that's been added to the Cocoon CVS :
- shouldn't all the ElementProcessor stuff be better located in the POI 
CVS repository ?
- is Cocoon the only product in which serializing XML to XLS is usefull ?

 From what I can see, all classes in 
components.elementprocessor.impl.poi.* are really POI-specific and can 
be understood and maintained only by people with POI knowledge. So why 
aren't they managed by the POI project itself and delivered in poi.jar ?

The strength of Cocoon is its ability to integrate many components 
(XIndice, JFor, FOP, Velocity, to mention a few). But IMO, it should 
only host "glue" classes for these components and not the components 
themselves.

 From a project management point of view, we have the danger for part of 
the traffic on cocoon lists being related to POI, which means noise for 
Cocoon and loss of information for POI, and lots of POI-related entries 
in Bugzilla (user reports and patches from the POI team).

So, what do you think about moving (back ?) the ElementProcessor stuff 
to the POI CVS, and keep only the Serializers in Cocoon CVS ?

Sylvain

-- 
Sylvain Wallez
  Anyware Technologies                  Apache Cocoon
  http://www.anyware-tech.com           mailto:sylvain@apache.org




---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message