Hi Matthias, As I remember, if you want to use Saxon in Cocoon, you have to modify the jar-file you can download from the Saxon guys. In my FAQ document (Whenever I run into a problem and find a solution, I document it for myself) I noted, that you have to remove the classes contained in the jars META-INF directory, since they overwrite some vital classes. After removing them Saxon runs like a charm.
By adding the "z" to your jar, I guess the replacement of the utility classes is prevented. Hope this explains/helps a little, Chris -----Ursprüngliche Nachricht----- Von: Matthias Müller [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 22. Oktober 2008 14:24 An: [email protected] Betreff: AW: [C2.2] Problem after Hosting Block To finish this thread, after renaming the saxon.jar to z-saxon.jar the FormManager finally accepted the form definition files. thanks again for your help, matthias ----- Ursprüngliche Mail ---- Von: Matthias Müller <[EMAIL PROTECTED]> An: [email protected] Gesendet: Mittwoch, den 22. Oktober 2008, 08:37:13 Uhr Betreff: AW: AW: AW: [C2.2] Problem after Hosting Block after searching for the error (for days!!!) i finally localized the source of my problem. it's a dependency to Saxon xslt processor (net.sf.saxon). it looks like the FormManager has problems to parse form definition files when saxon is bound to the project. is this a known problem? ----- Ursprüngliche Mail ---- Von: Matthias Müller <[EMAIL PROTECTED]> An: [email protected] Gesendet: Freitag, den 17. Oktober 2008, 11:22:03 Uhr Betreff: AW: AW: [C2.2] Problem after Hosting Block Hi again, i tried to host my block with another cocoon block (not webapp !) and there it works. so it's something special with the cocoon webapp archetype. i really don't know what to do anymore ----- Ursprüngliche Mail ---- Von: Matthias Müller <[EMAIL PROTECTED]> An: [email protected] Gesendet: Mittwoch, den 15. Oktober 2008, 12:25:13 Uhr Betreff: AW: [C2.2] Problem after Hosting Block no special protocol (so i think it's file). maybe it helps when you know that i use a flow.js ------ cocoon.load("servlet:forms:/resource/internal/flow/javascript/Form.js"); function myFunc() { var form = new Form(cocoon.parameters["definitionURI"]); form.showForm("myFunc-display-pipeline"); } ------- and the definitionURI parameter is is the filepath relative to the sitemap.xmap the error occurs in the Form function of the imported Form.js regards, matthias ----- Ursprüngliche Mail ---- Von: Reinhard Pötz <[EMAIL PROTECTED]> An: [email protected] Gesendet: Mittwoch, den 15. Oktober 2008, 11:48:47 Uhr Betreff: Re: [C2.2] Problem after Hosting Block Matthias Müller wrote: > i also used jetty for this, with the same effect. so, i don't think > that's a tomcat problem. the question is, why do i have problems only > when loading my block with a hosting webapp. What protocol do you use to get access to your form definitions? servlet, cocoon or (the implicit) file protocol? > i need a way to make a > war that includes my block and as far as i understood the only way to > do this is to create a new cocoon webapp project (with the block as > dependency) and deploy this as war. is this right? yes -- Reinhard Pötz Managing Director, {Indoqa} GmbH http://www.indoqa.com/en/people/reinhard.poetz/ Member of the Apache Software Foundation Apache Cocoon Committer, PMC member [EMAIL PROTECTED] ________________________________________________________________________ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
