[#XRP-104] Allow user-defined <output> implementation (by means of own Java Class)

Issue Details [XML]

Key:	XRP-104
Type:	New Feature
Status:	Resolved
Resolution:	Applied
Priority:	Minor
Assignee:	Marc Portier
Reporter:	Marc Portier
Votes:	0
Watchers:	0

Operations

If you were logged in you would be able to see more operations.

xReporter

Allow user-defined <output> implementation (by means of own Java Class)

Created: 15/Feb/06 06:56 AM Updated: 15/Feb/06 09:54 AM

Component/s:

None

Affects Version/s:

1.2.1

Fix Version/s:

1.3

Description

There exists already the possibility to let some custom java class perform arbitrary executions within the context of a flow-step.
However it is still required to let those prepare everything in temp-tables that can get read-out via the <output><database>.

This limitation requires that what in design are quite free-form result-pages are modeled into records in a database.
In contrast the <http> output mechanism allows for quite arbitrary external text to be pulled through xreporter.

Therefore the idea is to provide something like <ouput><java class=".."> </java></output> to allow for more flexible output generation while still reusing all benefits of the xreporter framework (common styling for information parts, shared access control to data and reports, ...)

All

Comments

Change History

Sort Order:

Comment by Marc Portier [15/Feb/06 09:54 AM]

[ Permlink ]

Applied a fix and a sample to svn

Actual fix is here: http://svn.cocoondev.org/viewsvn?root=xreporter&view=rev&rev=653
The sample got committed in various bits and pieces
http://svn.cocoondev.org/viewsvn?root=xreporter&view=rev&rev=654
http://svn.cocoondev.org/viewsvn?root=xreporter&view=rev&rev=655
http://svn.cocoondev.org/viewsvn?root=xreporter&view=rev&rev=656