You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Ruth Struck (JIRA)" <ji...@apache.org> on 2008/10/20 22:21:44 UTC

[jira] Created: (AXIS2C-1277) Must use empty header in request

Must use empty header in request
--------------------------------

                 Key: AXIS2C-1277
                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
             Project: Axis2-C
          Issue Type: Bug
            Reporter: Ruth Struck


Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?

The SOAP request:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
<SOAP-ENV:Body>
<GetVersion xmlns="urn:aewebservices71" />
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>



-- 
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Commented: (AXIS2C-1277) Must use empty header in request

Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641736#action_12641736 ] 

Damitha Kumarage commented on AXIS2C-1277:
------------------------------------------

I could reproduce this. Will fix asap

> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Ruth Struck
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Updated: (AXIS2C-1277) Must use empty header in request

Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

S.Uthaiyashankar updated AXIS2C-1277:
-------------------------------------

    Component/s: xml/soap

> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: xml/soap
>            Reporter: Ruth Struck
>             Fix For: 1.6.0
>
>         Attachments: get_version, screenshot-1.jpg, soap_header.c.diff, version_client.zip, version_service.zip
>
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AXIS2C-1277) Must use empty header in request

Posted by "Ruth Struck (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ruth Struck updated AXIS2C-1277:
--------------------------------

    Attachment: screenshot-1.jpg

I am still getting a failure when the 

<soapenv:Header/>

is not included in the envelope - the service works correctly if the tag is in the request.

> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Ruth Struck
>         Attachments: screenshot-1.jpg, soap_header.c.diff
>
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Updated: (AXIS2C-1277) Must use empty header in request

Posted by "Manjula Peiris (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manjula Peiris updated AXIS2C-1277:
-----------------------------------

    Fix Version/s: 1.6.0

> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Ruth Struck
>             Fix For: 1.6.0
>
>         Attachments: get_version, screenshot-1.jpg, soap_header.c.diff, version_client.zip, version_service.zip
>
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AXIS2C-1277) Must use empty header in request

Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damitha Kumarage updated AXIS2C-1277:
-------------------------------------

    Attachment: soap_header.c.diff

File attached has the desired solution. If there is no soap headers to be added then serialized envelope don't have a empty soap header. In the server side also it correctly handles when there is no soap header elemen present.
Can someone who is more familier with Axiom review this patch?

> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Ruth Struck
>         Attachments: soap_header.c.diff
>
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Commented: (AXIS2C-1277) Must use empty header in request

Posted by "Ruth Struck (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641979#action_12641979 ] 

Ruth Struck commented on AXIS2C-1277:
-------------------------------------

Thank you for the quick response. I will let you know if we have any
problems with this fix. 




> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Ruth Struck
>         Attachments: soap_header.c.diff
>
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Updated: (AXIS2C-1277) Must use empty header in request

Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damitha Kumarage updated AXIS2C-1277:
-------------------------------------

    Attachment: get_version
                version_client.zip
                version_service.zip

I could not reproduce the problem. When I run the attached version sample client and service it works fine. Attached also is the tcpmon messages. Make sure that your Axis2/C code have the patch applied.

> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>            Reporter: Ruth Struck
>         Attachments: get_version, screenshot-1.jpg, soap_header.c.diff, version_client.zip, version_service.zip
>
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


[jira] Resolved: (AXIS2C-1277) Must use empty header in request

Posted by "Manjula Peiris (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2C-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manjula Peiris resolved AXIS2C-1277.
------------------------------------

    Resolution: Fixed

I have tested the version sample and it does not send empty headers.

> Must use empty header in request
> --------------------------------
>
>                 Key: AXIS2C-1277
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-1277
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: xml/soap
>            Reporter: Ruth Struck
>             Fix For: 1.6.0
>
>         Attachments: get_version, screenshot-1.jpg, soap_header.c.diff, version_client.zip, version_service.zip
>
>
> Why must an empty </header> element be included in the SOAP request in order to use axis? I have two implementations of a web service, one is gsoap and the other is Axis2C - both have the same SOAP request - the gsoap implementation does not require the empty header element in the request, the Axis2C service does. How can I get around that requirement?
> The SOAP request:
> <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns1="http://localhost:80/axisae/aewebservices71.wsdl">
> <SOAP-ENV:Body>
> <GetVersion xmlns="urn:aewebservices71" />
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.