Re: [ginp-users] Setup Wizard fails with war v0.23 - xalan missing

[Brian B. <Br...@Pi...>]

On Sat, 18 Mar 2006 11:03:44 -0800, Justin wrote:
>Ginp is kind of touchy about the versions of the xml libs that are being used.
>This mostly has to do with features of the jdk1.4 preferences api which is used
>to bootstrap ginp.  Glad you got it to work.  You probably had an old
>version of xerces
>or xalan in your classpath that one of your other webapps was using.

Hi, Justin... thanks for taking the time to reply.. there haven't been any postings since last year and I wondered how long I might have to wait. Overnight in the UK counts as excellent service.

I should have said that I'm running linux with the sun jdk 1.5 and tomcat 5.0.28. I don't have a system classpath set at all... I always set a specific classpath when starting a java application. Tomcat sets its own 
(several, if you've not yet fought that particular fight) and there is a xerces.jar in common/lib, but I don't know what version. There definitely wasn't a copy of xalan.jar available until I manually copied it into 
ginp/WEB-INF/lib.

I was a bit lazy in trusting the diagnostic screen on my browser. The NullPointerException was in TransfarmerFactoryImpl, which I didn't recognise, so I started googling and found the mailing list entry.

I've subsequently gone back to catalina.log to look at the full stack trace, which shows that provider org.apache.xalan.processor.TransfarmerFactoryImpl could not be found. That would have been clear enough for 
me - if only I had looked. Sorry.

Given that you ship so many other jars with ginp, and given that you've found ginp "touchy" about xml versions, why don't you bundle the version of xalan that you prefer in WEB-INF/lib? Yes, it's quite bloated with 
jars and you have to draw the line somewhere, but I'm curious why not?

Of course, if you decide to leave the packaging alone, there is now a proper dialogue on the mailing list for others to find and use to resolve this problem quickly.


Regards,

Brian