Scott Nichol wrote:
If you are using Apache SOAP 2.3.1 or 2.2, you can use the method described in http://xml.apache.org/soap/docs/guide/migration.html. Specifically, you add a parameter of type SOAPContext as the first parameter in your method. You then use SOAPContext's "bag" to get the servlet associated with the call. From there, you can get servlet initialization information.1) OK .. .Read that part ... but what I do not understand is, what is the difference between the SOAPContext that is passed as the first argument, versus the other SOAPContexts ( requestCtx and responseCtx ), as mentioned in "Writing a Messaging Services":
void */name/*(SOAPEnvelope */request-envelope/*, SOAPContext */request-context/*, SOAPContext */response-context/*)
Meaning .... Why can't I get the property via requestContext.getProperty() or responseContext.getProperty()?
2) Even if you do get the servlet initialisation from the "bag" ... there are other issues with this approach:
2a) Although the parameters can be localised to either SOAP RPC or SOAP messaging servlets ( since there are two servlets deployed with soap.war ), any initialisation parameters to the SOAP messaging servlet are "global" for all SOAP messaging services ... likewise true for SOAP rpc servlet and SOAP rpc services. Would have been good if there is a way to specify initialisation parameters at the SOAP service level ... not the servlet level.
2b) This mean that you have to change the web.xml that comes with apache-soap. ( e.g.: Explode soap.war int $TOMCAT_HOME/web-apps/, remove soap.war, .... etc. .. There is a slight possibility someone may accidentally alter the configuration in such a way that the Apache-SOAP itself no longer works.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
