Davanum Srinivas wrote:
> 
> Team,
> 
> Here are the "significant" differences. Please go ahead and add your +1/-1/0 to each 
>item. If i
> have missed anything, please add it to the bottom of the list with your vote.
> 
>  1) XML:DB Generators - There are two generators in C2.1 for dealing with data from 
>XML:DB data
> sources

-1  This should be reason to upgrade, not necessary or as well tested as other C2.0 
generators.

>  2) FOP Serializers / Renderer Components - C2.1 has a configurable, SAX based 
>Serializer that
> supports PCL, PS and PDF.

+1  Latest FOP makes it easier to create XSL:FO documents and see expected results.

>  3) JUnit based Test cases - C2.1 has a framework for test cases from Stuart

+0  Avalon uses JUnit for Test cases, and I am all for it--this is somewhat lower 
+priority though.

>  4) Source Interface changes - C2.1 has changes from Ovidiu for better core 
>implementation.

+1  The API should be stable when we release C2.0

>  5) LogKit mechanism - C2.1 has better support for log messages from Giacomo

+10  Fine grained control of the Loggers is definitely needed.  This allows us to pay 
+attention
     only to the information we want to see.

>  6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.

-0  It would be nice to have, but the first thing I would ax on a time crunch

>  7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio

-10  SiteBuilder is in its infancy, I would like to see it mature before being in a 
cocoon release

>  8) Catalog Support - Entity Catalog support from David Crossley

+.5  I like the ability to set a bunch of entities (like all the ISO entities) and 
+have them
     resolve, but give precidence to stability and API consistency.

>  9) Better JSP Support - JspEngineImplWLS and JSPEngineImplNamedDispatcherInclude 
>from Bernhard

-0  I don't use JSP, so there is little for me to gain here.  (I am biased though).

> 10) Parent Component Manager Support - Specify a configurable parent Component 
>Manager from Leo

+0  I haven't seen it in full action yet.  Leo does good work and consults smart folks 
+;) but
    I would have it slated for C2.1

> 11) XSLTProcessor + TRaX Transformer update - componentize TRaX support from Ovidiu

+0  If it is critical functionality, ok.  If not, I would hold off on it.  Remember we 
+do want
    to give people a reason to upgrade.

> 12) Simple Profiler and related Event Pipelines - Profiler Support from Vadim

-1  I like profiler support, but this should be for C2.1

> 13) DatabaseSelectionAction.java

+1  This eases form development

> 14) ScriptAction.java

-1  Leave for C2.1 and make sure it works well

> 15) ServerPagesAction.java / action.xsl

-1  We need to see this mature a little more.

> 16) IncludeCacheValidity.java and CachingCIncludeTransformer.java

+1  It would speed up so many things for me.

> 17) Updated AbstractMarkupLanguage.java, LogicSheet.java, NamedLogicSheet.java.

+1

> 18) Slightly updated HttpRequest.java.

+1

> 19) Updated EnvironmentWrapper.java.

+1

> 20) Updated Directory/File Generator.java

+1

> 21) updated i18n Transformer.

+1

> 22) Trivial SOAP samples.

-1  This is new functionality that should probably wait.

> 23) RoleFilterTransformer.java

-1  I wrote it, but I know it needs a bit more testing

> 24) CocoonTargetFactory.java

-0  I am not familiar with this piece of code

> 25) XMLizable interface

-1  Additional API is acceptable--changed API makes people mad.

> 26) SEL taglib

-0  I am not familiar with this.  If it is XSPAction related then -1 for
    afforementioned reasons.

> 27) Action taglib

-1  Goes with XSP Action above.

> 28) More sub sitemap samples.

-0  Again it is probably trivial--but I would ax it when faced with a time crunch

> 
> Thanks,
> dims
> 
> =====
> Davanum Srinivas, JNI-FAQ Manager
> http://www.jGuru.com/faq/JNI
> 
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
> http://im.yahoo.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]

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

Reply via email to