Re: Problem with Maven Daisy plug-in
Grzegorz Kossakowski wrote:
Hi,
I tried to publish my screencast on RCL and stuck at the point that I
have no idea how to proceed from. Basically, I added flash file using
MultiMediaObject as document type. Then created the whole infrastructure
like page including the uploaded flash file, added to navigation files,
etc.
However the result I've got is far from being expected, you can see it
for you own here:
http://cocoon.zones.apache.org/nightly-docs/2.2/1448_1_1.html
Notice in the source code that there is a XML for included document that
has not been transformed into HTML. Does it mean that our plug-in fails
to handle MultiMediaObjects?
yes
If so how hard would it be to fix it?
You will have to extend
trunk\tools\cocoon-daisy-export-strategy\src\main\java\org\apache\cocoon\tools\maven\daisy\export\strategy\CocoonExportStrategy.java
and
trunk\tools\cocoon-daisy-export-strategy\src\main\resources\org\apache\cocoon\tools\maven\daisy\export\strategy\cocoon-doc-2-xdoc.xslt
so that they support MultiMediaObjects.
Maybe it would be easier to publish the screencast on e.g. Youtube.
However, I'm not sure if the necessary HTML snippet can be stored in a
document that is edited by the Daisy HTML editor without getting removed
by the HTMLCleaner.
--
Reinhard Pötz Managing Director, {Indoqa} GmbH
http://www.indoqa.com/en/people/reinhard.poetz/
Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member [EMAIL PROTECTED]
Re: Problem with Maven Daisy plug-in
Reinhard Pötz pisze: If so how hard would it be to fix it? You will have to extend trunk\tools\cocoon-daisy-export-strategy\src\main\java\org\apache\cocoon\tools\maven\daisy\export\strategy\CocoonExportStrategy.java and trunk\tools\cocoon-daisy-export-strategy\src\main\resources\org\apache\cocoon\tools\maven\daisy\export\strategy\cocoon-doc-2-xdoc.xslt so that they support MultiMediaObjects. I'll have a look at this. Maybe it would be easier to publish the screencast on e.g. Youtube. However, I'm not sure if the necessary HTML snippet can be stored in a document that is edited by the Daisy HTML editor without getting removed by the HTMLCleaner. Youtube is not a good hosting as it does not allow uploading flash files but only movies that are transformed into swf afterwards. There are probably other hosting sites that are better suited to our purposes but I wonder if it's a good idea to have our content stored externally. I have been willing to have a look at Daisy export plug-in for a long time now so I think it's perfect occasion now. In the long term I would like to upgrade our Daisy installation to 2.2 so I'll need to touch Daisy export plug-in anyway. -- Grzegorz Kossakowski
[jira] Created: (COCOON-2213) Change check on mime-type to enable custom encoding of the body
Change check on mime-type to enable custom encoding of the body --- Key: COCOON-2213 URL: https://issues.apache.org/jira/browse/COCOON-2213 Project: Cocoon Issue Type: Improvement Components: Blocks: Mail Affects Versions: 2.1.11 Reporter: Jasha Joachimsthal Priority: Minor Fix For: 2.1.12-dev (Current SVN) Since the patch in COCOON-1622 was applied, a check is done on the mime-type for the output format. It checks if the value is equal to either text/plain or text/html. It may be necessary to explicitly set a charset in the mime-type. This means the check for the mime type should not equals but startsWith. COCOON-1622 seems to be only applied in the 2.1 branch, not in 2.2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON-2213) Change check on mime-type to enable custom encoding of the body
[ https://issues.apache.org/jira/browse/COCOON-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jasha Joachimsthal updated COCOON-2213: --- Attachment: SendMailTransformer_mime-type.patch Patch with changed mime-type check Change check on mime-type to enable custom encoding of the body --- Key: COCOON-2213 URL: https://issues.apache.org/jira/browse/COCOON-2213 Project: Cocoon Issue Type: Improvement Components: Blocks: Mail Affects Versions: 2.1.11 Reporter: Jasha Joachimsthal Priority: Minor Fix For: 2.1.12-dev (Current SVN) Attachments: SendMailTransformer_mime-type.patch Since the patch in COCOON-1622 was applied, a check is done on the mime-type for the output format. It checks if the value is equal to either text/plain or text/html. It may be necessary to explicitly set a charset in the mime-type. This means the check for the mime type should not equals but startsWith. COCOON-1622 seems to be only applied in the 2.1 branch, not in 2.2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (COCOON-2213) Change check on mime-type to enable custom encoding of the body
[ https://issues.apache.org/jira/browse/COCOON-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605907#action_12605907 ] Jasha Joachimsthal commented on COCOON-2213: Useful in cases like email:body mime-type=text/html;charset=UTF-8 /email:body email:body mime-type=text/plain;charset=UTF-8 /email:body Change check on mime-type to enable custom encoding of the body --- Key: COCOON-2213 URL: https://issues.apache.org/jira/browse/COCOON-2213 Project: Cocoon Issue Type: Improvement Components: Blocks: Mail Affects Versions: 2.1.11 Reporter: Jasha Joachimsthal Priority: Minor Fix For: 2.1.12-dev (Current SVN) Attachments: SendMailTransformer_mime-type.patch Since the patch in COCOON-1622 was applied, a check is done on the mime-type for the output format. It checks if the value is equal to either text/plain or text/html. It may be necessary to explicitly set a charset in the mime-type. This means the check for the mime type should not equals but startsWith. COCOON-1622 seems to be only applied in the 2.1 branch, not in 2.2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Subscription: COCOON-open-with-patch
Issue Subscription Filter: COCOON-open-with-patch (106 issues) Subscriber: cocoon Key Summary COCOON-2213 Change check on mime-type to enable custom encoding of the body https://issues.apache.org/jira/browse/COCOON-2213 COCOON-2212 jx:attribute does not check name is correct before proceeding https://issues.apache.org/jira/browse/COCOON-2212 COCOON-2211 Support for jx:element https://issues.apache.org/jira/browse/COCOON-2211 COCOON-2210 The field 'type' in GenerateNode in corona-sitemap should not be final https://issues.apache.org/jira/browse/COCOON-2210 COCOON-2197 Making the cocoon-auth-block acegi-security-sample work https://issues.apache.org/jira/browse/COCOON-2197 COCOON-2177 ImageOp with requested height width both zero should be a no-op, instead it throws an exception https://issues.apache.org/jira/browse/COCOON-2177 COCOON-2173 AbstractCachingProcessingPipeline: Two requests can deadlock each other https://issues.apache.org/jira/browse/COCOON-2173 COCOON-2162 [PATCH] Fix for Paginator when accessing out of bounds Pagination page https://issues.apache.org/jira/browse/COCOON-2162 COCOON-2137 XSD Schemas for CForms Development https://issues.apache.org/jira/browse/COCOON-2137 COCOON-2114 fix sorting in TraversableGenerator https://issues.apache.org/jira/browse/COCOON-2114 COCOON-2108 xmodule:flow-attr Does not accept document objects https://issues.apache.org/jira/browse/COCOON-2108 COCOON-2104 [PATCH] Add base URI fixup support to XIncludeTransformer https://issues.apache.org/jira/browse/COCOON-2104 COCOON-2100 Retrieving mimeType returned by pipeline executed from Flow https://issues.apache.org/jira/browse/COCOON-2100 COCOON-2071 Option to turn off pooling for components (probably faster on new JVMs and simpler debugging) https://issues.apache.org/jira/browse/COCOON-2071 COCOON-2041 WebDAV Returns improper status on PUT https://issues.apache.org/jira/browse/COCOON-2041 COCOON-2040 Union widget does not work with booleanfield set as case widget https://issues.apache.org/jira/browse/COCOON-2040 COCOON-2037 New DynamicGroup widget https://issues.apache.org/jira/browse/COCOON-2037 COCOON-2035 NPE in the sorter of the EnhancedRepeater https://issues.apache.org/jira/browse/COCOON-2035 COCOON-2032 [PATCH] Sort order in paginated repeater https://issues.apache.org/jira/browse/COCOON-2032 COCOON-2030 submit-on-change doesn't work for a multivaluefield with list-type=checkbox https://issues.apache.org/jira/browse/COCOON-2030 COCOON-2018 Use thread context class loader to load custom binding classes https://issues.apache.org/jira/browse/COCOON-2018 COCOON-2017 More output beautification options for serializers https://issues.apache.org/jira/browse/COCOON-2017 COCOON-2015 Doctype added twice because root element (html) is inlined https://issues.apache.org/jira/browse/COCOON-2015 COCOON-2002 HTML transformer only works with latin-1 characters https://issues.apache.org/jira/browse/COCOON-2002 COCOON-1974 Donating ContextAttributeInputModule https://issues.apache.org/jira/browse/COCOON-1974 COCOON-1973 CaptchaValidator: allow case-insensitive matching https://issues.apache.org/jira/browse/COCOON-1973 COCOON-1964 Redirects inside a block called via the servlet protocol fail https://issues.apache.org/jira/browse/COCOON-1964 COCOON-1963 Add a redirect action to the browser update handler https://issues.apache.org/jira/browse/COCOON-1963 COCOON-1960 Pipeline errors for generator/reader already set should provide more information https://issues.apache.org/jira/browse/COCOON-1960 COCOON-1949 [PATCH] load flowscript from file into specified Rhino context object https://issues.apache.org/jira/browse/COCOON-1949 COCOON-1946 [PATCH] - Javaflow Sample errors trying to enhance Javaflow classes and showing cform templates https://issues.apache.org/jira/browse/COCOON-1946 COCOON-1943 [Patch] Parameters in blocks-protocol URIs get decoded too early https://issues.apache.org/jira/browse/COCOON-1943 COCOON-1932 [PATCH] correct styling of disabled suggestion lists https://issues.apache.org/jira/browse/COCOON-1932 COCOON-1929 [PATCH] Reloading classloader in Cocoon 2.2 https://issues.apache.org/jira/browse/COCOON-1929 COCOON-1917 Request Encoding problem: multipart/form vs. url encoded https://issues.apache.org/jira/browse/COCOON-1917 COCOON-1915 Nullable value with additional String or XMLizable in JavaSelectionList https://issues.apache.org/jira/browse/COCOON-1915 COCOON-1914 Text as XMLizable in EmptySelectionList https://issues.apache.org/jira/browse/COCOON-1914
Re: Moving XMLUtils class from cocoon-pipeline-impl to cocoon-xml-util
Vadim Gritsenko pisze: On Jun 17, 2008, at 6:49 AM, Grzegorz Kossakowski wrote: I've noticed that we have very handy XMLUtils[1] class in cocoon-pipeline-impl that is useful outside the cocoon-pipeline-impl and has no dependencies on the rest of the Cocoon. Therefore I would like to move it to cocoon-xml-util module which feels like natural location for such kind of class. Anyone minds? Not at all! Go ahead. Vadim, thanks for the green light but I've got stuck at the early beginning. The reason is that I originally missed one little dependency on DOMStreamer class from cocoon-pipeline-impl. This class itself does useful thing and probably should be moved to cocoon-xml-util but it is closely tied to the rest of cocoon-pipeline-impl code. I don't now how to proceed now. It feels wrong that the XMLUtils, the class useful in many situations, belongs to pipeline-impl but I fail to see how to move it out. Not sure if I'll just give up. Any suggestions? -- Grzegorz Kossakowski
[jira] Created: (COCOON-2214) Update C22 block building process through use of Maven archetype:generate command
Update C22 block building process through use of Maven archetype:generate command - Key: COCOON-2214 URL: https://issues.apache.org/jira/browse/COCOON-2214 Project: Cocoon Issue Type: Improvement Components: - Build System: Maven, - Documentation Affects Versions: 2.2, 2.2-dev (Current SVN) Reporter: David Legg Priority: Minor Version 2.0.9 (and maybe earlier) of Maven has deprecated the use of the archetype:create goal in favour of archetype:generate. As of this report the Cocoon Tutorial uses archetype:create in its instructions and this causes a warning to be issued when attempting to build blocks. After discussion on the list it was felt the solution was to start using archetype:generate but this changes the behaviour of Maven such that it interactively asks for values such as the artifactId and groupId etc. Unfortunately, the first question it asks is which archetype you wish to build and by default this list is huge and will continue to grow as more projects use it. Attached to this note is a file which if placed in a suitable location on the Cocoon web site could be used to reduce the archetype list to just those required for Cocoon (Currently 3 items). The Cocoon tutorial would need to be updated to replace the archetype:create command to something like the following: - mvn archetype:generate -DarchetypeCatalog=http://[path to catalog]/archetype-catalog.xml This would generate output similar to the following: - [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. ... [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - cocoon-22-archetype-block-plain (Creates an empty Cocoon block) 2: local - cocoon-22-archetype-block (Creates a minimal Cocoon block) 3: local - cocoon-22-archetype-webapp (Creates a web application Cocoon block) Choose a number: (1/2/3): Choose archetype: This should be much more comprehensible to new users. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COCOON-2214) Update C22 block building process through use of Maven archetype:generate command
[ https://issues.apache.org/jira/browse/COCOON-2214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Legg updated COCOON-2214: --- Attachment: archetype-catalog.xml A Maven archetype catalog file ready for uploading to the Cocoon web site. Update C22 block building process through use of Maven archetype:generate command - Key: COCOON-2214 URL: https://issues.apache.org/jira/browse/COCOON-2214 Project: Cocoon Issue Type: Improvement Components: - Build System: Maven, - Documentation Affects Versions: 2.2, 2.2-dev (Current SVN) Reporter: David Legg Priority: Minor Attachments: archetype-catalog.xml Version 2.0.9 (and maybe earlier) of Maven has deprecated the use of the archetype:create goal in favour of archetype:generate. As of this report the Cocoon Tutorial uses archetype:create in its instructions and this causes a warning to be issued when attempting to build blocks. After discussion on the list it was felt the solution was to start using archetype:generate but this changes the behaviour of Maven such that it interactively asks for values such as the artifactId and groupId etc. Unfortunately, the first question it asks is which archetype you wish to build and by default this list is huge and will continue to grow as more projects use it. Attached to this note is a file which if placed in a suitable location on the Cocoon web site could be used to reduce the archetype list to just those required for Cocoon (Currently 3 items). The Cocoon tutorial would need to be updated to replace the archetype:create command to something like the following: - mvn archetype:generate -DarchetypeCatalog=http://[path to catalog]/archetype-catalog.xml This would generate output similar to the following: - [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. ... [INFO] [archetype:generate] [INFO] Generating project in Interactive mode [INFO] No archetype defined. Using maven-archetype-quickstart (org.apache.maven.archetypes:maven-archetype-quickstart:1.0) Choose archetype: 1: local - cocoon-22-archetype-block-plain (Creates an empty Cocoon block) 2: local - cocoon-22-archetype-block (Creates a minimal Cocoon block) 3: local - cocoon-22-archetype-webapp (Creates a web application Cocoon block) Choose a number: (1/2/3): Choose archetype: This should be much more comprehensible to new users. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Editing rights
Hi, I'd like to be given document editing rights on the Cocoon CMS please. I've created the account 'djl' for this purpose. I've followed Cocoon for several years now. I've noticed the desperate need for documentation with the advent of version 2.2 and I'd like to help out. Regards, David Legg
