Re: [vote] Ross Gardler as a new Cocoon committer
On 10/5/05, Daniel Fagerstrom [EMAIL PROTECTED] wrote: Hi all! I'd like to propose Ross Gardler as a Cocoon committer. He is one of the driving forces in the Forrest project, he has been quite active in our documentation efforts and in integrating Forrest, Lenya and Cocoon. +1, Ross well deserves it. -- Gianugo Rabellino Pro-netics s.r.l. - http://www.pro-netics.com Orixo, the XML business alliance: http://www.orixo.com (blogging at http://www.rabellino.it/blog/)
Re: [vote] Ross Gardler as a new Cocoon committer
On 06.10.2005, at 08:10, Gianugo Rabellino wrote: On 10/5/05, Daniel Fagerstrom [EMAIL PROTECTED] wrote: Hi all! I'd like to propose Ross Gardler as a Cocoon committer. He is one of the driving forces in the Forrest project, he has been quite active in our documentation efforts and in integrating Forrest, Lenya and Cocoon. +1 -- Torsten PGP.sig Description: This is a digitally signed message part
DO NOT REPLY [Bug 36466] - ImageReader problem with grayScaleFilter
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36466. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36466 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 09:56 --- As i've said before, i've modified the code so that color and grayscalefilter are recycled after each usage. Can you test this with 2.1.8dev (built from SVN) and report back? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: Daisy on cocoon.zones.apache.org upgraded
Bruno Dumon wrote: The Daisy on the zone is now upgraded to version 1.4-M1. If you used the editor recently (within a day), it is best to clear your browsers' cache first so the new javascript files etc. get loaded. New in Daisy 1.4 is the ability to publish books out of Daisy documents. I have created/published two of them, one for the new documentation and one for the legacy documentation (the book structure is based on the navigation structure). You can view them here: http://cocoon.zones.apache.org/daisy/books/ (warning: PDFs are 1.2 MB and 4.3 MB for the legacy docs) Thanks, it's brilliant. Bye, Helma
Re: svn commit: r306534 - in /cocoon: blocks/portal-sample/trunk/samples/ blocks/portal-sample/trunk/samples/conf/ blocks/portal/trunk/java/org/apache/cocoon/portal/ blocks/portal/trunk/java/org/apach
Will you be applying this to 2.1.8? Ralph [EMAIL PROTECTED] wrote: Author: cziegeler Date: Wed Oct 5 22:57:28 2005 New Revision: 306534 URL: http://svn.apache.org/viewcvs?rev=306534view=rev Log: Further cleanup of profile handling, improve user related event handling and adding profile saving to group based profile manager. Added: cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/authenticationfw/ cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/authenticationfw/LoginAction.java - copied, changed from r294901, cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/acting/LoginAction.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/authenticationfw/LogoutAction.java - copied, changed from r294901, cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/acting/LogoutAction.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/authenticationfw/User.java (with props) cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/event/user/UserEventUtil.java (with props) cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/event/user/UserIsAccessingEvent.java (with props) Removed: cocoon/blocks/portal-sample/trunk/samples/conf/auth-fw.xconf cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/acting/LoginAction.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/acting/LogoutAction.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/PortalUserInfoProvider.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/impl/AuthenticationFWUserInfoProvider.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/impl/UserInfoProvider.java Modified: cocoon/blocks/portal-sample/trunk/samples/conf/auth-cowarp.xconf cocoon/blocks/portal-sample/trunk/samples/conf/cocoon-portal-sample.xconf cocoon/blocks/portal-sample/trunk/samples/sitemap-auth.xmap cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/event/impl/DefaultEventManager.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/portal.roles cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/ProfileManager.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/impl/AbstractProfileManager.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/impl/GroupBasedProfileManager.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/impl/MapProfileLS.java cocoon/blocks/portal/trunk/java/org/apache/cocoon/portal/profile/impl/UserInfo.java cocoon/trunk/lib/optional/cowarp-0.5-dev-20051002.jar Modified: cocoon/blocks/portal-sample/trunk/samples/conf/auth-cowarp.xconf URL: http://svn.apache.org/viewcvs/cocoon/blocks/portal-sample/trunk/samples/conf/auth-cowarp.xconf?rev=306534r1=306533r2=306534view=diff == --- cocoon/blocks/portal-sample/trunk/samples/conf/auth-cowarp.xconf (original) +++ cocoon/blocks/portal-sample/trunk/samples/conf/auth-cowarp.xconf Wed Oct 5 22:57:28 2005 @@ -34,25 +34,6 @@ -- component role=org.osoco.cowarp.Application/portal class=org.osoco.cowarp.portal.StandardPortalApplication - security-handler=portal -profiles - copletbasedata-global-load uri=cocoon:raw:/load-global-profile?profile=copletbasedata/ - copletdata-global-load uri=cocoon:raw:/load-global-profile?profile=copletdata/ - copletdata-role-load uri=cocoon:raw:/load-role-profile?profile=copletdata/ - copletdata-user-load uri=cocoon:raw:/load-user-profile?profile=copletdata/ - copletinstancedata-global-load uri=cocoon:raw:/load-global-profile?profile=copletinstancedata/ - copletinstancedata-role-load uri=cocoon:raw:/load-role-profile?profile=copletinstancedata/ - copletinstancedata-user-load uri=cocoon:raw:/load-user-profile?profile=copletinstancedata/ - copletinstancedata-user-save uri=cocoon:raw:/save-user-profile?profile=copletinstancedata/ - layout-global-load uri=cocoon:raw:/load-global-profile?profile=layout/ - layout-role-load uri=cocoon:raw:/load-role-profile?profile=layout/ - layout-user-load uri=cocoon:raw:/load-user-profile?profile=layout/ - layout-user-save uri=cocoon:raw:/save-user-profile?profile=layout/ -/profiles - /component - component class=org.apache.cocoon.portal.profile.impl.GroupBasedProfileManager - role=org.apache.cocoon.portal.profile.ProfileManager -parameter name=userinfo-provider value=org.osoco.cowarp.portal.UserInfoProviderImpl/ - /component + security-handler=portal/ /components Modified: cocoon/blocks/portal-sample/trunk/samples/conf/cocoon-portal-sample.xconf URL: http://svn.apache.org/viewcvs/cocoon/blocks/portal-sample/trunk/samples/conf/cocoon-portal-sample.xconf?rev=306534r1=306533r2=306534view=diff
Re: [RT] seven good reasons to close down users@cocoon.apache.org
Too bad you cannot cross-post between the two lists, that alone could have made things easier. The developer list should receive mails also from the user list with [Users] prepended. In this way developers get user mails, but users don't need to read all the longwinding discussions about internals (which tend to frighten some). TBH I think forwarding the mails from users to dev is nothing but saying developers have to be subscribed to users. Whether forcing this is a good or a bad idea is a different thing ...but I am still in favor of *not* forwarding. I don't really see the point of it. Let's better have a few more developer subscribed to users again. cheers -- Torsten PGP.sig Description: This is a digitally signed message part
Re: svn commit: r306534 - in /cocoon: blocks/portal-sample/trunk/samples/ blocks/portal-sample/trunk/samples/conf/ blocks/portal/trunk/java/org/apache/cocoon/portal/ blocks/portal/trunk/java/org/apach
Ralph Goers schrieb: Will you be applying this to 2.1.8? Yes, as soon as its working :) I'm just trying to test it. Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
Re: [RT] seven good reasons to close down users@cocoon.apache.org
Le 6 oct. 05, à 10:04, Torsten Curdt a écrit : ...Let's better have a few more developer subscribed to users again Yes, after this discussion I think it's good enough - and I like the idea of filtering both lists to the same folder in my mail client, so as not to overlook user's messages. I'll try that! -Bertrand
Re: [RT] seven good reasons to close down users@cocoon.apache.org
you want to reduce that count, I am still interested in hints on - why I'm getting Attempted to release a $Proxy20 but its handler could not be located. messages in my logs. [1] - why the ComponentManager appears to be null in my transformers' (SitemapComponentTestCase subclass) unit tests but not my actions'. [2] In my experience, it doesn't matter which list I ask for help on, it still gets ignored. That sounds really frustrated. Sorry about that. Or maybe it's just me. Maybe it just did not ring a bell when people read it. Being a developer does not necessarily mean having the answer right away. In the end it probably comes down to how much time a developer can spend on tracking down the bug you are seeing. If you can reduce that time you are more likely to get an answer. Just my 2 cents cheers -- Torsten PGP.sig Description: This is a digitally signed message part
DO NOT REPLY [Bug 36781] - [PATCH] repeater min and maxsize attributes
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36781. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36781 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 10:28 --- applied, thanks. I did not apply the modifications to the samples, it would be better to have a separate sample for this. I have updated the documentation in Daisy. Please check if all went in ok and close. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 34015] - Cforms greek messages
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34015. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34015 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 10:36 --- FormsMessages is added to the CForms block system resources. The other two files are saved for future processing. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36612] - [Link] OSN
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36612. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36612 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 10:48 --- Info added to Daisy -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36946] New: - error in forms samples
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36946. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36946 Summary: error in forms samples Product: Cocoon 2 Version: Current SVN 2.1 Platform: Other URL: http://localhost:/samples/blocks/forms/v2/example OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Samples AssignedTo: dev@cocoon.apache.org ReportedBy: [EMAIL PROTECTED] Validation rule value-count cannot be used with strings, error at file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/forms/v2/form1.xml:115:38 file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/forms/v2/form1.xml - 115:38 Error calling flowscript function example file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/forms/v2/form1.xml - 115:38 [Exception] resource://org/apache/cocoon/forms/flow/javascript/v2/Form.js - 53:-1 file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/forms/v2/forms_flow_example.js - 27:-1 file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/forms/v2/forms_flow_example.js - 22:-1 file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/forms/v2/sitemap.xmap - 68:39 map:call file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/forms/sitemap.xmap - 575:65 map:mount file:/D:/src/cocoon-2.1.x/build/webapp/samples/blocks/sitemap.xmap - 66:68 map:mount file:/D:/src/cocoon-2.1.x/build/webapp/samples/sitemap.xmap - 194:65 map:mount file:/D:/src/cocoon-2.1.x/build/webapp/sitemap.xmap - 663:66map:mount -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 34084] - [2.1.7 Testing] Various
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34084. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34084 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 10:55 --- @marco: the error still persists after applying your patch. I've moved this particular issue to #36946 -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36946] - error in forms samples
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36946. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36946 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 10:56 --- initial patch from marco rolappe (bug #34084) did not resolve the issue. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 34084] - [2.1.7 Testing] Various
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34084. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34084 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Antwort: RE: [GT2005] notetaking
Hi Arjé, Please invite me :-) mit freundlichen Grüßen / kind regards Manfred Weigel Raiffeisen Zentralbank Österreich AG ORG/IT - Software Development A-1030 Vienna, Am Stadtpark 9 [EMAIL PROTECTED]@inet [EMAIL PROTECTED]@inet 05.10.2005 12:00 Bitte antworten an dev@cocoon.apache.org@inet An dev@cocoon.apache.org Kopie Thema RE: [GT2005] notetaking Apparentely, you have to be invited to be able to join this page... Please reply on this thread and I'll invite you.. -Original Message- From: Arje Cahn Posted At: woensdag 5 oktober 2005 10:59 Posted To: Cocoon Dev List Conversation: [GT2005] notetaking Subject: [GT2005] notetaking we're taking notes now at www.jotlive.com/hippo/Cocoon%20GT feel free to join! Kind regards, Met vriendelijke groet, Arjé Cahn Hippo Oosteinde 11 1017WT Amsterdam The Netherlands Tel +31 (0)20 5224466 - [EMAIL PROTECTED] / www.hippo.nl -- This message and any attachment (the Message) are confidential. If you have received the Message in error, please notify the sender immediately and delete the Message from your system , any use of the Message is forbidden. Correspondence via e-mail is primarily for information purposes. RZB neither makes nor accepts legally binding statements unless otherwise agreed to the contrary.
DO NOT REPLY [Bug 36872] - Internal pipelines eat HTTP headers without warning
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36872. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36872 [EMAIL PROTECTED] changed: What|Removed |Added Summary|Internal pipelines and |Internal pipelines eat HTTP |map:mount eat HTTP headers |headers without warning |without warning | --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 11:19 --- Corrected the title, map:mount does not eat the headers -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36872] - Internal pipelines eat HTTP headers without warning
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36872. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36872 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 11:37 --- The initial problem (http://marc.theaimsgroup.com/?l=xml-cocoon-devm=109783251408219w=2) was I have the following case : generatorreader | | validator .. dtd | serializer Where the dtd reader sets Content-Length, which is obviously wrong for the final output. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 35979] - fi:validation-errors styling element does not work in AJAX mode
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35979. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35979 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |ASSIGNED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
DO NOT REPLY [Bug 33315] - cygwin detection in build.sh is not optimal
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33315. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33315 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 11:50 --- fixed using snippet from cocoon.sh -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
add --noconfig as a default ant option in build.sh?
Sandor Spruit suggests this, see http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=112858673106600w=2 Any objections to make this the default when ant is called from build.sh? If not I'll add it to the branch and trunk builds. What the option does for ant is: --noconfig suppress sourcing of /etc/ant.conf, $HOME/.ant/ant.conf, and $HOME/.antrc configuration files -Bertrand
Re: add --noconfig as a default ant option in build.sh?
Bertrand Delacretaz wrote: Sandor Spruit suggests this, see http://marc.theaimsgroup.com/?l=xml-cocoon-usersm=112858673106600w=2 Any objections to make this the default when ant is called from build.sh? If not I'll add it to the branch and trunk builds. What the option does for ant is: --noconfig suppress sourcing of /etc/ant.conf, $HOME/.ant/ant.conf, and $HOME/.antrc configuration files Makes a lot of sense. This would explain why some people seem to have trouble with our ant build. Regards, Upayavira
DO NOT REPLY [Bug 30406] - [javaflow] JavaFlow throws VerifyError when using .class in code
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30406. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30406 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|dev@cocoon.apache.org |commons- ||[EMAIL PROTECTED] Component|blocks |Sandbox Product|Cocoon 2|Commons Summary|JavaFlow throws VerifyError |[javaflow] JavaFlow throws |when using .class in code |VerifyError when using ||.class in code Version|2.1.5 |Nightly Builds -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 35595] - SQLTransformer makes Cocoon hang under high load
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35595. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35595 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 12:12 --- You missed several things: 1. Since Cocoon 2.1.8 (not released yet), SQLTransformer re-uses connection for nested queries, if possible. In your example, it will use 1 connection per request, and will not block. 2. Even if you do require multiple connections, connectAttempts and connectWaittime are configurable - see transformer docs. 3. Database connection pool can be configured either to block (and wait), or to throw exception immediately if no connections are available in the pool. Make sure you have properly configured both pool and transformer, and get latest transformer version from the SVN. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 23939] - document('relative-URI') seems to resolve wrongly depending on request-URI (SourceResolver?)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=23939. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=23939 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 12:36 --- (In reply to comment #3) Can someone tell the status of this bug? I have tried to reproduce this bug in Cocoon 2.1.7, but was unsuccessful. The scenarios described here all work. The only way to get a count of 0 (document cannot be read) is when the URL in the document function points to a non-existent file, or when the file contains a DOCTYPE declaration which cannot be resolved. That is normal behaviour. The files mentioned in this bug cannot be downloaded any more; they have disappeared from the server. So I reconstructed something very close on the basis of the info given. I think this bug can be resolved as FIXED. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 30894] - SQLTransformer doesn't support SPs that return a result set
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30894. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30894 [EMAIL PROTECTED] changed: What|Removed |Added CC||dev@cocoon.apache.org AssignedTo|dev@cocoon.apache.org |[EMAIL PROTECTED] -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is.
DO NOT REPLY [Bug 36949] New: - SendMailTransformer and HTML body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36949. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36949 Summary: SendMailTransformer and HTML body Product: Cocoon 2 Version: Current SVN 2.1 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: blocks AssignedTo: dev@cocoon.apache.org ReportedBy: [EMAIL PROTECTED] The SendMailTransformer is unable to handle XML tags directly in the SAX flow. ex : email:sendmail email:smtphostsmtp/email:smtphost email:from[EMAIL PROTECTED]/email:from email:to[EMAIL PROTECTED]/email:to email:subject Bogus sendmailtrasformer /email:subject email:body htmlbody pthis is a paragraph/p panother/p /body/html /email:body /email:sendmail It simply remove xml tags in the body ! It a a strange behaviour since DEFAULT_BODY_MIMETYPE = text/html ... -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36949] - SendMailTransformer and HTML body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36949. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36949 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 12:45 --- Created an attachment (id=16604) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16604action=view) Patch to make it working This patch solves the problem -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: [RT] seven good reasons to close down users@cocoon.apache.org
In my experience, it doesn't matter which list I ask for help on, it still gets ignored. That sounds really frustrated.Sorry about that. My experience (although probably not objectively realistic, and biased by bad experiences) is that my first request for help is usually answered, even by a few people, but without fully solving the problem (blame me: my first post contains most certainly insufficient information), and the second round is unanswered. So I usually get insightful answers which help me continue my research (good), but that does not necessarily means the problem is solved (bad). At most, what I tend to get is a kind of workaround (not too bad, but could be better). Maybe it just did not ringa bell when people read it. That's the strange point about my feeling. It seems to ring the bell the first time, but not loud enough to follow up. In the end it probably comesdown to how much time a developercan spend on tracking down the bug you are seeing.If you can reduce that timeyou are more likely to get ananswer. I try, but it is not always easy, if you don't have enough knowledge about internals. OTOH, I know many users (myself included) seldom try to help others, probably because of lack of time. But if users don't have time, why should developers?-- Antonio
DO NOT REPLY [Bug 23939] - document('relative-URI') seems to resolve wrongly depending on request-URI (SourceResolver?)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=23939. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=23939 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 12:54 --- Created an attachment (id=16605) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16605action=view) testcase (reconstructed from info in description) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 28522] - fd:aggregatefield and fd:split pattern
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=28522. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=28522 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 12:58 --- Created an attachment (id=16606) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16606action=view) Patch for AggregateField to check if the combined value matches the split pattern The problem is twofold: 1. The validation isn't done at all (patch fixes this) 2. Only the sub fields of the aggregate field are rendered, so any validation error which is associated with the aggregate field itself has to be extracted and displayed with separately. With the patch applied, you can use ft:validation-error id=myaggregatefieldid/ to render only the validation error (if there is one). I also adapted the sample for the aggregate field to reflect this. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 30796] - exception when form has no action attribute
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30796. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30796 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 13:42 --- Created an attachment (id=16607) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16607action=view) Checks if attributes are present The patch adds some checking and throws an exception in case some attributes are missing. The FormHandler catches the exception and throws a new SAXException with location information so you know where it went wrong. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 35811] - [html block] HTMLGenerator doesn't copy POST parameters
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=35811. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=35811 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 13:48 --- /at the GT2005 Hackaton/ There would be still a need for a proper test cast/scenario for this issue. Nevertheless a short exploration of the HTMLGenerator lead to two conclusions in the subject of passing POST parameters (in addition to GET parameters) passed to the Cocoon request that invoked this generator. 1. there is a chance of exceeding the GET request size limit that some servers might still have. this chance also exists in the current implementation of the HTMLGenerator as it concatenates the URI params from the Cocoon request and the params in the src attribute passed to the generator in the sitemap 2. at first you might want to change the implementation of HTMLGenerator in a simple manner, by changing: query.append(request.getQueryString()); to a loop iterating over the request.getParameterNames() and request.getParameterValues() BUT! this might lead to trouble as the request there is a Cocoon wrapper for the real HTTPServletRequest object, and it's getParameterValues() implementation decodes this array of parameters before returning them. this might not be an issue for the English language, but for many European languages this might break the resulting URL. So the second conclusion is actually a tip that this bug (or call it a restriction) can be overcome by adding a getRawParametersValues() method to the request wrapper that simply returns the HTTPServletRequest.getParameterValues() and iterating this array in the HTTPGenerator.setup instead of the getQueryString() call. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 33545] - [Enh] Make StatusGenerator show Cocoon version information
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33545. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33545 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 13:58 --- Created an attachment (id=16608) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16608action=view) patch for the StatusGenerator.java in order to show the contents of WEB-INF/lib patch for listing WEB-INF/lib directory contents, also added parameter lib in order to hide the output for security reasons -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is.
DO NOT REPLY [Bug 30796] - exception when form has no action attribute
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=30796. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=30796 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 14:01 --- Thanks, applied. Please check and close. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 33004] - Cocoon consumes 100% of CPU and never releases it
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33004. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33004 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||LATER -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 33004] - Cocoon consumes 100% of CPU and never releases it
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33004. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33004 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
[Docs] Semi-automatic update process of the Cocoon documentation
After talks to several people I feel we need a semi-automatic update process of the Cocoon documentation to cocoon.apache.org. Several reasons: - frequent updates show users that there is concern about their documentation wishes. We might even write documentation that answers FAQs and point the users to that, rather than rewriting the information on the mailing list. - semi-automatic updates avoid the reinvention of the wheel for every committer trying to update the website and avoid the errors that created the current crippled site. - the current Daisy on the cocoon.zones contains the most recent version of the documentation and provides an easier way of adding and updating the documentation. - with the current update of Daisy, Daisy books have become available and allow the documentation to be exported as a book in both HTML and PDF. New process: - set up a small Cocoon branding website in the current xdocs section with only a few pages that contain relative static content. Compare it to the Springframework website. - These pages contain links to the actual reference documentation which are available as Daisy book in both HTML (for browsing on the website) and in PDF (for downloading and printing). - on cocoon.zones a Forrest configuration is setup with all the tweaks necessary to get the job done. - a script is created that can do the Daisy books export, do the Forrest conversion and the upload on the cocoon.apache.org site and all the necessary steps in between. - the end result of the script is that the documentation is available as a complete website on cocoon.apache.org AND for inclusion in the next Cocoon release. - a secured button is available for committers to start this script. Whether it is available as a password protected page, a ssh command or whatever. - a notification can be sent to the dev-list when the site update hasn't been done in X days. WDYT? It would be good to get the end result as described (but manual, rather than semi-automatic for now) ASAP for inclusion in the upcoming 2.1.8 release. Bye, Helma
DO NOT REPLY [Bug 36949] - [PATCH] SendMailTransformer and HTML body
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36949. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36949 [EMAIL PROTECTED] changed: What|Removed |Added Severity|normal |critical Summary|SendMailTransformer and HTML|[PATCH] SendMailTransformer |body|and HTML body -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 33545] - [PATCH] Make StatusGenerator show Cocoon version information
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=33545. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=33545 [EMAIL PROTECTED] changed: What|Removed |Added Summary|[Enh] Make StatusGenerator |[PATCH] Make StatusGenerator |show Cocoon version |show Cocoon version |information |information -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. You are on the CC list for the bug, or are watching someone who is.
Re: [Docs] Semi-automatic update process of the Cocoon documentation
hepabolu wrote: After talks to several people I feel we need a semi-automatic update process of the Cocoon documentation to cocoon.apache.org. Several reasons: - frequent updates show users that there is concern about their documentation wishes. We might even write documentation that answers FAQs and point the users to that, rather than rewriting the information on the mailing list. This last sentence is IMO a very good idea from the community point of view for both users and developers. - users will be educated to search first in the docs, as we will have good and up to date docs, which is a kind of revolution :-) - developers will have go to the docs in search of information, which will make them care more about it. One of the current problems is that devs don't really need docs and thus don't care much about it (as we say in France: far from the eyes is far from the heart). - the documentation will be frequently updated based on user feeback and questions. So this makes the documentation a part of the community conversations on the mailing-list. And this is very easy solution to help ensure it is kept up to date. - semi-automatic updates avoid the reinvention of the wheel for every committer trying to update the website and avoid the errors that created the current crippled site. - the current Daisy on the cocoon.zones contains the most recent version of the documentation and provides an easier way of adding and updating the documentation. - with the current update of Daisy, Daisy books have become available and allow the documentation to be exported as a book in both HTML and PDF. New process: - set up a small Cocoon branding website in the current xdocs section with only a few pages that contain relative static content. Compare it to the Springframework website. - These pages contain links to the actual reference documentation which are available as Daisy book in both HTML (for browsing on the website) and in PDF (for downloading and printing). - on cocoon.zones a Forrest configuration is setup with all the tweaks necessary to get the job done. - a script is created that can do the Daisy books export, do the Forrest conversion and the upload on the cocoon.apache.org site and all the necessary steps in between. - the end result of the script is that the documentation is available as a complete website on cocoon.apache.org AND for inclusion in the next Cocoon release. - a secured button is available for committers to start this script. Whether it is available as a password protected page, a ssh command or whatever. - a notification can be sent to the dev-list when the site update hasn't been done in X days. This last point ensure we don't let the website become obsolete, without having to setup some completely automated publication which isn't good as we must have a human oversight on what is published on the official website. WDYT? +1000 :-) It would be good to get the end result as described (but manual, rather than semi-automatic for now) ASAP for inclusion in the upcoming 2.1.8 release. Another +1000. But we should not delay the release because of this, which probably means that the docs that will be shipped with 2.1.8 will not have a nice skin. But accurate information matters more than presentation. Sylvain -- Sylvain WallezAnyware Technologies http://people.apache.org/~sylvain http://www.anyware-tech.com Apache Software Foundation Member Research Technology Director
DO NOT REPLY [Bug 31275] - Add SitemapPathModule input module
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31275. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31275 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 14:55 --- In bug 35435, Sylvain says: The Environment object is internal to the Cocoon engine and the CocoonComponentManager is for internal use only. This makes the proposed input module a bad idea. However, there seems to be no other way to get the absolute path to the current sitemap (which may be mounted!). If only an input module could have a source resolver, this would be easy to implement. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 27147] - Cocoon Forms field styling: selection lists with optgroups
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=27147. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=27147 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #10484|0 |1 is obsolete|| --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 15:12 --- Created an attachment (id=16610) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16610action=view) Implements OptGroups in Static/Dynamic Selection lists for CForms The patch implements optgroups for the current cforms trunk. StaticSelectionList as well as the DynamicSelectionList now support it. Define like this: fd:selection-list fd:item value=fd:labelmylabel/fd:label/fd:item fd:optgroup fd:labelgrouplabel/fd:label fd:item value=1fd:labelsubitem 1/fd:label/fd:item fd:item value=2fd:labelsubitem 2/fd:label/fd:item /fd:optgroup /fd:selection-list The forms-field-styling.xsl currently only renders optgroups and nested items in a dropdown list. Radio-/Checkboxes and output types are not implemented yet. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 25115] - [Roadmap] General review of all XML elements
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=25115. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=25115 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 15:12 --- repeater-row = repeater-item row might be misleading -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 31813] - [Sample] DreamTeam (dependent widgets in a repeater)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31813. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31813 [EMAIL PROTECTED] changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 15:29 --- Shielding the vars from null fixes the problem and makes the content-view appear again. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
DO NOT REPLY [Bug 31813] - [Sample] DreamTeam (dependent widgets in a repeater)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31813. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31813 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Continuation Time-To-Live Config Not Being Honored
After experiencing some interesting behavior with Invalid Continuation Errors I have performed some tests and have found that no matter what I set the time-to-live value to in cocoon.xconf the continuations always expire after 10 minutes. Is the time-to-live attribute of the continuations-manager not being honored? Where is the default value of 10 minutes being set? Some more information based on the tests I ran is below. It seems that the period and offset are being followed, I can see this in the log files, but the time to live is being ignored. The session is not timing out at 10 minutes. The session is set to 30 minutes and the log file for the session show the sessions ending correctly. continuations-manager continuation-sharing-bug-compatible=false logger=flow.manager session-bound-continuations=true time-to-live=6 expirations-check type=periodic offset3/offset period3/period /expirations-check /continuations-manager Every 30 seconds I see a continuation check being run, but it is 10 minutes before the continuation is cleaned up. continuations-manager continuation-sharing-bug-compatible=false logger=flow.manager session-bound-continuations=true time-to-live=180 expirations-check type=periodic offset90/offset period90/period /expirations-check /continuations-manager These are the settings that I run with in my development environment. 30 minutes time to live, with a 15 minute offset and period. When running with these settings, continuations are still deleted after 10 minutes. It is harder to observe this happening in this environment, as the period of 15 minutes can mask this. To get a better picture I ran with continuations-manager continuation-sharing-bug-compatible=false logger=flow.manager session-bound-continuations=true time-to-live=180 expirations-check type=periodic offset6/offset period6/period /expirations-check /continuations-manager Still a 30 minute time-to-live, but a 1 minute offset and period. With these settings the continuations are cleaned up 10 minutes after they are created. Thanks, Dan
DO NOT REPLY [Bug 36612] - [Link] OSN
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36612. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36612 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 34015] - Cforms greek messages
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=34015. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=34015 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Introducing Guilder
Guilder is a little graphical interface whose aim is to simplify the life of Cocoon newbies by providing: - easy selection of blocks and features, taking dependencies in due consideration - starting the build - starting and stopping Cocoon via Jetty Most of the programming has been done by my colleague Daniele Madama (d.madama AT pronetics DOT it), who already introduced his work in this thread [1]. This is just a first, rough version, but we wanted to commit it as soon as possible, following the OSS mantra of release early, release often and what better occasion than the GetTogether to do it? Much work remains to be done, like for instance: - polishing the UI - stopping Jetty (does not work at the moment) - showing the progress of the build in a window - etc. but now that the code is available, if you want to contribute you can check out the code from [2] and start hacking away. Just use ant to build it. It will copy a JAR file in Cocoon's directory (by default ../../BRANCHES_2_1_X but you can ovveride it in guilder.properties) and you should then launch it by moving to Cocoon's home directory and running java -jar tools/lib/guilder.jar. It is our hope that this tool will make Cocoon more popular by presenting a simpler approach than what is provided by the present installation procedure, which might scare some users away. Once it is sufficiently polished, we could simply distribute the jar together with every Cocoon release, as this is a simple addition that does not change in any other way the existing build. Guilder is just for Cocoon 2.1. The configuration and build procedure in the coming major releases will be very different and won't probably need such a tool, but it is expected that many people will be working with 2.1 for a long time still. Why the name Guilder? The original name was Cocoon builder but soon it became something more than a simple builder. We also wanted to emphasize the GUI aspect. Since I am in Amsterdam right now, the name Guilder came up naturally. Guilder (gulden in Dutch) was the name of the Dutch currency before the Euro. Ugo [1] http://marc.theaimsgroup.com/?l=xml-cocoon-devm=112722937629151w=2 [2] http://svn.apache.org/repos/asf/cocoon/whiteboard/guilder -- Ugo Cei Tech Blog: http://agylen.com/ Open Source Zone: http://oszone.org/ Wine Food Blog: http://www.divinocibo.it/
DO NOT REPLY [Bug 31275] - Add SitemapPathModule input module
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=31275. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=31275 [EMAIL PROTECTED] changed: What|Removed |Added Attachment #12795|0 |1 is obsolete|| -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
[VOTE] snapshot release of the bricks-cms example app
I'd like to put a snapshot of the bricks-cms [1] example on our download servers, so that people can get it without requiring an SVN client. It is not a formal release, but I'd like to have the community's approval before doing it. Please cast your votes, here's my own: +1 -Bertrand [1] http://wiki.apache.org/cocoon/BricksCms
Problem with ESQL and Unicode
Using ESQL against MSSQL Server, any NTEXT or NVARCHAR are incorrectly re-encoded to ISO 8859. Directly using the driver yields the correct results.
DO NOT REPLY [Bug 36251] - Cocoon 2.1.7 does not compile - in mysterious circumstances
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36251. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36251 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 17:24 --- I got this same error with JDK 1.5.0_5, but it went away when I removed the following jars from lib/ext: avalon-framework-cvs-20020806.jar batik.jar fop.jar jai_codec.jar jai_core.jar mlibwrapper_jai.jar QTJava.zip resolver.jar saxon.jar saxon653.jar serializer.jar xalan.jar xalan25.jar xercesImpl.jar xml-apis.jar For me, this was a user-configuration error. I don't know which jar was causing the problem. Anyway, hope this helps. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Re: [Docs] Semi-automatic update process of the Cocoon documentation
hepabolu wrote: After talks to several people I feel we need a semi-automatic update process of the Cocoon documentation to cocoon.apache.org. snip what=details of proposal/ All sounds great, in fact, most of the automated publishing side an be done by the ForrestBot. See http://forrest.zones.apache.org/ The forrestbot can publish via various methods including SVN. I just have to find the time to do the test build using Forrest+Daisy (should be in the next day or two). Ross
Re: [VOTE] snapshot release of the bricks-cms example app
Bertrand Delacretaz schrieb: I'd like to put a snapshot of the bricks-cms [1] example on our download servers, so that people can get it without requiring an SVN client. It is not a formal release, but I'd like to have the community's approval before doing it. Please cast your votes, here's my own: +1 -Bertrand [1] http://wiki.apache.org/cocoon/BricksCms +1 (If you need some help, just let me know) Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
[CForms] add-row widget
Hi all,
I am trying to invoke the add-row action from a custom jscript but I do
not know how.
I need to invoke the add-row action after some other steps on the client
side. I thought in just copying the transformed html code it would work,
but no.
I tried with something like:
a href=javascript:void(0)
onClick=forms_submitForm(document.getElementById('section.0.story.0.add'),
'section.0.story.0.add')test/a
...but I get Error: forms_submitForm is not defined
On the other hand this is working fine when it is in the input /, so I
do not understand why it is not working in above code (I reckon it has
something to do with ajax, but not sure).
Is it possible to invoke the add-row action from custom jscript? If so
can somebody *please* give some hints. I am lost and spend the whole day
in try and error. :(
TIA for any hints
salu2
--
thorsten
Together we stand, divided we fall!
Hey you (Pink Floyd)
DO NOT REPLY [Bug 36954] New: - DELI Aspect Renderer for Cocoon Portal
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36954. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36954 Summary: DELI Aspect Renderer for Cocoon Portal Product: Cocoon 2 Version: Current SVN 2.2 Platform: All URL: http://www.mail- archive.com/users@cocoon.apache.org/msg29668.html OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: blocks AssignedTo: dev@cocoon.apache.org ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] I developed an aspect renderer for cocoon portal. It is similar to XSLTAspect but passes deli-capabilities parameter to the XSLT sheets used to render the portal. Any comments? -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
DO NOT REPLY [Bug 36954] - DELI Aspect Renderer for Cocoon Portal
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=36954. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36954 --- Additional Comments From [EMAIL PROTECTED] 2005-10-06 19:53 --- Created an attachment (id=16611) -- (http://issues.apache.org/bugzilla/attachment.cgi?id=16611action=view) Deli Aspect Renderer Class -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee.
Cocoon Fat Test
Carsten hates me when I just talk, so here is some action: let's measure cocoon's fat. Follow me and type the following in your terminal svn co http://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X/ \ cocoon svn co http://simile.mit.edu/repository/linotype/trunk/ linotype export COCOON_HOME=../cocoon/ cd linotype ant install ant run then point your browser at http://127.0.0.1:/linotype/ you should see an empty linotype running. Now, ctrl-break the above, and do zip -r linotype.war dist/ the resulting WAR is 12263572 bytes. How much of this is linotype? zip -r linotype.zip dist/linotype/ results in a 129673 bytes. Cocoon has a platform overhead of 11Mb. *compressed* Now let's see where the things are: cd dist du -d1 returns 1152./linotype 144 ./resources 128 ./stylesheets 27472 ./WEB-INF 29000 . so cd WEB-INF du -d1 returns 8 ./classes 1544./entities 25776 ./lib 27472 . So, it's clear that cocoon weight is in the jars. NOTE: the linotype build system builds cocoon from source with the most stripped-down version as Linotype does not depend on any blocks. This is the minimal 2.1.x cocoon possible right now. Let's see the list of jars cd lib ls -AlS (with some little hand cleaning) 2941481 jdtcore-3.0.2.jar 2730442 xalan-2.7.0.jar 1395202 cocoon-2.1.8-dev.jar 1203860 xercesImpl-2.7.1.jar 607235 rhino1.5r4-continuations-R26.jar 552263 commons-collections-3.1.jar 522143 jakarta-bcel-20040329.jar 394671 jcs-1.2.5-dev-20050313.jar 358085 log4j-1.2.12.jar 285104 commons-jxpath-1.2.jar 225375 commons-httpclient-2.0.2.jar 207723 commons-lang-2.1.jar 194205 xml-apis-1.3.02.jar 189284 util.concurrent-1.3.4.jar 131458 commons-jexl-1.0.jar 115506 excalibur-instrument-mgr-http-2.1.jar 89145 excalibur-logger-2.1.jar 86665 excalibur-xmlutil-2.1.jar 83582 avalon-logkit-2.1.jar 80572 excalibur-component-1.2.jar 78599 excalibur-sourceresolve-2.1.jar 65948 excalibur-naming-1.0.jar 60047 xml-commons-resolver-1.1.jar 59645 avalon-framework-impl-4.3.jar 57548 excalibur-instrument-mgr-impl-2.1.jar 47531 ehcache-1.1.jar 42137 excalibur-store-2.1.jar 40737 excalibur-io-1.1.jar 38015 commons-logging-1.0.4.jar 32112 avalon-framework-api-4.3.jar 30117 commons-cli-1.0.jar 28584 jakarta-regexp-1.4.jar 27833 excalibur-pool-impl-2.1.jar 21028 javacImpl-0.9.jar 20640 excalibur-instrument-mgr-api-2.1.jar 20328 excalibur-instrument-api-2.1.jar 18329 excalibur-pool-instrumented-2.1.jar 14728 excalibur-pool-api-2.1.jar 8238 excalibur-i18n-1.1.jar 3565 javacApi-0.9.jar now, let's take a look 1) I don't use XSP nor javaflow, therefore I wouldn't need JDTcore, nor BCEL, nor javacImpl and javacAPI, a total of several Mb. 2) I don't use the avalon instrumentation 3) I use logkit, so I don't need log4j 4) I put the latest xalan and xerces in my app server, no need to have it here too here is the slimmed down cocoon 1395202 cocoon-2.1.8-dev.jar 607235 rhino1.5r4-continuations-R26.jar 552263 commons-collections-3.1.jar 285104 commons-jxpath-1.2.jar 225375 commons-httpclient-2.0.2.jar 207723 commons-lang-2.1.jar 194205 xml-apis-1.3.02.jar 189284 util.concurrent-1.3.4.jar 131458 commons-jexl-1.0.jar 89145 excalibur-logger-2.1.jar 86665 excalibur-xmlutil-2.1.jar 83582 avalon-logkit-2.1.jar 80572 excalibur-component-1.2.jar 78599 excalibur-sourceresolve-2.1.jar 65948 excalibur-naming-1.0.jar 60047 xml-commons-resolver-1.1.jar 59645 avalon-framework-impl-4.3.jar 47531 ehcache-1.1.jar 42137 excalibur-store-2.1.jar 40737 excalibur-io-1.1.jar 38015 commons-logging-1.0.4.jar 32112 avalon-framework-api-4.3.jar 30117 commons-cli-1.0.jar 28584 jakarta-regexp-1.4.jar 27833 excalibur-pool-impl-2.1.jar 18329 excalibur-pool-instrumented-2.1.jar 14728 excalibur-pool-api-2.1.jar 8238 excalibur-i18n-1.1.jar which now yields a war file of 4Mb, still a lot but much better than before. Anyway, I know some of this has been discussed at lenght on the mail list already, so I tried cocoon 2.2.x to see if things are improving, let's redo the little dance: svn co http://svn.apache.org/repos/asf/cocoon/trunk/ cocoon svn co http://simile.mit.edu/repository/linotype/trunk/ linotype export COCOON_HOME=../cocoon/ cd linotype ant war results in a 11516061 file, which is better than before, well, let's see if it works ant run does cocoon work? [open http://127.0.0.1:/] yes it does. does linotype work? [open http://127.0.0.1:/linotype/] nope Type 'jx' does not exist for 'map:transform' at, let's see the sitemap map:components !-- include some additional components -- map:include dir=context://WEB-INF/sitemap-additions pattern=*.xconf/ /map:components ah, ok, cool, now the components are located somewhere else, let's see the sitemap-additions map:components xmlns:map=http://apache.org/cocoon/sitemap/1.0; map:generators map:generator
Re: Continuation Time-To-Live Config Not Being Honored
Daniel Curran wrote: After experiencing some interesting behavior with Invalid Continuation Errors I have performed some tests and have found that no matter what I set the time-to-live value to in cocoon.xconf the continuations always expire after 10 minutes. Is the time-to-live attribute of the continuations-manager not being honored? Where is the default value of 10 minutes being set? Thanks for reporting. I'll check that first thing in the morning. -- Leszek Gawron [EMAIL PROTECTED] IT Manager MobileBox sp. z o.o. +48 (61) 855 06 67 http://www.mobilebox.pl mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
Re: [VOTE] snapshot release of the bricks-cms example app
Hi, On 6 Oct 2005, at 15:07, Bertrand Delacretaz wrote: I'd like to put a snapshot of the bricks-cms [1] example on our download servers, so that people can get it without requiring an SVN client. +1 Andrew. -- Andrew Savory, Managing Director, Luminas Limited Tel: +44 (0)870 741 6658 Fax: +44 (0)700 598 1135 Web: http://www.luminas.co.uk/ Orixo alliance: http://www.orixo.com/
[cforms] template.jx vs. jx-macros.xml
Why do we still have src/blocks/forms/java/org/apache/cocoon/forms/generation/template.jx in BRANCH_2_1_X? Isn't it time to get rid of it? —ml—
Re: Cocoon Fat Test
With a serious diet and an improved build system, cocoon could lose half of its weight and generate webapps that are much more friendly for smaller sites or for inclusion in places where size is an issue. But even when size is not an issue, having smaller webapps helps in making users perceive what core functionality the cocoon framework gives them and what is add-on, something that we were never very good at marketing. ...one of the things I gonna tell the people on my talk (aside): strip down the baby - otherwise it's a pain. It would be more than nice if the build system would take care of that. Maybe even http://proguard.sourceforge.net can help with it ...but in theory our build system should be smart enough to take care of this. AND ...I am way in favor of shipping with a minimal installation instead of a cocoon-can-everything-lets-show-it configuration. We passed that size. TBH I think the complexity more scares people away than it helps. Let's get them a clean and simple ...minimal sitemap to start with and then improve the documentation you need this? - add that My 2 cents -- Torsten PGP.sig Description: This is a digitally signed message part
Re: [Docs] Semi-automatic update process of the Cocoon documentation
Ross Gardler wrote: hepabolu wrote: After talks to several people I feel we need a semi-automatic update process of the Cocoon documentation to cocoon.apache.org. We have always needed this, but not possible with the current setup of the project publishing mechanism at apache.org If committers want to help, then subscribe to site-dev at a.o snip what=details of proposal/ All sounds great, in fact, most of the automated publishing side an be done by the ForrestBot. See http://forrest.zones.apache.org/ The forrestbot can publish via various methods including SVN. Yes it can. However there are issues. Apache projects store the generated documents in SVN and they are 'svn checkout' on the server to create the website. The forrestbot on our zone cannot automatically commit them to the Cocoon SVN because forrestbot has no svn account. It is not a committer. All that forrestbot can do is to generate them on to the server (i.e. a staging area) but that does not get them published onto the actual server. Hence the site-dev discussion list is addressing this and other site publishing issues. Note that our zone is still very basic, only me working there occasionally. We don't even use the zone forrestbot for the Forrest project yet (just doing some useful continuous build and error reporting so far). For Forrest's own website, the committers use a local forrestbot. Two easy commands and a publish is done: 'build; deploy'. Then we have a cronjob on the server to do 'svn update'. See forrest-trunk/etc/publishing_our_site.txt That is the method that i recommend at this stage. -David I just have to find the time to do the test build using Forrest+Daisy (should be in the next day or two). Ross
Re: Continuation Time-To-Live Config Not Being Honored
I work with Dan and here's the rest of the story:
We ran into severe enough problems using flowscript on WebLogic 8.1
(Rhino issues, really), that we had to switch to Java flow. As we've
gone down that road, we've come to the realization that all of our
continuations seem to have a time to live of ten minutes, regardless
of how we configure the continuations-manager element in
cocoon.xconf. As it turns out, JavaInterpreter uses a hard-coded,
non-configurable value of 60 for continuation time to live. Have
we missed anything with regard to being able to configure that aspect
of JavaInterpreter?
During our investigation of the time to live issue, we also came
across some concurrency issues with ContinuationsManagerImpl. This
class uses the following to store/manage continuations:
protected SortedSet expirations =
Collections.synchronizedSortedSet(new TreeSet());
There are a couple of places where that collection is iterated by doing:
Iterator i = expirations.iterator();
while (...) {
// use i
}
This really should be changed to something like this:
synchronized(expirations) {
Iterator i = expirations.iterator();
while (...) {
// use i
}
}
This advice is contained within the Javadoc for
Collections.synchronizedSortedSet.
http://java.sun.com/j2se/1.3/docs/api/java/util/Collections.html#synchronizedSortedSet(java.util.SortedSet)
Some other references worth reading:
http://java.sun.com/j2se/1.3/docs/api/java/util/Iterator.html#remove()
http://java.sun.com/j2se/1.3/docs/api/java/util/ConcurrentModificationException.html
Having said that, it seems like someone would have been screaming by
now about continuation management being horribly broken. So, is Java
flow just not being used, or used under such low levels of concurrency
that the problem hasn't surfaced yet? Or is our analysis of the code
just incorrect?
Thanks for any additional insight.
On 10/6/05, Leszek Gawron [EMAIL PROTECTED] wrote:
Daniel Curran wrote:
After experiencing some interesting behavior with Invalid Continuation
Errors I have performed some tests and have found that no matter what I
set the time-to-live value to in cocoon.xconf the continuations always
expire after 10 minutes. Is the time-to-live attribute of the
continuations-manager not being honored? Where is the default value of
10 minutes being set?
Thanks for reporting. I'll check that first thing in the morning.
--
Leszek Gawron [EMAIL PROTECTED]
IT Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
--
Kris Schneider mailto:[EMAIL PROTECTED]
[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed
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 has an issue affecting its community integration. This issue affects 55 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-chaperon : Java XML Framework - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A jcr: protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... - lenya : Content Management System Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon] -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: [cocoon-testcase] -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: [cocoon-deprecated] -INFO- Made directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-06102005/test] -INFO- Failed with reason build failed -INFO- Project Reports in: /usr/local/gump/public/workspace/cocoon/build/cocoon-06102005/test/output -WARNING- No directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-06102005/test/output] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html Work Name: build_cocoon_cocoon (Type: Build) Work ended in a state of : Failed Elapsed: 18 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-06102005.jar -Dbuild=build/cocoon-06102005 gump-core [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
[EMAIL PROTECTED]: Project cocoon (in module cocoon) failed
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 has an issue affecting its community integration. This issue affects 55 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - cocoon : Java XML Framework - cocoon-block-ajax : Ajax - Utilities and resources for Ajax applications. - cocoon-block-apples : Java XML Framework - cocoon-block-asciiart : Java XML Framework - cocoon-block-authentication-fw : Java XML Framework - cocoon-block-axis : Java XML Framework - cocoon-block-batik : Java XML Framework - cocoon-block-bsf : Java XML Framework - cocoon-block-captcha : Utilites to generate simple CAPTCHAs - cocoon-block-chaperon : Java XML Framework - cocoon-block-core-samples-additional : Additional core samples. - cocoon-block-core-samples-main : Main core samples. - cocoon-block-cron : Java XML Framework - cocoon-block-databases : Java XML Framework - cocoon-block-deli : Java XML Framework - cocoon-block-eventcache : Java XML Framework - cocoon-block-fop : Java XML Framework - cocoon-block-forms : Java XML Framework - cocoon-block-hsqldb : Java XML Framework - cocoon-block-html : Java XML Framework - cocoon-block-itext : Java XML Framework - cocoon-block-javaflow : Java XML Framework - cocoon-block-jcr : A jcr: protocol for Cocoon - cocoon-block-jfor : Java XML Framework - cocoon-block-jms : Java XML Framework - cocoon-block-jsp : Java XML Framework - cocoon-block-linkrewriter : Java XML Framework - cocoon-block-lucene : Java XML Framework - cocoon-block-midi : Java XML Framework - cocoon-block-naming : Java XML Framework - cocoon-block-ojb : Java XML Framework - cocoon-block-paranoid : Java XML Framework - cocoon-block-petstore : Java XML Framework - cocoon-block-profiler : Java XML Framework - cocoon-block-proxy : Java XML Framework - cocoon-block-python : Java XML Framework - cocoon-block-qdox : Java XML Framework - cocoon-block-querybean : Java XML Framework - cocoon-block-repository : Java XML Framework - cocoon-block-serializers : Java XML Framework - cocoon-block-session-fw : Java XML Framework - cocoon-block-slop : Java XML Framework - cocoon-block-spring-app : A demo for Spring and Cocoon - cocoon-block-stx : Java XML Framework - cocoon-block-taglib : Java XML Framework - cocoon-block-template : Java XML Framework - cocoon-block-tour : Java XML Framework - cocoon-block-validation : In-pipeline validation of documents - cocoon-block-velocity : Java XML Framework - cocoon-block-web3 : Java XML Framework - cocoon-block-xmldb : Java XML Framework - cocoon-block-xsp : Java XML Framework - forrest : Apache Forrest is an XML standards-oriented documentation fr... - forrest-test : Apache Forrest is an XML standards-oriented documentation fr... - lenya : Content Management System Full details are available at: http://vmgump.apache.org/gump/public/cocoon/cocoon/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -DEBUG- Output [cocoon.jar] identifier set to output basename: [cocoon] -DEBUG- Output [cocoon-testcase.jar] identifier set to output basename: [cocoon-testcase] -DEBUG- Output [cocoon-deprecated.jar] identifier set to output basename: [cocoon-deprecated] -INFO- Made directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-06102005/test] -INFO- Failed with reason build failed -INFO- Project Reports in: /usr/local/gump/public/workspace/cocoon/build/cocoon-06102005/test/output -WARNING- No directory [/usr/local/gump/public/workspace/cocoon/build/cocoon-06102005/test/output] -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/cocoon/cocoon/gump_work/build_cocoon_cocoon.html Work Name: build_cocoon_cocoon (Type: Build) Work ended in a state of : Failed Elapsed: 18 secs Command Line: java -Djava.awt.headless=true -Xbootclasspath/p:/usr/local/gump/public/workspace/xml-commons/java/external/build/xml-apis.jar:/usr/local/gump/public/workspace/xml-xerces2/java/build/xercesImpl.jar org.apache.tools.ant.Main -Dgump.merge=/x1/gump/public/gump/work/merge.xml -Dbuild.sysclasspath=only -Dlogkit.jar=/usr/local/gump/public/workspace/avalon-trunk/runtime/logkit/target/deliverables/jars/avalon-logkit-06102005.jar -Dbuild=build/cocoon-06102005 gump-core [Working Directory: /usr/local/gump/public/workspace/cocoon] CLASSPATH:
