Jeremy Boynes wrote: > > I think we get the equivalent behaviour by having the Monitor load the > NetworkServerControlImpl directly; alternatively we could have > JDBCBoot start it up explicitly. > I might be misunderstanding what you are proposing, but wouldn't this cause the NetworkServerControlImpl and its dependencies to get pulled into derby.jar?
Kathey
