cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31668] New: - Cocoon Forms does not use default parser from cocoon.xconf
Date Tue, 12 Oct 2004 14:10:51 GMT
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=31668>.
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=31668

Cocoon Forms does not use default parser from cocoon.xconf

           Summary: Cocoon Forms does not use default parser from
                    cocoon.xconf
           Product: Cocoon 2
           Version: 2.1.5
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: CocoonForms
        AssignedTo: dev@cocoon.apache.org
        ReportedBy: jbq@anyware-tech.com


The Cocoon Forms block does not use the default XML parser defined in
cocoon.xconf.  As a result, the XML catalog in WEB-INF/entities/catalog is not
looked up when resolving public identifiers.

Example:
org.apache.cocoon.forms.binding.JXPathBindingManager.createBinding()

Form binding is unable to resolve public identifiers like:

<!DOCTYPE context [
  <!ENTITY % common-entities PUBLIC "-//Common Entities V1.0//EN"
		"entities.ent">
	%common-entities;
]>

Mime
View raw message