-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
-
None
Create a BRAND NEW DTD for jboss.xml for EJB3 jboss_ejb_3.dtd
This is listed in priority order.
Talk to me about stuff when you get to it.
<security-domain>
This is specified within <jboss> or can be specified within <session><message-driven>. This should add a @SecurityDomain annotation to the class.
<jndi-name />
<local-jndi-name />
These two should create @RemoteBinding and @LocalBinding annotations. They should check to see if @RemoteBindings @LocalBinding already exists as well and trash it. Look in ProxyDeployer for more information on creating default @RemoteBinding(s) @LocalBinding
<call-by-value>
Create a new Annotation for this. This metadata also needs to be set in the remote proxies so that IsLocalInterceptor knows whether or not to copy the parameters and a server side interceptor that stuffs the return value in a MarshalledObject in the Invocation object.
<configuration-name>
Change this to <aop-domain-name>
<ejb-ref>
<ejb-local-ref>
</security-identity>
<resource-ref>
<res-ref-name />
<resource-name />
</resource-ref>
<resource-env-ref>
These guys map references. We will need a new JBoss specific annotation to specify the global JNDI name. Talk to me about this when you start implementing it.
<security-identity>
<run-as-principal>
We will need JBoss specific annotations for this.
<clustered />
<cluster-config>
Maps to @Clustered. May need to
<loader-repository> stuff
We'll need to implement these classloader elements. They change classloader semantics.
Talk to me about any others after you finish these.
- blocks
-
EJBTHREE-281 Allow a default <security-domain> element in jboss.xml
- Closed