Hello Everyone, I am trying to modify Apache SOAP, so that it will be possible to use BEEP as an alternative protocol to HTTP as a transport protocol. So far I have written a (rudimentary) SOAPBEEPConnection to use instead of the SOAPHTTPConnection. This works as yet only with a BEEP server that is not at all integrated into the Apache SOAP classes. I am trying to understand what classes I have to replace on the server side so as to be able to receive RPCalls with a custon-made BEEP server that ultimately forwards these Calls to the respective classes. But I am stuck in trying to see through the hierachy and order in which the Apache SOAP classes interact and work on the server side.
My understanding so far is this: * Calls are received by the RPCRouterServlet. * The appropriate Service is then located through the Service Manager. * And the Call is then forwarded to that method What is unclear to me is from where the SOAPContext is taken and how the DeploymentDescriptor is accessed. Maybe someone can explain these aspects to me and maybe also verify my assumptions made above. Thanks in advance, Sebastian -- __________________________________________________________________________ sebastian thiebes [EMAIL PROTECTED] "Jetzt koennte ich hier tierisch die lange Inhaltsangabe Auflisten aber ich rechne mit Eurer Integenz" - gefunden bei eBay
