HI!
My problem is:
I do not want to provide any information about the available classes at all. Not with .wsdd files, not with XML files and not at run time. Because if I had to do this, I'll have to feed info about all available classes into the engine (and there are many of them) before the first call from a client arrives.
But I want that the engine accepts any call (to any service/class and method) and just calls my dispatcher class which then either calls the right method via reflection or fails, if the class or method does not exist. The servicename could be composed out of packagename and classname.
I already tried to deploy a dummy service which would just represent ALL classes, but had no luck with that approach, yet.
Problem is, that I'm running out of time to find a solution.
All I need Axis for is:
- generating WSDL from Java classes
- analyzing a SOAP XML, extracting the info and provide classname, methodname and parameters to some dispatcher
- generate an answer SOAP XML from return value or exception
I have:
- my own HTTP server (no servlets)
- my own dispatcher (that does security and the actual call via reflection)
Any ideas how to to this with Axis?
Regards,
Thomas
> -----Original Message-----
> From: Glyn Normington [mailto:[EMAIL PROTECTED]]
> Sent: Freitag, 25. Januar 2002 17:34
> To: [EMAIL PROTECTED]
> Subject: RE: Using Axis without deployment (totally dynamic)
>
>
>
> Thomas,
>
> You may like to take a look at the WSDD refactoring that is
> going on in cvs
> branch config-work. We are introducing an EngineConfiguration
> interface
> that could supply an engine with configuration data dynamically, i.e.
> without files. Take a look at the axis-dev archive too for a
> note on this.
>
> Glyn
>
>
>
