[adrian.brock]

BTW, puke like this is why I like the DOM approach so much better. XB seems way to inflexible and overbearing most of the time.

I think the problem is that as the title suggests, this is metadata simplication
instead of simplfication. ;-)

Incidently, the reason the old DOM stuff doesn't work is because it merges at parse time
meaning you can't recreate the original xml documents afterwards.

There should never have been an "override", we discussed this last friday.
It should be possible to override the whole of ejb-jar.xml with the jboss.xml
(or annonations) in fact, the ejb-jar.xml should be optional :-)

So the JBossXXXMetaData is the override.

[starksm64]

I think the problem is that as the title suggests, this is metadata simplication
instead of simplfication. ;-)

Great, then the problem is fixed with correction of the subject

[starksm64]

The latest simplified metadata that uses the jboss extension of the standard metadata as the unified view has been put out as the current 1.0.0.snapshot used by jbossas. The jbossxb snapshot was also updated since it has needed changes. The jbossas trunk is running against these versions.

[wolfc]

I still wasn't too happy about the usage side, so I genericed the final lot. This effectively makes the interfaces obsolete.

[anil.saldhana]

I have a case where the ear contains a jboss-app.xml but misses a jboss.xml.

So when I ask the JBossAssemblyDescritorMetaData for the securityroles configured, it is returning null because the "SecurityRoleMetaData" is not merged. It is available in the ear metadata.

What needs to be done here?

[starksm64]

We are still missing a merging deployer. I'm working on a MergedJBossMetaDataDeployer to combine the ejb-jar, jboss, and annotation views. It should also deal with ear level values that affect the resulting JBossMetaData object.

[anil.saldhana]

Not a burning issue for me. Thanks for the update, Scott.