jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • GeoServer
  • GEOS-3309

Provide a store edit extension point so specific store types can provide it's own config page

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.0-beta2
  • Fix Version/s: 2.0-RC1
  • Component/s: Wicket UI
  • Labels:
    None

Description

DataStorePanelInfo.componentClass is waiting to be used. This property can provide the implementation class for the store specific extension point

Issue Links

is depended upon by

Improvement - An improvement or enhancement to an existing feature or task. GEOS-3310 Implement a custom ArcSDE coverage store configuration panel

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Gabriel Roldán added a comment - 31/Jul/09 5:54 PM

implemented the extension point for coverages at r13039

  • introduced the base class org.geoserver.web.data.store.StoreEditPanel to be added at the store edit page to take care of the connection parameters. Workspace, store name and enabled properties keep being in control of the main store edit page
  • made DataStorePanelInfo.componentClass being StoreEditPanel
  • added StoreExtensionPoints to look up the GeoServerApplication for the StoreEditPanel appropriate for a given StoreInfo and provide a default StoreEditPanel if there's no one declared for a specific store type
  • introduced org.geoserver.web.data.store.DefaultCoverageStoreEditPanel that provides the input field for the coverage URL, being the default for coverage types that don't contribute to the UI
Show
Gabriel Roldán added a comment - 31/Jul/09 5:54 PM implemented the extension point for coverages at r13039
  • introduced the base class org.geoserver.web.data.store.StoreEditPanel to be added at the store edit page to take care of the connection parameters. Workspace, store name and enabled properties keep being in control of the main store edit page
  • made DataStorePanelInfo.componentClass being StoreEditPanel
  • added StoreExtensionPoints to look up the GeoServerApplication for the StoreEditPanel appropriate for a given StoreInfo and provide a default StoreEditPanel if there's no one declared for a specific store type
  • introduced org.geoserver.web.data.store.DefaultCoverageStoreEditPanel that provides the input field for the coverage URL, being the default for coverage types that don't contribute to the UI
Hide
Permalink
Gabriel Roldán added a comment - 05/Aug/09 8:15 AM

fixed at r13066

  • moved creation of datastore parameters form input fields to it's own class in order to implement the default contribution to the extension point for DataStoreInfo
Show
Gabriel Roldán added a comment - 05/Aug/09 8:15 AM fixed at r13066
  • moved creation of datastore parameters form input fields to it's own class in order to implement the default contribution to the extension point for DataStoreInfo

People

  • Assignee:
    Gabriel Roldán
    Reporter:
    Gabriel Roldán
Vote (0)
Watch (2)

Dates

  • Created:
    30/Jul/09 9:40 AM
    Updated:
    05/Aug/09 8:15 AM
    Resolved:
    05/Aug/09 8:15 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.