right. my choice of 'ceau.com' was mainly motivated by not wanting to get in the way of other tests which put up Server mbeans, for instance, that listen on port 9000 by default --- so a fully running externally set-up localhost server on port 9000 would tend to break the unit tests.
what about starting/stopping a full localhost jboss-mail server in the setUp() and tearDown() methods of the test? in a sense its similar to putting up a single mbean like in some of the other tests, but of course more extensive since 400-500 other mbeans would follow along... but if we did that, it may still wind up saving some time since the environment would be preset and the penalty would be only 1-2 minutes for starting/stopping a full jboss deployment. but then if we started a full jboss server in the background for testing, we'd probably try to get efficiencies with the other tests too by not putting up single mbeans in them. any comments/thoughts/criticisms welcome --- i'm not really sure what the best way to do this is. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831090#3831090 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831090 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
