MMBase

xsl transformation for objectypes processing dies quietly

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.7.0
  • Fix Version/s: 1.8.4
  • Component/s: Misc
  • Description:
    Hide
    original bugid: #6274
    When you checkout mmbase using eclipse 2.1 without setting xsl type to ascii in window/preferences/team/file_content the produced war file will not function properly. The following exception is ignored and will NOT show up in the logfiles:
    org.apache.xml.utils.WrappedRuntimeException: The output format must have a '{http://xml.apache.org/xalan}content-handler' property!
       at org.apache.xalan.serialize.SerializerFactory.getSerializer(SerializerFactory.java:142)
       at org.apache.xalan.transformer.TransformerIdentityImpl.createResultContentHandler (TransformerIdentityImpl.java:232)
       at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:296)
       at org.mmbase.module.corebuilders.ObjectTypes.storeBuilderFile(ObjectTypes.java:424)
       at org.mmbase.module.corebuilders.ObjectTypes.insert(ObjectTypes.java:150)
       at org.mmbase.module.tools.MMAdmin.installBuilders(MMAdmin.java:1177)
       at org.mmbase.module.tools.MMAdmin.installApplication(MMAdmin.java:682)
       at org.mmbase.module.tools.MMAdmin.installApplication(MMAdmin.java:658)
       at org.mmbase.module.tools.MMAdmin.process(MMAdmin.java:217)
       at org.mmbase.bridge.implementation.ModuleHandler.process(ModuleHandler.java:133)

    I encountered this problem using tomcat-4.1.
    Show
    original bugid: #6274 When you checkout mmbase using eclipse 2.1 without setting xsl type to ascii in window/preferences/team/file_content the produced war file will not function properly. The following exception is ignored and will NOT show up in the logfiles: org.apache.xml.utils.WrappedRuntimeException: The output format must have a '{http://xml.apache.org/xalan}content-handler' property!    at org.apache.xalan.serialize.SerializerFactory.getSerializer(SerializerFactory.java:142)    at org.apache.xalan.transformer.TransformerIdentityImpl.createResultContentHandler (TransformerIdentityImpl.java:232)    at org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:296)    at org.mmbase.module.corebuilders.ObjectTypes.storeBuilderFile(ObjectTypes.java:424)    at org.mmbase.module.corebuilders.ObjectTypes.insert(ObjectTypes.java:150)    at org.mmbase.module.tools.MMAdmin.installBuilders(MMAdmin.java:1177)    at org.mmbase.module.tools.MMAdmin.installApplication(MMAdmin.java:682)    at org.mmbase.module.tools.MMAdmin.installApplication(MMAdmin.java:658)    at org.mmbase.module.tools.MMAdmin.process(MMAdmin.java:217)    at org.mmbase.bridge.implementation.ModuleHandler.process(ModuleHandler.java:133) I encountered this problem using tomcat-4.1.

Activity

There are no subversion log entries for this issue yet.

People

Dates

  • Created:
    2004-01-15 17:22
    Updated:
    2007-02-25 16:52
    Resolved:
    2007-02-25 16:52