Konakart jars

[clinton]

Would it make things easier if the konakart-app.jar was split into two, with one jar containing non-customisable classes, whereas the second jar could contain all the Actions and Forms for which we currently have the source code?

Developers may want to provide their own customisations of the struts Actions and Forms, but currently these are bundled into konakart-app.jar alongside non-customisable classes.  This means developers wishing to customise the default Actions must either modify the jar, overriding classes as desired, or recreate/repackage the jar.  It could be a cleaner separation of concerns if we had a jar containing only customisable classes (ie: for which we have source code).

[julie]

Hi Clinton,

It's such a good point we have already done this for the next release    (that will be v 2.2.0.7)

What you will see is all the customisable application classes inside konakart_custom.jar and konakartadmin_custom.jar.   These classes will be all those for which you have source that's shipped under the examples directory in the kit.

This should make it a lot cleaner as you suggest and easier to build your own customisations into these custom jars.

The new release will be (should be?!) available this week.

Regards,
Julie

[clinton]

Thanks Julie, separate jars that developers can customise makes things easier.
- Clinton