[Jboss-dev-forums] [Design of JBossXB] - General schema parsing

[<ad...@jb...>]

When I discussed this with Scott (on the pojoserver thread) 
we decided we wanted to go down the road of allowing ANY inside the metadata.

There is an xml test for this in the testsuite, but I don't see it getting tested?
[url]http://cvs.sourceforge.net/viewcvs.py/jboss/jbosstest/src/resources/xml/pojoserver/test1-ejb-deployment.xml?rev=1.1&view=auto[url]

What we are really looking for is the ability to provide some kind of registry or
self bootstrap of
schema public id -> SchemaBinding

e.g. If I do

  | <?xml version="1.0" encoding="UTF-8"?>
  | <deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  |    xsi:schemaLocation="urn:jboss:xml-deployer xml-deployer_1_0.xsd"
  |    xmlns="urn:jboss:xml-deployer">
  | 

i.e. I can shove the xml at an unmarshaller and expect it to work out that the
urn:jboss:xml-deployer:deployment needs to go through
org.jboss.kernel.plugins.deployment.xml.PojoSchemaBinding

then when it hits

  | <bean name="EJBContainerConfig" class="org.jboss.ejb.Container">
  |       <property name="Config">
  |    <ejb:ejb-container xmlns="urn:jboss:testejb-ns1">
  | 

it knows it needs to go a different mapping
urn:jboss:xml-deployer:deployment ->
org.jboss.ejb.metadata.EJBContainerSchemaBinding

Since the number of these schema bindings is indeterminate (users could
potentially write their own - certainly each JBoss module will)
and "hot deployable" I don't want to hardwire these other namespaces into the pojo schemabinding.


View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3875815#3875815

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3875815