[jira] Commented: (CXF-3402) http://util.java in WSDL
[
https://issues.apache.org/jira/browse/CXF-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007850#comment-13007850
]
Jara Cesnek commented on CXF-3402:
--
I have about 100 SEI. Annotate all methods in all services is error-prone and
un-justifiable.
What about compatibility flag on Aegis binding
new AegisBinding().setCompatibilty(PRE_2_2_6)
I we will once pushed to use newer version of CXF, we anyway patch AegisBinding
instead of rewriting all our SEI.
> http://util.java in WSDL
> -
>
> Key: CXF-3402
> URL: https://issues.apache.org/jira/browse/CXF-3402
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
>Affects Versions: 2.3.2
>Reporter: Jara Cesnek
>Assignee: Daniel Kulp
>Priority: Minor
> Fix For: 2.4
>
> Attachments: IStringSl-List.xml, IStringSl-array.xml
>
>
> For SEI:
> {code}
> @WebService
> public interface IStringSl {
> void storeStrings(@WebParam(name = "stringsToStore") List
> stringToStore);
> }
> @XmlType ( name = "DtoString")
> public class DTOtra_string {
>
> }
> {code}
> there is many http://util.java namespaces in WSDL.
> Maybe this is bug maybe not? I dont know.
> But I expect same wsdl as List<> is replaces with array.
> WSDL with array is more clean.
> *Fortunately XML on-the-wire is almost same in booth cases.*
> And our customers can consume booth without reimporting changed WSDL.
> Xml with array.
> {code}
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:sl="http://sl.tra.modules.daisy.marbes.cz/";
> xmlns:dto="http://dto.tra.modules.daisy.marbes.cz";>
>
>
>
>
>
>?
>true
>
>
>
>
>
> {code}
> Xml with List<>.
> {code}
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:sl="http://sl.tra.modules.daisy.marbes.cz/";
> xmlns:util="http://util.java";
> xmlns:dto="http://dto.tra.modules.daisy.marbes.cz";>
>
>
>
>
>
>?
>true
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CXF-3405) Error reading XMLStreamReader.
[
https://issues.apache.org/jira/browse/CXF-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007911#comment-13007911
]
Prasad Deshpande commented on CXF-3405:
---
I checked with wireshark, problem is message is not going out, so even if
logger prints outbound message, it actually never reaches server & so can't get
response from server. In the class HttpConduit$WrappedOutputStream.class at
line number 2226, int responseCode = connection.getResponseCode(); is returning
-1. Also wireshark confirmed same that there wasn't any packet transmitted over
network.
I've created a simple test case, you can simply run it with
cxf-2.3.4-snapshot.jar & reproduce problem. If you run
TestWSServerHandler.class standalone, it works, but not from applet. However,
if I run same test case with cxf-2.2.6.jar using applet, it works.
> Error reading XMLStreamReader.
> --
>
> Key: CXF-3405
> URL: https://issues.apache.org/jira/browse/CXF-3405
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.3.4
> Environment: jdk 1.6.0_22, windows_xp, cxf 2.3.4-snapshot
>Reporter: Prasad Deshpande
> Fix For: NeedMoreInfo
>
> Attachments: TestApplet.java, TestWSServerHandler.java,
> WSTestService.java, WSTestServiceImpl.java
>
>
> Hi,
> I was trying fix for CXF-3383 from 2.3.4-snapshot from within applet & I'm
> getting exception as:
> {code}
> WARNING: Interceptor for
> {http://wsapi.api.client.caseware.banctec.com/}WSAPIServiceService#{http://wsapi.api.client.caseware.banctec.com/}login
> has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:222)
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:759)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2337)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2195)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2039)
> at
> org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
> at
> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:188)
> at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:697)
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:520)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:317)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:269)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> at $Proxy42.login(Unknown Source)
> at
> com.banctec.client.commonviewer.ViewerWSServerHandler.login(ViewerWSServerHandler.java:107)
> at
> com.banctec.client.viewer.ViewerController.login(ViewerController.java:248)
> at
> com.banctec.client.viewer.EfpViewer.ensureLoggedIn(EfpViewer.java:561)
> at com.banctec.client.viewer.EfpViewer.startViewer(EfpViewer.java:329)
> at com.banctec.client.viewer.EfpViewer.start(EfpViewer.java:257)
> at sun.applet.AppletPanel.run(AppletPanel.java:464)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
> Message: Content is not allowed in prolog.
> at
> com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:594)
> at
> com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1235)
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:122)
> ... 25 more
> javax.xml.ws.soap.SOAPFaultException: Error reading XMLStreamReader.
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
> at $Proxy42.login(Unknown Source)
> at
> com.banctec.client.commonviewer.ViewerWSServerHandler.login(ViewerWSServerHandler.java:107)
> at
> com.banctec.client.viewer.ViewerC
[jira] Updated: (CXF-3405) Error reading XMLStreamReader.
[
https://issues.apache.org/jira/browse/CXF-3405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasad Deshpande updated CXF-3405:
--
Attachment: WSTestServiceImpl.java
WSTestService.java
TestWSServerHandler.java
TestApplet.java
> Error reading XMLStreamReader.
> --
>
> Key: CXF-3405
> URL: https://issues.apache.org/jira/browse/CXF-3405
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.3.4
> Environment: jdk 1.6.0_22, windows_xp, cxf 2.3.4-snapshot
>Reporter: Prasad Deshpande
> Fix For: NeedMoreInfo
>
> Attachments: TestApplet.java, TestWSServerHandler.java,
> WSTestService.java, WSTestServiceImpl.java
>
>
> Hi,
> I was trying fix for CXF-3383 from 2.3.4-snapshot from within applet & I'm
> getting exception as:
> {code}
> WARNING: Interceptor for
> {http://wsapi.api.client.caseware.banctec.com/}WSAPIServiceService#{http://wsapi.api.client.caseware.banctec.com/}login
> has thrown exception, unwinding now
> org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:222)
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:759)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2337)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2195)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2039)
> at
> org.apache.cxf.io.CacheAndWriteOutputStream.postClose(CacheAndWriteOutputStream.java:47)
> at
> org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:188)
> at
> org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:697)
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:520)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:317)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:269)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> at $Proxy42.login(Unknown Source)
> at
> com.banctec.client.commonviewer.ViewerWSServerHandler.login(ViewerWSServerHandler.java:107)
> at
> com.banctec.client.viewer.ViewerController.login(ViewerController.java:248)
> at
> com.banctec.client.viewer.EfpViewer.ensureLoggedIn(EfpViewer.java:561)
> at com.banctec.client.viewer.EfpViewer.startViewer(EfpViewer.java:329)
> at com.banctec.client.viewer.EfpViewer.start(EfpViewer.java:257)
> at sun.applet.AppletPanel.run(AppletPanel.java:464)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
> Message: Content is not allowed in prolog.
> at
> com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:594)
> at
> com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1235)
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:122)
> ... 25 more
> javax.xml.ws.soap.SOAPFaultException: Error reading XMLStreamReader.
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:146)
> at $Proxy42.login(Unknown Source)
> at
> com.banctec.client.commonviewer.ViewerWSServerHandler.login(ViewerWSServerHandler.java:107)
> at
> com.banctec.client.viewer.ViewerController.login(ViewerController.java:248)
> at
> com.banctec.client.viewer.EfpViewer.ensureLoggedIn(EfpViewer.java:561)
> at com.banctec.client.viewer.EfpViewer.startViewer(EfpViewer.java:329)
> at com.banctec.client.viewer.EfpViewer.start(EfpViewer.java:257)
> at sun.applet.AppletPanel.run(AppletPanel.java:464)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]
> Message: Content is not allowed in prolog.
> at
> com.sun.org.apache.xerces.internal.impl.XMLStreamR
[jira] Commented: (CXF-3402) http://util.java in WSDL
[
https://issues.apache.org/jira/browse/CXF-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13007991#comment-13007991
]
Benson Margulies commented on CXF-3402:
---
Dan,
It's never been correct in Aegis to end up with http://util.java, I think. In
the past, I've pushed cases like that to use the TNS for the type. Mind you,
the whole @XmlType business is a late addition (relatively) to Aegis, and I've
never thought about it hard.
Just to make sure I'm following, your view is that changing this in 2.3.x is
incompatible with people who are currently living with the http://util.java
namespace and would be shocked for it to change on a point-release?
> http://util.java in WSDL
> -
>
> Key: CXF-3402
> URL: https://issues.apache.org/jira/browse/CXF-3402
> Project: CXF
> Issue Type: Bug
> Components: Aegis Databinding
>Affects Versions: 2.3.2
>Reporter: Jara Cesnek
>Assignee: Daniel Kulp
>Priority: Minor
> Fix For: 2.4
>
> Attachments: IStringSl-List.xml, IStringSl-array.xml
>
>
> For SEI:
> {code}
> @WebService
> public interface IStringSl {
> void storeStrings(@WebParam(name = "stringsToStore") List
> stringToStore);
> }
> @XmlType ( name = "DtoString")
> public class DTOtra_string {
>
> }
> {code}
> there is many http://util.java namespaces in WSDL.
> Maybe this is bug maybe not? I dont know.
> But I expect same wsdl as List<> is replaces with array.
> WSDL with array is more clean.
> *Fortunately XML on-the-wire is almost same in booth cases.*
> And our customers can consume booth without reimporting changed WSDL.
> Xml with array.
> {code}
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:sl="http://sl.tra.modules.daisy.marbes.cz/";
> xmlns:dto="http://dto.tra.modules.daisy.marbes.cz";>
>
>
>
>
>
>?
>true
>
>
>
>
>
> {code}
> Xml with List<>.
> {code}
> http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:sl="http://sl.tra.modules.daisy.marbes.cz/";
> xmlns:util="http://util.java";
> xmlns:dto="http://dto.tra.modules.daisy.marbes.cz";>
>
>
>
>
>
>?
>true
>
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CXF-3184) SOAPBindingUtil.getProxy can't load right class in OSGi
[
https://issues.apache.org/jira/browse/CXF-3184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13008310#comment-13008310
]
Willem Jiang commented on CXF-3184:
---
This issue is not a critical issue, as I said in the JIRA, there are two ways
to workaround it.
BTW, Apache CXF doesn't maintain CXF 2.2.x branch any more, if you still want
to use CXF 2.2.x, you may consider to the commercial product supports from
FuseSource.
> SOAPBindingUtil.getProxy can't load right class in OSGi
> ---
>
> Key: CXF-3184
> URL: https://issues.apache.org/jira/browse/CXF-3184
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.2.12, 2.3.1
>Reporter: Willem Jiang
>Assignee: Willem Jiang
> Fix For: 2.3.2, 2.2.13, 2.4
>
>
> As a fix for CXF-3143 SOAPBindingUtil.getProxy uses now thread context
> classloader.
> This causes the following problem:
> {code}
> Caused by: java.lang.IllegalArgumentException: interface
> org.apache.cxf.tools.common.extensions.soap.SoapBinding is not visible from
> class loader
> at java.lang.reflect.Proxy.getProxyClass(Proxy.java:353)
> at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
> at
> org.apache.cxf.tools.util.SOAPBindingUtil.getProxy(SOAPBindingUtil.java:87)
> at
> org.apache.cxf.tools.util.SOAPBindingUtil.getSoapBinding(SOAPBindingUtil.java:274)
> at
> org.apache.cxf.tools.util.SOAPBindingUtil.createSoapBinding(SOAPBindingUtil.java:426)
> at
> org.apache.cxf.binding.soap.SoapBindingFactory.createSoapBinding(SoapBindingFactory.java:190)
> at
> org.apache.cxf.binding.soap.SoapBindingFactory.createBindingInfo(SoapBindingFactory.java:175)
> at
> org.apache.cxf.binding.AbstractBindingFactory.createBindingInfo(AbstractBindingFactory.java:80)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createBindingInfo(AbstractWSDLBasedEndpointFactory.java:360)
> at
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.createBindingInfo(JaxWsServerFactoryBean.java:160)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpointInfo(AbstractWSDLBasedEndpointFactory.java:257)
> at
> org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:145)
> at
> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:105)
> at
> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:177)
> at
> com.sabre.gateway.g2g.G2GInConnector.(G2GInConnector.java:105)
> at
> com.sabre.gateway.g2g.G2GInConnector.(G2GInConnector.java:76)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at
> org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:126)
> {code}
> To avoid it we would to set context classloader to CXF bundle one before
> calling CXF code that causes this exception or import the cxf packages in our
> bundle and set context classloader to our bundle's one.
> Both solutions look like workarounds.
> We need to make the SOAPBindingUtil.getProxy more smart to load the class.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
