Reinhard Poetz wrote:
Leszek Gawron wrote:
Reinhard Poetz wrote:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Why is there no release of cocoon spring configurator?
because there has already been a final release 1.0.0 of it and there
haven't bee
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
I prepared another series of releases from trunk, see the list of all 43
artifacts below.
...
You can find the staged versions of the modules (sources, binaries,
javadocs + checksums + gpg signatures) at
http://people.apache.org/builds/cocoon/.
[
https://issues.apache.org/jira/browse/COCOON-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500580
]
Carsten Ziegeler commented on COCOON-2071:
--
I like the idea, but there is an issue with your patch: the cur
Reinhard Poetz wrote:
I prepared another series of releases from trunk, see the list of all 43
artifacts below.
...
You can find the staged versions of the modules (sources, binaries,
javadocs + checksums + gpg signatures) at http://people.apache.org/builds/cocoon/.
To produce a binding vote
Grzegorz Kossakowski wrote:
Joerg Heinicke pisze:
On 19.05.2007 14:28, Grzegorz Kossakowski wrote:
One more reason to always put the service URL into the src attribute
as you don't need to discuss and differentiate between GET and POST.
+1
Yes I have to explain meaning of the "postData" par
On 31.05.2007 19:40, Danny Bols wrote:
FYI
We replaced the js-1.6R5.jar with a build of the current development version
(rhino1_6R6pre) of rhino and all our performance have dissapeared.
--
Danny Bols
Performance or performance issues? :-)
Joerg
FYI
We replaced the js-1.6R5.jar with a build of the current development version
(rhino1_6R6pre) of rhino and all our performance have dissapeared.
--
Danny Bols
> -Original Message-
> From: Niels van Kampenhout [mailto:[EMAIL PROTECTED]
> Sent: dinsdag 29 mei 2007 15:40
> To: dev@cocoo
Hi All,
I had one more idea... I tried to insert a stylesheet between the xinclude
transformer and the zip serializer, that just copied the xml tree... this
didn't do anything either (same Null Pointer Exception)... I wonder what it
could be ?
AJ
Leszek Gawron wrote:
Reinhard Poetz wrote:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Why is there no release of cocoon spring configurator?
because there has already been a final release 1.0.0 of it and there haven't
been any changes that woul
Reinhard Poetz wrote:
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Why is there no release of cocoon spring configurator?
--
Leszek Gawron http://www.mobilebox.pl/krs.html
CTO at MobileBox Ltd.
Hi Geert!
I tried the CInclude transformer... same result! The problem must be with the
ZipArchiveSerializer...
AJ
>
> Also tried cinclude transformer?
>
> Kind regards,
> Geert
>
>
> Drs. G.P.H. Josten
> Consultant
>
>
>
> Daidalos BV
> Source of Innovation
> Hoekeindsehof 1-4
> 2665 JZ Bl
Reinhard Poetz wrote:
You can find the staged versions of the modules (sources, binaries,
javadocs +
checksums + gpg signatures) at http://people.apache.org/builds/cocoon/.
SVN tags
of all these artifacts can be found at
http://svn.apache.org/repos/asf/cocoon/tags/cocoon-2.2/.
+1
--
Reinh
Hi Joerg,
1) This resulted in the same error when I configured the pipeline like so:
2) I changed the XInclude to this:
http://apache.org/cocoon/zip-archive/1.0";
xmlns:xi="http://www.w3.org/2001/XInclu
I prepared another series of releases from trunk, see the list of all 43
artifacts below. This time most of the modules are proposed to be released as
"RC1" (release candidate 1). The exceptions are
- the forms and the ajax block which need more work related to their usage
of the servlet s
The proposed release artifacts are available at
http://people.apache.org/builds/cocoon/.
Except for the archetypes the easiest way to test the artifacts is by adding a
"cocoon-staging" profile to your ~/.m2/settings.xml:
cocoon-staging
cocoon.stagi
Ralph Goers pisze:
What am I missing? All of these syntaxes look invalid to me. Why isn't
the syntax of the normal form
protocol://[servername[:port]]/path
From the discussions it isn't obvious to me if the block name should be
the server name or part of the path.
It could be a server nam
JSR.168 Portlet-aware CookieModule
--
Key: COCOON-2072
URL: https://issues.apache.org/jira/browse/COCOON-2072
Project: Cocoon
Issue Type: Improvement
Components: Blocks: Portal
Reporter:
What am I missing? All of these syntaxes look invalid to me. Why isn't
the syntax of the normal form
protocol://[servername[:port]]/path
From the discussions it isn't obvious to me if the block name should be
the server name or part of the path.
Ralph
Alexander Klimetschek wrote:
Hi guys,
[
https://issues.apache.org/jira/browse/COCOON-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned COCOON-2071:
Assignee: Carsten Ziegeler
> Option to turn off pooling for components (probably f
[
https://issues.apache.org/jira/browse/COCOON-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated COCOON-2071:
--
Attachment: disable-pooling-config.patch
Patch for cocoon-sitemap-impl.
> Opt
Option to turn off pooling for components (probably faster on new JVMs and
simpler debugging)
-
Key: COCOON-2071
URL: https://issues.apache.org/jira/browse/COCOON-2071
Hi guys,
I have a hack for our local Cocoon release that integrates global bean ids
into the servlet protocol. It's not perfect and that's why I didn't provide
a patch yet for https://issues.apache.org/jira/browse/COCOON-2044 (and
because I have so much to do for our upcoming release).
But I
22 matches
Mail list logo
