Hello,
I am migrating from OTM 5.0 on Windows to Linux. Everything is working fine with one exception we have some custom Stylesheets that OTM seems unable to reference correctly. When these were originally created under the Windows environment the path referencing them used the Windows standard “\” convention in the file name. Thinking that this was the source of the error I changed these references to UNIX standard pathing (using “/”) however I am still getting the error. The ownership and permissions on these files is identical to the standard stylesheets and does not appear to be the issue. I suspect that the error “java.io.FileNotFoundException” is a non-sequitur and is not indicating the true problem. I say this because if the stylesheet is copied to both the glog/integration/client/xsl directory and the apache/htdocs/xsl/workflow directory the error shows up twice (once for each path) but if the stylesheet is actually removed from one of the directories only the directory that actually contains the stylesheet shows up as in error. So the file is not found only in the directory in which it actually exists!
The errors from the console.log look like this
INFO | jvm 1 | 2007/08/21 18:52:04 | java.io.FileNotFoundException: /u01/app/otm50prod/apache/htdocs/xsl/u01/app/otm50prod/glog/integration/client/xsl/public_plannedshipment.xsl: No such file or directory
INFO | jvm 1 | 2007/08/21 15:03:55 | java.io.FileNotFoundException: /u01/app/otm50prod/apache/htdocs/xsl/workflow/OutboundASN3.xsl: No such file or directory
Any suggestions would be appreciated.
Regards,
Alan
I am migrating from OTM 5.0 on Windows to Linux. Everything is working fine with one exception we have some custom Stylesheets that OTM seems unable to reference correctly. When these were originally created under the Windows environment the path referencing them used the Windows standard “\” convention in the file name. Thinking that this was the source of the error I changed these references to UNIX standard pathing (using “/”) however I am still getting the error. The ownership and permissions on these files is identical to the standard stylesheets and does not appear to be the issue. I suspect that the error “java.io.FileNotFoundException” is a non-sequitur and is not indicating the true problem. I say this because if the stylesheet is copied to both the glog/integration/client/xsl directory and the apache/htdocs/xsl/workflow directory the error shows up twice (once for each path) but if the stylesheet is actually removed from one of the directories only the directory that actually contains the stylesheet shows up as in error. So the file is not found only in the directory in which it actually exists!
The errors from the console.log look like this
INFO | jvm 1 | 2007/08/21 18:52:04 | java.io.FileNotFoundException: /u01/app/otm50prod/apache/htdocs/xsl/u01/app/otm50prod/glog/integration/client/xsl/public_plannedshipment.xsl: No such file or directory
INFO | jvm 1 | 2007/08/21 15:03:55 | java.io.FileNotFoundException: /u01/app/otm50prod/apache/htdocs/xsl/workflow/OutboundASN3.xsl: No such file or directory
Any suggestions would be appreciated.
Regards,
Alan
Comment