Forum Discussion
SmartBear_Suppo
Alumni
14 years agoHi Matt,
thanks for this!
I'm not sure this is the right way to go, since some internal SoapUI classes access the soapUI core via SoapUI.getSoapUICore() - I know this is a bad design but we have to live with it for now until we can refactor the whole core infrastructure..
One alternative would be to create and set the core only if it isn't already there, otherwise just use the existing one. I've added this to the current sources, this will be in the upcoming nightly build, maybe you can give it a try to see if it works ok in your setup!?
regards!
/Ole
eviware.com
thanks for this!
I'm not sure this is the right way to go, since some internal SoapUI classes access the soapUI core via SoapUI.getSoapUICore() - I know this is a bad design but we have to live with it for now until we can refactor the whole core infrastructure..
One alternative would be to create and set the core only if it isn't already there, otherwise just use the existing one. I've added this to the current sources, this will be in the upcoming nightly build, maybe you can give it a try to see if it works ok in your setup!?
regards!
/Ole
eviware.com