[
https://issues.apache.org/jira/browse/COCOON3-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Pieber updated COCOON3-22:
--
Attachment: StAX-classes.png
I'm not quite sure what I should think about this idea. On one
[
https://issues.apache.org/jira/browse/COCOON3-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668368#action_12668368
]
Jakob Spörk commented on COCOON3-22:
I'm of the same opinion as Andreas. Only because
[
https://issues.apache.org/jira/browse/COCOON3-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668370#action_12668370
]
Carsten Ziegeler commented on COCOON3-22:
-
Ok, having worked with the xml consumer
Hi,
I could imagine a future version of Lenya to use Sling for the
repository management. I wouldn't like to give up Cocoon's pipelining
and XML processing capabilities, though.
Me neither :)
I'm not sure in which way Sling and Cocoon would cooperate from a
request processing point of view
SEE https://issues.apache.org/jira/browse/COCOON3-22
Carsten Ziegeler commented on COCOON3-22:
-
Ok, having worked with the xml consumer interface for years now, I came to
the conclusion that things get much simpler if you just rely on content
handler
It
Juan José Vázquez Delgado wrote:
Hi,
I could imagine a future version of Lenya to use Sling for the
repository management. I wouldn't like to give up Cocoon's pipelining
and XML processing capabilities, though.
Me neither :)
I'm not sure in which way Sling and Cocoon would cooperate from
Carsten Ziegeler schrieb:
Juan José Vázquez Delgado wrote:
I could imagine a future version of Lenya to use Sling for the
repository management. I wouldn't like to give up Cocoon's pipelining
and XML processing capabilities, though.
Me neither :)
I'm not sure in which way Sling and Cocoon
[
https://issues.apache.org/jira/browse/COCOON-2173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12668390#action_12668390
]
Rudi Vaum commented on COCOON-2173:
---
Hi there,
we've experience a variation of this bug
Wow, great - what do you think about committing this into the Sling
whiteboard? So we can use this as a prototype and base for further
discussions.
Sure, Carsten, My purpose is committing the proof of concept in
sandbox this weekend.
On the other hand, I´m embedding the cocoon-pipeline jar
Juan José Vázquez Delgado pisze:
I´ve written a proof of concept with a Sling Servlet using the Cocoon
pipeline api to get the response. This proof was ok but I´m thinking
about a more natural Cocoon/Sling integration. IMHO, a pipeline, even
a sitemap, would be as a script in Sling.
Any
Grzegorz Kossakowski schrieb:
Juan José Vázquez Delgado pisze:
I´ve written a proof of concept with a Sling Servlet using the Cocoon
pipeline api to get the response. This proof was ok but I´m thinking
about a more natural Cocoon/Sling integration. IMHO, a pipeline, even
a sitemap, would be as
Hi Grzegorz,
Any pointers to Sling scripts? Quick look at Sling's home page didn't
reveal anything.
You can deploy ecma, jsp, groovy and other scripting flavours into
Sling to process requests. Have a look this tutorial [1].
[1]
On Thu, Jan 29, 2009 at 12:57 PM, Grzegorz Kossakowski
g...@tuffmail.com wrote:
Juan José Vázquez Delgado pisze:
...I´m thinking
about a more natural Cocoon/Sling integration. IMHO, a pipeline, even
a sitemap, would be as a script in Sling.
Any pointers to Sling scripts? Quick look at
Hi all,
I have a project where I want to read xml from the filesystem and
unmarshall to Java.
Suppose I have a request
http://localhost:/myproject/product/xyz-123
where xyz-123 is the product-id.
Based on this information cocoon I know where to read the product-xml
from
Andreas Pieber wrote:
I really like the idea of having a common base architecture between all
components (sax, stax, ...). I'm not sure if we really have to hold them in
sync since its more a basic architectural decision to rely on an a special
Producer/Consumer interface than a syncing
15 matches
Mail list logo