"[email protected]" wrote : | If my understanding is correct the fix should be easy - just change the output of EJB3 deployer to something like setOutput('internal.'+AnnotationEnviroment.class.getSimpleName()) which will make sure that both AnnotationEnviroments can co-exist happily :) EJB3 deployer can only use AnnotationEnvironment (AE), hence is shouldn't declare itself as an AE provider / output.
And like I said, having two AE's is wrong. e.g. it might load the classes too soon, when it's not intended - aop, ... The proper fix is to use the existing one and just build the info on top of it in a new deployer. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228588#4228588 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228588 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
