Ralph Goers wrote:
>
> Actually, I disagree. The one compelling (and exciting) thing for me
> about 2.2 is the ability to download a small core and to be able to use
> maven (or a tool that hides maven) to create my application. I want to
> be able to use maven 2 to create my component(s) and
Glen Ezkovich wrote:
On Nov 21, 2005, at 12:16 AM, Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Now as 2.1.8 is out, we should think about a 2.2 release. I think for a
2.2 release we should at least finish the following things:
- Finish the maven2 build
- Sync everything with 2.1.x (apply
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Aren't we aiming at a 2.2M1 release? If yes, the only must is a
working build system IMHO.
IIRC, ant build is working, so it's not a pre-requisite. No need to
rush maven into 2.2m1.
Vadim
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-cron has an issue affecting its community integration.
This issue af
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-cron has an issue affecting its community integration.
This issue af
Vadim Gritsenko wrote:
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Now as 2.1.8 is out, we should think about a 2.2 release. I think for a
2.2 release we should at least finish the following things:
- Finish the maven2 build
- Sync everything with 2.1.x (apply changes that were only applie
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-cron has an issue affecting its community integration.
This issue af
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project cocoon-block-cron has an issue affecting its community integration.
This issue af
On 11/21/05, Max Pfingsthorn <[EMAIL PROTECTED]> wrote:
> Hi Cocooners!
>
> I have a question: I couldn't find a nice EventAware object cache in Cocoon,
> the eventcache block only implements the o.a.c.caching.Cache which I need to
> pass a byte array. Serializing/deserializing is not really an o
> version?
SVN version of today, now I'm not on my notebook, so I can tell you the
correct revision.
>
> Best Regards,
>
> Antonio Gallardo
--
Daniele Madama
http://www.pronetics.it
http://www.danysoft.org/blogs/
Why are we getting jira emails with a German subject ? Can we enforce
English on this somehow?
I personally don't mind all that much, it's just for the sake of
consistency and those who don't understand the language that well.
Jorg
2 issues with Jira in one mail - maybe somebody (Pier?) knows how to fix
them?
1. I changed status to "On Hold". But as you can see you can see nothing
- at least in this mail :)
2. Why are the subjects of the mails localized? "Aktualisiert" and
"Kommentiert" in the last two Jira mails is Ge
[ http://issues.apache.org/jira/browse/COCOON-1529?page=all ]
Jörg Heinicke updated COCOON-1529:
--
> I18ntranformation output xmlns:i18n in the first element
> -
>
> Key: COCOON-1529
>
[
http://issues.apache.org/jira/browse/COCOON-1529?page=comments#action_12358179
]
Jörg Heinicke commented on COCOON-1529:
---
Is it really a bug or just a superfluous namespace declaration?
> I18ntranformation output xmlns:i18n in the first element
>
[
http://issues.apache.org/jira/browse/COCOON-1691?page=comments#action_12358178
]
Jörg Heinicke commented on COCOON-1691:
---
SVN commit 234125 (http://svn.apache.org/viewcvs.cgi?rev=234125&view=rev)
obviously broke this. I wonder if this could be bett
On Nov 21, 2005, at 10:18 AM, Antonio Gallardo wrote:
version?
I can corroborate this... in 2.1.7 is the only time I ever tried to use
the FS debugger, and the result was that my flowscripted pages didn't
work right when the debugger was turned on. I had been meaning to ask
about this, bu
version?
Best Regards,
Antonio Gallardo
Daniele Madama wrote:
Hola,
from a lot of time (3 months of course) the flowscipt debugger doesn't
work, if I try to enable it in cocoon.xconf ed execute the forms sample,
It broke the flow esecution.
I'm not a rhino expert, so I can say if It depends
Hi Cocooners!
I have a question: I couldn't find a nice EventAware object cache in Cocoon,
the eventcache block only implements the o.a.c.caching.Cache which I need to
pass a byte array. Serializing/deserializing is not really an option for me.
What I would like is a (not necessarily persistent)
ESQL compilation error
--
Key: COCOON-1691
URL: http://issues.apache.org/jira/browse/COCOON-1691
Project: Cocoon
Type: Bug
Components: Blocks: XSP
Versions: 2.1.8
Reporter: Feliciano Borrego
Priority: Critical
Attachments: xsp
Reinhard Poetz wrote:
Carsten Ziegeler wrote:
Now as 2.1.8 is out, we should think about a 2.2 release. I think for a
2.2 release we should at least finish the following things:
- Finish the maven2 build
- Sync everything with 2.1.x (apply changes that were only applied to
2.1.x if appropriate
Giacomo Pati wrote:
On Sat, 19 Nov 2005, Ralph Goers wrote:
Carsten Ziegeler wrote:
It would be great if more than the two of us would be interested in the
portal stuff. But I think we are very near to a cleanup version which
I'll start to document around christmas (hopefully) and then other
Andrew Stevens wrote:
or in your pipeline
Then implement Parameterizable. The conf parameter will be passed to
the parameterize method.
Or finally in your pipeline do:
I think you'll find that should be map:transform, not map:transformer...
Andrew.
Of course. Thanks for
Daniel Fagerstrom wrote:
The question is if we are going to start to have separate release
cycles of the blocks with 2.2. In that case the important part is a
cocoon-core 2.2 release. Then we should preferably have releases of
CForms, Template, Portal and some other important blocks that a
[
http://issues.apache.org/jira/browse/COCOON-1686?page=comments#action_12358152
]
Suzan Foster commented on COCOON-1686:
--
The JXPathContext's derived from the parent-path attribute on the multi-value
and repeater bindings are used without applying JX
Hello,
I just tried installing the default Cocoon 2.1.8, and I noticed an
error in the forms samples:
http://localhost:/samples/blocks/forms/do-fileExplorer.flow
An error has occured
java.lang.NoSuchMethodError:
javax.xml.transform.dom.DOMResult.getNextSibling()Lorg/w3c/dom/Node;
Cocoon s
Jorg Heymans wrote:
>
> +1, separate release cycles for more and quicker releases.
>
> We could start this process incrementally today by just deploying
> snapshots of the 2.2 core jar. No huge announcements or anything, just
> get it out there for the bleeding-edgers and to test the release
> p
[
http://issues.apache.org/jira/browse/COCOON-1686?page=comments#action_12358145
]
Suzan Foster commented on COCOON-1686:
--
The patch only partially solves the bug entry COCOON-1671. It is still not
binding to the multi-value with id 'drinks', or to th
Le 21 nov. 05, à 13:23, Jorg Heymans a écrit :
...We could start this process incrementally today by just deploying
snapshots of the 2.2 core jar. No huge announcements or anything, just
get it out there for the bleeding-edgers and to test the release
process..
Sounds like a good idea, I think
Jorg Heymans wrote:
Daniel Fagerstrom wrote:
The question is if we are going to start to have separate release cycles
of the blocks with 2.2. In that case the important part is a cocoon-core
2.2 release. Then we should preferably have releases of CForms,
Template, Portal and some other impor
Daniel Fagerstrom wrote:
>
> The question is if we are going to start to have separate release cycles
> of the blocks with 2.2. In that case the important part is a cocoon-core
> 2.2 release. Then we should preferably have releases of CForms,
> Template, Portal and some other important blocks th
Bertrand Delacretaz wrote:
> Le 20 nov. 05, à 19:41, Carsten Ziegeler a écrit :
>
>
>>Now as 2.1.8 is out, we should think about a 2.2 release. I think for a
>>2.2 release we should at least finish the following things:
>>
>>- Finish the maven2 build
>
>
> And get rid of the ant-based build?
Ex
Hola,
from a lot of time (3 months of course) the flowscipt debugger doesn't
work, if I try to enable it in cocoon.xconf ed execute the forms sample,
It broke the flow esecution.
I'm not a rhino expert, so I can say if It depends from new version of
rhino or not. But I think that it could be usefu
From: Ralph Goers <[EMAIL PROTECTED]>
Date: Sun, 20 Nov 2005 19:03:02 -0800
Stefan Pietschmann wrote:
The elements in the pipeline shall have attributes like
I don't believe you can do that. Instead you need to either do:
src="com.whatever.MyTransformer">
someID
Daniel Fagerstrom wrote:
>
> Maybe we could have automatic daily snapshot releases, preferably to an
> m2 repository.
>
we sure can :-)
1. cron daily maven deployment to snapshot repository
2. declare a dependency like
cocoon
cocoon-core
2.2-SNAPSHOT
The snapshot bit is resolved to the lates
It seems that EHCache gets closed even if it was never initialized...
I think this came out only as a result of start cocoon, shutdown
cocoon (no requests made).
BTW, this is 2.1.8 final...
Pier
Begin forwarded message:
From: Jose Manuel Urio <[EMAIL PROTECTED]>
Date: 21 Novem
BURGHARD Éric wrote:
>
> Perhaps it could be usefull for you, so you can find the sources on a svn
> repository (the server is not always online: no-ip rulez :-)
>
I'll have a look at this, thanks!
> https://tagloo.no-ip.info/svn/public/maven-groovyplugin-api
> https://tagloo.no-ip.info/svn/pu
Tree with table and Ajax broken
---
Key: COCOON-1690
URL: http://issues.apache.org/jira/browse/COCOON-1690
Project: Cocoon
Type: Bug
Components: Blocks: Forms
Versions: 2.1.8
Reporter: Freek Segers
It seems that whenever
Bertrand Delacretaz wrote:
Le 21 nov. 05, à 10:54, Daniel Fagerstrom a écrit :
...IMO we should go for separate release cycles for 2.2. Then the we
should release "2.2" when the core is stable enough, and consider
whether the blocks are stable enough, a separate concern...
I'm all for this
Le 20 nov. 05, à 19:41, Carsten Ziegeler a écrit :
Now as 2.1.8 is out, we should think about a 2.2 release. I think for a
2.2 release we should at least finish the following things:
- Finish the maven2 build
And get rid of the ant-based build?
I think we should remove it as soon as the maven
Le 21 nov. 05, à 10:54, Daniel Fagerstrom a écrit :
...IMO we should go for separate release cycles for 2.2. Then the we
should release "2.2" when the core is stable enough, and consider
whether the blocks are stable enough, a separate concern...
I'm all for this, but how would people get unre
roy huang wrote:
> Hi,Sylvain:
> I think you misunderstood my problem,my problem is I want to using Ajax
> mode even when form submit and it is validate.
> When form is validate and using submit widget,the form is exit from
> form.showForm,and sendpage or redirectto,this lead a total refr
Carsten Ziegeler wrote:
Now as 2.1.8 is out, we should think about a 2.2 release. I think for a
2.2 release we should at least finish the following things:
- Finish the maven2 build
- Sync everything with 2.1.x (apply changes that were only applied to
2.1.x if appropriate)
- Separate samples fr
Hi,
Thanks to you (i'm just a follower :-), i switch my building scripts from
jelly+ant to a better maven 2 build cycle model. maven was on my todo list
since a long time, and i must admit that it has overcome my expectations.
To help the jelly migration i wrote an archetype for writing quickly g
Hi,Sylvain:
I think you misunderstood my problem,my problem is I want to using Ajax
mode even when form submit and it is validate.
When form is validate and using submit widget,the form is exit from
form.showForm,and sendpage or redirectto,this lead a total refresh in
browser.My goal is
No actually you got it right, but the point is that every element can have
that attribute, so I'd have to write such an action around every element in
the pipeline. We have quite a long pipeline, so this seems a bit bulky to me
and I'd want a more elegant solution.
Stefan
| -Ursprüngliche Na
Stefan Pietschmann schrieb:
Hello,
> | What do you mean by "attributes". Transformers, etc. can have hardwired
> | attributes associated with them when they are configured in the
> | component section of the sitemap. In addition, they can have parameters
> | declared in the pipelines which are pa
46 matches
Mail list logo
