java.io.IOException

File name for xsql class CotizacionData is different than the class name defined inside the file: cotizacionData

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web22286

  • File name for xsql class CotizacionData is different than the class name defined inside the file: cotizacionData
  • via openbravo by marcantonichis
    , 11 months ago
    File name for xsql class LinesData is different than the class name defined inside the file: linesData
  • File name for xsql class CustomerRigData is different than the class name defined inside the file: Customer\_RigData
  • Stack trace

    • java.io.IOException: File name for xsql class CotizacionData is different than the class name defined inside the file: cotizacionData at org.openbravo.data.Sqlc.printInitClass(Unknown Source) at org.openbravo.data.Sqlc.endElement(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.openbravo.data.Sqlc.parseSqlFile(Unknown Source) at org.openbravo.data.Sqlc.listDir(Unknown Source) at org.openbravo.data.Sqlc.listDir(Unknown Source) at org.openbravo.data.Sqlc.listDir(Unknown Source) at org.openbravo.data.Sqlc.listDir(Unknown Source) at org.openbravo.data.Sqlc.listDir(Unknown Source) at org.openbravo.data.Sqlc.main(Unknown Source)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.