Re: jcontainer-interest digest, Vol 1 #191 - 5 msgs

jcontainer-interest wrote:
> As the above is a PITA to setup and configure it may be best to create a
> static utility class to help do all this in fewer steps. You may have
> something like a
> 
> class VirtualMockFactory
> {
>   static VirtualMockRuntime createRuntime() {...} //May read default config
> file from Classpath
>   static VirtualMockRuntime createRuntime( InputSource in ) {...} //For ones
> that use non-standard config file
> }

Would it also be acceptable to have a third overloaded method which 
takes a VirtualMockConfig as a parameter?  This would allow users to 
pass in a configuration that they have programatically created, if they 
don't want to deal with XML files.  Is this a standard/accepted approach?

Thanks,
Chad