[Geoserver-devel] [JIRA] (GEOS-7565) Cluster settings - "Couldn't resolve model type..." warning

[Maciej Filocha (JIRA)]

Title: Message Title

Maciej Filocha created an issue   GeoServer / GEOS-7565 Cluster settings - "Couldn't resolve model type..." warning Issue Type: Bug Affects Versions: 2.9.0 Assignee: Unassigned Components: UI Created: 31/May/16 2:50 PM Environment: Centos 7.2, tomcat 7.0.69, java-1.8.0-openjdk Priority: Medium Reporter: Maciej Filocha Opening a "Cluster settings" tab throws following warning: {WARN [form.AbstractTextComponent] - Couldn't resolve model type of Model:classname=[org.apache.wicket.model.CompoundPropertyModel$AttachedCompoundPropertyModel]:nestedModel=[Model:classname=[org.apache.w icket.model.CompoundPropertyModel]:nestedModel=[ {toggleSlave=true, topicName=VirtualTopic.>, connection=enabled, brokerURL=tcp://ng7:61616, durable=true, xbeanURL=./broker.xml, toggleMaster=false, embeddedBroker=disabled, CLUST ER_CONFIG_DIR=/var/lib/geoserver/cluster, embeddedBrokerProperties=embedded-broker.properties, connection.retry=3, instanceName=ng6, readOnly=enabled, group=geoserver-cluster, connection.maxwait=10000} ]] for [TextField [Compone nt id = toggleSlave]], please set the type yourself.} Add Comment   This message was sent by Atlassian JIRA (v1000.25.1#100000-sha1:fa89b69)

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel