[
https://issues.apache.org/jira/browse/OODT-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Imesha Sudasingha updated OODT-910:
-----------------------------------
Fix Version/s: (was: 2.0)
(was: 1.9)
> Create Skinny Dependencies for WARs
> -----------------------------------
>
> Key: OODT-910
> URL: https://issues.apache.org/jira/browse/OODT-910
> Project: OODT
> Issue Type: Improvement
> Components: opsui
> Reporter: Tom Barber
> Priority: Major
>
> Currently the OPSUI war files are huge because the drag in all of the OODT
> component transient dependencies which to the best of my knowledge are
> generally not required as the UI just sends commands to remote services.
> To combat this we should create some skinny components that dont' include all
> the transient dependencies.
> The "easy" but not very maintainable way would probably be to "exclude" a big
> list of transient dependencies in the pom files for the components you want
> to slim down.
> An alternative approach which I would favour, would be to create an API
> module, similar to OSGI design practices, that contain the various API
> interfaces for the component, say the filemanager. Then OPSUI can implement
> its required interfaces separately from the filemanager, which can also
> implement the interfaces if required on its side.
> I'm sure there are alternatives, just dictating my thoughts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
