0 Replies Latest reply on Sep 6, 2012 10:27 AM by Sławomir Wojtasiak

    JBoss 7 and PropertyEditorManager

    Sławomir Wojtasiak Newbie

      Hello,

       

      I'm trying to configure BasicThreadPool using following jboss-service.xml instance:

       

      {code:xml}

      <?xml version="1.0" encoding="UTF-8"?>

      <server xmlns="urn:jboss:service:7.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:jboss:service:7.0 jboss-service_7_0.xsd">

         <mbean code="org.jboss.util.threadpool.BasicThreadPool" name="jboss.system:service=ThreadPool">

              ...

              <attribute name="BlockingMode">wait</attribute>

          </mbean>

      </server>

      {code}

       

      As you can see, there is property "BlockingMode" of type org.jboss.util.threadpool.BlockingMode. It's not a simple type, so it needs PropertyEditor to be converted to appropriate value. Everything is fine till this point, because there is dedicated editor available in jboss-common-core module: org.jboss.util.propertyeditor.BlockingModeEditor, but PropertyEditorManager cannot resolve it.

       

      As far as I remember previous versions of JBoss AS (at least 6.x) register additional search pathes "org.jboss.util.propertyeditor" and "org.jboss.mx.util.propertyeditor" to instruct PropertyEditorManager where it should search for editor classes. It's org.jboss.util.propertyeditor.PropertyEditors class which is responsible for registering these pathes. This class is also available inside JBoss 7 AS, but it seems that it isn't used there, at least in plain standalone configuration (standalone.xml), so these pathes are never registered inside PropertyEditorManager.

       

      Was it intended to disable this feature? I don't think so, because there are editors which follows this naming convention, so maybe an additional extension should be configured in standalone.xml to enable it or maybe it's just a bug?

       

      Thanks in advance,

      Sławek