Bugzilla – Full Text Bug Listing
| Summary: | Large monitoring reports can not be sent to Jubula client | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Marc Steffens <Marc.Steffens> | ||||
| Component: | Agent | Assignee: | Zeb Ford-Reitz <zeb.ford-reitz> | ||||
| Status: | CLOSED FIXED | QA Contact: | Oliver Goetz <Oliver.Goetz> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | alexandra.schladebeck, zeb.ford-reitz | ||||
| Version: | unspecified | Flags: | zeb.ford-reitz:
juno+
|
||||
| Target Milestone: | Juno M5 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
patch applied (with small modifications such as local variable names, method names, and javadoc comments): http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=9d0c17465acb01b451b8c8c2a0186fd5b9c0c3e9 Tested using Windows, Linux and MacOS X machines generating large monitoring reports. |
Created attachment 208145 [details] This patch allows to stream monitoring reports to the Jubula client Jubula defines a monitoring framework which allows Jubula to calculate monitoring values and to generate monitoring reports. In some cases it is possible that the size of the generated monitoring report is to large to send it via the implemented message and command mechanism. The purpose of this patch is to avoid that the report could not be send to the client. The attached patch is implementing a streaming mechanism which will stream the report to client, instead of generating a large byte array which could in some cases not be send to the client. To implement this mechanism it was necessary to edit the IMonitoring interface. The buildMonitoring() method has now an argument of an OutputStream instead of generating and returning a byte array. Everything that was written to this OutputStream will be send to the client.