Gavin_King/Cirrus%CI...@ci... wrote:
>>What I was really curious about was what had changed that I now need
>>this, as I'm not doing XSL specific in any of my code. I imagine I've
>>had the wrong JAR files there from day one, but that nothing in my code
>>caused them to be needed and I've only just found out.
>>
>
> The session factory parses the generic XML -> custom XML stylesheet when
> its instantiated. This is suboptimal, I suppose, since most people aren't
> using the XML generation (its not even documented yet). You could parse it
> lazily, but then you would need a synchronized block, whic i've been
> avoiding as much as possible. It would be okay in this case.
>
I think that we need to document the dependancies a little better, in
particular what version's are required. Even better, what "spec" they
need to implement.
I'm trying to deploy in a Turbine / Velocity environment on a servlet
2.2 compliant app server. I've all kinds of dependencies, and some of
them conflict. Without knowing precisely what's where it's a *lot* of
just messing around until I find some combo what works, but not really
sure exactly why without trudgning around in source code.
To deploy this in any kind of production environment you'd expect to
know exactly what you're doing, and we don't really specify things to
that level at present.
PaulS :(
|
