[jira] Commented: (FOR-1215) The optional use of Cocoon Validation Transformers fails with Jing-20091111

2011-01-07 Thread David Crossley (JIRA) 

[ 
https://issues.apache.org/jira/browse/FOR-1215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12978674#action_12978674
 ] 

David Crossley commented on FOR-1215:
-

Yeah that sounds the correct process to upgrade one block. For those following, 
the full upgrade process is described at $FORREST_HOME/etc/cocoon_upgrade/

No configuration needed, and no block dependencies (as shown in those Cocoon 
notes).



 The optional use of Cocoon Validation Transformers fails with Jing-2009
 ---

 Key: FOR-1215
 URL: https://issues.apache.org/jira/browse/FOR-1215
 Project: Forrest
  Issue Type: Bug
  Components: XML grammars  validation
Affects Versions: 0.9-dev
Reporter: David Crossley
 Fix For: 0.10


 The optional use of Cocoon Validation Transformers is explained here:
 http://forrest.apache.org/howto-dev.html#debug-validation
 http://forrest.apache.org/howto-dev.html#validate-intermediate
 FOR-1172 enable validation of the internal xml
 This works okay with Jing-20081028
 However with the current release of Jing-2009 it fails with this message:
 ...
 * [178/93]  [93/135]  0.886s 10.0Kb  linkmap.validation-start.xml
 * [179/92]  [0/0] 0.089s 0b  
 docs_0_90/howto/howto-buildPlugin.validation.xml
 Exception in thread main java.lang.NoSuchFieldError: ENTITY_RESOLVER
   at 
 org.apache.cocoon.components.validation.jing.JingSchemaParser.parseSchema(JingSchemaParser.java:79)
   at 
 org.apache.cocoon.components.validation.impl.AbstractValidator.getSchema(AbstractValidator.java:410)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Upgrading Batik

2011-01-07 Thread Brian M Dube 
The Jing discussion reminded me of upgrading Batik. We currently
package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did
Cocoon or Forrest build a custom jar out of the modules that Batik
ships?

-Brian

Re: Upgrading Batik

2011-01-07 Thread David Crossley 
Brian M Dube wrote:
 The Jing discussion reminded me of upgrading Batik. We currently
 package batik-all-1.6.jar. Batik 1.7 does not ship an -all jar. Did
 Cocoon or Forrest build a custom jar out of the modules that Batik
 ships?

Forrest would have obtained that as-is from Cocoon
at the time of an etc/cocoon_upgrade process.

The svn log over in the Cocoon branch shows that it was
Antonio (2005-05-23) who commited it there. This gave me some
search clues and so found this around our 0.6 release:

http://s.apache.org/qx8
Subject: Re: REsizing batik to a minimum for us.
Date: May 27, 2004

-David