You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by ax...@ws.apache.org on 2004/07/20 11:23:39 UTC
[jira] Created: (AXIS-1465) Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1465
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1465
Summary: Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Type: Bug
Status: Unassigned
Priority: Critical
Project: Axis
Components:
Basic Architecture
Serialization/Deserialization
Versions:
current (nightly)
beta-2
Assignee:
Reporter: Yves Langisch
Created: Tue, 20 Jul 2004 2:23 AM
Updated: Tue, 20 Jul 2004 2:23 AM
Environment: SuSE 9.1, JDK 1.4.2-b28
Description:
Description from my mail to the mailing-list:
****************
On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> Follow-up: I have the same behaviour when I set the handlers on the call
> (setClientHandlers). It's already enough to invoke the method with an
> empty chain to get the described behaviour.
>
> Tested with 1.2beta1 and 1.2beta2.
>
> What's wrong here?
>
> Yves
>
>
>
> On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > All,
> >
> > I have a document/literal web service which I invoke through the
> > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > client-config.wsdd to define some handlers, it seems that the
> > client-config.wsdd overrides the encoding settings made by the stub
> > although there is no encodingStyle -> call seems to be soap-encoded
> > instead of literal afterwards. Following the client-config.wsdd:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <deployment name="defaultClientConfig"
> > xmlns="http://xml.apache.org/axis/wsdd/"
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="java"
> > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > <service name="SalaryDeclaration">
> > <requestFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </requestFlow>
> > <responseFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </responseFlow>
> > </service>
> > </deployment>
> >
> > Is this a normal behaviour?
> >
> > Yves
>
>
********************
In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
start the server with 'ant server' ...
change the port in the TestClient in order to use TCPMon
start client with 'ant client'
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1465) Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Posted by ax...@ws.apache.org.
The following issue has been updated:
Updater: Yves Langisch (mailto:yves@langisch.ch)
Date: Tue, 20 Jul 2004 2:24 AM
Changes:
Attachment changed to clthandler.tgz
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1465?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1465
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1465
Summary: Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Type: Bug
Status: Unassigned
Priority: Critical
Project: Axis
Components:
Basic Architecture
Serialization/Deserialization
Versions:
current (nightly)
beta-2
Assignee:
Reporter: Yves Langisch
Created: Tue, 20 Jul 2004 2:23 AM
Updated: Tue, 20 Jul 2004 2:24 AM
Environment: SuSE 9.1, JDK 1.4.2-b28
Description:
Description from my mail to the mailing-list:
****************
On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> Follow-up: I have the same behaviour when I set the handlers on the call
> (setClientHandlers). It's already enough to invoke the method with an
> empty chain to get the described behaviour.
>
> Tested with 1.2beta1 and 1.2beta2.
>
> What's wrong here?
>
> Yves
>
>
>
> On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > All,
> >
> > I have a document/literal web service which I invoke through the
> > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > client-config.wsdd to define some handlers, it seems that the
> > client-config.wsdd overrides the encoding settings made by the stub
> > although there is no encodingStyle -> call seems to be soap-encoded
> > instead of literal afterwards. Following the client-config.wsdd:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <deployment name="defaultClientConfig"
> > xmlns="http://xml.apache.org/axis/wsdd/"
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="java"
> > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > <service name="SalaryDeclaration">
> > <requestFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </requestFlow>
> > <responseFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </responseFlow>
> > </service>
> > </deployment>
> >
> > Is this a normal behaviour?
> >
> > Yves
>
>
********************
In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
start the server with 'ant server' ...
change the port in the TestClient in order to use TCPMon
start client with 'ant client'
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1465) Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Yves Langisch
Created: Wed, 21 Jul 2004 12:00 AM
Body:
After doing some debugging I saw that the problem seems to be the call of the setClientHandlers method. It forces the creation of a new SOAPService which is then associated with the MessageContext. The problem here is that we loose the whole TypeMapping we have done in the stub since the registering in stub happens in the default axisengine.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1465?page=comments#action_36802
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1465
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1465
Summary: Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Type: Bug
Status: Unassigned
Priority: Critical
Project: Axis
Components:
Basic Architecture
Serialization/Deserialization
Versions:
current (nightly)
beta-2
Assignee:
Reporter: Yves Langisch
Created: Tue, 20 Jul 2004 2:23 AM
Updated: Wed, 21 Jul 2004 12:00 AM
Environment: SuSE 9.1, JDK 1.4.2-b28
Description:
Description from my mail to the mailing-list:
****************
On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> Follow-up: I have the same behaviour when I set the handlers on the call
> (setClientHandlers). It's already enough to invoke the method with an
> empty chain to get the described behaviour.
>
> Tested with 1.2beta1 and 1.2beta2.
>
> What's wrong here?
>
> Yves
>
>
>
> On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > All,
> >
> > I have a document/literal web service which I invoke through the
> > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > client-config.wsdd to define some handlers, it seems that the
> > client-config.wsdd overrides the encoding settings made by the stub
> > although there is no encodingStyle -> call seems to be soap-encoded
> > instead of literal afterwards. Following the client-config.wsdd:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <deployment name="defaultClientConfig"
> > xmlns="http://xml.apache.org/axis/wsdd/"
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="java"
> > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > <service name="SalaryDeclaration">
> > <requestFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </requestFlow>
> > <responseFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </responseFlow>
> > </service>
> > </deployment>
> >
> > Is this a normal behaviour?
> >
> > Yves
>
>
********************
In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
start the server with 'ant server' ...
change the port in the TestClient in order to use TCPMon
start client with 'ant client'
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Assigned: (AXIS-1465) Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Posted by ax...@ws.apache.org.
Message:
The following issue has been re-assigned.
Assignee: Davanum Srinivas (mailto:davanum@gmail.com)
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1465
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1465
Summary: Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Type: Bug
Status: Open
Priority: Critical
Project: Axis
Components:
Basic Architecture
Serialization/Deserialization
Versions:
current (nightly)
beta-2
Assignee: Davanum Srinivas
Reporter: Yves Langisch
Created: Tue, 20 Jul 2004 2:23 AM
Updated: Wed, 21 Jul 2004 2:14 AM
Environment: SuSE 9.1, JDK 1.4.2-b28
Description:
Description from my mail to the mailing-list:
****************
On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> Follow-up: I have the same behaviour when I set the handlers on the call
> (setClientHandlers). It's already enough to invoke the method with an
> empty chain to get the described behaviour.
>
> Tested with 1.2beta1 and 1.2beta2.
>
> What's wrong here?
>
> Yves
>
>
>
> On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > All,
> >
> > I have a document/literal web service which I invoke through the
> > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > client-config.wsdd to define some handlers, it seems that the
> > client-config.wsdd overrides the encoding settings made by the stub
> > although there is no encodingStyle -> call seems to be soap-encoded
> > instead of literal afterwards. Following the client-config.wsdd:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <deployment name="defaultClientConfig"
> > xmlns="http://xml.apache.org/axis/wsdd/"
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="java"
> > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > <service name="SalaryDeclaration">
> > <requestFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </requestFlow>
> > <responseFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </responseFlow>
> > </service>
> > </deployment>
> >
> > Is this a normal behaviour?
> >
> > Yves
>
>
********************
In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
start the server with 'ant server' ...
change the port in the TestClient in order to use TCPMon
start client with 'ant client'
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1465) Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Yves Langisch
Created: Wed, 6 Oct 2004 8:50 AM
Body:
Jayachandra,
I just downloaded again my uploaded archive and could reproduce the issue without changing anything except changing the port in order to bring TcpMon between client and server. This is strange that it works okay in your env. Following the request I see in TcpMon:
POST /axis/services/SD HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.2beta2
Host: 127.0.0.1
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 736
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<SDRequest xsi:type="ns1:SDRequestType" xmlns="http://www.abc.ch/sdc" xmlns:ns1="http://www.abc.ch/sdc">
<UserAgent xsi:nil="true" xmlns=""/>
<LanguageCode xsi:type="ns1:LanguageCodeType" xmlns="">en</LanguageCode>
<RequestID xmlns="">0815</RequestID>
<SDs schemaVersion="150" xsi:type="ns2:SDsType" xmlns="" xmlns:ns2="http://www.abc.ch/sd">
<SD xsi:type="ns2:SDType">
<Company xsi:type="ns2:CompanyType">
<Name xsi:type="ns2:CompanyNameType">
<HR-RC-Name>testCompany</HR-RC-Name>
</Name>
</Company>
</SD>
</SDs>
</SDRequest>
</soapenv:Body></soapenv:Envelope>
And this is not a valid request (xmlns="" and so on...) Any ideas what could be the difference between our installation? JDK version?
Thanks
Yves
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1465?page=comments#action_53763
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1465
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1465
Summary: Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Type: Bug
Status: Open
Priority: Critical
Project: Axis
Components:
Basic Architecture
Serialization/Deserialization
Versions:
current (nightly)
beta-2
Assignee: Davanum Srinivas
Reporter: Yves Langisch
Created: Tue, 20 Jul 2004 2:23 AM
Updated: Wed, 6 Oct 2004 8:50 AM
Environment: SuSE 9.1, JDK 1.4.2-b28
Description:
Description from my mail to the mailing-list:
****************
On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> Follow-up: I have the same behaviour when I set the handlers on the call
> (setClientHandlers). It's already enough to invoke the method with an
> empty chain to get the described behaviour.
>
> Tested with 1.2beta1 and 1.2beta2.
>
> What's wrong here?
>
> Yves
>
>
>
> On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > All,
> >
> > I have a document/literal web service which I invoke through the
> > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > client-config.wsdd to define some handlers, it seems that the
> > client-config.wsdd overrides the encoding settings made by the stub
> > although there is no encodingStyle -> call seems to be soap-encoded
> > instead of literal afterwards. Following the client-config.wsdd:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <deployment name="defaultClientConfig"
> > xmlns="http://xml.apache.org/axis/wsdd/"
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="java"
> > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > <service name="SalaryDeclaration">
> > <requestFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </requestFlow>
> > <responseFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </responseFlow>
> > </service>
> > </deployment>
> >
> > Is this a normal behaviour?
> >
> > Yves
>
>
********************
In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
start the server with 'ant server' ...
change the port in the TestClient in order to use TCPMon
start client with 'ant client'
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1465) Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Jayachandra Sekhara Rao Sunkara
Created: Wed, 6 Oct 2004 10:30 PM
Body:
Hi Yves,
Okay let me share what I did.
On my end, I ran it on 1.2 RC1 (got from CVS 2 days ago). JDK version is j2sdk1.4.2_05
I just cut copy pasted the client-config given in your bug reporting post into a client-config.wsdd file and placed it in the classes directory. Classes directory is set in my classpath.
I modified the server-config.wsdd present in the root directory of your archive (i.e. tstCltHandlers) to add the lines
...
<handler name="TestHandler" type="java:ch.TestHandler" />
...
...
<service name="SD" ...>
<requestFlow>
<handler type="TestHandler" />
</requestFlow>
<requestFlow>
<handler type="TestHandler" />
</requestFlow>
...
...
I ran the 'start ant server' to start the SAS on port 9000
Then I started tcpmon on port 7010 redirecting to 9000, this port number is changed in TestClient also and the existing TestClient.class in classes/ch location is overridden with the new one.
Then I said 'start ant client'
In the tcpmon on the client side released soap request looks like
POST /axis/services/SD HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.2RC1
Host: 127.0.0.1:7010
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: ""
Content-Length: 534
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<SDRequest xmlns="http://www.abc.ch/sdc">
<UserAgent xsi:nil="true"/>
<LanguageCode>en</LanguageCode>
<RequestID>0815</RequestID>
<SDs schemaVersion="150">
<ns1:SD xmlns:ns1="http://www.abc.ch/sd">
<ns1:Company>
<ns1:Name>
<ns1:HR-RC-Name>testCompany</ns1:HR-RC-Name>
</ns1:Name>
</ns1:Company>
</ns1:SD>
</SDs>
</SDRequest>
</soapenv:Body></soapenv:Envelope>
Note that there are no xsi:type declarations anywhere.
But I don't see any response in tcpmon and also SimpleAxisServer session is getting killed with just one run of TestClient. Again this is something to do with TestHandler contents I guess and not of interest to the way client side processing is done by Axis.
So in summary after the above said modifications are done I am still seeing that SEND_TYPE_ATTR is understood to be Boolean.FALSE only and is not overwritten. Tell me if I missed any steps.
I think remeady to all drudgery is to get AXIS-RC1 and try :)
Thank you,
jayachandra
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1465?page=comments#action_53794
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1465
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1465
Summary: Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Type: Bug
Status: Open
Priority: Critical
Project: Axis
Components:
Basic Architecture
Serialization/Deserialization
Versions:
current (nightly)
beta-2
Assignee: Davanum Srinivas
Reporter: Yves Langisch
Created: Tue, 20 Jul 2004 2:23 AM
Updated: Wed, 6 Oct 2004 10:30 PM
Environment: SuSE 9.1, JDK 1.4.2-b28
Description:
Description from my mail to the mailing-list:
****************
On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> Follow-up: I have the same behaviour when I set the handlers on the call
> (setClientHandlers). It's already enough to invoke the method with an
> empty chain to get the described behaviour.
>
> Tested with 1.2beta1 and 1.2beta2.
>
> What's wrong here?
>
> Yves
>
>
>
> On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > All,
> >
> > I have a document/literal web service which I invoke through the
> > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > client-config.wsdd to define some handlers, it seems that the
> > client-config.wsdd overrides the encoding settings made by the stub
> > although there is no encodingStyle -> call seems to be soap-encoded
> > instead of literal afterwards. Following the client-config.wsdd:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <deployment name="defaultClientConfig"
> > xmlns="http://xml.apache.org/axis/wsdd/"
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="java"
> > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > <service name="SalaryDeclaration">
> > <requestFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </requestFlow>
> > <responseFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </responseFlow>
> > </service>
> > </deployment>
> >
> > Is this a normal behaviour?
> >
> > Yves
>
>
********************
In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
start the server with 'ant server' ...
change the port in the TestClient in order to use TCPMon
start client with 'ant client'
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1465) Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Posted by ax...@ws.apache.org.
The following comment has been added to this issue:
Author: Jayachandra Sekhara Rao Sunkara
Created: Wed, 6 Oct 2004 3:00 AM
Body:
Hi Yves!
This appeared interesting and I wanted to work on it. I've tried to reproduce the bug. I was able to get a HTTP 200 OK response when the TestClient is run with all the environment provided in your .tgz file AS IS (i.e. without bringing into picture TestHandler details). Then I modified my server-config.wsdd to add your TestHandler as a requestFlow and responseFlow handler for the SDService. Even after I do that in server-config.wsdd and rerun the application I still am seeing just the same old type of request response sequences on tcpmon (i.e. a 200 OK status when TestClient is run, and not any fault or error). Plz hint me if I missed some things, so that I can reproduce the exact erroneous behaviour on my side too. I solicit your help in patching up this bug at the earliest.
Awaiting your response,
Jayachandra
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1465?page=comments#action_53745
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1465
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1465
Summary: Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
Type: Bug
Status: Open
Priority: Critical
Project: Axis
Components:
Basic Architecture
Serialization/Deserialization
Versions:
current (nightly)
beta-2
Assignee: Davanum Srinivas
Reporter: Yves Langisch
Created: Tue, 20 Jul 2004 2:23 AM
Updated: Wed, 6 Oct 2004 3:00 AM
Environment: SuSE 9.1, JDK 1.4.2-b28
Description:
Description from my mail to the mailing-list:
****************
On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> Follow-up: I have the same behaviour when I set the handlers on the call
> (setClientHandlers). It's already enough to invoke the method with an
> empty chain to get the described behaviour.
>
> Tested with 1.2beta1 and 1.2beta2.
>
> What's wrong here?
>
> Yves
>
>
>
> On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > All,
> >
> > I have a document/literal web service which I invoke through the
> > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > client-config.wsdd to define some handlers, it seems that the
> > client-config.wsdd overrides the encoding settings made by the stub
> > although there is no encodingStyle -> call seems to be soap-encoded
> > instead of literal afterwards. Following the client-config.wsdd:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <deployment name="defaultClientConfig"
> > xmlns="http://xml.apache.org/axis/wsdd/"
> > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > <transport name="http"
> > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > <transport name="local"
> > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > <transport name="java"
> > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > <service name="SalaryDeclaration">
> > <requestFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </requestFlow>
> > <responseFlow>
> > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > </responseFlow>
> > </service>
> > </deployment>
> >
> > Is this a normal behaviour?
> >
> > Yves
>
>
********************
In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
start the server with 'ant server' ...
change the port in the TestClient in order to use TCPMon
start client with 'ant client'
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1465) Client-side handlers override settings
(encoding, send_type_attr, ...) on the call object
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/AXIS-1465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS-1465:
-----------------------------------
Assignee: (was: Davanum Srinivas)
> Client-side handlers override settings (encoding, send_type_attr, ...) on the call object
> -----------------------------------------------------------------------------------------
>
> Key: AXIS-1465
> URL: https://issues.apache.org/jira/browse/AXIS-1465
> Project: Axis
> Issue Type: Bug
> Components: Basic Architecture, Serialization/Deserialization
> Affects Versions: current (nightly), beta-2
> Environment: SuSE 9.1, JDK 1.4.2-b28
> Reporter: Yves Langisch
> Priority: Critical
> Attachments: clthandler.tgz
>
>
> Description from my mail to the mailing-list:
> ****************
> On Mon, 19 Jul 2004 14:00:20 +0200, Yves Langisch <li...@langisch.ch> wrote:
> > Follow-up: I have the same behaviour when I set the handlers on the call
> > (setClientHandlers). It's already enough to invoke the method with an
> > empty chain to get the described behaviour.
> >
> > Tested with 1.2beta1 and 1.2beta2.
> >
> > What's wrong here?
> >
> > Yves
> >
> >
> >
> > On Mon, 2004-07-19 at 11:31, Yves Langisch wrote:
> > > All,
> > >
> > > I have a document/literal web service which I invoke through the
> > > wsdl2java generated stub. So far everything is okay. Now, if I create a
> > > client-config.wsdd to define some handlers, it seems that the
> > > client-config.wsdd overrides the encoding settings made by the stub
> > > although there is no encodingStyle -> call seems to be soap-encoded
> > > instead of literal afterwards. Following the client-config.wsdd:
> > >
> > > <?xml version="1.0" encoding="UTF-8"?>
> > > <deployment name="defaultClientConfig"
> > > xmlns="http://xml.apache.org/axis/wsdd/"
> > > xmlns:java="http://xml.apache.org/axis/wsdd/providers/java">
> > > <transport name="http"
> > > pivot="java:org.apache.axis.transport.http.HTTPSender"/>
> > > <transport name="local"
> > > pivot="java:org.apache.axis.transport.local.LocalSender"/>
> > > <transport name="java"
> > > pivot="java:org.apache.axis.transport.java.JavaSender"/>
> > > <service name="SalaryDeclaration">
> > > <requestFlow>
> > > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > > </requestFlow>
> > > <responseFlow>
> > > <handler type="java:a.b.c.SOAPMonitorHandlerClient"/>
> > > </responseFlow>
> > > </service>
> > > </deployment>
> > >
> > > Is this a normal behaviour?
> > >
> > > Yves
> >
> >
> ********************
> In the meantime I also saw that other properties like SEND_TYPE_ATTR are not preserved since for each element there is xsi:type.
> I could locate where the switching of the encoding happens. It's in the MessageContext class in the setService method (-> setEncodingStyle(service...). Since I call setClientHandlers there is a new SOAPService generated which has no (or default encoded) encoding settings. Properties don't seem to preserved too.
> I'll attach a test project (with ant script) which shows the issue. I hope with these resources the issue is solved soon since I didn't find any workaround to get client-side handlers working and we really need them.
> start the server with 'ant server' ...
> change the port in the TestClient in order to use TCPMon
> start client with 'ant client'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org