this error is caused by your jdk setup and you are hitting some
incompatibility issue.
switching from 2.7.x to 3.1.x is a bigger move (as 3.1.x requires jdk7
and also needs newer versions of other libraries compared to 2.7.x)
so, it might be easier for you to upgrade to 3.0.x.
but i believe the old 2.7.x should also  be able tohandle the soap headers.


2015-12-02 14:47 GMT+01:00 Mercader, Felix <felix.merca...@firstdata.com>:
> Hi again Aki
>
> I tried to use the last CXF version. For that I removed the one I was using 
> (2.7.12) and I added this one: 3.1.4
>
> I clean and build from scratch. Everything fine at building time.
>
> Then I deployed the Web Service in WebLogic and I got this error/Exception:
>
> java.lang.VerifyError: JVMCFRE004 unknown bytecode; 
> class=server/com/omnipay/webservice/webService/jaxws_asm/GetMerchantDetails, 
> method=setInstitutionNumber(Ljava/lang/String;)V, pc=1
>
> I put back version 2.7.12 and I can deploy successfully in WebLogic again. I 
> put again 3.1.4 just to be sure I did nothing wrong and same error !!
>
> Any idea ?
>
> Thanks
> flx
>
>
> -----Original Message-----
> From: Aki Yoshida [mailto:elak...@gmail.com]
> Sent: 02 December 2015 12:26
> To: users@cxf.apache.org
> Cc: Mercader, Felix
> Subject: Re: CXF incorrect WSDL automatically generated ? Please help !
>
> which cxf version are you using?
> it could be an old bug.
>
> Questions should go to users@cxf, so I have moved this thread to there..
>
>
> 2015-12-02 13:07 GMT+01:00 Felix.1973 <felix.merca...@omnipaygroup.com>:
>> Hi there. I am fighting the last two days with the same problem and I
>> don't know how to fix this. Even not sure if it is an error or not.
>>
>> I have a CXF Web Service with something I consider very strange and I
>> would like to fix. This is one of the calls that the Web Service deals with:
>>
>>     @WebResult (name="merchantHierarchyParentResponse")
>> MerchantHierarchyParentResponseDTO
>>     getParent(
>>             @WebParam(name="institutionNumber")
>> @XmlElement(required=true) String institutionNumber,
>>             @WebParam(name="clientNumber") String clientNumber,
>>             @WebParam(name="ourReference") String ourReference,
>>             @WebParam(name="accessMerch") String accessMerch,
>>             @WebParam(header=true, name="callerId") String callerId,
>>             @WebParam(header=true, name="timestamp") String timestamp,
>>             @WebParam(header=true, name="signature") String signature
>>     );
>>
>> As you can see, it receives 4 normal parameters plus 3 extra
>> parameters in the header (callerId, timestamp and signature).
>>
>> It compiles successfully. Then I deploy it also successfully in a
>> WebLogic server.
>>
>> Finally, I use SoapUI to test it. I provide SoapUI with the URL that
>> WebLogic is providing me with the WSDL. This is, I am not doing any
>> change in the automatic generated WSDL. This is what I am getting for
>> this getParent in SoupUI:
>>
>> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>> xmlns:web="http://webService.webservice.omnipay.com.server/";>
>>    <soapenv:Header>
>> *      <web:signature>?</web:signature>
>>       <web:timestamp>?</web:timestamp>
>>       <web:callerId>?</web:callerId>*
>>    </soapenv:Header>
>>    <soapenv:Body>
>>       <web:getParent>
>>          <institutionNumber>?</institutionNumber>
>>
>>          <clientNumber>?</clientNumber>
>>
>>          <ourReference>?</ourReference>
>>
>>          <accessMerch>?</accessMerch>
>>       </web:getParent>
>> /*      <web:callerId>?</web:callerId>
>>       <web:timestamp>?</web:timestamp>
>>       <web:signature>?</web:signature>*/
>>    </soapenv:Body>
>> </soapenv:Envelope>
>>
>> My question is very clear. I see the 3 parameters in the header
>> section (callerId, timestamp and signature) but why these 3 parameters
>> are *AGAIN* at the end in the body part ??? I don't want them in the
>> body part, I want them only in the header.
>>
>> Any idea why this is happening ? Is that normal ? is it a bug ? Thank
>> you for your help !
>>
>> thanks
>> Felix Mercader
>>
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://cxf.547215.n5.nabble.com/CXF-incorrect-WSDL-automatically-gener
>> ated-Please-help-tp5763489.html Sent from the cxf-dev mailing list
>> archive at Nabble.com.
>
> The information in this message may be proprietary and/or confidential, and 
> protected from disclosure. If the reader of this message is not the intended 
> recipient, or an employee or agent responsible for delivering this message to 
> the intended recipient, you are hereby notified that any dissemination, 
> distribution or copying of this communication is strictly prohibited. If you 
> have received this communication in error, please notify First Data 
> immediately by replying to this message and deleting it from your computer.

Reply via email to