ModelMBean Persistence using PersisterMBean Limitation

Since only the persistName attribute of the mbeanDescriptor is used to lookup a registered PersisterMBean within the RequiredModelMBean class and the location and name attributes are ignored, it seems that you must have a 1:1 association of ModelMBean to PersisterMBean in order to implement a custom persistence mechanism. The FilePersister, on the other hand uses these attributes to allow a single FilePersister to service the persistence needs of multiple MBeans.

I would like to create a JDBCPersister, but do not want to have a registered bean for each bean I wish to persist. Is there any reason that the other two fields could not be passed in the constructor of the PersisterMBean like the FilePersister is?

Thanks,
Richard Williams