Jump to content
We've recently updated our Privacy Statement, available here ×

uio100

Members
  • Posts

    3
  • Joined

  • Last visited

uio100's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Dear Forum, I'm in search of a tool that allows for deployment of Jasper Server Reports (=jrxml, resources, input controls) to a Jasper Server installation. The idea is to have similar structured environments "production", "test/uat" and "dev" and a report developed on "dev" shall be unloaded and passed untouched to "test/uat" and then to "production". Such report would reference its resource by standardized names, such as "/datasources/MYSOURCE" where MYSOURCE points to different real database connections on each environment. Toying with js-export and js-import was not satisfactory. Besides being a dangerous tool, js-export also exports the data source definition of a report. As long as the report does not exist on the target side, js-import is safe when not in update mode. It would sense that "/datasources/MYSOURCE" already exists and just create the report. However, if you want to update the report through the same mechanism, one would have to specifiy --update as an argument to js-import and the datasource reference would get updated, too. Desastrous if applied to a production installation. I can imagine that with web services, one could implement a tool that picks up a deployment unit (whatever that is and how this is implemented, basically containing the jrxml, the resources, references to data sources etc.) and installs it with the proper permission on a target jasper server. I wonder if such tool exists or if I have to create it from scratch. kind regards Michael
  2. Dear Mariano, thank you so much for you help. I've followed your advice and assembled everything in a zip file: log output MySQL table structure + data domain xml definition file Notabene: when exporting the file to xml from the doman editor, upon sending it back via "upload" the domain editor complains about "invalid file". kind regards Michael
  3. Dear Forum, we're currently evaluating jasperserver PRO 4.5 with strong emphasis on end-user reporting capabilities. Now having no-tech end users trying out the Ad Hoc Report functionality, I'm struck with a weird error in the ad hoc report editor: When adding a filter to the report, one cannot add a further column from the fields picker. Example: Imaging having mapped a Table (Oracle 11g) TEST_01_SP with fields ACCOUNT_NO, ACCOUNT_TYPE, CUSTOMER_ID, the user wants to filter its report by CUSTOMER_ID without showing this column in the report. So she or he adds a filter on CUSTOMER_ID. In the next step, upon adding e.g. ACCOUNT_NO, a JavaScript alert pops up reading "An error occurred while perfoming the previous request". Besides this being a completely useless message, the server log shows something like at com.jaspersoft.commons.dataset.expr.ExpressionJSONConverter.createJSONObject(ExpressionJSONConverter.java:270) ... 90 moreCaused by: java.lang.RuntimeException: can't resolve type for var 'SP01.CUSTOMER_ID' of type com.jaspersoft.commons.semantic.impl.QueryExpressionEvaluator$QueryResourceVariable at com.jaspersoft.commons.dataset.expr.ExpressionJSONConverter.createJSONObject(ExpressionJSONConverter.java:240) ... 91 more which seems to be related to the error the user gets in the browser, both by point in time and content of message. I'm going to make another test to see if this is probably bound to a specific type of datasource (Oracle 11g via JNDI) or is to be considered a bug in ad hoc report editor in general. Any pointers towards a fix or workaround are greatly appreciated. kind regards Michael
×
×
  • Create New...