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/01/21 03:30:18 UTC
Passing initliasation parameters to SOAP services
Since Aapche-SOAP itself is a servlet, initialised via web.xml within
soap.war .... and the SOAP services that developers write are "not"
really servlets in the since that it does not have access to
ServletConfig and it does not implement the Servlet interface .... what
is the best way to add initialisation parameters for SOAP services?
--
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: R: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
The error indicates that the server closed the connection without
even sending an HTTP status message. I am not sure what would cause
this, as Tomcat usually catches errors that occur in servlets and
returns information about them to the client. The only things I can
suggest are to check the Tomcat error logs, and if nothing is found
there, turn on some Tomcat debug (although I am not sure what debug
is available in version 3.2.3).
On 21 Jan 2003 at 17:38, Antonino Galletta wrote:
> Dear all,
>
> I used the Apache-Soap 2.2 with TOMCAT Version 3.2.3 to develop a
> distribuited application over many european country.
> The norvegian client application raises the following exception:
>
> Caught SOAPException (SOAP-ENV:Client): Error parsing HTTP status line "":
> java.util.NoSuchElementException
> [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status
> line "": java.util.NoSuchElementException; targ
> etException=java.lang.IllegalArgumentException: Error parsing HTTP status
> line "": java.util.NoSuchElementException]
> at
> org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
> va:324)
> at org.apache.soap.rpc.Call.invoke(Call.java:205)
> at
> com.Alenia.rtp1113.wp8.SoapHandler.soapOrb.ProxySoap.invoke(ProxySoap.java:1
> 84)
>
> Can somebody help me ?
>
> Many thanks
> Antonino Galletta
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Scott Nichol
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
Re: Passing initliasation parameters to SOAP services
Posted by "Jesus M. Salvo Jr." <je...@migasia.com>.
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>.
On 22 Jan 2003 at 10:22, Jesus M. Salvo Jr. wrote:
>
> Scott Nichol wrote:
>
> >If you are using Apache SOAP 2.3.1 or 2.2, you can use the method
> >described in http://xml.apache.org/soap/docs/guide/migration.html.
> >Specifically, you add a parameter of type SOAPContext as the first
> >parameter in your method. You then use SOAPContext's "bag" to get
> >the servlet associated with the call. From there, you can get
> >servlet initialization information.
> >
> >
> >
> 1) OK .. .Read that part ... but what I do not understand is, what is
> the difference between the SOAPContext that is passed as the first
> argument, versus the other SOAPContexts ( requestCtx and responseCtx ),
> as mentioned in "Writing a Messaging Services":
>
> void */name/*(SOAPEnvelope */request-envelope/*, SOAPContext
> */request-context/*, SOAPContext */response-context/*)
>
> Meaning .... Why can't I get the property via
> requestContext.getProperty() or responseContext.getProperty()?
The SOAPContext that is the first parameter for an RPC is the same as
the SOAPContext that is requestCtx for a messaging service. It is
the context of the request. Therefore, if you are writing a
messaging service, you can get parameters through requestCtx.
>
>
> 2) Even if you do get the servlet initialisation from the "bag" ...
> there are other issues with this approach:
>
> 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.
>
> 2b) This mean that you have to change the web.xml that comes with
> apache-soap. ( e.g.: Explode soap.war int $TOMCAT_HOME/web-apps/, remove
> soap.war, .... etc. .. There is a slight possibility someone may
> accidentally alter the configuration in such a way that the Apache-SOAP
> itself no longer works.
>
True. The same goes for the "global" web.xml that some servlet
containers, such as Tomcat, use.
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Scott Nichol
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
On 22 Jan 2003 at 10:22, Jesus M. Salvo Jr. wrote:
>
> Scott Nichol wrote:
>
> >If you are using Apache SOAP 2.3.1 or 2.2, you can use the method
> >described in http://xml.apache.org/soap/docs/guide/migration.html.
> >Specifically, you add a parameter of type SOAPContext as the first
> >parameter in your method. You then use SOAPContext's "bag" to get
> >the servlet associated with the call. From there, you can get
> >servlet initialization information.
> >
> >
> >
> 1) OK .. .Read that part ... but what I do not understand is, what is
> the difference between the SOAPContext that is passed as the first
> argument, versus the other SOAPContexts ( requestCtx and responseCtx ),
> as mentioned in "Writing a Messaging Services":
>
> void */name/*(SOAPEnvelope */request-envelope/*, SOAPContext
> */request-context/*, SOAPContext */response-context/*)
>
> Meaning .... Why can't I get the property via
> requestContext.getProperty() or responseContext.getProperty()?
The SOAPContext that is the first parameter for an RPC is the same as
the SOAPContext that is requestCtx for a messaging service. It is
the context of the request. Therefore, if you are writing a
messaging service, you can get parameters through requestCtx.
>
>
> 2) Even if you do get the servlet initialisation from the "bag" ...
> there are other issues with this approach:
>
> 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.
>
> 2b) This mean that you have to change the web.xml that comes with
> apache-soap. ( e.g.: Explode soap.war int $TOMCAT_HOME/web-apps/, remove
> soap.war, .... etc. .. There is a slight possibility someone may
> accidentally alter the configuration in such a way that the Apache-SOAP
> itself no longer works.
>
True. The same goes for the "global" web.xml that some servlet
containers, such as Tomcat, use.
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Scott Nichol
Re: Passing initliasation parameters to SOAP services
Posted by "Jesus M. Salvo Jr." <je...@migasia.com>.
Scott Nichol wrote:
>If you are using Apache SOAP 2.3.1 or 2.2, you can use the method
>described in http://xml.apache.org/soap/docs/guide/migration.html.
>Specifically, you add a parameter of type SOAPContext as the first
>parameter in your method. You then use SOAPContext's "bag" to get
>the servlet associated with the call. From there, you can get
>servlet initialization information.
>
>
>
1) OK .. .Read that part ... but what I do not understand is, what is
the difference between the SOAPContext that is passed as the first
argument, versus the other SOAPContexts ( requestCtx and responseCtx ),
as mentioned in "Writing a Messaging Services":
void */name/*(SOAPEnvelope */request-envelope/*, SOAPContext
*/request-context/*, SOAPContext */response-context/*)
Meaning .... Why can't I get the property via
requestContext.getProperty() or responseContext.getProperty()?
2) Even if you do get the servlet initialisation from the "bag" ...
there are other issues with this approach:
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.
2b) This mean that you have to change the web.xml that comes with
apache-soap. ( e.g.: Explode soap.war int $TOMCAT_HOME/web-apps/, remove
soap.war, .... etc. .. There is a slight possibility someone may
accidentally alter the configuration in such a way that the Apache-SOAP
itself no longer works.
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Passing initliasation parameters to SOAP services
Posted by "Jesus M. Salvo Jr." <je...@migasia.com>.
Scott Nichol wrote:
>If you are using Apache SOAP 2.3.1 or 2.2, you can use the method
>described in http://xml.apache.org/soap/docs/guide/migration.html.
>Specifically, you add a parameter of type SOAPContext as the first
>parameter in your method. You then use SOAPContext's "bag" to get
>the servlet associated with the call. From there, you can get
>servlet initialization information.
>
>
>
1) OK .. .Read that part ... but what I do not understand is, what is
the difference between the SOAPContext that is passed as the first
argument, versus the other SOAPContexts ( requestCtx and responseCtx ),
as mentioned in "Writing a Messaging Services":
void */name/*(SOAPEnvelope */request-envelope/*, SOAPContext
*/request-context/*, SOAPContext */response-context/*)
Meaning .... Why can't I get the property via
requestContext.getProperty() or responseContext.getProperty()?
2) Even if you do get the servlet initialisation from the "bag" ...
there are other issues with this approach:
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.
2b) This mean that you have to change the web.xml that comes with
apache-soap. ( e.g.: Explode soap.war int $TOMCAT_HOME/web-apps/, remove
soap.war, .... etc. .. There is a slight possibility someone may
accidentally alter the configuration in such a way that the Apache-SOAP
itself no longer works.
Re: R: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
The error indicates that the server closed the connection without
even sending an HTTP status message. I am not sure what would cause
this, as Tomcat usually catches errors that occur in servlets and
returns information about them to the client. The only things I can
suggest are to check the Tomcat error logs, and if nothing is found
there, turn on some Tomcat debug (although I am not sure what debug
is available in version 3.2.3).
On 21 Jan 2003 at 17:38, Antonino Galletta wrote:
> Dear all,
>
> I used the Apache-Soap 2.2 with TOMCAT Version 3.2.3 to develop a
> distribuited application over many european country.
> The norvegian client application raises the following exception:
>
> Caught SOAPException (SOAP-ENV:Client): Error parsing HTTP status line "":
> java.util.NoSuchElementException
> [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status
> line "": java.util.NoSuchElementException; targ
> etException=java.lang.IllegalArgumentException: Error parsing HTTP status
> line "": java.util.NoSuchElementException]
> at
> org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
> va:324)
> at org.apache.soap.rpc.Call.invoke(Call.java:205)
> at
> com.Alenia.rtp1113.wp8.SoapHandler.soapOrb.ProxySoap.invoke(ProxySoap.java:1
> 84)
>
> Can somebody help me ?
>
> Many thanks
> Antonino Galletta
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Scott Nichol
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: R: Passing initliasation parameters to SOAP services
Posted by Carl Cabou <ex...@sncf.fr>.
It seems to be a XML parsing error.
Maybe your norvegian client doesn't use the good XML data (bad arguments
...).
Or maybe a bug in the "norvegian" part of the service code.
Did it work some day or always making fault ?
Carl.
Antonino Galletta wrote:
> Dear all,
>
> I used the Apache-Soap 2.2 with TOMCAT Version 3.2.3 to develop a
> distribuited application over many european country.
> The norvegian client application raises the following exception:
>
> Caught SOAPException (SOAP-ENV:Client): Error parsing HTTP status line "":
> java.util.NoSuchElementException
> [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status
> line "": java.util.NoSuchElementException; targ
> etException=java.lang.IllegalArgumentException: Error parsing HTTP status
> line "": java.util.NoSuchElementException]
> at
> org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
> va:324)
> at org.apache.soap.rpc.Call.invoke(Call.java:205)
> at
> com.Alenia.rtp1113.wp8.SoapHandler.soapOrb.ProxySoap.invoke(ProxySoap.java:1
> 84)
>
> Can somebody help me ?
>
> Many thanks
> Antonino Galletta
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: R: Passing initliasation parameters to SOAP services
Posted by Carl Cabou <ex...@sncf.fr>.
It seems to be a XML parsing error.
Maybe your norvegian client doesn't use the good XML data (bad arguments
...).
Or maybe a bug in the "norvegian" part of the service code.
Did it work some day or always making fault ?
Carl.
Antonino Galletta wrote:
> Dear all,
>
> I used the Apache-Soap 2.2 with TOMCAT Version 3.2.3 to develop a
> distribuited application over many european country.
> The norvegian client application raises the following exception:
>
> Caught SOAPException (SOAP-ENV:Client): Error parsing HTTP status line "":
> java.util.NoSuchElementException
> [SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status
> line "": java.util.NoSuchElementException; targ
> etException=java.lang.IllegalArgumentException: Error parsing HTTP status
> line "": java.util.NoSuchElementException]
> at
> org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
> va:324)
> at org.apache.soap.rpc.Call.invoke(Call.java:205)
> at
> com.Alenia.rtp1113.wp8.SoapHandler.soapOrb.ProxySoap.invoke(ProxySoap.java:1
> 84)
>
> Can somebody help me ?
>
> Many thanks
> Antonino Galletta
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
R: Passing initliasation parameters to SOAP services
Posted by Antonino Galletta <an...@openvision.it>.
Dear all,
I used the Apache-Soap 2.2 with TOMCAT Version 3.2.3 to develop a
distribuited application over many european country.
The norvegian client application raises the following exception:
Caught SOAPException (SOAP-ENV:Client): Error parsing HTTP status line "":
java.util.NoSuchElementException
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status
line "": java.util.NoSuchElementException; targ
etException=java.lang.IllegalArgumentException: Error parsing HTTP status
line "": java.util.NoSuchElementException]
at
org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
va:324)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at
com.Alenia.rtp1113.wp8.SoapHandler.soapOrb.ProxySoap.invoke(ProxySoap.java:1
84)
Can somebody help me ?
Many thanks
Antonino Galletta
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
R: Passing initliasation parameters to SOAP services
Posted by Antonino Galletta <an...@openvision.it>.
Dear all,
I used the Apache-Soap 2.2 with TOMCAT Version 3.2.3 to develop a
distribuited application over many european country.
The norvegian client application raises the following exception:
Caught SOAPException (SOAP-ENV:Client): Error parsing HTTP status line "":
java.util.NoSuchElementException
[SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP status
line "": java.util.NoSuchElementException; targ
etException=java.lang.IllegalArgumentException: Error parsing HTTP status
line "": java.util.NoSuchElementException]
at
org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.ja
va:324)
at org.apache.soap.rpc.Call.invoke(Call.java:205)
at
com.Alenia.rtp1113.wp8.SoapHandler.soapOrb.ProxySoap.invoke(ProxySoap.java:1
84)
Can somebody help me ?
Many thanks
Antonino Galletta
Re: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
If you are using a nightly build of Apache SOAP, your service class
can implement the ConfigurableService interface. This interface has
a single method that is called after instantiation with parameters
for the webapp, the servlet and the service (from the deployment
descriptor).
If you are using Apache SOAP 2.3.1 or 2.2, you can use the method
described in http://xml.apache.org/soap/docs/guide/migration.html.
Specifically, you add a parameter of type SOAPContext as the first
parameter in your method. You then use SOAPContext's "bag" to get
the servlet associated with the call. From there, you can get
servlet initialization information.
On 21 Jan 2003 at 13:30, Jesus M. Salvo Jr. wrote:
>
> Since Aapche-SOAP itself is a servlet, initialised via web.xml within
> soap.war .... and the SOAP services that developers write are "not"
> really servlets in the since that it does not have access to
> ServletConfig and it does not implement the Servlet interface .... what
> is the best way to add initialisation parameters for SOAP services?
>
> --
> 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
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Scott Nichol
Re: Passing initliasation parameters to SOAP services
Posted by Scott Nichol <sn...@scottnichol.com>.
If you are using a nightly build of Apache SOAP, your service class
can implement the ConfigurableService interface. This interface has
a single method that is called after instantiation with parameters
for the webapp, the servlet and the service (from the deployment
descriptor).
If you are using Apache SOAP 2.3.1 or 2.2, you can use the method
described in http://xml.apache.org/soap/docs/guide/migration.html.
Specifically, you add a parameter of type SOAPContext as the first
parameter in your method. You then use SOAPContext's "bag" to get
the servlet associated with the call. From there, you can get
servlet initialization information.
On 21 Jan 2003 at 13:30, Jesus M. Salvo Jr. wrote:
>
> Since Aapche-SOAP itself is a servlet, initialised via web.xml within
> soap.war .... and the SOAP services that developers write are "not"
> really servlets in the since that it does not have access to
> ServletConfig and it does not implement the Servlet interface .... what
> is the best way to add initialisation parameters for SOAP services?
>
> --
> 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
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Scott Nichol
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>