You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Davanum Srinivas <di...@yahoo.com> on 2001/09/04 22:01:11 UTC
[C2][VOTE] Sync C2.0 and C2.1 branches
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
2) FOP Serializers / Renderer Components - C2.1 has a configurable, SAX based Serializer that
supports PCL, PS and PDF.
3) JUnit based Test cases - C2.1 has a framework for test cases from Stuart
4) Source Interface changes - C2.1 has changes from Ovidiu for better core implementation.
5) LogKit mechanism - C2.1 has better support for log messages from Giacomo
6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.
7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio
8) Catalog Support - Entity Catalog support from David Crossley
9) Better JSP Support - JspEngineImplWLS and JSPEngineImplNamedDispatcherInclude from Bernhard
10) Parent Component Manager Support - Specify a configurable parent Component Manager from Leo
11) XSLTProcessor + TRaX Transformer update - componentize TRaX support from Ovidiu
12) Simple Profiler and related Event Pipelines - Profiler Support from Vadim
13) DatabaseSelectionAction.java
14) ScriptAction.java
15) ServerPagesAction.java / action.xsl
16) IncludeCacheValidity.java and CachingCIncludeTransformer.java
17) Updated AbstractMarkupLanguage.java, LogicSheet.java, NamedLogicSheet.java.
18) Slightly updated HttpRequest.java.
19) Updated EnvironmentWrapper.java.
20) Updated Directory/File Generator.java
21) updated i18n Transformer.
22) Trivial SOAP samples.
23) RoleFilterTransformer.java
24) CocoonTargetFactory.java
25) XMLizable interface
26) SEL taglib
27) Action taglib
28) More sub sitemap samples.
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Carsten Ziegeler <cz...@sundn.de>.
> Giacomo Pati wrote:
>
> Quoting Carsten Ziegeler <cz...@sundn.de>:
>
> > On Wed, 5 Sep 2001, Davanum Srinivas wrote:
> >
> > > Team,
> > >
> > > First round of Sync is done.....The "core" should be exactly
> > the same. Experimental components and
> > > samples are left out of C2.0. Here's a list of the items that
> > > are only in C2.1 and NOT in C2.0
> > >
> > > 1) SiteBuilder Samples
> > > 2) SOAP Samples
> > > 3) Profiler and support files
> > > 4) XML:DB generators
> > > 5) DatabaseSelectAction.java
> > > 6) ScriptAction.java & ServerPagesAction.java
> > > 7) action.xsl and sel.xsl LogicSheets
> > > 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> > > 9) JUnit based Test framework.
> > > 10) Script Action samples.
> > >
> > > If i have made any mistakes, please bear with me and let me
> > know, i will fix or roll them back.
> > > Please go ahead and test C2.0. Let us try to get the "Release
> > > Candidate #1" out the door by end of
> > > next week (Sep 15, 2001).
> > >
> > Great and quick work! Thanks dims!!
> >
> > Yes, a release candidate by the end of next week would be great.
> > Let's see if we can do it!
>
> Did we collect the outstanding issues so far?
>
I was just creating an email for this...will come in some minutes.
Carsten
> Giacomo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Carsten Ziegeler <cz...@sundn.de>:
> On Wed, 5 Sep 2001, Davanum Srinivas wrote:
>
> > Team,
> >
> > First round of Sync is done.....The "core" should be exactly
> the same. Experimental components and
> > samples are left out of C2.0. Here's a list of the items that
> > are only in C2.1 and NOT in C2.0
> >
> > 1) SiteBuilder Samples
> > 2) SOAP Samples
> > 3) Profiler and support files
> > 4) XML:DB generators
> > 5) DatabaseSelectAction.java
> > 6) ScriptAction.java & ServerPagesAction.java
> > 7) action.xsl and sel.xsl LogicSheets
> > 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> > 9) JUnit based Test framework.
> > 10) Script Action samples.
> >
> > If i have made any mistakes, please bear with me and let me
> know, i will fix or roll them back.
> > Please go ahead and test C2.0. Let us try to get the "Release
> > Candidate #1" out the door by end of
> > next week (Sep 15, 2001).
> >
> Great and quick work! Thanks dims!!
>
> Yes, a release candidate by the end of next week would be great.
> Let's see if we can do it!
Did we collect the outstanding issues so far?
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Carsten Ziegeler <cz...@sundn.de>.
On Wed, 5 Sep 2001, Davanum Srinivas wrote:
> Team,
>
> First round of Sync is done.....The "core" should be exactly
the same. Experimental components and
> samples are left out of C2.0. Here's a list of the items that
> are only in C2.1 and NOT in C2.0
>
> 1) SiteBuilder Samples
> 2) SOAP Samples
> 3) Profiler and support files
> 4) XML:DB generators
> 5) DatabaseSelectAction.java
> 6) ScriptAction.java & ServerPagesAction.java
> 7) action.xsl and sel.xsl LogicSheets
> 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> 9) JUnit based Test framework.
> 10) Script Action samples.
>
> If i have made any mistakes, please bear with me and let me
know, i will fix or roll them back.
> Please go ahead and test C2.0. Let us try to get the "Release
> Candidate #1" out the door by end of
> next week (Sep 15, 2001).
>
Great and quick work! Thanks dims!!
Yes, a release candidate by the end of next week would be great.
Let's see if we can do it!
Carsten
Open Source Group sunShine - b:Integrated
================================================================
Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn
www.sundn.de mailto: cziegeler@sundn.de
================================================================
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by giacomo <gi...@apache.org>.
On Wed, 5 Sep 2001, Davanum Srinivas wrote:
> Team,
>
> First round of Sync is done.....The "core" should be exactly the same. Experimental components and
> samples are left out of C2.0. Here's a list of the items that are only in C2.1 and NOT in C2.0
>
> 1) SiteBuilder Samples
> 2) SOAP Samples
> 3) Profiler and support files
> 4) XML:DB generators
> 5) DatabaseSelectAction.java
> 6) ScriptAction.java & ServerPagesAction.java
> 7) action.xsl and sel.xsl LogicSheets
> 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> 9) JUnit based Test framework.
> 10) Script Action samples.
>
> If i have made any mistakes, please bear with me and let me know, i will fix or roll them back.
> Please go ahead and test C2.0. Let us try to get the "Release Candidate #1" out the door by end of
> next week (Sep 15, 2001).
Great work, Dims. I'll give my best to throw stones on it ;)
Giacomo
>
> 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: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
[C2] FileGenerator Exception Handling (was RE: [C2][VOTE] Sync C2.0 and C2.1 branches)
Posted by Davanum Srinivas <di...@yahoo.com>.
Vadim,
Please take a look now.
Thanks,
dims
--- Vadim Gritsenko <vg...@yahoo.com> wrote:
> Dims,
>
> I'm not sure is it yours mistake or somebody's else, but:
>
> Correct exception handling is vanished from (at least) FileGenerator,
> and may be from some other places (did not cvecked rest).
> The problem is that instead of ResourceNotFoundException,
> SAXException is thrown back in sitemap (and processed by 500
> error handler instead of 404).
>
> Previously, FileNotFoundException were cought by generator.
> Now, this piece of code is gone and FileNotFoundException is
> wrapped into SAXException.
>
> Vadim
>
>
> > -----Original Message-----
> > From: Davanum Srinivas [mailto:dims@yahoo.com]
> > Sent: Wednesday, September 05, 2001 6:29 PM
> > To: cocoon-dev@xml.apache.org
> > Subject: Re: [C2][VOTE] Sync C2.0 and C2.1 branches
> >
> >
> > Team,
> >
> > First round of Sync is done.....The "core" should be exactly the same. Experimental components
> and
> > samples are left out of C2.0. Here's a list of the items that are only in C2.1 and NOT in C2.0
> >
> > 1) SiteBuilder Samples
> > 2) SOAP Samples
> > 3) Profiler and support files
> > 4) XML:DB generators
> > 5) DatabaseSelectAction.java
> > 6) ScriptAction.java & ServerPagesAction.java
> > 7) action.xsl and sel.xsl LogicSheets
> > 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> > 9) JUnit based Test framework.
> > 10) Script Action samples.
> >
> > If i have made any mistakes, please bear with me and let me know, i will fix or roll them
> back.
> > Please go ahead and test C2.0. Let us try to get the "Release Candidate #1" out the door by
> end of
> > next week (Sep 15, 2001).
> >
> > 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: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
=====
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Vadim Gritsenko <vg...@hns.com>.
Dinms,
Situation is a little bit more complex then this. See my posting
"New Source Interface & Exception Handling Issues".
The problem is in SAXException which wraps FileNotFoundException.
I think it is needed to add "throws ProcessingException" to toSAX method and
analyze exception in XXXXXSource.toSAX method(s) and throw ProcessingException
or ResourceNotFoundException from within body of this method.
Vadim
> -----Original Message-----
> From: Davanum Srinivas [mailto:dims@yahoo.com]
> Sent: Thursday, September 06, 2001 7:14 AM
> To: cocoon-dev@xml.apache.org
> Subject: RE: [C2][VOTE] Sync C2.0 and C2.1 branches
>
>
> Vadim,
>
> Please ignore my previous e-mail....I think the inputSource is now being resolved in setup() can
> you please add additional code there to throw ResourceNotFoundException?
>
> Thanks,
> dims
>
> --- Vadim Gritsenko <vg...@yahoo.com> wrote:
> > Dims,
> >
> > I'm not sure is it yours mistake or somebody's else, but:
> >
> > Correct exception handling is vanished from (at least) FileGenerator,
> > and may be from some other places (did not cvecked rest).
> > The problem is that instead of ResourceNotFoundException,
> > SAXException is thrown back in sitemap (and processed by 500
> > error handler instead of 404).
> >
> > Previously, FileNotFoundException were cought by generator.
> > Now, this piece of code is gone and FileNotFoundException is
> > wrapped into SAXException.
> >
> > Vadim
> >
> >
> > > -----Original Message-----
> > > From: Davanum Srinivas [mailto:dims@yahoo.com]
> > > Sent: Wednesday, September 05, 2001 6:29 PM
> > > To: cocoon-dev@xml.apache.org
> > > Subject: Re: [C2][VOTE] Sync C2.0 and C2.1 branches
> > >
> > >
> > > Team,
> > >
> > > First round of Sync is done.....The "core" should be exactly the same. Experimental components
> > and
> > > samples are left out of C2.0. Here's a list of the items that are only in C2.1 and NOT in C2.0
> > >
> > > 1) SiteBuilder Samples
> > > 2) SOAP Samples
> > > 3) Profiler and support files
> > > 4) XML:DB generators
> > > 5) DatabaseSelectAction.java
> > > 6) ScriptAction.java & ServerPagesAction.java
> > > 7) action.xsl and sel.xsl LogicSheets
> > > 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> > > 9) JUnit based Test framework.
> > > 10) Script Action samples.
> > >
> > > If i have made any mistakes, please bear with me and let me know, i will fix or roll them
> > back.
> > > Please go ahead and test C2.0. Let us try to get the "Release Candidate #1" out the door by
> > end of
> > > next week (Sep 15, 2001).
> > >
> > > 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: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
> =====
> 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: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Davanum Srinivas <di...@yahoo.com>.
Vadim,
Please ignore my previous e-mail....I think the inputSource is now being resolved in setup() can
you please add additional code there to throw ResourceNotFoundException?
Thanks,
dims
--- Vadim Gritsenko <vg...@yahoo.com> wrote:
> Dims,
>
> I'm not sure is it yours mistake or somebody's else, but:
>
> Correct exception handling is vanished from (at least) FileGenerator,
> and may be from some other places (did not cvecked rest).
> The problem is that instead of ResourceNotFoundException,
> SAXException is thrown back in sitemap (and processed by 500
> error handler instead of 404).
>
> Previously, FileNotFoundException were cought by generator.
> Now, this piece of code is gone and FileNotFoundException is
> wrapped into SAXException.
>
> Vadim
>
>
> > -----Original Message-----
> > From: Davanum Srinivas [mailto:dims@yahoo.com]
> > Sent: Wednesday, September 05, 2001 6:29 PM
> > To: cocoon-dev@xml.apache.org
> > Subject: Re: [C2][VOTE] Sync C2.0 and C2.1 branches
> >
> >
> > Team,
> >
> > First round of Sync is done.....The "core" should be exactly the same. Experimental components
> and
> > samples are left out of C2.0. Here's a list of the items that are only in C2.1 and NOT in C2.0
> >
> > 1) SiteBuilder Samples
> > 2) SOAP Samples
> > 3) Profiler and support files
> > 4) XML:DB generators
> > 5) DatabaseSelectAction.java
> > 6) ScriptAction.java & ServerPagesAction.java
> > 7) action.xsl and sel.xsl LogicSheets
> > 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> > 9) JUnit based Test framework.
> > 10) Script Action samples.
> >
> > If i have made any mistakes, please bear with me and let me know, i will fix or roll them
> back.
> > Please go ahead and test C2.0. Let us try to get the "Release Candidate #1" out the door by
> end of
> > next week (Sep 15, 2001).
> >
> > 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: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
=====
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Vadim Gritsenko <vg...@yahoo.com>.
Dims,
I'm not sure is it yours mistake or somebody's else, but:
Correct exception handling is vanished from (at least) FileGenerator,
and may be from some other places (did not cvecked rest).
The problem is that instead of ResourceNotFoundException,
SAXException is thrown back in sitemap (and processed by 500
error handler instead of 404).
Previously, FileNotFoundException were cought by generator.
Now, this piece of code is gone and FileNotFoundException is
wrapped into SAXException.
Vadim
> -----Original Message-----
> From: Davanum Srinivas [mailto:dims@yahoo.com]
> Sent: Wednesday, September 05, 2001 6:29 PM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [C2][VOTE] Sync C2.0 and C2.1 branches
>
>
> Team,
>
> First round of Sync is done.....The "core" should be exactly the same. Experimental components and
> samples are left out of C2.0. Here's a list of the items that are only in C2.1 and NOT in C2.0
>
> 1) SiteBuilder Samples
> 2) SOAP Samples
> 3) Profiler and support files
> 4) XML:DB generators
> 5) DatabaseSelectAction.java
> 6) ScriptAction.java & ServerPagesAction.java
> 7) action.xsl and sel.xsl LogicSheets
> 8) CachingCIncludeTransformer and IncludeCacheValidity.java
> 9) JUnit based Test framework.
> 10) Script Action samples.
>
> If i have made any mistakes, please bear with me and let me know, i will fix or roll them back.
> Please go ahead and test C2.0. Let us try to get the "Release Candidate #1" out the door by end of
> next week (Sep 15, 2001).
>
> 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: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Davanum Srinivas <di...@yahoo.com>.
Team,
First round of Sync is done.....The "core" should be exactly the same. Experimental components and
samples are left out of C2.0. Here's a list of the items that are only in C2.1 and NOT in C2.0
1) SiteBuilder Samples
2) SOAP Samples
3) Profiler and support files
4) XML:DB generators
5) DatabaseSelectAction.java
6) ScriptAction.java & ServerPagesAction.java
7) action.xsl and sel.xsl LogicSheets
8) CachingCIncludeTransformer and IncludeCacheValidity.java
9) JUnit based Test framework.
10) Script Action samples.
If i have made any mistakes, please bear with me and let me know, i will fix or roll them back.
Please go ahead and test C2.0. Let us try to get the "Release Candidate #1" out the door by end of
next week (Sep 15, 2001).
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Sergio Carvalho <se...@acm.org>.
On Wed, 5 Sep 2001 08:26:46 -0700 (PDT), Davanum Srinivas wrote:
From: Davanum Srinivas <di...@yahoo.com>
--
Sorry, I managed to miss the vote on my current mail storm...
7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio
-1 from me. It needs a lot more features to be really more usefull than my
emacs :)
9) Better JSP Support - JspEngineImplWLS and JSPEngineImplNamedDispatcherInclude
from Bernhard
+1 from me. JSP has a huge deployed base, and is really important to allow
Cocoon to mingle with existing projects.
I'm neutral on all other votes.
--
Sergio Carvalho
---------------
sergio.carvalho@acm.org
If at first you don't succeed, skydiving is not for you
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Package and Constant Conventions [and a little Java 101] (was: Re:
[C2][VOTE - it is a new one] Sync C2.0 and C2.1 branches)
Posted by Berin Loritsch <bl...@apache.org>.
"Piroumian, Konstantin" wrote:
> > Samples should never be packaged with the main jar. They should be
> compiled
> > into the WEB-INF/classes/ directory. Use the package name:
> >
> > org.apache.cocoon.sample
> >
>
> Btw, should the actions be in the core? I noticed some action specific
> constants in the org.apache.cocoon.Constants (related to form validation).
We should probably clean that part up.
Cocooners,
We should probably come to a consensus as to where things belong. Our
code conventions cover most issues, but here are a few more good
idioms that we should probably adopt:
1) If a Constant is ONLY used by one Component (i.e. Action, Generator, etc),
that constant should be included inside the class that uses it.
2) If a Constant is used by all clients of a Work Interface, then that
constant should be included inside the interface that requires its
use.
3) If a Constant is not tied to an implementation OR an interface, then
(and only then) should it be placed in the org.apache.cocoon.Constants
interface.
4) All compiled code for samples should never be part of the Cocoon.jar,
the classes should be compiled into the WEB-INF/classes directory of
the samples webapp. We should use the package naming convention of
org.apache.cocoon.samples.{sampleName} where "{sampleName}" is replaced
with the name of the sample you are creating.
Idioms 1-3 can be summarized in an approach I use that helps me write
maintainable and predictable code:
"Localize as much as possible".
I have another one that says, "Always use Explicit scoping".
Those two approaches minimize the number of Classes and Interfaces you
must import to get your implementation working, and assures you that
you are using the correct variable.
Examples of Explicit Scoping:
static variable: ClassName.myStaticVariable;
static method: ClassName.staticMethod();
class variable: this.myClassVariable;
class method: this.myClassMethod();
super variable: super.superClassVariable;
super method: super.superClassMethod();
local variable: localVariable;
By using these common sense approaches, all your scope related bugs
go away. There were a number of bugs in my company's proprietary
software that dealt with novice programmers and scoping related
issues. Basically, they declared a class variable that they expected
to share for all the methods. In the initialization code, they
declared and initialized a LOCAL instance of the variable with the
same name as the class variable. The end result was that when
another method tried to use the class variable it didn't work.
Bad Example:
class Java101BadClass {
private JComboBox myCombo;
public Java101BadClass() {
// Note the local variable and class variable
// have the same name
JComboBox myCombo = new JComboBox();
// These methods are called on the local variable
myCombo.addItem("This");
myCombo.addItem("won't");
myCombo.addItem("show");
}
public JComboBox getBadInstance() {
// The class variable doesn't work, and the reason
// for it isn't all that obvious
return myCombo;
}
}
Good Example:
class Java101GoodClass {
private final JComboBox myCombo;
public Java101GoodClass() {
this.myCombo = new JComboBox();
this.myCombo.addItem("This");
this.myCombo.addItem("will");
this.myCombo.addItem("show");
}
public JComboBox getBadInstance() {
// The class variable works
return this.myCombo;
}
}
In the above example, even if you made the same mistake with
creating a local variable with the same name the code will
fail earlier and the cause would be much more obvious. In
fact, some compilers might warn you that the variable may not
have been initialized (only works with final class variables)!
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE - it is a new one] Sync C2.0 and C2.1 branches
Posted by "Piroumian, Konstantin" <KP...@flagship.ru>.
> > - Package name for sample components.
org.apache.cocoon.components.sample?
> > (Will move the parent component manager here as well.)
>
> Samples should never be packaged with the main jar. They should be
compiled
> into the WEB-INF/classes/ directory. Use the package name:
>
> org.apache.cocoon.sample
>
Btw, should the actions be in the core? I noticed some action specific
constants in the org.apache.cocoon.Constants (related to form validation).
Konstantin
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2][VOTE - it is a new one] Sync C2.0 and C2.1 branches
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
> Sent: den 6 september 2001 15:02
> To: cocoon-dev@xml.apache.org
> Subject: Re: [C2][VOTE - it is a new one] Sync C2.0 and C2.1 branches
>
> I like your vision. Can you pull it off in time?
Starting now. Shouldn't take more than a few hours for the sample and then
some for the documentation as I have everything fresh in memory. The major
hurdle is the changes that made C2.1 incompatible with C2.0. If I can't get
the CVS version to work on my machine then I have problems.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE - it is a new one] Sync C2.0 and C2.1 branches
Posted by Berin Loritsch <bl...@apache.org>.
Leo Sutic wrote:
>
> > -----Original Message-----
> > From: Berin Loritsch [mailto:bloritsch@apache.org]
> >
> > Davanum Srinivas wrote:
> > > > 10) Parent Component Manager Support - Specify a configurable
> > parent Component Manager from Leo
> > >
> > > Carsten : +1
> > > Berin : +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
> > > Giacomo : +1
> > > John : +1
> > > Dims : +1 But we need better documentation for this.
>
> Berin, Dims,
>
> I have yet to see it in full action myself. I am considering classloader/RMI
> regarding how one would use it in a clustered environment. At the moment the
> best choice seems to be a parent component manager that:
>
> 1) Looks up a Configuration instance via JNDI.
> 2) Instantiates an ExcaliburComponentManager with that configuration.
> 3) Delegates all lookup/release messages to that instance.
This is probably the best and most preferred approach.
> Remote objects would be handled by specifying in the configuration an
> implementing class that looks up and delegates everything to the remote
> object. Since we're using the factory pattern here it can be changed, but
> I'd like to have some way of doing it that enables me to write in the docs
> that "this is the preferred way of doing it".
Ok. Keep in mind that Remote objects that are core to Cocoon are a bad
idea--it will bring Cocoon to a crawl.
> Having the feature in C2.0 is good for me because it meshes quite well with
> my own development roadmap. The alternative would be to fork the involved
> classes until C2.1 becomes ready for use and that's a mess I do not even
> want to think about.
>
> The downside is that it is a feature without a preferred usage pattern, with
> almost nonexistent documentation and with nothing but a trivial example.
>
> What I see as needed from me before the release candidate is:
>
> - xdocs/parent-component-manager.xml
> - A sample involving the preferred method outlined above which I think will
> be:
> - A component that gives you the current time.
> - A small server that binds a Configuration object to a JNDI name,
> probably via the Excalibur naming package.
There are two implementations: a pure in-memory JNDI solution and an RMI
solution. Choose wisely.
> - A CM that looks up the Configuration and does you-know-what.
> - A generator that looks up the time component and emits the current
> time-of-day.
> - A stylesheet to present the time.
>
> The "small server" part is the hard one. I am considering putting everything
> into a static initializer for a class and then specifying that class in the
> load-class init parameter in web.xml.
>
> So what I need to know is:
>
> - Package name for sample components. org.apache.cocoon.components.sample?
> (Will move the parent component manager here as well.)
Samples should never be packaged with the main jar. They should be compiled
into the WEB-INF/classes/ directory. Use the package name:
org.apache.cocoon.sample
> - Do we have an agreement on the preferred method.
I like your vision. Can you pull it off in time?
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
[C2][VOTE - it is a new one] Sync C2.0 and C2.1 branches
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> -----Original Message-----
> From: Berin Loritsch [mailto:bloritsch@apache.org]
>
> Davanum Srinivas wrote:
> > > 10) Parent Component Manager Support - Specify a configurable
> parent Component Manager from Leo
> >
> > Carsten : +1
> > Berin : +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
> > Giacomo : +1
> > John : +1
> > Dims : +1 But we need better documentation for this.
Berin, Dims,
I have yet to see it in full action myself. I am considering classloader/RMI
regarding how one would use it in a clustered environment. At the moment the
best choice seems to be a parent component manager that:
1) Looks up a Configuration instance via JNDI.
2) Instantiates an ExcaliburComponentManager with that configuration.
3) Delegates all lookup/release messages to that instance.
Remote objects would be handled by specifying in the configuration an
implementing class that looks up and delegates everything to the remote
object. Since we're using the factory pattern here it can be changed, but
I'd like to have some way of doing it that enables me to write in the docs
that "this is the preferred way of doing it".
Having the feature in C2.0 is good for me because it meshes quite well with
my own development roadmap. The alternative would be to fork the involved
classes until C2.1 becomes ready for use and that's a mess I do not even
want to think about.
The downside is that it is a feature without a preferred usage pattern, with
almost nonexistent documentation and with nothing but a trivial example.
What I see as needed from me before the release candidate is:
- xdocs/parent-component-manager.xml
- A sample involving the preferred method outlined above which I think will
be:
- A component that gives you the current time.
- A small server that binds a Configuration object to a JNDI name,
probably via the Excalibur naming package.
- A CM that looks up the Configuration and does you-know-what.
- A generator that looks up the time component and emits the current
time-of-day.
- A stylesheet to present the time.
The "small server" part is the hard one. I am considering putting everything
into a static initializer for a class and then specifying that class in the
load-class init parameter in web.xml.
So what I need to know is:
- Package name for sample components. org.apache.cocoon.components.sample?
(Will move the parent component manager here as well.)
- Do we have an agreement on the preferred method.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Berin Loritsch <bl...@apache.org>.
Davanum Srinivas wrote:
>
> Team,
> Here's a summary of the VOTE so far. If anyone has not voted yet, please add your vote below:
Everything that has clean +1 sweeps we can go ahead and implement.
Everything with clean +/-0 sweeps we should either hold off or use
the "if there's time" approach.
Anything with a -1 either needs more diliberation (there is a couple I
was the odd man out, and I might be convinced to change my stance) or
should be axed from the immediate todo list.
Anything with a clean -1 sweep should be axed from the backporting list.
>
> Thanks,
> dims
>
> --- Berin Loritsch <bl...@apache.org> wrote:
> > 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
>
> Carsten : +0 (These are additional components which do not affect the core)
> Berin : -1 This should be reason to upgrade, not necessary or as well tested as other C2.0
> generators.
> Giacomo : +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'])?
> John : +0
> Dims : +0 Need out of the box samples
>
> > 2) FOP Serializers / Renderer Components - C2.1 has a configurable, SAX based Serializer that
> supports PCL, PS and PDF.
>
> Carsten : +1 (I tend to think that the FOP serializer belongs to the core)
> Berin : +1 Latest FOP makes it easier to create XSL:FO documents and see expected results.
> Giacomo : +1
> John : +1 This shouldn't impact anyone currently using 2.0
> Dims : +1
>
> > 3) JUnit based Test cases - C2.1 has a framework for test cases from Stuart
>
> Carsten : +0
> Berin : +0 Avalon uses JUnit for Test cases, and I am all for it--this is somewhat lower
> priority though.
> Giacomo : +0
> John : +0 Good for 2.1 - required for 2.0? Prob not.
> Dims : +0 We need to work start adding more of them.
>
> > 4) Source Interface changes - C2.1 has changes from Ovidiu for better core implementation.
>
> Carsten : +5 (Important core changes)
> Berin : +1 The API should be stable when we release C2.0
> Giacomo : +1
> John : +1 Best to try and keep the core in sync
> Dims : +5 We need to keep the core in sync.
>
> > 5) LogKit mechanism - C2.1 has better support for log messages from Giacomo
> Carsten : +5 (Great work from Giacomo)
> Berin : +10 Fine grained control of the Loggers is definitely needed. This allows us to pay
> attention only to the information we want to see.
> Giacomo : +1, thanks :)
> John : +1 Seconded!
> Dims : +5
>
> > 6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.
>
> Carsten : +0 to +1 (could make SITE maintanance a bit easier?)
> Berin : -0 It would be nice to have, but the first thing I would ax on a time crunch
> Giacomo : +1
> John : +1
> Dims : +0 Maybe later for C2.1
>
> > 7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio
>
> Carsten : Haven't tested it yet.
> Berin : -10 SiteBuilder is in its infancy, I would like to see it mature before being in a
> cocoon release
> Giacomo : -0. I still see it throwing exceptions.
> John : I've not used this either
> Dims : -1 Definitely needs more work
>
> > 8) Catalog Support - Entity Catalog support from David Crossley
>
> Carsten : +1
> Berin : +.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.
> Giacomo : +1
> John : Or this - but I can see why it's needed! (+1)
> Dims : +1
>
> > 9) Better JSP Support - JspEngineImplWLS and JSPEngineImplNamedDispatcherInclude from Bernhard
>
> Carsten : +1
> Berin : -0 I don't use JSP, so there is little for me to gain here. (I am biased though).
> Giacomo : +0
> John : 0 - I don't use JSP
> Dims : +1 Some people need it.
>
> > 10) Parent Component Manager Support - Specify a configurable parent Component Manager from Leo
>
> Carsten : +1
> Berin : +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
> Giacomo : +1
> John : +1
> Dims : +1 But we need better documentation for this.
>
> > 11) XSLTProcessor + TRaX Transformer update - componentize TRaX support from Ovidiu
>
> Carsten : +1 (core changes)
> Berin : +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.
> Giacomo : +1
> John : +1
> Dims : +1 - We should also check our SAXON support to see if anything is broken
>
> > 12) Simple Profiler and related Event Pipelines - Profiler Support from Vadim
>
> Carsten : +1 (could help in starting with C2)
> Berin : -1 I like profiler support, but this should be for C2.1
> Giacomo : +0. Don't know the stability of it.
> John : +0 I need to look into this soon...
> Dims : -1 Need to flesh it out.
>
> > 13) DatabaseSelectionAction.java
>
> Carsten : +0
> Berin : +1 This eases form development
> Giacomo : +0 Didn't know this is in 2.1 only.
> John : +0 Don't use...
> Dims : +0 Have not used it.
>
> > 14) ScriptAction.java
>
> Carsten : +1 (simple writing of actions)
> Berin : -1 Leave for C2.1 and make sure it works well
> Giacomo : +1
> John : +0 Again, don't use.
> Dims : +0 Haven't used it.
>
> > 15) ServerPagesAction.java / action.xsl
>
> Carsten : +0
> Berin : -1 We need to see this mature a little more.
> Giacomo : -0
> John : +0 guess what...
> Dims : +0 Maybe later
>
> > 16) IncludeCacheValidity.java and CachingCIncludeTransformer.java
>
> Carsten : -1 (it depends on to many internal assumptions right now)
> Berin : +1 It would speed up so many things for me.
> Giacomo : +0 Don't know its state.
> John : +0
> Dims : +1 Need to test...
>
> > 17) Updated AbstractMarkupLanguage.java, LogicSheet.java, NamedLogicSheet.java.
>
> Carsten : If this affects core changes +1
> Berin : +1
> Giacomo : +1
> John : Agreed +1
> Dims : +1 definitely
>
> > 18) Slightly updated HttpRequest.java.
>
> Carsten : +1
> Berin : +1
> Giacomo : +1
> John : +1
> Dims : +1
>
> > 19) Updated EnvironmentWrapper.java.
>
> Carsten : +1
> Berin : +1
> Giacomo : +1
> John : +1
> Dims : +1
>
> > 20) Updated Directory/File Generator.java
>
> Carsten : +1
> Berin : +1
> Giacomo : +1
> John : +1
> Dims : +1
>
> > 21) updated i18n Transformer.
>
> Carsten : +1
> Berin : +1
> Giacomo : +5
> John : +1
> Dims : +1
>
> > 22) Trivial SOAP samples.
>
> Carsten : +1 (Examples, yes!)
> Berin : -1 This is new functionality that should probably wait.
> Giacomo : +0
> John : +0 I do think that it's xsl files ought to be moved from docs/samples/soap though...
> Dims : -1 Need SOAP Taglib from Ovidiu
>
> > 23) RoleFilterTransformer.java
>
> Carsten : What's this? I must have missed it.
> Berin : -1 I wrote it, but I know it needs a bit more testing
> Giacomo : +0
> John : +0
> Dims : -1 Needs samples too.
>
> > 24) CocoonTargetFactory.java
>
> Carsten : What's this? I must have missed it, too.
> Berin : -0 I am not familiar with this piece of code
> Giacomo : 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.
> John : No Vote Needed as per Giacomo.
> Dims : No Vote Needed as per Giacomo.
>
> > 25) XMLizable interface
>
> Carsten : +1
> Berin : -1 Additional API is acceptable--changed API makes people mad.
> Giacomo : +1
> John : +1
> Dims : +1 as this is part of the Source changes (?)
>
> > 26) SEL taglib
>
> Carsten : +0
> Berin : -0 I am not familiar with this. If it is XSPAction related then -1 for afforementioned
> reasons
> Giacomo : +0 What the hell is this. Must have missed it.
> John : 0 Me too!
> Dims : +0
>
> > 27) Action taglib
>
> Carsten : +0
> Berin : -1 Goes with XSP Action above.
> Giacomo : +0
> John : +0
> Dims : +0
>
> > 28) More sub sitemap samples.
>
> Carsten : +5 (yes, examples!)
> Berin : -0 Again it is probably trivial--but I would ax it when faced with a time crunch
> Giacomo : +1
> John : +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?
> Dims : +1 Need to test it.
>
> =====
> 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: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Torsten Curdt <tc...@dff.st>.
> > > 26) SEL taglib
> >
> > Carsten : +0
> > Berin : -0 I am not familiar with this. If it is XSPAction related then -1 for afforementioned
> > reasons
> > Giacomo : +0 What the hell is this. Must have missed it.
> > John : 0 Me too!
> > Dims : +0
...to a solve a great mystery ;)
with the sel(ection) taglib you can divide your XSP page into
different parts than can be selected via e.g. sitemap or request
parameters. This CAN be used for a install-wizard-like page
navigation.
It shares some of the aims of the FragmentExtractorTransformer
and is not XSPAction related.
PS: I just read somewhere that voting is for committers only. Sorry, for
my inappropriate votes on foregoing votes. Didn't know that.
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
RE: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Vadim Gritsenko <vg...@hns.com>.
> -----Original Message-----
> From: Davanum Srinivas [mailto:dims@yahoo.com]
> Sent: Wednesday, September 05, 2001 11:27 AM
> To: cocoon-dev@xml.apache.org
> Subject: Re: [C2][VOTE] Sync C2.0 and C2.1 branches
>
>
> Team,
> Here's a summary of the VOTE so far. If anyone has not voted yet, please add your vote below:
>
> Thanks,
> dims
>
> --- Berin Loritsch <bl...@apache.org> wrote:
> > 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
>
> Carsten : +0 (These are additional components which do not affect the core)
> Berin : -1 This should be reason to upgrade, not necessary or as well tested as other C2.0
> generators.
> Giacomo : +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'])?
> John : +0
> Dims : +0 Need out of the box samples
+0. Needs caching (if possible) and samples.
>
> > 2) FOP Serializers / Renderer Components - C2.1 has a configurable, SAX based Serializer that
> supports PCL, PS and PDF.
>
> Carsten : +1 (I tend to think that the FOP serializer belongs to the core)
> Berin : +1 Latest FOP makes it easier to create XSL:FO documents and see expected results.
> Giacomo : +1
> John : +1 This shouldn't impact anyone currently using 2.0
> Dims : +1
+1
>
> > 3) JUnit based Test cases - C2.1 has a framework for test cases from Stuart
>
> Carsten : +0
> Berin : +0 Avalon uses JUnit for Test cases, and I am all for it--this is somewhat lower
> priority though.
> Giacomo : +0
> John : +0 Good for 2.1 - required for 2.0? Prob not.
> Dims : +0 We need to work start adding more of them.
+0
>
> > 4) Source Interface changes - C2.1 has changes from Ovidiu for better core implementation.
>
> Carsten : +5 (Important core changes)
> Berin : +1 The API should be stable when we release C2.0
> Giacomo : +1
> John : +1 Best to try and keep the core in sync
> Dims : +5 We need to keep the core in sync.
+1
>
> > 5) LogKit mechanism - C2.1 has better support for log messages from Giacomo
> Carsten : +5 (Great work from Giacomo)
> Berin : +10 Fine grained control of the Loggers is definitely needed. This allows us to pay
> attention only to the information we want to see.
> Giacomo : +1, thanks :)
> John : +1 Seconded!
> Dims : +5
+5
>
> > 6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.
>
> Carsten : +0 to +1 (could make SITE maintanance a bit easier?)
> Berin : -0 It would be nice to have, but the first thing I would ax on a time crunch
> Giacomo : +1
> John : +1
> Dims : +0 Maybe later for C2.1
+0 to +1.
>
> > 7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio
>
> Carsten : Haven't tested it yet.
> Berin : -10 SiteBuilder is in its infancy, I would like to see it mature before being in a
> cocoon release
> Giacomo : -0. I still see it throwing exceptions.
> John : I've not used this either
> Dims : -1 Definitely needs more work
0
>
> > 8) Catalog Support - Entity Catalog support from David Crossley
>
> Carsten : +1
> Berin : +.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.
> Giacomo : +1
> John : Or this - but I can see why it's needed! (+1)
> Dims : +1
+0
>
> > 9) Better JSP Support - JspEngineImplWLS and JSPEngineImplNamedDispatcherInclude from Bernhard
>
> Carsten : +1
> Berin : -0 I don't use JSP, so there is little for me to gain here. (I am biased though).
> Giacomo : +0
> John : 0 - I don't use JSP
> Dims : +1 Some people need it.
+1. JSPReader also would be nice component to have.
>
> > 10) Parent Component Manager Support - Specify a configurable parent Component Manager from Leo
>
> Carsten : +1
> Berin : +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
> Giacomo : +1
> John : +1
> Dims : +1 But we need better documentation for this.
+0
>
> > 11) XSLTProcessor + TRaX Transformer update - componentize TRaX support from Ovidiu
>
> Carsten : +1 (core changes)
> Berin : +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.
> Giacomo : +1
> John : +1
> Dims : +1 - We should also check our SAXON support to see if anything is broken
+1
>
> > 12) Simple Profiler and related Event Pipelines - Profiler Support from Vadim
>
> Carsten : +1 (could help in starting with C2)
> Berin : -1 I like profiler support, but this should be for C2.1
> Giacomo : +0. Don't know the stability of it.
> John : +0 I need to look into this soon...
> Dims : -1 Need to flesh it out.
+0
>
> > 13) DatabaseSelectionAction.java
>
> Carsten : +0
> Berin : +1 This eases form development
> Giacomo : +0 Didn't know this is in 2.1 only.
> John : +0 Don't use...
> Dims : +0 Have not used it.
+0.5. Also would be nice to keep syntax of Database*Action descriptors in sync
>
> > 14) ScriptAction.java
>
> Carsten : +1 (simple writing of actions)
> Berin : -1 Leave for C2.1 and make sure it works well
> Giacomo : +1
> John : +0 Again, don't use.
> Dims : +0 Haven't used it.
+0
>
> > 15) ServerPagesAction.java / action.xsl
>
> Carsten : +0
> Berin : -1 We need to see this mature a little more.
> Giacomo : -0
> John : +0 guess what...
> Dims : +0 Maybe later
+0
>
> > 16) IncludeCacheValidity.java and CachingCIncludeTransformer.java
>
> Carsten : -1 (it depends on to many internal assumptions right now)
> Berin : +1 It would speed up so many things for me.
> Giacomo : +0 Don't know its state.
> John : +0
> Dims : +1 Need to test...
0
>
> > 17) Updated AbstractMarkupLanguage.java, LogicSheet.java, NamedLogicSheet.java.
>
> Carsten : If this affects core changes +1
> Berin : +1
> Giacomo : +1
> John : Agreed +1
> Dims : +1 definitely
+1
>
> > 18) Slightly updated HttpRequest.java.
>
> Carsten : +1
> Berin : +1
> Giacomo : +1
> John : +1
> Dims : +1
+1
>
>
> > 19) Updated EnvironmentWrapper.java.
>
> Carsten : +1
> Berin : +1
> Giacomo : +1
> John : +1
> Dims : +1
+1
>
> > 20) Updated Directory/File Generator.java
>
> Carsten : +1
> Berin : +1
> Giacomo : +1
> John : +1
> Dims : +1
+1
>
> > 21) updated i18n Transformer.
>
> Carsten : +1
> Berin : +1
> Giacomo : +5
> John : +1
> Dims : +1
+0
>
> > 22) Trivial SOAP samples.
>
> Carsten : +1 (Examples, yes!)
> Berin : -1 This is new functionality that should probably wait.
> Giacomo : +0
> John : +0 I do think that it's xsl files ought to be moved from docs/samples/soap though...
> Dims : -1 Need SOAP Taglib from Ovidiu
0
>
> > 23) RoleFilterTransformer.java
>
> Carsten : What's this? I must have missed it.
> Berin : -1 I wrote it, but I know it needs a bit more testing
> Giacomo : +0
> John : +0
> Dims : -1 Needs samples too.
0
>
> > 24) CocoonTargetFactory.java
>
> Carsten : What's this? I must have missed it, too.
> Berin : -0 I am not familiar with this piece of code
> Giacomo : 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.
> John : No Vote Needed as per Giacomo.
> Dims : No Vote Needed as per Giacomo.
>
> > 25) XMLizable interface
>
> Carsten : +1
> Berin : -1 Additional API is acceptable--changed API makes people mad.
> Giacomo : +1
> John : +1
> Dims : +1 as this is part of the Source changes (?)
+0
>
> > 26) SEL taglib
>
> Carsten : +0
> Berin : -0 I am not familiar with this. If it is XSPAction related then -1 for afforementioned
> reasons
> Giacomo : +0 What the hell is this. Must have missed it.
> John : 0 Me too!
> Dims : +0
0
>
> > 27) Action taglib
>
> Carsten : +0
> Berin : -1 Goes with XSP Action above.
> Giacomo : +0
> John : +0
> Dims : +0
0
>
> > 28) More sub sitemap samples.
>
> Carsten : +5 (yes, examples!)
> Berin : -0 Again it is probably trivial--but I would ax it when faced with a time crunch
> Giacomo : +1
> John : +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?
> Dims : +1 Need to test it.
+1
Vadim
>
>
>
>
> =====
> Davanum Srinivas, JNI-FAQ Manager
> http://www.jGuru.com/faq/JNI
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Davanum Srinivas <di...@yahoo.com>.
Team,
Here's a summary of the VOTE so far. If anyone has not voted yet, please add your vote below:
Thanks,
dims
--- Berin Loritsch <bl...@apache.org> wrote:
> 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
Carsten : +0 (These are additional components which do not affect the core)
Berin : -1 This should be reason to upgrade, not necessary or as well tested as other C2.0
generators.
Giacomo : +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'])?
John : +0
Dims : +0 Need out of the box samples
> 2) FOP Serializers / Renderer Components - C2.1 has a configurable, SAX based Serializer that
supports PCL, PS and PDF.
Carsten : +1 (I tend to think that the FOP serializer belongs to the core)
Berin : +1 Latest FOP makes it easier to create XSL:FO documents and see expected results.
Giacomo : +1
John : +1 This shouldn't impact anyone currently using 2.0
Dims : +1
> 3) JUnit based Test cases - C2.1 has a framework for test cases from Stuart
Carsten : +0
Berin : +0 Avalon uses JUnit for Test cases, and I am all for it--this is somewhat lower
priority though.
Giacomo : +0
John : +0 Good for 2.1 - required for 2.0? Prob not.
Dims : +0 We need to work start adding more of them.
> 4) Source Interface changes - C2.1 has changes from Ovidiu for better core implementation.
Carsten : +5 (Important core changes)
Berin : +1 The API should be stable when we release C2.0
Giacomo : +1
John : +1 Best to try and keep the core in sync
Dims : +5 We need to keep the core in sync.
> 5) LogKit mechanism - C2.1 has better support for log messages from Giacomo
Carsten : +5 (Great work from Giacomo)
Berin : +10 Fine grained control of the Loggers is definitely needed. This allows us to pay
attention only to the information we want to see.
Giacomo : +1, thanks :)
John : +1 Seconded!
Dims : +5
> 6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.
Carsten : +0 to +1 (could make SITE maintanance a bit easier?)
Berin : -0 It would be nice to have, but the first thing I would ax on a time crunch
Giacomo : +1
John : +1
Dims : +0 Maybe later for C2.1
> 7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio
Carsten : Haven't tested it yet.
Berin : -10 SiteBuilder is in its infancy, I would like to see it mature before being in a
cocoon release
Giacomo : -0. I still see it throwing exceptions.
John : I've not used this either
Dims : -1 Definitely needs more work
> 8) Catalog Support - Entity Catalog support from David Crossley
Carsten : +1
Berin : +.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.
Giacomo : +1
John : Or this - but I can see why it's needed! (+1)
Dims : +1
> 9) Better JSP Support - JspEngineImplWLS and JSPEngineImplNamedDispatcherInclude from Bernhard
Carsten : +1
Berin : -0 I don't use JSP, so there is little for me to gain here. (I am biased though).
Giacomo : +0
John : 0 - I don't use JSP
Dims : +1 Some people need it.
> 10) Parent Component Manager Support - Specify a configurable parent Component Manager from Leo
Carsten : +1
Berin : +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
Giacomo : +1
John : +1
Dims : +1 But we need better documentation for this.
> 11) XSLTProcessor + TRaX Transformer update - componentize TRaX support from Ovidiu
Carsten : +1 (core changes)
Berin : +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.
Giacomo : +1
John : +1
Dims : +1 - We should also check our SAXON support to see if anything is broken
> 12) Simple Profiler and related Event Pipelines - Profiler Support from Vadim
Carsten : +1 (could help in starting with C2)
Berin : -1 I like profiler support, but this should be for C2.1
Giacomo : +0. Don't know the stability of it.
John : +0 I need to look into this soon...
Dims : -1 Need to flesh it out.
> 13) DatabaseSelectionAction.java
Carsten : +0
Berin : +1 This eases form development
Giacomo : +0 Didn't know this is in 2.1 only.
John : +0 Don't use...
Dims : +0 Have not used it.
> 14) ScriptAction.java
Carsten : +1 (simple writing of actions)
Berin : -1 Leave for C2.1 and make sure it works well
Giacomo : +1
John : +0 Again, don't use.
Dims : +0 Haven't used it.
> 15) ServerPagesAction.java / action.xsl
Carsten : +0
Berin : -1 We need to see this mature a little more.
Giacomo : -0
John : +0 guess what...
Dims : +0 Maybe later
> 16) IncludeCacheValidity.java and CachingCIncludeTransformer.java
Carsten : -1 (it depends on to many internal assumptions right now)
Berin : +1 It would speed up so many things for me.
Giacomo : +0 Don't know its state.
John : +0
Dims : +1 Need to test...
> 17) Updated AbstractMarkupLanguage.java, LogicSheet.java, NamedLogicSheet.java.
Carsten : If this affects core changes +1
Berin : +1
Giacomo : +1
John : Agreed +1
Dims : +1 definitely
> 18) Slightly updated HttpRequest.java.
Carsten : +1
Berin : +1
Giacomo : +1
John : +1
Dims : +1
> 19) Updated EnvironmentWrapper.java.
Carsten : +1
Berin : +1
Giacomo : +1
John : +1
Dims : +1
> 20) Updated Directory/File Generator.java
Carsten : +1
Berin : +1
Giacomo : +1
John : +1
Dims : +1
> 21) updated i18n Transformer.
Carsten : +1
Berin : +1
Giacomo : +5
John : +1
Dims : +1
> 22) Trivial SOAP samples.
Carsten : +1 (Examples, yes!)
Berin : -1 This is new functionality that should probably wait.
Giacomo : +0
John : +0 I do think that it's xsl files ought to be moved from docs/samples/soap though...
Dims : -1 Need SOAP Taglib from Ovidiu
> 23) RoleFilterTransformer.java
Carsten : What's this? I must have missed it.
Berin : -1 I wrote it, but I know it needs a bit more testing
Giacomo : +0
John : +0
Dims : -1 Needs samples too.
> 24) CocoonTargetFactory.java
Carsten : What's this? I must have missed it, too.
Berin : -0 I am not familiar with this piece of code
Giacomo : 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.
John : No Vote Needed as per Giacomo.
Dims : No Vote Needed as per Giacomo.
> 25) XMLizable interface
Carsten : +1
Berin : -1 Additional API is acceptable--changed API makes people mad.
Giacomo : +1
John : +1
Dims : +1 as this is part of the Source changes (?)
> 26) SEL taglib
Carsten : +0
Berin : -0 I am not familiar with this. If it is XSPAction related then -1 for afforementioned
reasons
Giacomo : +0 What the hell is this. Must have missed it.
John : 0 Me too!
Dims : +0
> 27) Action taglib
Carsten : +0
Berin : -1 Goes with XSP Action above.
Giacomo : +0
John : +0
Dims : +0
> 28) More sub sitemap samples.
Carsten : +5 (yes, examples!)
Berin : -0 Again it is probably trivial--but I would ax it when faced with a time crunch
Giacomo : +1
John : +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?
Dims : +1 Need to test it.
=====
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: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Berin Loritsch <bl...@apache.org>.
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: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Carsten Ziegeler <cz...@sundn.de>:
> > Giacomo Pati wrote:
> >
> > Quoting Gianugo Rabellino <g....@bibop.it>:
> >
> > > On Wed, Sep 05, 2001 at 08:38:55AM +0200, Giacomo Pati wrote:
> > > > > > 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'])?
> > >
> > > More than willing to add this feature, but I need to look deep
> inside
> > > Cocoon internals to understand exactly how to do it. Any starting
> > > points? :)
> >
> > I'm not sure if the URLFactory is still the way to go since we
> > have the Source
> > interface (Carsten?).
> >
> There are two possibilities: The URLFactory and the SourceFactory.
> If your protocol can be mapped to an existing (= from the jdk supported
> protocol), e.g. to http, you can simply implement a URL factory.
> The URLFactory would create e.g. from dbxml:/hallo the real URL
> "http://dbserver/hallo".
> Examples for this a the Resource and the Context factory.
Yes, now I remember again. URLFactory is for mapping custom protocols onto a
real java supported protocol.
> If this is not possible, you have to implement a SourceFactory
> which does not create java.net.URL objects but
> org.apache.cocoon.environment.Source
> objects. Examples for this are the SourceHandlerImpl and the
> CocoonSourceFactory.
>
> The Source interface is very simple and straightforward, you can
> look at the URLSource implementation.
So, for the dbxml if think a SourceFactory will be the way to go.
Giacomo
>
> Carsten
>
> > Giacomo
> >
> > >
> > > Ciao,
> > >
> > > --
> > > Gianugo Rabellino
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: cocoon-dev-help@xml.apache.org
> > >
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Carsten Ziegeler <cz...@sundn.de>.
> Giacomo Pati wrote:
>
> Quoting Gianugo Rabellino <g....@bibop.it>:
>
> > On Wed, Sep 05, 2001 at 08:38:55AM +0200, Giacomo Pati wrote:
> > > > > 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'])?
> >
> > More than willing to add this feature, but I need to look deep inside
> > Cocoon internals to understand exactly how to do it. Any starting
> > points? :)
>
> I'm not sure if the URLFactory is still the way to go since we
> have the Source
> interface (Carsten?).
>
There are two possibilities: The URLFactory and the SourceFactory.
If your protocol can be mapped to an existing (= from the jdk supported
protocol), e.g. to http, you can simply implement a URL factory.
The URLFactory would create e.g. from dbxml:/hallo the real URL
"http://dbserver/hallo".
Examples for this a the Resource and the Context factory.
If this is not possible, you have to implement a SourceFactory
which does not create java.net.URL objects but
org.apache.cocoon.environment.Source
objects. Examples for this are the SourceHandlerImpl and the
CocoonSourceFactory.
The Source interface is very simple and straightforward, you can
look at the URLSource implementation.
Carsten
> Giacomo
>
> >
> > Ciao,
> >
> > --
> > Gianugo Rabellino
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> > For additional commands, email: cocoon-dev-help@xml.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Gianugo Rabellino <g....@bibop.it>:
> On Wed, Sep 05, 2001 at 08:38:55AM +0200, Giacomo Pati wrote:
> > > > 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'])?
>
> More than willing to add this feature, but I need to look deep inside
> Cocoon internals to understand exactly how to do it. Any starting
> points? :)
I'm not sure if the URLFactory is still the way to go since we have the Source
interface (Carsten?).
Giacomo
>
> Ciao,
>
> --
> Gianugo Rabellino
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Gianugo Rabellino <g....@bibop.it>.
On Wed, Sep 05, 2001 at 08:38:55AM +0200, Giacomo Pati wrote:
> > > 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'])?
More than willing to add this feature, but I need to look deep inside
Cocoon internals to understand exactly how to do it. Any starting
points? :)
Ciao,
--
Gianugo Rabellino
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Giacomo Pati <gi...@apache.org>.
Quoting Carsten Ziegeler <cz...@sundn.de>:
> 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'])?
> > 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
> > 3) JUnit based Test cases - C2.1 has a framework for test cases
> > from Stuart
> +0
+0
> > 4) Source Interface changes - C2.1 has changes from Ovidiu for
> > better core implementation.
> +5 (Important core changes)
+1
> > 5) LogKit mechanism - C2.1 has better support for log messages
> > from Giacomo
> +5 (Great work from Giacomo)
+1, thanks :)
> > 6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.
> +0 to +1 (could make SITE maintanance a bit easier?)
+1
> > 7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio
> Haven't tested it yet.
-0. I still see it throwing exceptions.
> > 8) Catalog Support - Entity Catalog support from David Crossley
> +1
+1
> > 9) Better JSP Support - JspEngineImplWLS and
> > JSPEngineImplNamedDispatcherInclude from Bernhard
> +1
+0
> > 10) Parent Component Manager Support - Specify a configurable
> > parent Component Manager from Leo
> +1
+1
> > 11) XSLTProcessor + TRaX Transformer update - componentize TRaX
> > support from Ovidiu
> +1 (core changes)
+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.
> > 13) DatabaseSelectionAction.java
> +0
+0 Didn't know this is in 2.1 only.
> > 14) ScriptAction.java
> +1 (simple writing of actions)
+1
> > 15) ServerPagesAction.java / action.xsl
> +0
-0
> > 16) IncludeCacheValidity.java and CachingCIncludeTransformer.java
> -1 (it depends on to many internal assumptions right now)
+0 Don't know its state.
> > 17) Updated AbstractMarkupLanguage.java, LogicSheet.java,
> > NamedLogicSheet.java.
> If this affects core changes +1
+1
> > 18) Slightly updated HttpRequest.java.
> +1
+1
> > 19) Updated EnvironmentWrapper.java.
> +1
+1
> > 20) Updated Directory/File Generator.java
> +1
+1
> > 21) updated i18n Transformer.
> +1
+5
> > 22) Trivial SOAP samples.
> +1 (Examples, yes!)
+0
> > 23) RoleFilterTransformer.java
> What's this? I must have missed it.
+0
> > 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.
> > 25) XMLizable interface
> +1
+1
> > 26) SEL taglib
> +0
+0 What the hell is this. Must have missed it.
> > 27) Action taglib
> +0
+0
> > 28) More sub sitemap samples.
> +5 (yes, examples!)
+1
Hey, Dims, your work in keeping track what is happening in the code base is
great. many thanks.
Giacomo
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
AW: [C2][VOTE] Sync C2.0 and C2.1 branches
Posted by Carsten Ziegeler <cz...@sundn.de>.
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)
> 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)
> 3) JUnit based Test cases - C2.1 has a framework for test cases
> from Stuart
+0
> 4) Source Interface changes - C2.1 has changes from Ovidiu for
> better core implementation.
+5 (Important core changes)
> 5) LogKit mechanism - C2.1 has better support for log messages
> from Giacomo
+5 (Great work from Giacomo)
> 6) Site WEBAPP - Separate Webapp for SITE from Donald Ball.
+0 to +1 (could make SITE maintanance a bit easier?)
> 7) SiteBuilder - Sitemap editor cocoon app contribution from Sergio
Haven't tested it yet.
> 8) Catalog Support - Entity Catalog support from David Crossley
+1
> 9) Better JSP Support - JspEngineImplWLS and
> JSPEngineImplNamedDispatcherInclude from Bernhard
+1
> 10) Parent Component Manager Support - Specify a configurable
> parent Component Manager from Leo
+1
> 11) XSLTProcessor + TRaX Transformer update - componentize TRaX
> support from Ovidiu
+1 (core changes)
> 12) Simple Profiler and related Event Pipelines - Profiler
> Support from Vadim
+1 (could help in starting with C2)
> 13) DatabaseSelectionAction.java
+0
> 14) ScriptAction.java
+1 (simple writing of actions)
> 15) ServerPagesAction.java / action.xsl
+0
> 16) IncludeCacheValidity.java and CachingCIncludeTransformer.java
-1 (it depends on to many internal assumptions right now)
> 17) Updated AbstractMarkupLanguage.java, LogicSheet.java,
> NamedLogicSheet.java.
If this affects core changes +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 (Examples, yes!)
> 23) RoleFilterTransformer.java
What's this? I must have missed it.
> 24) CocoonTargetFactory.java
What's this? I must have missed it, too.
> 25) XMLizable interface
+1
> 26) SEL taglib
+0
> 27) Action taglib
+0
> 28) More sub sitemap samples.
+5 (yes, examples!)
>
> 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: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org