[ 
https://issues.apache.org/jira/browse/AXIS2-3948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620887#action_12620887
 ] 

srinivas koyya commented on AXIS2-3948:
---------------------------------------

Hi,

Same issue. My wsdl contains operation with input contains header + body, 
output contains header + body.
However, in the method signature no paramter to access header.

Is there any example found in Axis2 samples on how to handle this?

> WSDL2Java doesn't allow to add a custom header element through the Skeleton
> ---------------------------------------------------------------------------
>
>                 Key: AXIS2-3948
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3948
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.4, 1.3
>         Environment: OS: Microsoft Windows Server 2003/Mac OS X 10.5
> IDE: Eclipse 3.2/Eclipse 3.4 with plugin Axis2Codegen Wizard
> Tool: WSDL2java as command line or called by the Axis2Codegen Wizard
>            Reporter: Emidio Stani
>         Attachments: wsdlsoapheader.zip
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Hi all,
> I created a WSDL file WS-I compliant (Basic Profile 1.1) where I specify an 
> header. After that I generated stub and skeleton with the wsdl2java tool; 
> inside the stub I have the method to call the service which allows me to add 
> my custom header element but from the skeleton side the method allows only to 
> work on the object that will be included in the body and not on the header.
> It seems that the only way is to modify the MessageReceiverInOut java class  
> to add the header manually when it created a new soap message.

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to