[
https://issues.apache.org/jira/browse/GERONIMO-3350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Jencks closed GERONIMO-3350.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.1
This took a lot of commits between Jeff Genender, Paul McMahan, and myself..
hopefully they all show up in the "All" view.
> Console needs to administer all the web connectors. Needs WebManager change.
> -----------------------------------------------------------------------------
>
> Key: GERONIMO-3350
> URL: https://issues.apache.org/jira/browse/GERONIMO-3350
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: console, Jetty, management, Tomcat
> Affects Versions: 2.0-M6
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 2.0, 2.1
>
>
> After a discussion on IRC of the problems with the console administering web
> connectors jgenender, pmcmahan, and I (djencks) came up with this plan:
> Modify the WebManager interface to have 3 connector related methods:
> List<connectorType> getConnectorTypes();// returns a list of what kinds of
> connectors are available
> List<configItem> getConnectorAttributes(connectorType);/ returns a list of
> what you can configure on that connector, including display name, attribute
> name, description, and value.
> GBeanData configureConnector(connectorType, List<configItem>);/ configures a
> GBeanData with all the stuff needed.
> Then the tomcat and jetty WebManager can tell the console what connectors are
> available, how to configure them, and give it the configured gbean.
> I don't know what the "WebConnector" class is for... returning GBeanData in
> the last step may not be the best.
> This might not be the best long term solution but seems like it will work and
> be doable by 2.0.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
