Dear Mr. Shafie We stumbled across a different URI-related issue using the JNLP deployed version of XXE-7.3, we wondered if it adds a new light on the URI path problem... Unfortunately, this one is a complete blocker :(.
We fail to convert DocBook4 books onto PDF with the JNLP deployed version of XXE-7.3; we got the following error message from FOP: Converting XSL-FO file "__doc.fo" to "__doc.pdf" using FOP FOP XSL-FO processor error: java.lang.IllegalArgumentException: URI is not absolute The DocBook4 document itself has not changed and can be converted successfully into PDF using the JNLP deployed version of XXE-6.3, which is the version that we currently use in production. The JNLP deployment uses the deployment tool provided with XXE and is therefore the same as for the previous version of XXE. Is there any chance that the URI file path management has changed since XXE 6.3 ? Many thanks for your feedback Best regards. Philippe Nobili Subsurface Imaging - Product Engineering Tel: +33 16447 4090 | Mobile: +33 63756 6441 CGG, 27 avenue Carnot Massy, 91341 - France http://www.cgg.com Please consider the environment before printing. -----Original Message----- From: xmleditor-support-boun...@xmlmind.com [mailto:xmleditor-support-boun...@xmlmind.com] On Behalf Of Hussein Shafie Sent: Thursday, March 09, 2017 11:00 AM To: 'xmleditor-support@xmlmind.com' Subject: Re: [XXE] Java FX exception while embedding video objects (DocBook 5.1) Philippe N. wrote: > > Back on the player creation issue, we digged into the issue; we are > pretty much convinced that it is related to Java FX and not XXE. Below > some details about our findings, hoping that it will be useful. > > > The cause of the issue seems more complicated to understand than we > first thought... Yes. That's right. I tried to reproduce the problem on Linux, Windows 7 and Windows 10 using the steps you explained us in your previous email and didn't manage to do it. It worked really well for me on all the above platforms (all using Oracle Java 1.8.0_121 64-Bit). > > > > As you mentioned, the Ogg format is not supported by Java FX, but we get > a clear and non-ambiguous exception about unrecognized formats: > > javafx.scene.media.MediaException: Unrecognized file signature Yes, this is not really a problem. Even Web browsers do this. Suffice to also specify alternate video files having a different format. > > > > The exception we got with supported video formats (like > $XXE/doc/dita/images/video.mp4) is a different one, it runs: "Could not > create player". > > What confused us is that when this happens, *all players embedded in > XXE* suddenly appear in error, including those that were previously OK... > > > > The question is why this "Could not create player" exception happens ? > It is not related to video formats as far as we could see. > > > > It seems that depending on the video file location, the Java FX player > fails to be created correctly with this exception. Once it fails, it has > an incidence on all players embedded in XXE; we get another FX > exception in this case: "[] ERROR_MEDIA_CREATION: ERROR MEDIA CREATION". > > > > Something that is reproducible in our location: > > > > *On Windows:* if we use the *.mp4 files you sent us, or those from > http://xmlmind.com, or from $XXE/doc/dita/images, it works fine: the > Java FX player is correctly created. If instead of using these > locations, we copy the exact same files on our Linux file servers and > access them through a Samba server, it ceases to work and we get the > exception that we first reported. > > > > *On Linux:* the problem shows up systematically and we can't never get > a working Java FX player; but oddly enough, if we try to use the > *create_doc.mp4* file located on your Website, we get an empty grey box > instead of the instantiated player, and no exception... > > If we download this file locally and use it instead of the remote > version, we get the exception back... > > > > Our understanding is that there is a subtle issue with Java Fx player, > linked to the storage devices characteristics. It shows up on both > Windows and Linux, but only when using our Linux driven data storage > systems... For Linux, I have no clue. Our embedded media player works really well on my openSUSE Linux box, albeit with media files stored on a local ext4 file system and no samba server running on my Linux box. For Windows and its Samba-based shared folder, I may have an idea. How do you specify the URL of the media file stored on the Samba server? Is it something like: file:/Z:/videos/video.mp4 or something like: file:///Z:/videos/video.mp4 or something like: file://my_shared_folder/videos/video.mp4 To be sure, please test each of the above string forms by typing them in the media dialog box. I mean, please do not rely on XXE's file chooser. XXE supports all the above string forms, but may be NOT JavaFX (which must be passed URLs in string form). > I attached the information from XXE, but with little hope > that it can help you... Attached file indeed looks fine. -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support This email and any accompanying attachments are confidential. If you received this email by mistake, please delete it from your system. Any review, disclosure, copying, distribution, or use of the email by others is strictly prohibited. -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
