The importance of the naming convention adding an export channel

Dear all,
I want to understand the importante of the naming convention in the definition of a new export channel.
 
I read the guide "Adding Custom Export Channels" here http://community.jaspersoft.com/documentation/tibco-jasperreports-server...
The guide reports an example thaht adds the export channel in three places: the report viewer, the scheduler, and web services.
 
Really the guide talks about the report viewer and the scheduler.
 
I followed all guidelines except one:
 
That, where the instructions read <MyFormat>, you have used the correct name for your export format. For example, if you're creating an exporter that generates .DBF files, where the instructions describe the Report<MyFormat>Exporter class, your class is called ReportDBFExporter.
 
At the end of implementation and configuration, the export channel works well for the report viewer and the scheduler.
 
Also, I use rest apis V2:
 
 
example of the usage:
 
- request 1
 
BODY:
 
<reportExecutionRequest>
<reportUnitUri>/TEST/Reports/QRCode_Test</reportUnitUri>
<async>true</async>
<freshData>true</freshData>
<saveDataSnapshot>false</saveDataSnapshot>
<outputFormat>wraphtml</outputFormat>
<interactive>false</interactive>
<ignorePagination>false</ignorePagination>
<parameters>
<reportParameter name="param001">
<value>Text</value>
</reportParameter>
<reportParameter name="param002">
<value>123321</value>
</reportParameter>
</parameters>
</reportExecutionRequest>
 
- response 1
 
BODY:
 
<reportExecution>
<exports>
<export>
<id>d1c3698f-c7c2-4003-ba4f-223a02c670be</id>
<status>queued</status>
</export>
</exports>
<reportURI>/TEST/Reports/QRCode_Test</reportURI>
<requestId>91d072f5-2723-4237-86ca-6b8deb147f41</requestId>
<status>queued</status>
</reportExecution>
 
- request 2
 
 
 
- response 2:
BODY:
 
{
"value": "failed",
"errorDescriptor":{
"errorCode": "webservices.error.errorExportingReportUnit",
"parameters": [
"Export format wraphtml not supported or misconfigured"
]
}
}
 
The class name and beannames don't follow guidilines: 
 
-  class name Report<MyFormat>Exporter
-  bean name <MyFormat>ExportParametersBean
 
== EDIT 05/10/2015 ==
 
I changed all definition and the service doesn't still work. Logs aren't helpful. 
mgenova's picture
Joined: Aug 23 2010 - 12:49am
Last seen: 6 years 3 days ago

0 Answers:

No answers yet
Feedback
randomness