Hi Jeffery, On 29.01.18 16:13, Jeffery Painter wrote: > Hi Georg, > > I have a fix, but I don't understand "why" it works. From all my > debugging, this should not be a bug, but the exception is occurring in > the JAXB unmarshalling method when the intake xml file is passed as a > file reference. > > The following snippet works in parallel deployment. I would like to > understand the difference, but since this is a class from Oracle, it is > not giving me great insight from the debugger (also hard to test in > Eclipse since it wants to debug with the application root set to just > "/testapp" and I can't figure out how to deploy in debug mode with > "/testapp##001"). I am happy to push this upstream if you think this > looks OK to you.
If you look at lines 724 and following, you'll see that a check for readability of the xml file is already there. If that is not successful, you should never reach the unmarshalling code. What does the debug log tell you? Nevertheless, my blood runs cold when looking at the code of javax.xml.bind.helpers.AbstractUnmarshallerImpl.unmarshal(File) For some strange reason the file path is converted to a string, massaged heavily, then converted to a file-URL and then to an InputSource. It is probably way better to open the FileInputStream as you did. Just leave out the test for existence and add some exception handling to make sure the file is being closed if something blows up. Bye, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
