Re: [Exist-open] 1.4.1dev now builds OK, but dies with an Internal Server Error (in Cocoon 2.1.11)

[ron.vandenbranden <ron...@ka...>]

Hi,


Martin Holmes wrote:
> 
> However, Ron Van Den Branden has shared a working build script he 
> created based on my original, which he has updated, and which seems to 
> be working. It looks like it's easier to build against Cocoon 2.1.12 (a 
> dev version) rather than 2.1.11, which is the stable release.
> 

Here I have to contradict you, Martin: I've tested my build scripts today
with Cocoon-2.1.11 and eXist-1.4.x and got it working. If I recall
correctly, Cocoon-2.1.12 made the switch to FOP-1.0 easier but it has no
influence on eXist integration.

I agree, however, that the current Cocoon build scripts in eXist-1.4.x still
fail. I didn't have the time to flesh it out, but on first sight, there are
errors w.r.t. incorrect version numbers in references to jar files etc. A
while ago, Wolfgang applied the patches I supplied at
http://sourceforge.net/tracker/?func=detail&aid=3025442&group_id=17691&atid=317691
in rev.12600 of eXist-trunk. Yet, the old version numbers in the eXist-1.4.x
build scripts suggest that this patch has not been ported back from trunk to
1.4.x. 

For the time being, I suppose it will suffice to patch the files in
%EXIST_HOME%\build\scripts\cocoon to make it work in eXist-1.4.x.

Hope this helps,

Ron
-- 
View this message in context: http://exist.2174344.n4.nabble.com/1-4-1dev-now-builds-OK-but-dies-with-an-Internal-Server-Error-in-Cocoon-2-1-11-tp3049356p3051064.html
Sent from the exist-open mailing list archive at Nabble.com.