Morrison, John wrote:
 >>-----Original Message-----
 >>From: Giacomo Pati [mailto:[EMAIL PROTECTED]]
 >>Sent: Wednesday, 05 September 2001 7:39 am
 >>To: [EMAIL PROTECTED]
 >>Subject: Re: AW: [C2][VOTE] Sync C2.0 and C2.1 branches
 >>
 >>
 >>Quoting Carsten Ziegeler <[EMAIL PROTECTED]>:
 >>
 >>
 >>>Many thanks for this research, dims!
 >>>
 >>>
 >>>>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
 >>>>
 >>>+0 (These are additional components which do not affect the core)
 >>>
 >>+0 as well. Yes, they don't affect the core. But as it is an
 >>XML stream comming
 >>from an xmldb what about making it a protocl
 >>(dbxml:/db/mydocs/foo[is='bar'])?
 >>
 >
 > +0
 >
+0. BTW, Source is better than URLFactory since it this is natively XML 
(URLs must go through a parser)

 >>>> 2) FOP Serializers / Renderer Components - C2.1 has a
 >>>>configurable, SAX based Serializer that
 >>>>supports PCL, PS and PDF.
 >>>>
 >>>+1 (I tend to think that the FOP serializer belongs to the core)
 >>>
 >>+1
 >>
 >
 > +1 This shouldn't impact anyone currently using 2.0
 >
 >
+1 : Dynamic PDF is a major cocoon feature.

 >>>> 3) JUnit based Test cases - C2.1 has a framework for test cases
 >>>>from Stuart
 >>>>
 >>>+0
 >>>
 >>+0
 >>
 >
 > +0 Good for 2.1 - required for 2.0?  Prob not.
 >
 >
+1 if they don't rely on 2.1-only classes (i.e. no specific port for 2.0)

 >>>> 4) Source Interface changes - C2.1 has changes from Ovidiu for
 >>>>better core implementation.
 >>>>
 >>>+5 (Important core changes)
 >>>
 >>+1
 >>
 >
 > +1 Best to try and keep the core in sync
 >
 >
+1 also

 >>>> 5) LogKit mechanism - C2.1 has better support for log messages
 >>>>from Giacomo
 >>>>
 >>>+5 (Great work from Giacomo)
 >>>
 >>+1, thanks :)
 >>
 >
 > +1 Seconded!
+10 for this great feature, even if it requires a non-released Excalibur.
 >>>> 6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.
 >>>>
 >>>+0 to +1 (could make SITE maintanance a bit easier?)
 >>>
 >>+1
 >>
 >
 > +1
 >
+1

 >>>> 7) SiteBuilder - Sitemap editor cocoon app contribution
 >>>>
 >>from Sergio
 >>
 >>>Haven't tested it yet.
 >>>
 >>-0. I still see it throwing exceptions.
 >>
 >
 > I've not used this either
 >
 >
+0.

 >>>> 8) Catalog Support - Entity Catalog support from David Crossley
 >>>>
 >>>+1
 >>>
 >>+1
 >>
 >
 > Or this - but I can see why it's needed! (+1)
 >
 >
+1

 >>>> 9) Better JSP Support - JspEngineImplWLS and
 >>>>JSPEngineImplNamedDispatcherInclude from Bernhard
 >>>>
 >>>+1
 >>>
 >>+0
 >>
 >
 > 0 - I don't use JSP
 >
 >
+1. JSP integration allows some smooth "rewamping" of existing apps.

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

 >>>>11) XSLTProcessor + TRaX Transformer update - componentize TRaX
 >>>>support from Ovidiu
 >>>>
 >>>+1 (core changes)
 >>>
 >>+1
 >>
 >
 > +1
 >
 >
+1

 >>>>12) Simple Profiler and related Event Pipelines - Profiler
 >>>>Support from Vadim
 >>>>
 >>>+1 (could help in starting with C2)
 >>>
 >>+0. Don't know the stability of it.
 >>
 >
 > +0 I need to look into this soon...
 >
 >
+0.

 >>>>13) DatabaseSelectionAction.java
 >>>>
 >>>+0
 >>>
 >>+0 Didn't know this is in 2.1 only.
 >>
 >
 > +0 Don't use...
 >
 >
+O don't use also

 >>>>14) ScriptAction.java
 >>>>
 >>>+1 (simple writing of actions)
 >>>
 >>+1
 >
 > +0 Again, don't use.
 >
+1

 >>>>15) ServerPagesAction.java / action.xsl
 >>>>
 >>>+0
 >>>
 >>-0
 >>
 >
 > +0 guess what...
 >
 >
+0 : more thinking is needed about an action MarkupLanguage.

 >>>>16) IncludeCacheValidity.java and CachingCIncludeTransformer.java
 >>>>
 >>>-1 (it depends on to many internal assumptions right now)
 >>>
 >>+0 Don't know its state.
 >>
 >
 > +0
 >
 >
+0 (don't know).

 >>>>17) Updated AbstractMarkupLanguage.java, LogicSheet.java,
 >>>>NamedLogicSheet.java.
 >>>>
 >>>If this affects core changes +1
 >>>
 > +1
 >
 > Agreed +1
 >
 >
+1 (change on LogicSheet is related to XSLTProcessor)

 >>>>18) Slightly updated HttpRequest.java.
 >>>>
 >>>+1
 >>>
 >>+1
 >>
 >
 > +1
 >
 >
+1

 >>>>19) Updated EnvironmentWrapper.java.
 >>>>
 >>>+1
 >>>
 >>+1
 >>
 >
 > +1
 >
 >
+1
 >>>>20) Updated Directory/File Generator.java
 >>>>
 >>>+1
 >>>
 >>+1
 >>
 >
 > +1
 >
 >
+1
 >>>>21) updated i18n Transformer.
 >>>>
 >>>+1
 >>>
 >>+5
 >>
 >
 > +1
 >
 >
+1
 >>>>22) Trivial SOAP samples.
 >>>>
 >>>+1 (Examples, yes!)
 >>>
 >>+0
 >>
 >
 > +0 I do think that it's xsl files ought to be moved from 
docs/samples/soap
 > though...
 >
 >
-0 : isn't Axis to young to be included in 2.0 ?

 >>>>23) RoleFilterTransformer.java
 >>>>
 >>>What's this? I must have missed it.
 >>>
 >>+0
 >>
 >
 > +0
 >
 >
+1. Useful sitemap component implementations are good, but I wonder if 
we shouldn't create a "examples" or "optional" package (like in Ant) in 
org.apache.cocoon to hold all those classes that aren't core.

 >>>>24) CocoonTargetFactory.java
 >>>>
 >>>What's this? I must have missed it, too.
 >>>
 >>It's part of the move to the LogKit Management where you have
 >>Factories for
 >>different LogTargets. As Cocoon has a custom LogTarget
 >>(CocoonLogTarget) I've
 >>written the corresponding Factory for it. So here is no voting
 >>needed/acceptable.
 >>
 >>
+1

 >>>>25) XMLizable interface
 >>>>
 >>>+1
 >>>
 >>+1
 >>
 >
 > +1
 >
 >
+1 (goes with Source changes)

 >>>>26) SEL taglib
 >>>>
 >>>+0
 >>>
 >>+0 What the hell is this. Must have missed it.
 >>
 >
 > 0 Me too!
 >
 >
Seems it allows to select parts of an XSP depending on a sitemap 
parameter. Torsten, can you give us some use cases ?

 >>>>27) Action taglib
 >>>>
 >>>+0
 >>>
 >>+0
 >>
 > +0
 >
 >
+0 (used with ServerPagesAction)

 >>>>28) More sub sitemap samples.
 >>>>
 >>>+5 (yes, examples!)
 >>>
 >>+1
 >>
 >
 > +1 examples - the more the merrier :)  Donald - you've had some prettily
 > formatted documents on your site - what ever happened to them?  Could 
they
 > be added too?
 >
+1

 >>Hey, Dims, your work in keeping track what is happening in
 >>the code base is
 >>great. many thanks.
 >>
 >
 > Yeah - how did you find all these?
 >
 > J.
 >
Thanks also. Just to know : did you perform a diff between the two 
branches, or do you keep track of cvs-commits ?

-- 
Sylvain Wallez
Anyware Technologies - http://www.anyware-tech.com


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

Reply via email to