The following elements will be removed from EJB3 jboss.xml

[aloubyansky]

I went through the elements in jboss_5_1.xsd and listed those that couldn't find being used by EJB3. So I consider them EJB2 legacy and am going to remove them for metadata GA. Maybe some of them are actually used, so, please, have a look.
(If some look useful but aren't used yet I'll remove them anyway. I think there shouldn't be meaningless config elements. We'll add them when they become effective)

jboss

- enforce-ejb-restrictions (this one has been deprecated)
- exception-on-rollback (Whether to throw an exception if the transaction is marked for rollback, used in EJB2 only)
- what's with jacc-context-id? (used only in ejb2? no tests in AS or EJB3?)


message-driven

- local-jndi-name
- jndi-binding-policy
- exception-on-rollback
- timer-persistence (used only EJB2?)
- configuration-name
- invoker-bindings
- security-proxy
- ior-security-config (used only in EJB2?)
- no tests for jndi-refs?


consumer

- jndi-name
- local-jndi-name
- jndi-binding-policy


service

- call-by-value (used only in EJB2)
- exception-on-rollback
- timer-persistence
- configuration-name
- invoker-bindings
- security-proxy
- cache-config (service is stateless? if so doesn't need a cache?)
- ior-security-config


session

- call-by-value
- exception-on-rollback
- timer-persistence
- configuration-name
- invoker-bindings
- security-proxy
- ior-security-config


generic-bean

- call-by-value
- exception-on-rollback
- timer-persistence
- configuration-name
- invoker-bindings
- security-proxy
- ior-security-config

Thanks.

[jaikiran]

I went through the elements in jboss_5_1.xsd and listed those that couldn't find being used by EJB3. So I consider them EJB2 legacy and am going to remove them for metadata GA.

Does this mean, that the jboss.xml (with jboss_5_1 xsd) is only meant for EJB3 applications? So EJB2.x applications should use older xsd declarations in the jboss.xml?

[aloubyansky]

Yes, jboss.xml for EJB2 references DTDs.

[dimitris]

Alexey, just go ahead, I don't see people willing to provide more input on this.

But if someone needs those of those elements, he'll have to add it back himself :-)

[wolfc]

No, regression means rollback.

Fact of the matter is that this case shows that jboss.xsd should not be part of the metadata project. Within Metadata there is no way to assert completeness, because the actual logic that dictates this demand is in the EJB 3 project.

I think I'm going to pull it out. If a component uses EJB 3 metadata it should depend on an EJB 3 component anyway.