Clean up org.adempiere.extend

Description

  1. Remove org.adempiere.extend project.

  2. Move unit testing code that’s still some what working to a new project org.idempiere.test (to be created later).

Environment

None

Activity

Show:
Carlos Ruiz
May 5, 2020, 12:28 PM

Hi , thanks I finally figured out how that plugin works.

Indeed is not a provider for jasper files, it can provide any file, for example it seems like an easy way to provide images within the fragment plugin to be used in the webserver (for example for the logos).

The name of the plugin is org.adempiere.report.jasper.webapp, but maybe a better name would something like org.idempiere.staticwebfiles

Now, from my review I have some concerns about this plugin that I'll discuss via email.

Regards,

Carlos Ruiz

Heng Sin Low
May 5, 2020, 12:51 PM

Yes, it is just a static file server. I think we probably should just remove it as it is kind of unnecessary - you can host that static file (jasper report file or otherwise) anyway and we don’t need a plugin created just for that.

Carlos Ruiz
May 5, 2020, 2:28 PM

I think is fine to keep it as an external plugin somewhere else. Whoever likes it can install it.
The only mechanism "jasper" related there is the md5 verification.

Carlos Ruiz
May 5, 2020, 2:35 PM

I just did the same changing the org.adempiere.report.jasper.fragment.test to be a fragment of org.adempiere.server instead of the jasper webapp.

The result is the same (without the md5 validation), not much loss, in the end downloading a jrxml file from the same server must have so insignificant bandwidth.

Heng Sin Low
May 5, 2020, 2:53 PM

I think the initial idea is to host .jrxml file and to avoid recompilation rather than saving bandwidth. However, in practice, people usually host .jasper file (safer to avoid compilation on the fly) making this kind of pointless.

Assignee

Heng Sin Low

Reporter

Heng Sin Low

Labels

None

Tested By

None

Components

Fix versions

Priority

Minor
Configure