[
https://issues.apache.org/jira/browse/PIVOT-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731402#comment-13731402
]
Sandro Martini commented on PIVOT-914:
--------------------------------------
Ok, I understand that the title is too much generic, probably could be renamed
... and this is just to start focus better what could be needed ... the general
idea in this issue is to start exploring a set of little utilities that could
help to split a big application in different modules (but all in the same
tier). But without doing something too complex (like OSGi or other complete
modularization system).
Anyway, the idea could be to provide something to try isolate Pivot-related
features, hiding parts to the rest of the application (so the idea of a
Classloader per module), and maybe enabling/disabling modules when necessary.
And of course by default 1 module with (full) application scope like today.
Roger, you developed a big application with Pivot, so maybe you could write
some things that could be improved in this field.
Probably it would be better to discuss this in dev mailing list, and write here
some updates ... but could be for Pivot 2.5 .
> Modularization of applications
> ------------------------------
>
> Key: PIVOT-914
> URL: https://issues.apache.org/jira/browse/PIVOT-914
> Project: Pivot
> Issue Type: Improvement
> Reporter: Sandro Martini
> Assignee: Sandro Martini
> Fix For: 2.5, 2.1
>
>
> Verify if find a way (maybe using different Classloaders) to modularize
> applications
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
