[Building Sakai] Strange issue with Reports tool following upgrade to jdk 1.6

[Matthew Jones]

I believe that if you have the xalan and serializer dependencies in your
project's class path, it will use those instead of the internal transformer.
Having these enabled me to get much more predictable xsl transforms for a
number of the projects I was working on. I even wrote up some unit tests to
verify that xalan was available and correctly in the classpath, otherwise my
xslt didn't work at all.

I can't find too much info either, but I'm pretty sure that
whatever TransformerFactoryImpl is in Java 1.6 by default is different from
1.5 and certainly different than xalan 2.7.1.

Just needed

        <dependency>
            <groupId>xalan</groupId>
            <artifactId>xalan</artifactId>
            <version>2.7.1</version>
        </dependency>
        <dependency>
            <groupId>xalan</groupId>
            <artifactId>serializer</artifactId>
            <version>2.7.1</version>
        </dependency>

-Matthew

On Thu, Mar 10, 2011 at 1:49 PM, Maurer, Christopher Wayne <
chmaurer at iupui.edu> wrote:

>  As a slight follow up to this, I see that there are a couple
> tools/components (rwiki and samigo) that have xalan and xerces packaged up
> along with them.  My question is does anyone know if that actually does
> anything?  Again, my googling has indicated that it does not.  I'd love to
> be proven wrong on this point, however!
>
>  Chris
>
>   From: Chris Maurer <chmaurer at iupui.edu>
> Date: Thu, 10 Mar 2011 14:05:26 +0000
> To: sakai-dev sakai-dev <sakai-dev at collab.sakaiproject.org>
> Subject: [Building Sakai] Strange issue with Reports tool following
> upgrade to jdk 1.6
>
>   As we prepare to upgrade our app servers to java 1.6.23 and Tomcat
> 5.5.32, we're seeing issues with some of our reports.  I don't think very
> many folks are using the Reports tool, but maybe someone is out there and
> can give me some more data points!
> What we're seeing is one of them throws a stack overflow, one other shows
> some of the table headers, but not any of the table data.  If I run that
> second one through some "passthrough" xsl, all of the data that I expect to
> see is there.  We can run the same report on a different app server that has
> java 1.5 with no problems.  So, something seems to have changed in the JDKs
> xsl processing.
>  Some googling has pointed to suggestions of adding serializer.jar,
> xalan.jar, xercesImpl.jar and xml-apis.jar to the jdk's endorsed directory.
>  That way it'll pick up those versions instead of using what it packaged
> with the jdk.  I'm a bit hesitant of doing that as that'll impact all of
> Sakai and I don't know if by fixing one problem I'll be creating more.
> Other rumors have claimed that adding those things elsewhere in the
> classpath (like in the reports tool itself) will not work as it'll still use
> what's in the jdk.
> Anyone have any experience with this type of thing or know of a way that I
> can "upgrade" this for just one tool?
>
>  Chris
>  _______________________________________________ sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev TO UNSUBSCRIBE:
> send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject
> of "unsubscribe"
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110310/829bc5e9/attachment.html