[
https://issues.apache.org/jira/browse/GERONIMO-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul McMahan closed GERONIMO-3413.
----------------------------------
Resolution: Fixed
console plugins available in SVN at /repos/asf/geronimo/plugins
> factor the console portlets into separate plugins
> -------------------------------------------------
>
> Key: GERONIMO-3413
> URL: https://issues.apache.org/jira/browse/GERONIMO-3413
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: console
> Affects Versions: 2.1
> Reporter: Paul McMahan
> Assignee: Paul McMahan
> Fix For: 2.1
>
> Attachments: geronimo-3413.patch
>
>
> The administration console contains portlets for configuring the components
> in a JEE5 server, and a few more things like debugging, creating deployment
> plans, etc. Right now the collection of portlets is "hard coded" in the
> console's pluto configuration. This makes it difficult for users to choose
> which portlets they want in their console. For example some users may not
> want the various classloader/dependency/JMX/LDAP/etc viewers because they
> require the dojo library, which adds a non-trivial server footprint. But
> more importantly this makes it difficult to deploy the administration console
> into a customized geronimo assembly (like the minimal ones) because those
> assemblies typically don't have all the JEE5 components installed that would
> be necessary to satisfy the console's dependencies.
> There is some work going on to make the console customizable using pluto
> 1.2's portal driver framework. The portal driver allows the console to
> dynamically add/remove portlets. Using this new capability from pluto
> provides the capability to create an administration console for the minimal
> assembly that contains only the base portlets, such as those necessary for
> deployment and web server configuration. The other portlets need to be
> factored out of the admin console as separately deployable WAR files and
> provided as plugins. This allows the user to selectively install portlets
> from the plugin catalog. And when the user deploys a component into the
> minimal assembly such as ActiveMQ they should be able to install the JMS
> administration portlet at that point in time, if desired.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
