The current hard-coded publicID to dtd/xsd mapping in the JBossEntityResolver needs to be externalized to allow for augmenting with user schemas. I created the following feature request issue:
http://jira.jboss.com/jira/browse/JBAS-2038
The whole publicID/systemID/namespaceURI resolution behavior needs to be consistent across the various xml contexts. As I mention in the case I have not gotten the xml catalog resolver from apache to work as I would like, but I don't see a problem with using the xml catalog syntax for the externalization of the mappings.
I need some feedback on how schemas are being resolved today in webservices and the like along with how this need to change with the introduction of jaxb.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886434#3886434
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886434
|
