Jump to content
We've recently updated our Privacy Statement, available here ×
  • Custom query executors: How to run import/export scripts when using them?


    Raphaël Peguet

    The problem

    [toc on_off::hide=1]

    If you are on this page that probably means that you have implemented a custom query executor and that you may have an error like this doing your import from the Buildomatic (using the js-export.bat):

    2012-06-25 06:26:28,761 ERROR BaseExportImportCommand:45 - com.jaspersoft.jasperserver.api.JSExceptionWrapper:

    net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'XXX' language. com.jaspersoft.jasperserver.api.JSExceptionWrapper:

    net.sf.jasperreports.engine.JRException: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the 'XXX' language. at

    net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:247) at

    net.sf.jasperreports.engine.xml.JRXmlLoader.loadXML(JRXmlLoader.java:230) at

    net.sf.jasperreports.engine.xml.JRXmlLoader.load(JRXmlLoader.java:218)

    where XXX is the custom query language.

    The Solution

    Prior to run js-export.bat you need to add the customization in the Buildomatic's sub-folder conf_source/iePro so that the query executor language can be identified. It should also include jasperreports.properties where it needs to be configured to use soap query executor language.

     


    User Feedback

    Recommended Comments

    There are no comments to display.



    Guest
    This is now closed for further comments

×
×
  • Create New...