I am writing a simple SOAP router that, essentially, does the same as the
ProxyService from the axis samples. The main difference is that the URL
that the message is to be delivered to is determined from request elements.
Moving forward, the destination will be determined base on info in the SOAP
I wonder if it might be possible to create our own SAX InputSource that
filters the incoming XML stream and throws an exception when it hits an XML
construct that is considered dangerous?
ADK
There is no magic.
I agree this is odd. The console output here is part of the business
function of the app. Separation of concerns would have us view logging as
distinct from the core business logic. What we are in fact doing is
relying on logging to provide an integral part of our functionality.
IMO This shou
