Re: DOMImplementation method not found
Hi I will just write a note that I succeeded to create fo - pdf with fop beta 0.92 on Domino 6.5.2 June 01, 2004 with java 1.3 I copied all needed *.jar in the Domino/jvm/lib/ext directory in notes.ini I've put: JavaUserClasses=C:\Lotus\Domino\jvm\lib\ext\xml-apis-1.3.02.jar Before I've put this to my notes.ini I was getting the same exception (DOMImplementation method not found) Did this not work for you? Bye, Jelka [EMAIL PROTECTED] wrote on 27.10.2006 16:23:09: Jeremias Maerki [EMAIL PROTECTED] wrote on 27.10.2006 15:52:10: No. FOP needs the namespace feature for the DOM if it wants to support stuff like XMP metadata. So if the DOM implementation in Notes 6.5 doesn't have that feature and can't be replaced you're out of luck. You can try to disable the whole XMP stuff in the source code because you probably don't need it anyway, but FOP may simply crash in a different place later. Ok, I think I'm not going to try it this way - if fop could crash in some cases. That sounds very very ugly. Notes 6.5 is also rather old. Maybe you should consider upgrading if you also upgrade FOP. Furthermore, J2SE 1.3 at the end of the end-of-life phase. We may even drop support for J2SE 1.3 at some point because it gets in our way more and more. There are a lot of bigger companys which use notes R6 and I think they don't want to offer a lot of money to upgreate to R7. - I think the only thing I could do is to stick on Version 0.20.5. That Version is working for me very well, even in R6 (6.5.1)
Re: DOMImplementation method not found
[EMAIL PROTECTED] wrote: J.Pietschmann [EMAIL PROTECTED] wrote on 26.10.2006 21:12:31: Yes the Problem is that notes 6.5 uses an older version of org.w3c.dom, the methods used in the new version changed! In FOP 0.92 package org.apache.fop.pdf in the class PDFMetadata there are dom methods used with namespace to create a dom document. Is there any way to use it like in 0.20.5 - There I got no problems with the dom. FOP 0.92 works with a DOM when creating a PDF now. I don't see anything wrong with that and I don't see why we should change the internals of FOP just to help solve your classpath problem. I can't change the classpath so that fop uses the dom out of my java-agent. Why not? snip/ Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DOMImplementation method not found
Chris Bowditch [EMAIL PROTECTED] wrote on 27.10.2006 09:39:15: FOP 0.92 works with a DOM when creating a PDF now. I don't see anything wrong with that and I don't see why we should change the internals of FOP just to help solve your classpath problem. There is nothing wrong with the implementation now, I don't want you to understand it this way. But is there any way to modify the implementation easily, so that it works with the notes dom, not by changing the classpath?! I can't change the classpath so that fop uses the dom out of my java-agent. Why not? I can't change the classpath out of a notes agent and I can't set the path where the jvm 1.3 extracts the jars. Notes is using a mixture of the sun / ibm jvm. Additional to that I can't set System.properties out of a java agent or load property files. Its realy hard with those circumstances. It is a very special problem - I know! But it is the only way to generate PDFs of NotesDocuments in a java-agent! I'm a little bit sad if there is no way to solve it, because 0.20.5 is running great! I'm using that Version in Notes now and its working fine! But I also want to use the new features like dotted border and so on :D ! thanks at all [EMAIL PROTECTED] wrote: J.Pietschmann [EMAIL PROTECTED] wrote on 26.10.2006 21:12:31: Yes the Problem is that notes 6.5 uses an older version of org.w3c.dom, the methods used in the new version changed! In FOP 0.92 package org.apache.fop.pdf in the class PDFMetadata there are dom methods used with namespace to create a dom document. Is there any way to use it like in 0.20.5 - There I got no problems with the dom. FOP 0.92 works with a DOM when creating a PDF now. I don't see anything wrong with that and I don't see why we should change the internals of FOP just to help solve your classpath problem. I can't change the classpath so that fop uses the dom out of my java-agent. Why not? snip/ Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DOMImplementation method not found
On 27.10.2006 15:16:54 Tobias.Soloschenko wrote: Chris Bowditch [EMAIL PROTECTED] wrote on 27.10.2006 09:39:15: FOP 0.92 works with a DOM when creating a PDF now. I don't see anything wrong with that and I don't see why we should change the internals of FOP just to help solve your classpath problem. There is nothing wrong with the implementation now, I don't want you to understand it this way. But is there any way to modify the implementation easily, so that it works with the notes dom, not by changing the classpath?! No. FOP needs the namespace feature for the DOM if it wants to support stuff like XMP metadata. So if the DOM implementation in Notes 6.5 doesn't have that feature and can't be replaced you're out of luck. You can try to disable the whole XMP stuff in the source code because you probably don't need it anyway, but FOP may simply crash in a different place later. I can't change the classpath so that fop uses the dom out of my java-agent. Why not? I can't change the classpath out of a notes agent and I can't set the path where the jvm 1.3 extracts the jars. Notes is using a mixture of the sun / ibm jvm. Additional to that I can't set System.properties out of a java agent or load property files. Its realy hard with those circumstances. That sounds very very ugly. Notes 6.5 is also rather old. Maybe you should consider upgrading if you also upgrade FOP. Furthermore, J2SE 1.3 at the end of the end-of-life phase. We may even drop support for J2SE 1.3 at some point because it gets in our way more and more. Maybe you can also find a different way to start a custom JVM. I don't know much about Notes (only that I don't like using it), so I don't know if it's possible. It is a very special problem - I know! But it is the only way to generate PDFs of NotesDocuments in a java-agent! I'm a little bit sad if there is no way to solve it, because 0.20.5 is running great! I'm using that Version in Notes now and its working fine! But I also want to use the new features like dotted border and so on :D ! thanks at all [EMAIL PROTECTED] wrote: J.Pietschmann [EMAIL PROTECTED] wrote on 26.10.2006 21:12:31: Yes the Problem is that notes 6.5 uses an older version of org.w3c.dom, the methods used in the new version changed! In FOP 0.92 package org.apache.fop.pdf in the class PDFMetadata there are dom methods used with namespace to create a dom document. Is there any way to use it like in 0.20.5 - There I got no problems with the dom. FOP 0.92 works with a DOM when creating a PDF now. I don't see anything wrong with that and I don't see why we should change the internals of FOP just to help solve your classpath problem. I can't change the classpath so that fop uses the dom out of my java-agent. Why not? snip/ Chris Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DOMImplementation method not found
Jeremias Maerki [EMAIL PROTECTED] wrote on 27.10.2006 15:52:10: No. FOP needs the namespace feature for the DOM if it wants to support stuff like XMP metadata. So if the DOM implementation in Notes 6.5 doesn't have that feature and can't be replaced you're out of luck. You can try to disable the whole XMP stuff in the source code because you probably don't need it anyway, but FOP may simply crash in a different place later. Ok, I think I'm not going to try it this way - if fop could crash in some cases. That sounds very very ugly. Notes 6.5 is also rather old. Maybe you should consider upgrading if you also upgrade FOP. Furthermore, J2SE 1.3 at the end of the end-of-life phase. We may even drop support for J2SE 1.3 at some point because it gets in our way more and more. There are a lot of bigger companys which use notes R6 and I think they don't want to offer a lot of money to upgreate to R7. - I think the only thing I could do is to stick on Version 0.20.5. That Version is working for me very well, even in R6 (6.5.1) On 27.10.2006 15:16:54 Tobias.Soloschenko wrote: Chris Bowditch [EMAIL PROTECTED] wrote on 27.10.2006 09:39:15: FOP 0.92 works with a DOM when creating a PDF now. I don't see anything wrong with that and I don't see why we should change the internals of FOP just to help solve your classpath problem. There is nothing wrong with the implementation now, I don't want you to understand it this way. But is there any way to modify the implementation easily, so that it works with the notes dom, not by changing the classpath?! No. FOP needs the namespace feature for the DOM if it wants to support stuff like XMP metadata. So if the DOM implementation in Notes 6.5 doesn't have that feature and can't be replaced you're out of luck. You can try to disable the whole XMP stuff in the source code because you probably don't need it anyway, but FOP may simply crash in a different place later. I can't change the classpath so that fop uses the dom out of my java-agent. Why not? I can't change the classpath out of a notes agent and I can't set the path where the jvm 1.3 extracts the jars. Notes is using a mixture of the sun / ibm jvm. Additional to that I can't set System.properties out of a java agent or load property files. Its realy hard with those circumstances. That sounds very very ugly. Notes 6.5 is also rather old. Maybe you should consider upgrading if you also upgrade FOP. Furthermore, J2SE 1.3 at the end of the end-of-life phase. We may even drop support for J2SE 1.3 at some point because it gets in our way more and more. Maybe you can also find a different way to start a custom JVM. I don't know much about Notes (only that I don't like using it), so I don't know if it's possible. It is a very special problem - I know! But it is the only way to generate PDFs of NotesDocuments in a java-agent! I'm a little bit sad if there is no way to solve it, because 0.20.5 is running great! I'm using that Version in Notes now and its working fine! But I also want to use the new features like dotted border and so on :D ! thanks at all [EMAIL PROTECTED] wrote: J.Pietschmann [EMAIL PROTECTED] wrote on 26.10.2006 21:12:31: Yes the Problem is that notes 6.5 uses an older version of org.w3c.dom, the methods used in the new version changed! In FOP 0.92 package org.apache.fop.pdf in the class PDFMetadata there are dom methods used with namespace to create a dom document. Is there any way to use it like in 0.20.5 - There I got no problems with the dom. FOP 0.92 works with a DOM when creating a PDF now. I don't see anything wrong with that and I don't see why we should change the internals of FOP just to help solve your classpath problem. I can't change the classpath so that fop uses the dom out of my java-agent. Why not? snip/ Chris Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DOMImplementation method not found
Hello, when I try to export a pdf im receiving the error message: java.lang.NoSuchMethodError: org.w3c.dom.DOMImplementation: method createDocument(Ljava/lang/String;Ljava/lang/String;Lorg/w3c/dom/DocumentType;)Lorg/w3c/dom/Document; not found at org.apache.fop.pdf.PDFMetadata.createXMPFromUserAgent(PDFMetadata.java:197) at org.apache.fop.render.pdf.PDFRenderer.startPageSequence(PDFRenderer.java:573) at org.apache.fop.area.RenderPagesModel.startPageSequence(RenderPagesModel.java:94) at org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:140) at org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:320) at org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:147) at org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:357) at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:193) at org.apache.xml.serializer.ToXMLSAXHandler.endElement(ToXMLSAXHandler.java:261) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:1399) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2411) at org.apache.xalan.templates.ElemLiteralResult.execute(ElemLiteralResult.java:1374) at org.apache.xalan.transformer.TransformerImpl.executeChildTemplates(TransformerImpl.java:2411) at org.apache.xalan.transformer.TransformerImpl.applyTemplateToNode(TransformerImpl.java:2281) at org.apache.xalan.transformer.TransformerImpl.transformNode(TransformerImpl.java:1367) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:709) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1284) at org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1262) at de.timetoact.ntopdf.PDFTranslator.convertFileToPDF(PDFTranslator.java:84) at de.timetoact.ntopdf.PDFTranslator.convertFilesToPDF(PDFTranslator.java:110) at JavaAgent.NotesMain(JavaAgent.java:83) at lotus.domino.AgentBase.runNotes(Unknown Source) at lotus.domino.NotesThread.run(NotesThread.java:218) I looked in my packages, the class is in the xml-apis.jar and it contains that class with that method ... What could that be?! Im using java 1.3 / fop0.92 beta Thanks!
Re: DOMImplementation method not found
[EMAIL PROTECTED] wrote: ... when I try to export a pdf im receiving the error message: java.lang.NoSuchMethodError: org.w3c.dom.DOMImplementation: method createDocument(Ljava/lang/String;Ljava/lang/String;Lorg/w3c/dom/DocumentType;)Lorg/w3c/dom/Document; not found ... at lotus.domino.NotesThread.run(NotesThread.java:218) I looked in my packages, the class is in the xml-apis.jar and it contains that class with that method ... What could that be?! The most likely reason is that there is another class without this method in the CLASSPATH before xml-apis.jar. Sorry, you'll have to ask someone familar with Lotus Domino in order to resolve this. J.Pietschmann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
