Santiago Gala wrote:
>
> Santiago Gala wrote:
>
> > [EMAIL PROTECTED] wrote:
> >
> >> David Sean Taylor wrote:
> >>
> >>> Santiago -- Im failing to get your recent xalan mods to work.
> >>> (cvs commit: jakarta-jetspeed/lib xalan-2.0.1.jar xalan.jar)
> >>>
> >>>
> >>
> >> I tried with a Tomcat 3.2 on Windows and set the property in
> >> TOMCAT_OPTS, this solves a few problems but not all since
> >> I now have "Unable to display for this browsers" for all
> >> SimpleTransform based portlets.
> >>
> >
> >
> > Can you be more specific? I have never seen this error before.
> >
This is fixed in CVS now. I also had to update the JetspeedContent XSL stylesheet
because I got broken images with Xalan 2.
> > WRT the -D, it is specified in JAXP. But I don't know anything about the
> > other error your mention. Please, give me the stack trace complete. It
> > could be an interaction between un-commited mods in my machine or yours.
> >
>
> I have seen your mail. But still that leaves us with the problem of the
> definition of the property.
>
> For instance, Cocoon2 code contains the following function:
>
> /** Sets required system properties . */
> protected void setSystemProperties() {
> java.util.Properties props = new java.util.Properties();
> // FIXME We shouldn't have to specify the SAXParser...
> // This is needed by Xalan2, it is used by
>org.xml.sax.helpers.XMLReaderFactory
> // to locate the SAX2 driver.
> props.put("org.xml.sax.driver", "org.apache.xerces.parsers.SAXParser");
> java.util.Properties systemProps = System.getProperties();
> Enumeration propEnum = props.propertyNames();
> while (propEnum.hasMoreElements()) {
> String prop = (String)propEnum.nextElement();
> if (!systemProps.containsKey(prop))
> systemProps.put(prop, props.getProperty(prop));
> }
> System.setProperties(systemProps);
> }
>
> and it is called in the Cocoon constructor. Maybe we should do something
> similar in a place where we centralize all XML parsing in Jetspeed.
>
Sure, why not move the SimpleTransform static class to a service (and possibly
merge it with the xslt one found in Turbine, although we would have to extend its
interface because the XSLTService in Turbine does not accept parameters).
That way we can set this property in the init of the service and use a configuration
key to actually chose which parser we want to use...
I let you handle this, ok ?
--
Rapha�l Luta - [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
