[jboss-dev-forums] [Design of POJO Server] - Re: Unifying metadata

[adrian@jboss.org]

"scott.stark at jboss.org" wrote : 
  | 1. The existing ObjectModelFactoryDeployer based deployers producing legacy metadata need to be converted to SchemaResolverDeployer type deployers that produce the new metadata, and then create the legacy wrapper using the new metadata as the delegate. The JBossXBBuilder would be used to create the SchemaBinding for the new metadata.
  | 
  | One little issue here is that the SchemaResolverDeployer does not have a SchemaBindingResolver getResolver() method to allow subclasses to easily extend the default resolver.
  | 

This was something I asked Alex to look at.
I'm not sure how much he has done?

Currently there is a POJO/MBean that lets you specify
schema -> SchemaBindingInitializer
(there are factory settings)

What's required for the JBossXBBuilder is instead
schema -> annotated class name (the root class)
and build the schemabinding from that.

In fact, since the annotated class name contains the schema name
as an annotation, all that's really required is being able to add classes
(unless we also want to specify aliases as well).

Also, JBossXB needs updating so we can do
dtd -> annotated class name
or
dtd -> schema
so we can parse xmls with legacy dtds using the schema binding.

This requires a change to JBossXB's SAXParser to trap the dtd event
and store it somewhere for when the schema handling tries to resolve
schema. i.e. resolve using the dtd public/system id instead of the non-existant
xmlns declaration.

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

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