Hello David, Friday, May 24, 2002, 5:17:19 PM, you wrote:
DJ> The FoeDeployer should register with MainDeployer as the last thing it does DJ> in startService(), when it is in fact usable. So at least you should move DJ> super.startService() to the end. Yes, it even caused problem determining correct tmp directory. I've corrected it and sent to Andreas. That's our working scheme for now :) DJ> I just looked at the code and think that a simpler design would be to DJ> simply have the WLC be a SubDeployer. You can make a common superclass DJ> with utility methods all the foe deployers will need. Otherwise you will DJ> have to either give foedeployer a list of all the converters it will get, DJ> which is kind of silly, or implement another layer of waiting behavior in DJ> FoeDeployer, which is even sillier. As far as I can tell from a quick DJ> glance, FoeDeployer doesn't do anything that couldn't be done at least as DJ> well in a superclass of WLC. Also I thought some of the file manipulation DJ> methods were already in SubDeployerSupport?? I havne't looked at it for a DJ> while though. I've got your idea. It's another aproach than Andreas' one is. For now the idea is to create a manager for convertors to add and remove them on the fly. But your idea doesn't exclude this in any way, as I see. Maybe Andreas will write something on it. I just retold his idea. alex _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
