Hi guys,
I guess its about time to write something myself...
As a colleague of Reinhard I participated in the Micro-Cocoon effort in
February.
Just as Reinhard wrote, at the end of those 3 days, there was the idea
of doing a rewrite.
The number of use cases and the appr. 5500 lines of code
Ralph Goers schrieb:
Reinhard Poetz wrote:
Pipeline API + java.net.URL + XML-SAX components
A more advanced scenario could consist of
Pipeline API + Sourceresolve + XML-SAX components + Sitemap
Engine
or maybe you need the full stack that corresponds to Cocoon Core
Carsten Ziegeler schrieb:
The pipeline writer needs to know how uri resolving works. He needs to
know what input values are allowed, what relative values mean etc.
But I will turn around the questions :) What caching do you need? The
ultra complex caching we currently have which can cache
Vadim Gritsenko schrieb:
On Mar 26, 2008, at 11:09 AM, Steven Dolg wrote:
Carsten Ziegeler schrieb:
The pipeline writer needs to know how uri resolving works. He needs
to know what input values are allowed, what relative values mean etc.
But I will turn around the questions :) What
Joerg Heinicke schrieb:
On 26.03.2008 09:14, Reinhard Poetz wrote:
What I want to see is a concise pipeline API that comes with only
little overhead in terms of its learning curve and its dependencies
on third-party software. Usually this means that we stick with
standard APIs as much as
Carsten Ziegeler schrieb:
Reinhard Poetz wrote:
ok. Steven and I will work on Corona next week again so that the code
reflects the layered design that we have discussed recently. When
doing this we will also improve the package structure to make it
becomes cleaner in general (and more OSGi
Carsten Ziegeler schrieb:
Steven Dolg wrote:
How about:
URL url = new URL(some url);
UrlConnection connection = url.openConnection();
connection.getLastModified();
Not sure it this really works in all cases, but appears to be quite
suitable and easily extensible.
Yes, this works for many
Carsten Ziegeler schrieb:
Ralph Goers wrote:
Consider this:
URL baseUrl = new URL(file:///C:/temp/);
Pipeline pipeline = new NonCachingPipeline();
pipeline.addComponent(new FileGenerator(new URL(baseUrl, xyz.xml));
pipeline.addComponent(new XSLTTransformer(new URL(baseUrl, xyz.xslt));
Carsten Ziegeler schrieb:
Andreas Hartmann schrieb:
Carsten Ziegeler schrieb:
Bertrand Delacretaz wrote:
On Wed, Jul 16, 2008 at 5:14 AM, Sylvain Wallez
[EMAIL PROTECTED] wrote:
...Can't we just give the parameters they need
individually to every pipeline component, thus allowing
Peter Hunsberger schrieb:
On Thu, Jul 17, 2008 at 9:22 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Andreas Hartmann wrote:
I don't think that the calling code has to know the actual components,
but rather the environment-specific interfaces of the components. It
only makes sense
Carsten Ziegeler schrieb:
Reinhard Pötz write:
Agreed. How do you know what kind of wrapper do you need if you don't
know what kind of events components consume and produce?
My assumption is that the developer that uses the pipeline knows what he
does.
:) While this
Carsten Ziegeler schrieb:
Steven Dolg wrote:
Carsten Ziegeler schrieb:
Wouldn't it be better/easier to have a sax pipeline, a dom pipeline, a
stax pipeline, perhaps sharing a common interface?
From my point of view:
Currently the user must know which components he needs
Grzegorz Kossakowski schrieb:
Reinhard Pötz pisze:
My assumption is that the developer that uses the pipeline knows what he
does.
This is rather good assumption. The problem I can see is that developer has to
check sources of each component in order
to know what he does as
Grzegorz Kossakowski schrieb:
Steven Dolg pisze:
Configuration and setup is clearly not the most important aspect of a
pipeline component.
But AFAIK interfaces are not designed by what is most important or not,
but by what is common to the implementating classes and by what is
really
Carlos Tejo Alonso schrieb:
[Sorry for the last empty email.]
Hello,
I was looking for documentacion about how to develop a
Generator and
how to develop a serializer. This is the last documentation that I
have found: [1] and [2].
Is this documentation the properly one to
Vadim Gritsenko schrieb:
On Jan 15, 2009, at 9:05 AM, Reinhard Pötz wrote:
Steven Dolg wrote:
I planned to come up with an Imaging Module for quite some time now.
I'm +1 to add the patch to the C3 code base.
+1.
But question is, can you aggregate, include images?
There is no component
Andy Stevens schrieb:
2009/1/19 Steven Dolg steven.d...@indoqa.com:
Vadim Gritsenko schrieb:
On Jan 15, 2009, at 9:05 AM, Reinhard Pötz wrote:
But question is, can you aggregate, include images?
There is no component for that yet. But I'm confident this is easily
possible
Grzegorz Kossakowski schrieb:
Hi Thorsten,
Thorsten Scherler pisze:
Who is talking about that?
The point is that patches should not been sent to a ml. I am subscribed
to around 50 different ml and if I receive only one attachment (let us
say around 1 MB) from each list I have 50 MB
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.
Regards,
Steven
Regards,
Mike
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:
Carsten Ziegeler schrieb:
Hi,
as part of COCOON3-22 I've refactored the whole SAX module and removed a
lot of classes :)
Before committing these changes I would like to discuss them (I can
provided a patch but not sure if this works).
Ok, the aim is to reduce the number of interfaces and
Steven Dolg schrieb:
Carsten Ziegeler schrieb:
Hi,
as part of COCOON3-22 I've refactored the whole SAX module and removed a
lot of classes :)
Before committing these changes I would like to discuss them (I can
provided a patch but not sure if this works).
Ok, the aim is to reduce the number
Yoann Archambault schrieb:
Hi everyone!
Hello Yoann,
I started coding for a new project and decided to go ahead with Cocoon 3
(i'm pretty much sticking to the trunk) and i like what i see. Alot
actually! Really looks like the next step forward for XML based webapp
frameworks.
I'm not
Okay, here's what I did.
Sitemap
map:pipeline
map:match pattern=data/done
map:generate src=bug-fixing/BasicOperationResponse.xml /
map:transform type=include /
map:transform src=bug-fixing/referenceNodeCRUD.xslt /
map:serialize type=xml /
/map:match
stylesheet.
I`ll confirm that when i get home later.
Thanks
Yoann
On Sun, 22 Mar 2009 14:49 +0100, Steven Dolg steven.d...@indoqa.com
wrote:
Okay, here's what I did.
Sitemap
map:pipeline
map:match pattern=data/done
map:generate src=bug-fixing/BasicOperationResponse.xml
Bertrand Delacretaz schrieb:
On Wed, Apr 1, 2009 at 3:57 PM, Sylvain Wallez sylv...@apache.org wrote:
Andrew Savory wrote:
...If I might make a suggestion: understanding the problem and possible
solutions is where the cocoon developer community can really help as well.
It's how many
Hello Dariusz,
great to have on board.
I'm really looking forward to all the nice stuff you will create for us :-P
Have a good time,
Steven
Dariusz Łuksza schrieb:
Hi cocoon dev community,
After official GSoC announcement[1] I'm and Reinhard (as my mentor)
are in the program.
I already
Reinhard Pötz schrieb:
I have created release artifacts of 4 of our 5 subprojects:
. Block Deployer: http://tinyurl.com/c9j3a9
Better error messages if a block can't be found or if there aren't any
blocks available at all.
. Spring Configurator: http://tinyurl.com/dcvgpt
Support a
Felix Knecht schrieb:
H Christoph
Hello,
we are two of the students who work on cocoon-profiling.
Now that the implementing phase of the project has started we provided
an initial patch [1] to add cocoon-profiling and
cocoon-profiling-firebug to the code base. As of now the firebug
Hi,
Passing parameters into the sitemap will work when you do it this way:
sitemap:
map:match pattern=*
map:generate src=xml/{map:1}.xml/
map:transform src=xsl/{map:1}.xsl
map:parameter name=firmaElectronica value={jexl:firmaElectronica}/
map:parameter name=hash
Jos Snellings schrieb:
Dear,
Just a small question, testing:
When I get:
java.lang.NullPointerException
at
org.apache.cocoon.stringtemplate.StringTemplateGenerator.constructCacheKey(StringTemplateGenerator.java:75)
I notice that StringTemplateGenerator has two constructors: one with a
Johannes Lichtenberger schrieb:
On Sun, 2009-11-29 at 07:32 +0100, Jos Snellings wrote:
In the samples, a typical use of StringTemplate is shown: a page is to
be interpreted by the StringTemplate engine, and a number of properties
are passed via the hashtable.
The idea is that you would open
Steven Dolg schrieb:
Johannes Lichtenberger schrieb:
On Sun, 2009-11-29 at 07:32 +0100, Jos Snellings wrote:
In the samples, a typical use of StringTemplate is shown: a page is to
be interpreted by the StringTemplate engine, and a number of properties
are passed via the hashtable.
The idea
Sylvain Wallez schrieb:
Reinhard Pötz wrote:
snip/
But let me broaden the picture: Based on our work from about two weeks
ago, I created another aspect which implements the support for
conditional GET requests and also takes care that a pipeline isn't
executed unless it is really necessary. I
Reinhard Pötz schrieb:
I propose Simone Tripodi as a new Cocoon committer and PMC member.
Simone has been participating on our mailing lists since Sept 2008.
Recently he provided an extensive patch that adds XInclude support to
Cocoon 3. Additionally he provided 6 other patches.
That shows
Am 12.04.2011 13:42, schrieb Thorsten Scherler:
Hi all,
as I mentioned in another mail I am ATM developing a prototype based on
c3. In another recent project we worked with jersey [1], which is the
reference implementation for JAX-RS (JSR 311).
Our c3 prototype will expose a couple of REST
Hey,
picking up some speed would be really great for this project.
Seeing that some of the issues are older than a year and the rest
approaching their first anniversary very soon feels almost awkward.
As mentioned in his email, Reinhard and I are working on something for
the Pipeline API
Am 27.04.2011 11:59, schrieb Thorsten Scherler:
On Wed, 2011-04-27 at 09:45 +0200, Francesco Chicchiriccò wrote:
On 27/04/2011 07:26, Francesco Chicchiriccò wrote:
On 26/04/2011 19:04, Thorsten Scherler wrote:
Hi all,
I could not find anything related to i18n/locale in c3.
Did I not look
Am 28.04.2011 16:12, schrieb Peter Hunsberger:
However I guess c3 only for is easiest for
everyone more familiar with c3. If we have a rewrite I can create the
c2.2 wrapper quite easy so I say do the c3 and when finish I do the
rest. ;)
Basically:
AbstractI18n = spring based transformer no
Am 11.07.2011 17:10, schrieb Lars Huttar:
Dear Cocoon developers,
Congratulations on the alpha-3 release of C3. I was just telling my
customer how Cocoon seemed to have languished, when I saw the
announcement about C3a3. That is encouraging.
We have been developing and using Cocoon
Am 05.07.2011 14:49, schrieb Simone Tripodi:
Hi Robby!!!
as I wrote you on Twitter, this is something *really* interesting that
must be included in the Cocoon distribution :)
We can include that module quite easy, all you have to do is
* checkout/update the C3 /trunk;
* add needed
Am 14.07.2011 11:12, schrieb Simone Tripodi:
Hi Steven!!!
+1 to your suggestion. I've never been fan of 'optional' module that
aggregates every 3rd parties integrations, I'd like to see it rather
splitted in a multi-module structure.
Please let me know if you want me to work on it, I'll fill an
Am 15.07.2011 16:12, schrieb Reinhard Pötz:
On 07/07/2011 12:09 PM, Robby Pelssers wrote:
Hi,
Are my following assumptions right?
-setConfiguration is typically used when using sitemap
yes
-but for setup(params) method the API states that this is the shared map
for all components… so it
Am 02.08.2011 10:16, schrieb Francesco Chicchiriccò:
On 01/08/2011 21:06, Simone Tripodi wrote:
Hi all guys!!!
My question is instead: is there any advantage we can get by targeting
Cocoon to Java6? Is there any specific Java6 APIs we need to improve
the existing codebase?
If yes, please can
Am 05.08.2011 11:25, schrieb Nathaniel, Alfred:
Hi Francesco,
I am a big fan of Findbugs and persueing a zero-warnings policy.
In other projects we use a Findbugs exclude filter file to
disable warnings and document the deliberation for doing so.
That's what we do as well.
TBH, the default
Hey guys,
as some might have seen, I crashed our Jenkins build about an hour ago:
[ERROR]
/home/jenkins/jenkins-slave/workspace/Cocoon-trunk/trunk/cocoon-sitemap/src/main/java/org/apache/cocoon/sitemap/util/SpringProxyHelper.java:[30,28]
type parameters of TT cannot be determined; no unique
Oops!... I did it again
But this time I'm innocent :P
It took me some time to figure this one out since I didn't touch
anything near it.
My theory is this:
With COCOON3-69 ehcache was upgraded from 1.6.1 to 2.4.3.
Between those versions, the serialVersionUID of net.sf.ehcache.Element
Am 04.08.2011 00:03, schrieb Sylvain Wallez:
Le 01/08/11 16:26, Nathaniel, Alfred a écrit :
Hi all,
C3 is still set to 1.5 as source and target version.
Java5 is end of life since almost two years now.
Is there any good reason not to go 1.6?
Here's an additional one to the ones already
Am 14.08.2011 14:18, schrieb Sylvain Wallez:
Le 12/08/11 21:08, Thorsten Scherler a écrit :
Hi all,
I am migrating a StAX development from a customer to c3 StAX, since the
resulting code will be much more generic and understandable.
In my case I need to process all files from different
Am 19.08.2011 22:29, schrieb Simone Tripodi:
Hi all guys,
I noticed some code format during commits: please avoid it or do at
least in a separate commit, otherwise it makes not easy to understand
which are real changes and which are formats in the diff.
Moreover, code format in C3 is now
Am 23.08.2011 00:00, schrieb Igor Malinin:
Hello, C3 developers.
After C3 has updated its dependencies to use AspectJ 1.6.11 it become
impossible to use it with Jetty 7.
The problem could be easily reproduced in cocoon-sample-webapp by
replacing maven-jetty-plugin of Jetty 6 with the
Am 25.08.2011 21:11, schrieb Steven Dolg:
Am 23.08.2011 00:00, schrieb Igor Malinin:
Hello, C3 developers.
After C3 has updated its dependencies to use AspectJ 1.6.11 it become
impossible to use it with Jetty 7.
The problem could be easily reproduced in cocoon-sample-webapp by
replacing
Am 28.08.2011 12:18, schrieb Igor Malinin:
https://jira.springsource.org/browse/SPR-7678 another interesting
bug-report... I've just checked, my simplistic Cocoon example that is
basically empty web-app with just two pages eats up 500 MB right after
start!!! Is it what called light-weight?
Am 09.09.2011 10:33, schrieb Thorsten Scherler:
...
Hmm, Jakarta RegExp does some things different and IMO much better then
java.util. Even if it is retired that does not mean it is not worth
using it, more since this way the component works exactly as in our
prior versions. Not sure when I
Am 19.09.2011 23:03, schrieb Nathaniel, Alfred:
+1 = Yes, Cocoon3 shall require Java 1.6
-1 = No, Cocoon3 must remain usable with Java 1.5 (with justification
for the veto)
+1
Am 31.10.2011 11:17, schrieb Thorsten Scherler:
On Sun, 2011-10-30 at 12:53 +0100, Simone Tripodi wrote:
Hi Thorsten!
thanks for leading this!
+1, new modules - even if incomplete - should be added in the pom.
Many thanks in advance for taking care of it!
Actually till now there are no *sample
Am 31.10.2011 13:49, schrieb Jurgen Derksen:
So is he Windows 7 Compatible? According to you guys? I don't have an answer to
the question.
I look forward to your reply
Cocoon is based on Java™, as such it is compatible with all platforms a
Java Virtual Machine is available for.
I suggest you
Am 31.10.2011 14:19, schrieb Francesco Chicchiriccò:
Hi all,
I've developed a fix for COCOON3-79, attached [1] as a patch.
Some background information is available at [2].
Since the aforementioned patch will involve changing some interface,
I'm calling the vote on Code Modification [3]:
+1 =
Hi Javier,
that's the first time, I've heard of concurrency issues in C3.
That's not to say there cannot be any, just that it's probably a rare
case or you're stressing the system more than anyone else has yet.
Some thoughts top off my head:
- providers and factories should be singletons, as
I cannot look into this right now, but I'll sure do this evening.
I had some frustrating problems with svn yesterday and after a full hour
of not being able to do a simple svn up I gave up.
Seems to work now, so I'll try again this evening...
Hello again,
using the test project from Thorsten [1] I created a very simple client,
running several threads to send requests for a randomly selected static
resource (one of the image files).
(Of course I reverted the synchronized in SpringComponentProvider
before running the tests!)
I ran
Hey guys,
has there been any progress in this matter? Any new insights?
We have a jira issue classified as Major Bug accusing us of
concurrency issues - IMO the worst thing that can happen to a web
application framework - and there's been no word for almost 2 weeks.
I'd like to see that
Reporter: Steven Dolg
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/COCOON-2180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2180:
Attachment: corona.zip
Corona - A proposal for a reimplementation
Add caching to corona
--
Key: COCOON-2190
URL: https://issues.apache.org/jira/browse/COCOON-2190
Project: Cocoon
Issue Type: New Feature
Components: * Cocoon Core
Reporter: Steven Dolg
[
https://issues.apache.org/jira/browse/COCOON-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2190:
Attachment: caching.txt
A patch adding very simple caching to the CachingPipeline.
Caching
[
https://issues.apache.org/jira/browse/COCOON-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2190:
Attachment: caching.txt
Just realized I uploaded an incomplete patch...
Add caching to corona
[
https://issues.apache.org/jira/browse/COCOON-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2190:
Attachment: (was: caching.txt)
Add caching to corona
Affects Versions: 2.2-dev (Current SVN)
Reporter: Steven Dolg
The method public void write(byte b[], int off, int len) does not cache all
relevant bytes to the internal buffer.
The method actually copies all len bytes to its internal buffer, but
increments the byte counter only
[
https://issues.apache.org/jira/browse/COCOON-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2192:
Attachment: CachingOutputStreamTest.txt
A patch with a unit test that demonstrates the problem
[
https://issues.apache.org/jira/browse/COCOON-2192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2192:
Attachment: CachingOutputStream.txt
A patch that fixes the problem.
CachingOutputStream does
)
Reporter: Steven Dolg
Additional components:
* XSLT Transformer
* first attempt at Controllers
Additional features:
* JNet integration (not finished, but working)
* Mime-Type handling (not finished, but working)
* Input parameters provided for all pipeline components
* Controller can redirect
[
https://issues.apache.org/jira/browse/COCOON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2195:
Attachment: patch.txt
Added patch.
Additional components and features
[
https://issues.apache.org/jira/browse/COCOON-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587849#action_12587849
]
Steven Dolg commented on COCOON-2195:
-
Of course I can create smaller patches.
I'm
)
Reporter: Steven Dolg
Attachments: transformNode.txt
Currently the transform node's src attribute is mandatory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/COCOON-2198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2198:
Attachment: transformNode.txt
Fix for this issue.
TransformNode's src attribute must
)
Reporter: Steven Dolg
Priority: Minor
Currently one part of the XMLSerializer's configuration is hard-coded in the
class (output-method = xml), the other is in the application context defining
the XMLSerializer.
Remove the harded-part and add it to the other
[
https://issues.apache.org/jira/browse/COCOON-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2199:
Attachment: XMLSerializer.txt
Patch with the changes mentioned above.
Streamline
Issue Type: New Feature
Components: Corona (experimental)
Reporter: Steven Dolg
Support setting the mime-type for the FileReaderComponent from the sitemap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/COCOON-2200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2200:
Attachment: FileReaderComponent.txt
A patch with the changes mentioned above.
Enable explicit
Issue Type: Improvement
Components: Corona (experimental)
Reporter: Steven Dolg
Set the header fields (like content-type, content-length) properly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/COCOON-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2201:
Attachment: SitemapServlet.txt
Set (some of) the header fields correctly.
Additionally some
[
https://issues.apache.org/jira/browse/COCOON-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2202:
Attachment: CallNode.txt
A patch with the changes mentioned above.
Resolve Sitemap parameters
Components: Corona (experimental)
Reporter: Steven Dolg
Attachments: CallNode.txt
Currently Sitemap parameters are not resolved when passing them to a Controller.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue
Issue Type: Bug
Components: Corona (experimental)
Reporter: Steven Dolg
Attachments: SpringControllerComponent.txt
Currently the SpringControllerComponent only forwards the input parameters to
the Controller.
Also add the configuration (= Sitemap parameters
[
https://issues.apache.org/jira/browse/COCOON-2203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2203:
Attachment: SpringControllerComponent.txt
A patch with the changes mentioned above.
Provide
)
Reporter: Steven Dolg
Provide a caching mechanism that performs cache updates asynchronously, if the
cached value is no longer valid, and uses the previously cached result until
the updated result is available.
--
This message is automatically generated by JIRA.
-
You can reply
[
https://issues.apache.org/jira/browse/COCOON-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2205:
Attachment: async-caching.txt
A patch that introduces a new pipeline type that implements
[
https://issues.apache.org/jira/browse/COCOON-2206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON-2206:
Attachment: controller.txt
A patch with the changes described above.
Relative to corona
Type: Bug
Components: Corona (experimental)
Reporter: Steven Dolg
Attachments: controller.txt
Currently sitemap and input parameters are passed to the controller in a single
map.
This can lead to parameters overriding each other.
Pass them separately to prevent
[
https://issues.apache.org/jira/browse/COCOON3-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12638314#action_12638314
]
Steven Dolg commented on COCOON3-2:
---
Ah, never mind.
This is some code we took from Cocoon
://issues.apache.org/jira/browse/COCOON3-9
Project: Cocoon 3
Issue Type: Improvement
Components: cocoon-pipeline
Affects Versions: 3.0.0-alpha-1
Reporter: Steven Dolg
Assignee: Cocoon Developers Team
Fix For: 3.0.0-alpha-2
Currently
[
https://issues.apache.org/jira/browse/COCOON3-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON3-9:
--
Attachment: cache.patch
The provided patch basically renames
[
https://issues.apache.org/jira/browse/COCOON3-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Dolg updated COCOON3-9:
--
Description:
Currently the PipelineCache is very specific for caching the complete results
[
https://issues.apache.org/jira/browse/COCOON3-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666545#action_12666545
]
Steven Dolg commented on COCOON3-14:
Although we cannot prevent every misconfiguration
[
https://issues.apache.org/jira/browse/COCOON3-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666921#action_12666921
]
Steven Dolg commented on COCOON3-14:
Is this event-based communication guaranteed
[
https://issues.apache.org/jira/browse/COCOON3-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12666957#action_12666957
]
Steven Dolg commented on COCOON3-14:
This gives me following output:
class
Type: Bug
Components: cocoon-pipeline
Affects Versions: 3.0.0-alpha-1
Reporter: Steven Dolg
Assignee: Steven Dolg
Fix For: 3.0.0-alpha-2
The interface o.a.c.p.c.Consumer does not extend o.a.c.p.c.PipelineComponent.
--
This message
[
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
[
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
1 - 100 of 127 matches
Mail list logo
