You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by "Jesus M. Salvo Jr." <je...@migasia.com> on 2003/02/03 01:26:18 UTC
Re: Passing initliasation parameters to SOAP services
Scott Nichol wrote:
>
>
>>2a) Although the parameters can be localised to either SOAP RPC or SOAP
>>messaging servlets ( since there are two servlets deployed with soap.war
>>), any initialisation parameters to the SOAP messaging servlet are
>>"global" for all SOAP messaging services ... likewise true for SOAP rpc
>>servlet and SOAP rpc services. Would have been good if there is a way to
>>specify initialisation parameters at the SOAP service level ... not the
>>servlet level.
>>
>>
>
>If you use Apache SOAP 2.3 or later, there is a way: the deployment
>descriptor for the service. That can be accessed from the
>SOAPContext bag using Constants.BAG_DEPLOYMENTDESCRIPTOR.
>
>
>
Are you talking here about the element <isd:option/>?
Where is the Apache-SOAP deployment descriptor schema definittion file?
Re: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
You are right, it's not in the 2.3.1 release. We will have a new
release when a more experienced committer can help me through the
process, but I've been waiting for months now.
On 7 Feb 2003 at 10:06, Jesus M. Salvo Jr. wrote:
>
> Hmmm ... I assume this is not part of the 2.3.1 release .. only on the
> nightly builds?
> When will we have a new release?
>
>
> Scott Nichol wrote:
>
> >The configure method of the ConfigurableService interface is only
> >called immediately after the constructor. It is *not* called each
> >time a service method is called. Therefore, you could just
> >instantiate the listener in the configure method instead of the
> >constructor, and use an application or servlet or deployment
> >descriptor parameter rather than a System property.
> >
> >On 6 Feb 2003 at 10:43, Jesus M. Salvo Jr. wrote:
> >
> >
> >
> >>Just realised that it would have been good that such parameters are
> >>accessible via the service's constructor .. or a init() method just like
> >>in servlets ... at least in the case of what I am doing, that is ...
> >>the SOAP service will need to pass on a Java object that represents the
> >>SOAP message into a "listener" class.
> >>
> >>Currently, what I do is instantiate this "listener" class within the
> >>SOAP service's constructor by checking for a system property. Therefore,
> >>this checking is only called once, and is placed in an instance variable.
> >>
> >>If I move this checking from the constructor to the SOAP service
> >>method(s), and the instance variable is not null ... then each of the
> >>service methods would need have to have a synchronized block to a) check
> >>if there is a listener, b) if no listener, get the class to instantiate
> >>from the parameters <isd:option>, c) create the instance and place it in
> >>the instance variable. Of course, once created, only [a] will need to be
> >>checked .. but you still have the overhead of a synchronized block
> >>within the service method.
> >>
> >>Oh well
> >>
> >>
> >>Scott Nichol wrote:
> >>
> >>
> >>
> >>>Yes, I am referring to <isd:option>. The schema is at
> >>>http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-
> >>>soap/java/docs/schema/dd.xsd?rev=HEAD&content-type=text/plain
> >>>
> >>>On 3 Feb 2003 at 11:26, Jesus M. Salvo Jr. wrote:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >Scott Nichol
> >
> >Do not reply directly to this e-mail address, as it is filtered to
> >only receive e-mail
> >from specific mailing lists.
> >
> >
> >
> >
> >
>
>
> --
> Jesus M. Salvo Jr.
> Mobile Internet Group Pty Ltd
> (formerly Softgame International Pty Ltd)
> M: +61 409 126699
> T: +61 2 94604777
> F: +61 2 94603677
>
> PGP Public key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0BA5348
>
>
>
Scott Nichol
Do not reply directly to this e-mail address, as it is filtered to
only receive e-mail from specific mailing lists.
Re: Passing initliasation parameters to SOAP services
Posted by "Jesus M. Salvo Jr." <je...@migasia.com>.
Hmmm ... I assume this is not part of the 2.3.1 release .. only on the
nightly builds?
When will we have a new release?
Scott Nichol wrote:
>The configure method of the ConfigurableService interface is only
>called immediately after the constructor. It is *not* called each
>time a service method is called. Therefore, you could just
>instantiate the listener in the configure method instead of the
>constructor, and use an application or servlet or deployment
>descriptor parameter rather than a System property.
>
>On 6 Feb 2003 at 10:43, Jesus M. Salvo Jr. wrote:
>
>
>
>>Just realised that it would have been good that such parameters are
>>accessible via the service's constructor .. or a init() method just like
>>in servlets ... at least in the case of what I am doing, that is ...
>>the SOAP service will need to pass on a Java object that represents the
>>SOAP message into a "listener" class.
>>
>>Currently, what I do is instantiate this "listener" class within the
>>SOAP service's constructor by checking for a system property. Therefore,
>>this checking is only called once, and is placed in an instance variable.
>>
>>If I move this checking from the constructor to the SOAP service
>>method(s), and the instance variable is not null ... then each of the
>>service methods would need have to have a synchronized block to a) check
>>if there is a listener, b) if no listener, get the class to instantiate
>>from the parameters <isd:option>, c) create the instance and place it in
>>the instance variable. Of course, once created, only [a] will need to be
>>checked .. but you still have the overhead of a synchronized block
>>within the service method.
>>
>>Oh well
>>
>>
>>Scott Nichol wrote:
>>
>>
>>
>>>Yes, I am referring to <isd:option>. The schema is at
>>>http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-
>>>soap/java/docs/schema/dd.xsd?rev=HEAD&content-type=text/plain
>>>
>>>On 3 Feb 2003 at 11:26, Jesus M. Salvo Jr. wrote:
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>Scott Nichol
>
>Do not reply directly to this e-mail address, as it is filtered to
>only receive e-mail
>from specific mailing lists.
>
>
>
>
>
--
Jesus M. Salvo Jr.
Mobile Internet Group Pty Ltd
(formerly Softgame International Pty Ltd)
M: +61 409 126699
T: +61 2 94604777
F: +61 2 94603677
PGP Public key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC0BA5348
Re: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
The configure method of the ConfigurableService interface is only
called immediately after the constructor. It is *not* called each
time a service method is called. Therefore, you could just
instantiate the listener in the configure method instead of the
constructor, and use an application or servlet or deployment
descriptor parameter rather than a System property.
On 6 Feb 2003 at 10:43, Jesus M. Salvo Jr. wrote:
>
> Just realised that it would have been good that such parameters are
> accessible via the service's constructor .. or a init() method just like
> in servlets ... at least in the case of what I am doing, that is ...
> the SOAP service will need to pass on a Java object that represents the
> SOAP message into a "listener" class.
>
> Currently, what I do is instantiate this "listener" class within the
> SOAP service's constructor by checking for a system property. Therefore,
> this checking is only called once, and is placed in an instance variable.
>
> If I move this checking from the constructor to the SOAP service
> method(s), and the instance variable is not null ... then each of the
> service methods would need have to have a synchronized block to a) check
> if there is a listener, b) if no listener, get the class to instantiate
> from the parameters <isd:option>, c) create the instance and place it in
> the instance variable. Of course, once created, only [a] will need to be
> checked .. but you still have the overhead of a synchronized block
> within the service method.
>
> Oh well
>
>
> Scott Nichol wrote:
>
> >Yes, I am referring to <isd:option>. The schema is at
> >http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-
> >soap/java/docs/schema/dd.xsd?rev=HEAD&content-type=text/plain
> >
> >On 3 Feb 2003 at 11:26, Jesus M. Salvo Jr. wrote:
> >
> >
> >
>
>
Scott Nichol
Do not reply directly to this e-mail address, as it is filtered to
only receive e-mail
from specific mailing lists.
Re: Passing initliasation parameters to SOAP services
Posted by "Jesus M. Salvo Jr." <je...@migasia.com>.
Just realised that it would have been good that such parameters are
accessible via the service's constructor .. or a init() method just like
in servlets ... at least in the case of what I am doing, that is ...
the SOAP service will need to pass on a Java object that represents the
SOAP message into a "listener" class.
Currently, what I do is instantiate this "listener" class within the
SOAP service's constructor by checking for a system property. Therefore,
this checking is only called once, and is placed in an instance variable.
If I move this checking from the constructor to the SOAP service
method(s), and the instance variable is not null ... then each of the
service methods would need have to have a synchronized block to a) check
if there is a listener, b) if no listener, get the class to instantiate
from the parameters <isd:option>, c) create the instance and place it in
the instance variable. Of course, once created, only [a] will need to be
checked .. but you still have the overhead of a synchronized block
within the service method.
Oh well
Scott Nichol wrote:
>Yes, I am referring to <isd:option>. The schema is at
>http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-
>soap/java/docs/schema/dd.xsd?rev=HEAD&content-type=text/plain
>
>On 3 Feb 2003 at 11:26, Jesus M. Salvo Jr. wrote:
>
>
>
Re: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
Yes, I am referring to <isd:option>. The schema is at
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-
soap/java/docs/schema/dd.xsd?rev=HEAD&content-type=text/plain
On 3 Feb 2003 at 11:26, Jesus M. Salvo Jr. wrote:
> Scott Nichol wrote:
>
> >
> >
> >>2a) Although the parameters can be localised to either SOAP RPC or SOAP
> >>messaging servlets ( since there are two servlets deployed with soap.war
> >>), any initialisation parameters to the SOAP messaging servlet are
> >>"global" for all SOAP messaging services ... likewise true for SOAP rpc
> >>servlet and SOAP rpc services. Would have been good if there is a way to
> >>specify initialisation parameters at the SOAP service level ... not the
> >>servlet level.
> >>
> >>
> >
> >If you use Apache SOAP 2.3 or later, there is a way: the deployment
> >descriptor for the service. That can be accessed from the
> >SOAPContext bag using Constants.BAG_DEPLOYMENTDESCRIPTOR.
> >
> >
> >
>
> Are you talking here about the element <isd:option/>?
> Where is the Apache-SOAP deployment descriptor schema definittion file?
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Scott Nichol