This content has been marked as final.
Show 4 replies
-
1. Re: [jboss-metadata] Additional post-merge processing
alrubinger Oct 14, 2008 6:40 AM (in response to alrubinger)The second case I mention is exposed by the EJB3 Integration TestSuite "changexml" and "service" tests:
vfszip:/home/alrubinger/business/jboss/wc/jbossas/projects/ejb3/trunk/testsuite/target/test-lib/changexml.jar -> java.lang.RuntimeException: @Remote and @Local may not both be specified on the same interface "interface org.jboss.ejb3.test.changexml.TesterRemote" for EJB "TesterBean" per EJB3 Spec 4.6.6, Bullet 5.4
S,
ALR -
2. Re: [jboss-metadata] Additional post-merge processing
alrubinger Oct 15, 2008 4:31 AM (in response to alrubinger)JBMETA-121 and r79515.
S,
ALR -
3. Re: [jboss-metadata] Additional post-merge processing
alrubinger Oct 20, 2008 12:06 AM (in response to alrubinger)jboss-metadata:1.0.0.CR2 is invalid due to JBMETA-131.
The issue is that some processors will need to be explicitly given a ClassLoader for the deployment, so I've defined JBMETA-132 to remove processing from JBoss50Creator and instead put this responsibility on the caller/consumer to create a ProcessorChain and run it.
For AS this will be implemented as another deployer in the mix; I'm considering using this to start an EJB3 Deployers project. The JNDI Binding Policy Decorator Deployer would likely move here as well.
S,
ALR -
4. Re: [jboss-metadata] Additional post-merge processing
alrubinger Oct 23, 2008 5:29 AM (in response to alrubinger)"ALRubinger" wrote:
For AS this will be implemented as another deployer in the mix; I'm considering using this to start an EJB3 Deployers project.
@see http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/deployers/src/main/java/org/jboss/ejb3/deployers/Ejb3MetadataProcessingDeployer.java
S,
ALR