WG: [Fwd: configure instances of a SOAP provider class?]

[sa...@sdm.de]

Hi Doug,

as far as I understood Apache SOAP the SOAPContext is a dynamic
context provided with each invocation. By now our providers (to
be exact: the class mentioned in the DeploymentDescriptor.xml)
actually aren't SOAP-aware.
SOAP (more specific org.apache.soap.server.RPCRouter and the
serialization ;-) wraps nicely around our classes, so we actually
don't see the SOAPContext. Would we have to add an own provider
next to org.apache.soap.providers.RPCJavaProvider to gain access?

What we are looking for is something more static, say sth. like
configuring the name of the file where to dump log information,
set a debug flag and so on, and the class in the
DeploymentDescriptor should have easy access to it.
This is information that we need only once at the start of the
provider's life cycle.
Right now we do that by means of Properties, accessed as
resources. However, it would be nice to have a single point of
definition and one way to do that, in XML.

What about using the DeploymentDescriptor.xml itself and applying a
mechanism similar to the initialization of Servlets? Maybe I get the
concept all wrong, but right now we have got no real deployment-
specific information in it, only things which are dependent on
the Java-implementation only. So our various "Info"-service
descriptors all look the same and we configure the different settings
(log files etc.) via the Properties explained above.
Putting a section <options>...</options> in the DeploymentDescriptor
would do the job of customizing/deploying the service for a specific
task, and if the RPCJavaProvider did look for an (optional)
'init(Element)'-method to call it with the <options> Element immediately
after creation, we could configure it all in one place (and backward
compatible :-).

Does that sound sensible to you?
Cheers,
Sasan


-----Ursprüngliche Nachricht-----
Von: Christian Spanner [mailto:spanner@sdm.de]
Gesendet am: Freitag, 30. März 2001 10:05
An: Sasan Baba-Esfahani
Betreff: [Fwd: configure instances of a SOAP provider class?]

Doug Davis schrieb:
> 
> I think you're right, right now there is no way to put options
> in the servlet config file and have them passed on to the
> provider - it wouldn't take a whole lot to do.  We could just
> have the 'readConfigFile' method look for an 'options'
> element just below the root and stick 'em in a hashtable
> that is then placed in the SOAPContext for the provider
> to read.  Would that work for you?
> -Dug
> 
> Christian Spanner <sp...@sdm.de> on 03/29/2001 09:19:01 AM
> 
> Please respond to soap-user@xml.apache.org
> 
> To:   SOAP User Mailinglist <so...@xml.apache.org>
> cc:
> Subject:  configure instances of a SOAP provider class?
> 
> Hi all,
> 
> anyone knows if there's a way to configure
> multiple instances of the same SOAP provider class
> that run as different webapps in Tomcat?
> 
> say, we have the same service class "Info" running
> multiple times as different webapp on different data sets
> (configured as different XML-Files).
> 
> now, is it possible to configure the XML-File on
> the webapp-level? obviously there is no parameter-passing
> from Tomcat through the rpcrouter-Servlet to the SOAP provider class.
> Is there some environment variable, system property
> specific to the webapp, say, directory or something?
> Any other possibility?
> 
> thanx,
>   Christian
> 
> --
> Christian Spanner        mailto:spanner@sdm.de
> sd&m AG                  http://www.sdm.de
> software design & management
> Thomas-Dehler-Str. 27, 81737 Muenchen, Germany
> Tel +49 89 63812-457, Fax -515
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
> For additional commands, email: soap-user-help@xml.apache.org


-- 
Christian Spanner		mailto:spanner@sdm.de
sd&m AG          		http://www.sdm.de
software design & management
Thomas-Dehler-Str. 27, 81737 Muenchen, Germany
Tel +49 89 63812-457, Fax -515

---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@xml.apache.org
For additional commands, email: soap-user-help@xml.apache.org