User development, A new message was posted in the thread "JBDEPLOY-226 - DeployerClient change extension":
http://community.jboss.org/message/527972#527972 Author : Adrian Brock Profile : http://community.jboss.org/people/adr...@jboss.org Message: -------------------------------------------------------------- I've added a new mixin interface to implement this feature. https://svn.jboss.org/repos/jbossas/projects/jboss-deployers/trunk/deployers-client-spi/src/main/java/org/jboss/deployers/client/spi/DeployerClientChangeExt.java since I want to be able to do this as well in some of the stuff I'm doing. There's also a mixin interface on DeployersImpl, so it won't work for Thomas unless he changes his wangy wrapper to delegate the new method. If the Deployers doesn't implement the new mixin interface, it falls back to doing the deployments one by one, i.e. the old behaviour. I've left the JIRA open in case we want to add some other methods? One possiblity would be to have a addChange(DeploymentStage, String name); processChanges(); type api that let you move deployments to different stages at the same time. But I'm not sure how useful that would be and the implementation would be a bit more complicated and probably less efficient? :-) If everybody is happy with just this one new method we can close the JIRA. -------------------------------------------------------------- To reply to this message visit the message page: http://community.jboss.org/message/527972#527972
_______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
