Fix for ajax periodicalUpdate

Hi, I had some big trouble with the Internet-Explorer and periodical updates. The Internet-Explorer didnt really send the requests to the sever, but answered them from it's cache. Everytime the cache was manually cleared a real update was made, but only once. The following modifications made

SuggestionLists and JavaFlow

Hi, I am currently having some problems with JavaFlow and SuggestionLists. My application used to generate dynamic suggestion lists in the _cocoon/forms/suggest pipeline. Unfortunately the FormsGenerator, SuggestionListGenerator, JXGenerator and Transformer and my custom Generator seem to be

Re: SuggestionLists and JavaFlow

? Chris Torsten Curdt schrieb: On 09.05.2007, at 15:56, Christofer Dutz wrote: I am currently having some problems with JavaFlow and SuggestionLists. My application used to generate dynamic suggestion lists in the _cocoon/forms/suggest pipeline. Unfortunately the FormsGenerator

Re: SuggestionLists and JavaFlow

the FormInstance available automatically. Unfortunately this doesn't solve my SuggestionListProblem. My guess and my next try would be, to manually attach the FormInstance to the WebContinuation object, since this is not destroyed. Any suggestions or objections? Chris Christofer Dutz schrieb: Hi

[Solved] JavaFlow and SuggestionLists

Hi, For th last two weeks I was dealing with the problem, that SuggestionLists didn't work with JavaFlow anymore. In addition to this, also my Pipelines for saving form-data stopped workling. I could track both of them down to the problem, that the JavaInterpreter class constructs a

Re: [Solved] JavaFlow and SuggestionLists

everything runing without doing really big refactoring. Chris Torsten Curdt schrieb: Hm... sounds a bit hack'ish (and even worse) more work that it should be. What version of cocoon/javaflow are you talking about? cheers -- Torsten On 11.05.2007, at 10:10, Christofer Dutz wrote: Hi, For th

AW: Client-side validation in CForms

When I was working on my first attempts to do exactly what you are trying to do (CForms using dojo 1.1 and client side validation), I ran into exactly the same problem as you did. I too think it would be easily possible to implement client and server-side validation using dojo. Even if it would

AW: AW: Client-side validation in CForms

Betreff: Re: AW: Client-side validation in CForms Hi Christofer On 13 Jul 2008, at 13:13, Christofer Dutz wrote: When I was working on my first attempts to do exactly what you are trying to do (CForms using dojo 1.1 and client side validation), I ran into exactly the same problem as you

AW: AW: AW: Client-side validation in CForms

for a while :) Thanks again regards Jeremy On 14 Jul 2008, at 14:45, Christofer Dutz wrote: snip/ I think generating the validation-output needed for client side- validation shouldn't be a big problem, since it’s the same for almost all widgets the class having to be patched should

AW: AW: AW: AW: Client-side validation in CForms

Hi Chris Sorry it took me so long to reply. On 17 Jul 2008, at 16:48, Christofer Dutz wrote: Hi Jeremy, doesn't dojo load a i18n resource for the messages? It does, but this may be perceived as a problem because CForms users expect to supply all of their own i18n messages (and I personally

AW: CForms and Dojo

Gruber Senior Consultant +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Workflow EDV GmbH, Dannebergplatz 6/23, A-1030 Wien Christofer Dutz [EMAIL PROTECTED] 12.06.2008 09:54 Please respond to [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject CForms

AW: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

Here’s the KEYS file … there wasn’t any, so I initialized it with my key. https://dist.apache.org/repos/dist/dev/cocoon/KEYS Chris Von: Christofer Dutz Datum: Sonntag, 29. Oktober 2023 um 21:09 An: dev@cocoon.apache.org Cc: Cocoon PMC List Betreff: Re: [VOTE] Apache Cocoon 2.3.0 RC2 https

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ Everything looks good except I can't check the signature, I get "No public key" from gpg. I believe I need a copy of your public key to import? Peter Hunsberger On Sun, Oct 29, 2023 at 6:55 AM

[VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Release tag:

[CANCELLED] [VOTE] Apache Cocoon 2.3.0 RC1

I’m cancelling this RC, as we noticed that it only worked on Mac with Java 11, 17 and 21 and nothing on Windows and Linux or Java 1.8. RC2 will support Java 1.8, 11, 17, 21 on Mac, Linux, Windows. Chris Von: Christofer Dutz Datum: Dienstag, 24. Oktober 2023 um 20:49 An: Cocoon PMC List

AW: [VOTE] Apache Cocoon 2.3.0 RC1

compile with JDK 8, due to external dependencies being only JDK11+ And I also can't compile with JDK11+, due to XSP block complaining that it can't find tools.jar Cédric Le 24/10/2023 à 20:50, Christofer Dutz a écrit : Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote on accepting

[VOTE] Apache Cocoon 2.3.0 RC1

Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are required to pass. Release tag:

[DISCUSS][VOTE] Apache Cocoon 2.3.0 RC1

-24 12:50 p.m., Christofer Dutz wrote: Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote on accepting it for release. All Maven artifacts are available under [1]. Voting will be open for 72hr. A minimum of 3 binding +1 votes and more binding +1 than binding -1 are require

AW: "Fatal Error: Unable to locate package java.lang in classpath or bootclasspath" when upgrading to Tomcat9

I think I remember this being an issue with XSP … it required an SDK and not just a Java Runtime as it needs to compile stuff at runtime. Chris Von: Modou DIA Datum: Mittwoch, 25. Oktober 2023 um 11:35 An: dev@cocoon.apache.org Betreff: "Fatal Error: Unable to locate package java.lang in

Mailing list threading improvements

TL;DR: We’re updating how auto-generated email from Github will be threaded on your mailing lists. If you want to keep the old defaults, details are below. We’re pleased to let you know that we’re tweaking the way that auto- generated email from Github will appear on your mailing lists. This will

Need help?

Hi all, as I mentioned in your last report. I could possibly help with getting cocoon into a releaseable shape. Is there anything in particular, that you need help with? Chris

AW: Probably first user-question since many years ;-)

it frequently to call Cocoon pipelines from random threads, not linked to an actual http request. I've developed my own BackgroundRequest/BackgroundResponse more suiting my needs, but the concept is the same. Cédric Le 14/12/2023 à 08:50, Christofer Dutz a écrit : Hi all, as we’re thinking

Probably first user-question since many years ;-)

Hi all, as we’re thinking of giving 2.3 another try … I’m trying to make the ideas I had a bit more concrete … As some of you might know, I’m working mainly in the Industrial IoT area … here we have loads of data in odd data-structures and in general industial IoT consists of converting one

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

How about a Mexican style funeral party at Community Over Code? ;-) Cocoon 2.1 was such a big part of my early IT carreer … Chris Von: Cédric Damioli Datum: Montag, 18. Dezember 2023 um 19:40 An: dev@cocoon.apache.org Betreff: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x The vote is now over and

AW: [VOTE] Retire 2.1/3.0 and keep 2.x

+1 (non-binding) Chris Von: Cédric Damioli Datum: Mittwoch, 13. Dezember 2023 um 15:00 An: dev@cocoon.apache.org Betreff: [VOTE] Retire 2.1/3.0 and keep 2.x Hi, Following and according to last weeks' discussions, it seems that the general consensus would be to retire 2.1 (too old to be

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

So, I guess the deletion of the “retired” branches should probably be done by a PMC member. I’m happy to help with migrating 2.3.x to git as soon as the old stuff is buried, if the project wants this to happen. Chris Von: Christofer Dutz Datum: Montag, 18. Dezember 2023 um 20:25 An: dev

AW: [ANN] Apache Cocoon 2.3.0 Released

Anyone sharing this on LinkedIn and X? Chris Von: Cédric Damioli Datum: Dienstag, 28. November 2023 um 14:17 An: us...@cocoon.apache.org , dev@cocoon.apache.org , annou...@apache.org Betreff: [ANN] Apache Cocoon 2.3.0 Released Apache Cocoon 2.3.0 Released -

Re: [DISCUSS] Retiring 3.0 ? (Was: Re: Future of the Cocoon project)

I'd also vote +1 on retiring 3.0. There's only little activity overall I'd opt for concentrating it instead of fuchsig on too many things in parallel. Chris Gesendet von Outlook für Android From: Francesco Chicchiriccò Sent: Friday,

Re: [DISCUSS] Retiring 2.1.x ? (Was: Re: Future of the Cocoon project)

I'd be +1 to retire 2.1.x Even if I have fond memories of it, as it was my first major apache project. However it's grown quite old technically and refreshing things would be a huge effort. Some of the jvm versions needed are no longer available and I failed to even build it on 1.8. Don't

Re: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

I'd be -1 on retiring 2.x. I put in the work to fix things, cause I still think there's valid usecases for it. I would be willing to help and try to see, if we can reinitialize a small community around it. Chris Gesendet von Outlook für Android

AW: [DISCUSS] Retiring 2.x ? (Was: Re: Future of the Cocoon project)

Even if in the end we decide to keep 2.3.x running, we probably should go through the module list and retire some of the modules. I know that for some I couldn’t update to good versions, as the technology they use was abandoned. So, cutting the hair of our modules, might be necessary. Chris

AW: AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x +1 Cédric Le 23/01/2024 à 17:25, Christofer Dutz a écrit : Yeah … I also think that possibly making them read-only (and additionally prefixing them with a “retired/” prefix should be enough. Chris Von: Cédric Damioli <mailto:cdami...@apache.

AW: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

should retired branches be deleted ? Shouldn't they instead be somehow put in read-only state but kept available for anyone needing them ? My 2 cents, Cédric Le 09/01/2024 à 14:40, Christofer Dutz a écrit : So, I guess the deletion of the “retired” branches should probably be done by a PMC member

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

essary prerequisite to revive the community since it reduces the hurdle to get people involved. Jörg On 23.01.24 17:54, Christofer Dutz wrote: > Possibly worth discussing if it’s easier to port to Git and do that then > … or if better done in SVN … I guess the final discussion Git vs. SVN > still ne

AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x

Well, I guess as there were no objections, I’ll go forward with this. Chris Von: Christofer Dutz Datum: Dienstag, 30. Januar 2024 um 10:41 An: dev@cocoon.apache.org Betreff: AW: [RESULT][VOTE] Retire 2.1/3.0 and keep 2.x I’d be happy to take care of that. Chris Von: Gabriel Gruber Datum

Re: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

gratitude to you for taking on this task. -David On Sun, Oct 29, 2023 at 09:01:12PM +0000, Christofer Dutz wrote: > Here’s the KEYS file … there wasn’t any, so I initialized it with my key. > > https://dist.apache.org/repos/dist/dev/cocoon/KEYS > > Chris > > Von: Christofer Dutz >

AW: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

expect someone else to also have to move the RC to the distribution area, because I would expect to also not be allowed to move the files in SVN. Chris Von: Christofer Dutz Datum: Mittwoch, 15. November 2023 um 21:40 An: Cocoon PMC List , dev@cocoon.apache.org Cc: Cocoon PMC List Betreff: Re

[RESULT] [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

for going to the attic. Chris Von: Christofer Dutz Datum: Donnerstag, 16. November 2023 um 10:03 An: Cocoon PMC List , dev@cocoon.apache.org Cc: Cocoon PMC List Betreff: AW: [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ Ok. So I didn’t wait

AW: [RESULT] [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/

to finish this release. Chris Von: Christofer Dutz Datum: Sonntag, 19. November 2023 um 11:11 An: Cocoon PMC List , dev@cocoon.apache.org Cc: Cocoon PMC List Betreff: [RESULT] [VOTE] Apache Cocoon 2.3.0 RC2 https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc2/ Ok, So, I will now announce

Now that the release is out, what's next?

Hi folks, So, it seems that we finally have finished the last missing steps to formally get the release out the door. Now I think comes a time where we should reflect and discuss, what should happen with the Project. So instead of simply saying: Releasing it was such a struggle (not

AW: Now that the release is out, what's next?

java 21 and spring 6. However I need some help to become a formal contributor. Maybee you could help me in that? Thank you Gabriel From: Christofer Dutz Date: Monday, 20. November 2023 at 10:08 To: dev@cocoon.apache.org Subject: AW: Now that the release is out, what's next? Hi all, let me

AW: Now that the release is out, what's next?

On 2023-11-19 10:20 a.m., Christofer Dutz wrote: Hi folks, So, it seems that we finally have finished the last missing steps to formally get the release out the door. Now I think comes a time where we should reflect and discuss, what should happen with the Project. So instead of simply saying

[DISCUSS] Switching to GIt?

Hi all, I know that we currently have a mirror of the SVN in Github, however still the root repository is SVN, I would like to propose switching to using Git as the main repo. This would allow us to start using the normal GitHub Pull-Request workflow and possibly make it a lot easier for new

Re: Now that the release is out, what's next?

ements, and have evolved differently over the years. The community could either decide to stop the project as-is and go to the Attic, or start over maintaining only one or two branches. Cédric Le 19/11/2023 à 18:20, Christofer Dutz a écrit : Hi folks, So, it seems that we finally have f

Re: Now that the release is out, what's next?

ipated in this beautiful piece of software. Dan === On 2023-11-21 6:46 a.m., Peter Hunsberger wrote: On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz mailto:christofer.d...@c-ware.de>> wrote: Well guess I haven't stated it yet: I would be willing to work on it (I've especially for some ideas

Re: Now that the release is out, what's next?

what's next? Maybe a docker version could be attractive for non java users, who just want to work with xslt Pipelines and web resources? Gesendet von Outlook für Android<https://aka.ms/AAb9ysg> ____ From: Christofer Dutz Sent: Tuesday, November 21, 2023 10:55:5

AW: [IMPORTANT] Developer Survey on the State of Cocoon

Hi all, So, what’s the status of this? I haven’t started the Git migration as I thought it might make more sense to wait for the end of this. Chris Von: Torsten Curdt Datum: Dienstag, 20. Februar 2024 um 15:03 An: dev@cocoon.apache.org Betreff: [IMPORTANT] Developer Survey on the State of

AW: Developer Survey Results

Hi all, Admittedly the Chair position is a simple secretarial role. So, if this is the problem nobody wants to take on … I’d be willing to do that paperwork for a while. Chris Von: Torsten Curdt Datum: Donnerstag, 29. Februar 2024 um 01:19 An: dev@cocoon.apache.org Betreff: Developer Survey

AW: AW: Developer Survey Results

Hi all, What does another hat on the wall change? It’s sort of a slightly increased number of hats here ;-) Chris Von: Torsten Curdt Datum: Donnerstag, 29. Februar 2024 um 21:19 An: dev@cocoon.apache.org Betreff: Re: AW: Developer Survey Results During the past years, I always felt it was

Next steps?

Hi all, So, it’s been a while and I think we were waiting for the results of the survey. Not quite sure what we agreed upon what the next steps were. So far, I think one of the first steps I recall was a formal migration to using Git as a primary SCM. If that’s the case I would volunteer to do

AW: Next steps?

So, as this project is so low-volume … I think I’ll do what I did with similar projects. So, if I don’t hear anything else within the next 72h, I’ll initiate the Git migration. Chris Von: Christofer Dutz Datum: Samstag, 11. Mai 2024 um 19:12 An: dev@cocoon.apache.org Betreff: Next steps

[jira] [Commented] (COCOON-2359) [2.2] Fix incompatibility of cocoon-captcha with JDK 1.7/1.8

[ https://issues.apache.org/jira/browse/COCOON-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17791653#comment-17791653 ] Christofer Dutz commented on COCOON-2359: - Yeah ... I actually replaced all usages of JPEG types