wsn component fails to start if there is no transport connector available

The error occurs if the activemq.xml file does not have a transportConnector defined. This doesn't seem desired in all cases in which one wishes to utilize a vm transport and not allow connections on a tcp socket. I'm not sure how this would affect the wsn component directly since we are not using it. The current workaround for us it remove wsn component from hotdeploy directory in this certain configuration. I've attached an error log showing the offending error.