Hi Roy
Sorry, no progress, I am busy on a commercial project at the
moment .
Will get back to it soon I hope
regards Jeremy
On 22 Jan 2009, at 09:46, lingerer huang wrote:
Hi,Jeremy
Is there any progress?I know it is not appropriate to ask that,but I
want to
help to speed it
Reinhard Pötz wrote:
Carsten Ziegeler wrote:
Hi,
I think we should use the new xml subproject (containing sax and dom
utility classes) in C3.
If noone objects, I could do the changes in the next days.
Do you have any plans for a release of the xml subproject? I'm asking
because I'd like
If I only had known that this simple enhancement starts these discussions :)
Now, my understanding of C3 is that it is kind of a prototype (the
current code of course works perfectly and is stable, so marking this
a prototype might seem wrong from this pov). We can use this as a good
base for
Steven Dolg wrote:
Michael Seydl schrieb:
What purpose or intention has it that the Consumer isn't a
PipelineComponent?
Actually that's just a design flaw we haven't fixed yet.
Of course it should be a PipelineComponent.
So let's fix this :)
Carsten
--
Carsten Ziegeler
Reinhard Pötz wrote:
I'd like to release Cocoon 3 alpha-2 very soon. The open tasks are
Great,
. rename SAX components and interfaces (i.e. follow the naming
scheme that is used in the stax module)
which naming scheme is this? SAXSomething I hope as this is the way
everyone else is
Carsten Ziegeler wrote:
Reinhard Pötz wrote:
. rename SAX components and interfaces (i.e. follow the naming
scheme that is used in the stax module)
which naming scheme is this? SAXSomething I hope as this is the way
everyone else is writing these class names.
yes
--
Reinhard Pötz
Use Java 5 Regex instead of internal sun classes
Key: COCOON3-15
URL: https://issues.apache.org/jira/browse/COCOON3-15
Project: Cocoon 3
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/COCOON3-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed COCOON3-15.
---
Resolution: Fixed
Changed in revision: 737809
Use Java 5 Regex instead of internal sun
Fix the class hierarchy of org.apache.cocoon.pipeline.component.Consumer
Key: COCOON3-16
URL: https://issues.apache.org/jira/browse/COCOON3-16
Project: Cocoon 3
Issue
Carsten Ziegeler pisze:
Steven Dolg wrote:
Michael Seydl schrieb:
What purpose or intention has it that the Consumer isn't a
PipelineComponent?
Actually that's just a design flaw we haven't fixed yet.
Of course it should be a PipelineComponent.
So let's fix this :)
Do we have an idea how
On Monday 26 January 2009 22:33:17 Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
Steven Dolg wrote:
Michael Seydl schrieb:
What purpose or intention has it that the Consumer isn't a
PipelineComponent?
Actually that's just a design flaw we haven't fixed yet.
Of course it should
Andreas Pieber pisze:
On Monday 26 January 2009 22:33:17 Grzegorz Kossakowski wrote:
Carsten Ziegeler pisze:
Steven Dolg wrote:
Michael Seydl schrieb:
What purpose or intention has it that the Consumer isn't a
PipelineComponent?
Actually that's just a design flaw we haven't fixed yet.
Of
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON3-16:
---
Attachment: consumer.patch
Changed o.a.c.p.c.Consumer to extend o.a.c.p.c.PipelineComponent and
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667459#action_12667459
]
Grzegorz Kossakowski commented on COCOON3-16:
-
Steven, I can see some other
Carsten Ziegeler (JIRA) schrieb:
Use generics for pipeline assembly
--
Key: COCOON3-14
URL: https://issues.apache.org/jira/browse/COCOON3-14
Project: Cocoon 3
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/COCOON3-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON3-17:
---
Attachment: stax-generics.patch
This patch contains the StAXPipelineComponent interface and
Introduce the marker interface StAXPipelineComponent for the generified
Pipeline interface.
---
Key: COCOON3-17
URL: https://issues.apache.org/jira/browse/COCOON3-17
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667468#action_12667468
]
Andreas Pieber commented on COCOON3-16:
---
Looks quite nice, but wouldn't it better to
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667465#action_12667465
]
Steven Dolg commented on COCOON3-16:
Yes, just checked that - sorry for that.
I guess
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON3-16:
---
Attachment: (was: consumer.patch)
Fix the class hierarchy of
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON3-16:
---
Attachment: consumer.patch
Patch without formatting changes...
Fix the class hierarchy of
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667531#action_12667531
]
Steven Dolg commented on COCOON3-16:
Actually I'm not sure about those classes
[
https://issues.apache.org/jira/browse/COCOON3-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667534#action_12667534
]
Andreas Pieber commented on COCOON3-17:
---
Please dont commit this patch. We did too
[
https://issues.apache.org/jira/browse/COCOON3-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667543#action_12667543
]
Steven Dolg commented on COCOON3-17:
That's why I created a patch, rather than just
Steven Dolg wrote
Is it just me or is the patch you applied not really complete?
Because doing
PipelineSAXPipelineComponent pipeline = new
NonCachingPipelineSAXPipelineComponent();
pipeline.addComponent(new StringGenerator(xmlInput));
pipeline.addComponent(new
[
https://issues.apache.org/jira/browse/COCOON3-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12667598#action_12667598
]
Carsten Ziegeler commented on COCOON3-16:
-
We should use the SAXBuffer from
Hi,
I think we can reduce the number of interfaces in the SAX module by just
removing XMLProducer and XMLConsumer. XMLProducer is just a marker
interface combining Producer and SAXPipelineComponent, so we can just
remove it.
XMLConsumer combines LexicalHandler, ContentHandler and Consumer. I
27 matches
Mail list logo