User development, A new message was posted in the thread "Deployer ordering issue for EJB/JAX-RS/WAR?":
http://community.jboss.org/message/519398#519398 Author : Adrian Brock Profile : http://community.jboss.org/people/adr...@jboss.org Message: -------------------------------------------------------------- I think Carlo has a better understanding of what Bill is talking about - terminology problem again. :-) He is talking about Components rather than SubDeployments. But that doesn't sound like the right thing to order after? Ordering after the ComponentDeployer for EJBs would work since it controls the ordering in which the deployers are invoked (for the whole deployment - parent/child/components). It's only the mandatory input - setInput() or passed to the constructor - that decides whether to ignore your deployer if it doesn't have it. The problem with ordering after the ComponentDeployer would be that it is very late. It is when you start doing stuff to the runtime. Typically you want to get your metadata all sorted out before that, otherwise different parts of the runtime would see different config. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/519398#519398
_______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
