"bstansberry(a)jboss.com" wrote : | First obvious step was to add property loadBalancePolicy to ClusterConfigMetaData. Doesn't help. | | Tricky thing here is for EJB2 the relevant cluster-config subelements are "home-load-balance-policy" and "bean-load-balance-policy". For EJB3 its just "load-balance-policy". This difference is reflected in different specifications for cluster-config in jboss_5_0.dtd vs jboss_5_0.xsd. | | When I stop the deploy in a debugger I see that JBossXB is expecting the EJB2 properties, even though ejb-jar specifies ejb-jar_3_0.xsd. The jboss.xml is properly specifying the xmlns and xsi:schemaLocation as well. | | The parsing is being handling by the JBossEjbParsing deployer when this happens. | | Any ideas? JBossXB doesn't look at the schema or dtd. It looks at the class to generate the SchemaBinding. Try enabling TRACE logging for org.jboss.xb and see what it says when it analyzes the ClusterConfigMetaData class. The SAXParser will give you a validation error if it doesn't match the schema or dtd. You want to write a test in the metadata project (e.g. the everything tests). It's easier to debug as well. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4104327#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...