[Design of EJB 3.0] - Plug-able default JNDI binding policy
by bdecoste
This is something we've discussed in the past, but it's come up again. I propose that we create a plug-able default jbndi policy. It's becoming clear that no matter what we choose for a default policy, somebody doesn't like it. SEAM is having problems with embedded in multiple wars and would like the default policy to be warName/bean/Name.
I don't think it would be that much work - maybe a day or 2. The jndi code is fairly isolated now. Here's what we would need to do
- create the policy api. Probably just 1 method like
| String getJndiBinding(String deploymentName, String beanName, boolean
| isLocal, isHome);
|
- create an impl for the current policy
- create an annotation like @JndiPolicy for setting the policy impl
- modify ejb3-interceptors-aop.xml to default the default policy
- modify the jboss.xml schema and code to add the new annotation
Thoughts?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101485#4101485
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101485
18 years, 2 months
[Design of EJB 3.0] - New Build Artifact - EJB3 External API
by ALRubinger
I've added a new artifact to the EJB3 build script, producing:
jboss-ejb3-ext-api.jar
...whose intent is to expose any classes needed by a bean provider for development (compilation) of EJB3 and JBoss-specific extensions. To develop EJB3 applications on JBoss, all that should be required on the build CP is this library and jboss-javaee.jar
Currently the external API is limited to all annotations (minus the Impls), Stateful Cache support, and RemoteProxyFactory (as is currently required for compilation).
The key here is ensuring that we don't expose any implementation internals to the bean provider, externalizing out as interfaces whenever possible but providing enough support for custom implementations.
Testing the validity of this JAR is proving difficult; the test suite itself tests many internals and cannot compile against the external API alone.
How can we ensure that we're providing everything necessary for an external API in this JAR? Separate source tree of test EJBs compiled against the Ext API and jboss-javaee.jar alone?
The alternative is the status quo I used to employ as a bean provider - grabbing internals from JARs under ejb3.deployer and using those for compilation.
This must be completed for Beta 3.
http://jira.jboss.com/jira/browse/EJBTHREE-1099
S,
ALR
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101476#4101476
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101476
18 years, 2 months