HI! We are using our own provider, because we need our own security and stuff for calling methods. So, we copied code from Axis' RPCProvider to our own and enhanced it with our security. If I compare the RPCProvider code from 2 weeks ago with today, it has changed much and keeping up with the changes is a bit annoying over time.
So, it would be nice, if we had clean extensiblity points in the RPCProvider. This is what we would need: 1. Access to the MessageContext. Our own transport stores properties there, like caller name. 2. Control over the method invocation. We need the ability to refuse (by exception) the method call for certain callers. 3. Searching for the method ourselves, because we only have one service deployed that handles all classes, and so the javaclass is always the same. Maybe it would be best to seperate the wandering through the SOAP message and the constructing of the answer from the reflection part. So, one could extend RPCProvider and override the necessary methods (not the whole processMessage() method). Any chance that this might find a way into Axis? Thanks! Regards, Thomas
