Re: [Cocoon 2.2] Why use a shielding repository ?
Carsten Ziegeler wrote: Reinhard Poetz wrote: Olivier Billard wrote: Hi all, The Cocoon Maven plug-in can be configured given a useShieldingRepository configuration parameter. The effect is that all JARs / classes are moved from WEB-INF/lib and WEB-INF/classes respectively to WEB-INF/shielded/lib and WEB-INF/shielded/classes. The Cocoon documentation [1] does not explain what is the purpose of this configuration option. Can anyone tell me, please ? Thanks ! Hmm, I guess to make the change in the classloader hierarchy explicit. Yes, and to avoid that the app server picks up the classes as well for nothing. This is just an optimization parameter. Without it, the app server constructs a class path with all jars from the webapp and the shielding stuff constructs a child class loader with exactly the same class path. Carsten OK, thanks for your explanation, Carsten. (cross-posting this answer to the users list as this answers to my original question.) -- Olivier Billard
Re: Why has the PanaoidCocoonServlet disappear ?
Reinhard Poetz wrote: Olivier Billard wrote: Hi all, Still annoyed with that problem. Can anyone confirm or not ? Should I feed JIRA ? Yes, please do so. I'm sorry, but I can't help with the problem till the end of September when I'm back from my vacations. No problem Reinhard, you already help me a lot on other subjects. I must finish hot-boiling stuff for now but I'll try to write a clean (easy to reproduce with Cocoon sources) bug report for it ASAP. Good luck all for RC2 release :) -- Olivier Billard
[jira] Commented: (COCOON-806) [PATCH]: HSSF Serializer does not process gmr:PrintInformation
[ https://issues.apache.org/jira/browse/COCOON-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523215 ] Grzegorz Kossakowski commented on COCOON-806: - Antonio, this issue is very old. Shouldn't we close it as is with proper fix version set and wait for another report of missing functionality that is still not implemented? [PATCH]: HSSF Serializer does not process gmr:PrintInformation Key: COCOON-806 URL: https://issues.apache.org/jira/browse/COCOON-806 Project: Cocoon Issue Type: Bug Components: Blocks: POI Affects Versions: 2.1.8 Environment: Operating System: All Platform: All Reporter: Antonio Gallardo Assignee: Cocoon Developers Team Attachments: EP_Grid.java.diff, EP_Orientation.java.diff, EP_Paper.java.diff, Sheet.java.diff The gmr:PrintInformation element is where we configure all the info related to print configuration of the stylesheet generated. For example: landscape orientation, papelsize, margins, etc. Currenlty the HSSF Serializer is ignoring all the info the user send. Here is a example of the element: gmr:PrintInformation gmr:Margins gmr:top PrefUnit=cm Points=28.3/ gmr:bottom PrefUnit=cm Points=28.3/ gmr:left PrefUnit=cm Points=28.3/ gmr:right PrefUnit=cm Points=28.3/ gmr:header PrefUnit=cm Points=14.2/ gmr:footer PrefUnit=cm Points=14.2/ /gmr:Margins gmr:Scale percentage=100 type=percentage/ gmr:vcenter value=0/ gmr:hcenter value=0/ gmr:grid value=0/ gmr:even_if_only_styles value=0/ gmr:monochrome value=0/ gmr:draft value=0/ gmr:titles value=0/ gmr:repeat_top value=/ gmr:repeat_left value=/ gmr:orderr_then_d/gmr:order gmr:orientationlandscape/gmr:orientation gmr:Header Right= Middle=amp;[TAB] Left=/ gmr:Footer Right= Middle=Page amp;[PAGE] Left=/ gmr:paperA4/gmr:paper /gmr:PrintInformation -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON-2038) Implement true Object Oriented approach for handling super calls
[ https://issues.apache.org/jira/browse/COCOON-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523222 ] Grzegorz Kossakowski commented on COCOON-2038: -- I added few test case for ServletServiceContext so context handling is covered by tests now. I'm not sure if testContextInServletCalledFromExplicitSuperCall fails due to bug in current implementation or my misunderstanding of how contexts should be handled. Rice, is it the same bug you were talking about? Daniel, could you take a look at these tests? Implement true Object Oriented approach for handling super calls Key: COCOON-2038 URL: https://issues.apache.org/jira/browse/COCOON-2038 Project: Cocoon Issue Type: Task Components: - Servlet service framework Reporter: Grzegorz Kossakowski Assignee: Grzegorz Kossakowski Fix For: 2.2-dev (Current SVN) Attachments: BlockCallHttpServletResponse.java.patch, cocoon-servlet-service-impl.patch, DispatcherServlet.java.patch, ServletServiceContext.java.patch, StatusRetrievableResponse.java As discussed here: http://thread.gmane.org/gmane.text.xml.cocoon.devel/72317 implementation of super calls should be changed to make it more OO-like. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON-2038) Implement true Object Oriented approach for handling super calls
[ https://issues.apache.org/jira/browse/COCOON-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523226 ] Daniel Fagerstrom commented on COCOON-2038: --- There is a known bug in handling of multi level super calls (COCOON-1939) I linked this issue to that issue. Implement true Object Oriented approach for handling super calls Key: COCOON-2038 URL: https://issues.apache.org/jira/browse/COCOON-2038 Project: Cocoon Issue Type: Task Components: - Servlet service framework Reporter: Grzegorz Kossakowski Assignee: Grzegorz Kossakowski Fix For: 2.2-dev (Current SVN) Attachments: BlockCallHttpServletResponse.java.patch, cocoon-servlet-service-impl.patch, DispatcherServlet.java.patch, ServletServiceContext.java.patch, StatusRetrievableResponse.java As discussed here: http://thread.gmane.org/gmane.text.xml.cocoon.devel/72317 implementation of super calls should be changed to make it more OO-like. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (COCOON-806) [PATCH]: HSSF Serializer does not process gmr:PrintInformation
Thanks for fixing the versions. Best Regards, Antonio Gallardo. Grzegorz Kossakowski (JIRA) escribió: [ https://issues.apache.org/jira/browse/COCOON-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Kossakowski updated COCOON-806: Fix Version/s: (was: 2.1.11-dev (Current SVN)) 2.1.6 Affects Version/s: (was: 2.1.8) 2.1.6 According to this http://cocoon.apache.org/2.1/changes.html document, it was fixed in Cocoon 2.1.6, not 2.1.11-dev. [PATCH]: HSSF Serializer does not process gmr:PrintInformation Key: COCOON-806 URL: https://issues.apache.org/jira/browse/COCOON-806 Project: Cocoon Issue Type: Bug Components: Blocks: POI Affects Versions: 2.1.6 Environment: Operating System: All Platform: All Reporter: Antonio Gallardo Assignee: Cocoon Developers Team Fix For: 2.1.6, 2.2-dev (Current SVN) Attachments: EP_Grid.java.diff, EP_Orientation.java.diff, EP_Paper.java.diff, Sheet.java.diff The gmr:PrintInformation element is where we configure all the info related to print configuration of the stylesheet generated. For example: landscape orientation, papelsize, margins, etc. Currenlty the HSSF Serializer is ignoring all the info the user send. Here is a example of the element: gmr:PrintInformation gmr:Margins gmr:top PrefUnit=cm Points=28.3/ gmr:bottom PrefUnit=cm Points=28.3/ gmr:left PrefUnit=cm Points=28.3/ gmr:right PrefUnit=cm Points=28.3/ gmr:header PrefUnit=cm Points=14.2/ gmr:footer PrefUnit=cm Points=14.2/ /gmr:Margins gmr:Scale percentage=100 type=percentage/ gmr:vcenter value=0/ gmr:hcenter value=0/ gmr:grid value=0/ gmr:even_if_only_styles value=0/ gmr:monochrome value=0/ gmr:draft value=0/ gmr:titles value=0/ gmr:repeat_top value=/ gmr:repeat_left value=/ gmr:orderr_then_d/gmr:order gmr:orientationlandscape/gmr:orientation gmr:Header Right= Middle=amp;[TAB] Left=/ gmr:Footer Right= Middle=Page amp;[PAGE] Left=/ gmr:paperA4/gmr:paper /gmr:PrintInformation
True OO for servlet service
Hello, I don't have that much time to spend these days on Cocoon but I would really like to see true Object Oriented approach implemented in upcoming[1] release of cocoon-servlet-service. The main task is tracked by COCOON-2038[2] where Rice Yeh has uploaded his patch implementing true OO behaviour in servlet-service-fw. According to Rice, this patch contains a bug-fix as well (details in the comments). After reviewing Rice's patch I decided that we really need test coverage for this quite complicated functionality for both ServletServiceContext class usage clarity and casual hunting for bugs. Daniel pointed me to another bug report (COCOON-1939[3]) that involves OO aspects of servlet-service-fw. That makes point about test coverage even more strong. What I would like to ask you for in this e-mail is to add additional tests to ServletServiceContextTestCase class that exhibit problems mentioned in both issues. As soon as I have working test cases I guess that fixing problems would be quite easy. Since it was you who discovered problems it should be quite easy to write tests for them, too. Alexander and Rice, can I count on your help with this before next release in late September is cut? [1] http://article.gmane.org/gmane.text.xml.cocoon.devel/74999 [2] https://issues.apache.org/jira/browse/COCOON-2038 [3] https://issues.apache.org/jira/browse/COCOON-1939 -- Grzegorz Kossakowski http://reflectingonthevicissitudes.wordpress.com/
Re: CocoonGT hotels
On 8/27/07, Reinhard Poetz [EMAIL PROTECTED] wrote: The GT website doesn't have much to say about recommended hotels yet (http://www.cocoongt.org/Venue.html). Will there be some updates by the end of the weekend? (I will be offline afterwards and would like to have a reservation before my holidays.) Indeed. I expect to finalize that tomorrow. Thanks for your patience, -- Gianugo Rabellino Sourcesense, making sense of Open Source: http://www.sourcesense.com Orixo, the XML business alliance: http://www.orixo.com (blogging at http://www.rabellino.it/blog/)
[jira] Assigned: (COCOON-2108) xmodule:flow-attr Does not accept document objects
[ https://issues.apache.org/jira/browse/COCOON-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Kossakowski reassigned COCOON-2108: Assignee: Grzegorz Kossakowski xmodule:flow-attr Does not accept document objects -- Key: COCOON-2108 URL: https://issues.apache.org/jira/browse/COCOON-2108 Project: Cocoon Issue Type: Bug Components: * Cocoon Core Affects Versions: 2.1.11-dev (Current SVN), 2.2-dev (Current SVN) Reporter: Hugh Sparks Assignee: Grzegorz Kossakowski Priority: Minor Attachments: Cocoon-2.2-truck-JXPathHelper.java.patch, Cocoon-BRANCH-2.1.X-JXPathHelper.java.patch, xmodulePuzzle.txt Sending document objects from flowscript back to the pipeline using xmodule:flow-attr produces unexpected results. Also, the examples from the documentation do not work as described: http://cocoon.apache.org/2.1/861.daisy.html The most common error reported is: 'The object type: class java.lang.String could not be serialized to XML This issue was discussed recently on the cocoon-users mailing list. The thread was introduced by Kazo Csaba with the subject Sending DOM from flowscript to pipeline. (July 17, 2007) He has attempted to trace this behavior in the source code and believes that a possibly-inappropriate conversion to string occurs in some cases. Jason Johnston suggested moving the issue to JIRA. I've created a demonstration of this apparent bug and some related problems in this very brief example: http://www.csparks.com/xmodulePuzzle.txt I hope someone can fix or explain the correct usage of xmodule:flow-attr. Thanks to all, -Hugh Sparks, [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON-2108) xmodule:flow-attr Does not accept document objects
[ https://issues.apache.org/jira/browse/COCOON-2108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grzegorz Kossakowski updated COCOON-2108: - Other Info: [Patch available] Affects Version/s: 2.2-dev (Current SVN) xmodule:flow-attr Does not accept document objects -- Key: COCOON-2108 URL: https://issues.apache.org/jira/browse/COCOON-2108 Project: Cocoon Issue Type: Bug Components: * Cocoon Core Affects Versions: 2.1.11-dev (Current SVN), 2.2-dev (Current SVN) Reporter: Hugh Sparks Assignee: Grzegorz Kossakowski Priority: Minor Attachments: Cocoon-2.2-truck-JXPathHelper.java.patch, Cocoon-BRANCH-2.1.X-JXPathHelper.java.patch, xmodulePuzzle.txt Sending document objects from flowscript back to the pipeline using xmodule:flow-attr produces unexpected results. Also, the examples from the documentation do not work as described: http://cocoon.apache.org/2.1/861.daisy.html The most common error reported is: 'The object type: class java.lang.String could not be serialized to XML This issue was discussed recently on the cocoon-users mailing list. The thread was introduced by Kazo Csaba with the subject Sending DOM from flowscript to pipeline. (July 17, 2007) He has attempted to trace this behavior in the source code and believes that a possibly-inappropriate conversion to string occurs in some cases. Jason Johnston suggested moving the issue to JIRA. I've created a demonstration of this apparent bug and some related problems in this very brief example: http://www.csparks.com/xmodulePuzzle.txt I hope someone can fix or explain the correct usage of xmodule:flow-attr. Thanks to all, -Hugh Sparks, [EMAIL PROTECTED] -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
