Talk:POS - Cashregister log report
Dear Janar. Thanks for the code. I have tried it but get the following error:
snip-----------------
com.openbravo.pos.forms.BeanFactoryException: com.openbravo.pos.scripting.ScriptException: Sourced file: inline evaluation of: ``report = new com.openbravo.pos.reports.PanelReportBean(); report.setTitleKey . . . Token Parsing Error: Lexical error at line 1, column 1. Encountered: "\ufeff" (65279), after : ""
My version of OpenbravoPOS is 2.30beta on Windows XP Pro (SP3) with Postgresql 8.3
Regards Rudolf
Rudolf,
Well I solved the following problem:
com.openbravo.pos.forms.BeanFactoryException: com.openbravo.pos.scripting.ScriptException: Sourced file: inline evaluation of: ``report = new com.openbravo.pos.reports.PanelReportBean(); report.setTitleKey . . . Token Parsing Error: Lexical error at line 1, column 1. Encountered: "\ufeff" (65279), after : ""
This occurs if you save the *.bs or *.properties file as UTF-8 instead of ANSI, must be ANSI on these two files or you will get this error.
I have also solved the problem when the following error occurs:
Menu.Logi: Cannot load the report definition
net.sf.jasperreports.engine.JRException: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 1 of 1-byte UTF-8 sequence.
The solution is to re-save the *.jrxml file in notepad using UTF-* encoding, the *.bs and *.properties files need to be save in ANSI encoding though. The problem occurs when the UTF sequence is screwed up by wordpad or other editor, re-saving using UTF-8 corrects the problem.
Hope this helps.
Rgards, Todd Kempf