0 Replies Latest reply on Apr 8, 2008 8:34 AM by Scott Stark

    JBDEPLOY-32, how to deal with custom schemas with class bind

    Scott Stark Master

      This usage of a custom schema binding in an mc bean property:

      is essentially the same as annotation processing. We need the deployment class loader to be able to create the binding classes. Right now there is no notion of parsing having to interact with a deployment class loader.

      Essentially the parsing of the bean property fragment needs to be delayed until the deployment class loader is available.

      The question is how to do this. Have jbossxb throw a unresolvable schema classes error that results in a partial KernelDeployment/BeanMetaData, or just have the value passed in the for bean property be an unresolved binding metadata value that has to be resolved after the class loader is established. Of course if the class loader setting itself has the unresolved value its a broken deployment.