Alex schrieb: >> java.lang.RuntimeException: Exception constructing service >> 'TemplateParser': >> Error invoking constructor >> org.apache.tapestry5.internal.services.TemplateParserImpl(Map, >> boolean) (at TemplateParserImpl.java:50) via >> org.apache.tapestry5.internal.services.InternalModule.bind(ServiceBinder) >> (at InternalModule.java:65) (for service 'TemplateParser'): >> com.caucho.xml.stream.XMLInputFactoryImpl >> cannot be cast to org.codehaus.stax2.XMLInputFactory2
> It seems that tapestry expects a particular parser implementation. You > can force one by supplying a system property If they really want a particular implementation, they should not be using the JAXP mechanism at all, but directly instantiate their implementation class. > <web-app> > <system-property > javax.xml.stream.XMLInputFactory="org.codehaus.stax2.XMLInputFactory2"/> > </web-app> But wouldn't that set the property for the entire JVM instead of for one particular webapp/context? > The <system-property> tag could also go under <resin>, <cluster> or > <host> tags. And likewise this? Which may create problems for other apps? Nabble - Tomcat - User - Problem with system property http://www.nabble.com/Problem-with-system-property-td24389677.html -- Michael Ludwig _______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
