[jboss-dev-forums] [Design of EJB 3.0] - The following elements will be removed from EJB3 jboss.xml

alex.loubyansky@jboss.com do-not-reply at jboss.com
Thu Apr 2 03:58:19 EDT 2009


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.

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

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



More information about the jboss-dev-forums mailing list