Carsten Ziegeler wrote:
So my idea was to start simple and extend the functionality if needed.
First step was to always include all configurations, the next step will
be to disable this. I'll update the code today.
Ok, forget most of the stuff I said above, you can disable the inclusion
by
Marc Portier wrote:
Reinhard Poetz wrote:
Currently we use the xreporter artifact from
http://people.apache.org/repo/m1-snapshot-repository/xreporter/jars/xreporter-expression-r683.jar
in cocoon-forms.
After getting the Avalon and Excalibur artifacts published to the
central Maven repo, this
Carsten Ziegeler wrote:
Leszek Gawron wrote:
controlled via an additional attribute).
I have been trying to use configurator outside cocoon for my other
spring based projects. Thing is the configurator automatically imports
property files and contexts in META-INF/cocoon/spring. What should I
Reinhard Poetz wrote:
I wanted to write a mail about this today, funny. My usecase is that I want
to
replace Xalan by Saxon.
Am I right that creating a cocoon-xalan module would be the best solution for
this because it would make it possible to exclude it at POM level.
Yes, this is
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
I wanted to write a mail about this today, funny. My usecase is that I want to
replace Xalan by Saxon.
Am I right that creating a cocoon-xalan module would be the best solution for
this because it would make it possible to exclude it at POM
It's time for another series of module releases, see the list of all 41
artifacts below. SVN tags of all these artifacts can be found at
http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
Note that this time there are two artifacts that are proposed to be final
releases. See
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
I wanted to write a mail about this today, funny. My usecase is that I want
to
replace Xalan by Saxon.
Am I right that creating a cocoon-xalan module would be the best solution
for
this because it would make it
These artifacts are available at http://people.apache.org/builds/cocoon/ for
your tests:
Cocoon 2.2: Core modules
-
cocoon-core-2.2.0-M3.jar
cocoon-core-2.2.0-M3-tests.jar
cocoon-xml-api-1.0.0-M1.jar
cocoon-xml-impl-1.0.0-M1.jar
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
I wanted to write a mail about this today, funny. My usecase is that I want to
replace Xalan by Saxon.
Am I right that creating a cocoon-xalan module would be the best solution for
this because it
Reinhard Poetz wrote:
Hmm, yes and no :) Our xslt transformer implementation uses an xslt
processor. So we can define a static xalan xslt processor together
with a static xalan xslt transformer.
And this works because when the processor bean is created by Spring there is
no
need to have
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
Hmm, yes and no :) Our xslt transformer implementation uses an xslt
processor. So we can define a static xalan xslt processor together
with a static xalan xslt transformer.
And this works because when the processor bean is created by Spring there is
[
https://issues.apache.org/jira/browse/COCOON-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475933
]
Alexander Klimetschek commented on COCOON-1985:
---
Hi, I experienced the same problem with a Cocoon 2.2
[
https://issues.apache.org/jira/browse/COCOON-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ellis Pritchard updated COCOON-1985:
Fix Version/s: 2.1.9
2.1.10
2.2-dev
[
https://issues.apache.org/jira/browse/COCOON-1985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475998
]
Ellis Pritchard commented on COCOON-1985:
-
A quick check reveals that this has been patched in trunk (2.2):
On 22.02.2007 17:36, Daniel Fagerstrom wrote:
I'd like to propose Grzegorz Kossakowski (aka Grek) as a new Cocoon
committer.
+1
Jörg
Daniel Fagerstrom wrote:
Please cast your votes.
+1
-David
16 matches
Mail list logo
