axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glen Daniels" <gdani...@macromedia.com>
Subject Fw: configuring java class service
Date Thu, 16 Aug 2001 02:39:42 GMT

Guys:

What do you think of this idea?  We could implement this as either a Service
option or as a MessageContext property with constructor params....  Might be
good to add to the to-do list.

--Glen

----- Original Message -----
From: "Dmitri Colebatch" <dim@bigpond.net.au>
To: <soap-user@xml.apache.org>
Sent: Wednesday, August 15, 2001 10:41 PM
Subject: configuring java class service


> hey all,
>
> I'm relatively new to soap and hence the apache soap package.  My
> understanding is that you can (serlialization issues aside) basically grab
> any java class, and expose it through soap.  Now what apache soap does is
> create an instance of the class at the appropriate time (depending on the
> scope of the class).  My question is related to this point - soap uses the
> default constructor yes?  What I think might be worthwhile would be to
> allow the deployment descriptor to look like:
>
>   <isd:provider type="java"
>                 scope="Application"
>                 methods="foo bar">
>     <isd:java class="MyClass" static="false">
>       <arg type="java.lang.String">to be passed to constructor</arg>
>     </isd:java>
>   </isd:provider>
>
> which would then use the constructor MyClass("to be passed to
> constructor") instead of MyClass() - following JMX's flavour.  Does this
> make sense?
>
> I suppose my first question is, am I missing something here?  Obviously
> what I'm trying to do is customize the class performing the service, in
> this case, know where to get a db connection from.  If there's another way
> to do this already, then I'd love to know it, otherwise, does anyone else
> see a need for this?
>
> cheesr
> dim
>


Mime
View raw message