[jira] Updated: (CXF-2895) CXF is unable to correctly generate embedded WSDL for schemas without XML namespaces.

[ https://issues.apache.org/jira/browse/CXF-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2895: -- Attachment: noNamespaceBug.tar > CXF is unable to correctly generate embedded WSDL for schemas without XM

[jira] Created: (CXF-2895) CXF is unable to correctly generate embedded WSDL for schemas without XML namespaces.

CXF is unable to correctly generate embedded WSDL for schemas without XML namespaces. -- Key: CXF-2895 URL: https://issues.apache.org/jira/browse/CXF-2895 Project: C

[jira] Created: (CXF-2628) StaxUtils.writeStartElement(XMLStreamReader reader, XMLStreamWriter writer) does not write namespace for header elements that have a namespace URI and an empty prefix

StaxUtils.writeStartElement(XMLStreamReader reader, XMLStreamWriter writer) does not write namespace for header elements that have a namespace URI and an empty prefix --

[jira] Updated: (CXF-2628) StaxUtils.writeStartElement(XMLStreamReader reader, XMLStreamWriter writer) does not write namespace for header elements that have a namespace URI and an empty prefix

[ https://issues.apache.org/jira/browse/CXF-2628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2628: -- Attachment: StaxUtils.patch > StaxUtils.writeStartElement(XMLStreamReader reader, XMLStreamWriter writer)

[jira] Created: (CXF-2552) CXF should use Spring's BeanFactory.isSingleton(name) instead of BeanDefinition.isSingleton() because any such checks break when using bean definition inheritance or bean de

CXF should use Spring's BeanFactory.isSingleton(name) instead of BeanDefinition.isSingleton() because any such checks break when using bean definition inheritance or bean definition post-processing ---

[jira] Created: (CXF-2387) CXF does not call ConduitSelector.complete() on the server side.

CXF does not call ConduitSelector.complete() on the server side. Key: CXF-2387 URL: https://issues.apache.org/jira/browse/CXF-2387 Project: CXF Issue Type: Improvement

[jira] Updated: (CXF-2375) CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes.

[ https://issues.apache.org/jira/browse/CXF-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2375: -- Attachment: JaxWsServiceConfiguration.java.patch > CXF treats synthetic methods as web methods. In the st

[jira] Created: (CXF-2375) CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes.

CXF treats synthetic methods as web methods. In the strict sense, this is not against the JAX-WS spec, but it causes issues with AspectJ instrumented classes. ---

[jira] Updated: (CXF-2152) Certain Spring AOP proxies cannot be used any more as service bean since CXF 2.1.4 because the real (non-proxy) target class is not found correctly by SpringAopClassHelper

[ https://issues.apache.org/jira/browse/CXF-2152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2152: -- Attachment: SpringAopClassHelper.patch > Certain Spring AOP proxies cannot be used any more as service be

[jira] Created: (CXF-2152) Certain Spring AOP proxies cannot be used any more as service bean since CXF 2.1.4 because the real (non-proxy) target class is not found correctly by SpringAopClassHelper

Certain Spring AOP proxies cannot be used any more as service bean since CXF 2.1.4 because the real (non-proxy) target class is not found correctly by SpringAopClassHelper -

[jira] Updated: (CXF-2097) If wrapped style is used and multiple message parts are generated (because, for example, a soap header parameter is declared), the generated wsdl does not interop with RI or

[ https://issues.apache.org/jira/browse/CXF-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2097: -- Attachment: ReflectionServiceFactoryBean.patch Fixed the patch as you suggested, only name the out messag

[jira] Updated: (CXF-2104) Caller application hangs in case it uses the polling (Response) method with JAX-WS async mapping and an http error occurs during sending. In case of callback style (AsyncHan

[ https://issues.apache.org/jira/browse/CXF-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2104: -- Description: This happens if, for example, an http 404 occurs at sending. If the caller app wants to ret

[jira] Updated: (CXF-2104) Caller application hangs in case it uses the polling (Response) method with JAX-WS async mapping and an http error occurs during sending. In case of callback style (AsyncHan

[ https://issues.apache.org/jira/browse/CXF-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2104: -- Attachment: ClientOutFaultObserver.patch JaxWsClientProxy.patch > Caller application hang

[jira] Created: (CXF-2104) Caller application hangs in case it uses the polling (Response) method with JAX-WS async mapping and an http error occurs during sending. In case of callback style (AsyncHan

Caller application hangs in case it uses the polling (Response) method with JAX-WS async mapping and an http error occurs during sending. In case of callback style (AsyncHandler), the client application has no way of getting the exception.

[jira] Updated: (CXF-2097) If wrapped style is used and multiple message parts are generated (because, for example, a soap header parameter is declared), the generated wsdl does not interop with RI or

[ https://issues.apache.org/jira/browse/CXF-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-2097: -- Attachment: ReflectionServiceFactoryBean.patch > If wrapped style is used and multiple message parts are

[jira] Created: (CXF-2097) If wrapped style is used and multiple message parts are generated (because, for example, a soap header parameter is declared), the generated wsdl does not interop with RI or

If wrapped style is used and multiple message parts are generated (because, for example, a soap header parameter is declared), the generated wsdl does not interop with RI or CXF client. ---

[jira] Updated: (CXF-1850) org.apache.cxf.endpoint.ServerImpl does not shut down destination in stop() when MultipleEndpointObserver is used.

[ https://issues.apache.org/jira/browse/CXF-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyorgy Orban updated CXF-1850: -- Attachment: ServerImpl.patch > org.apache.cxf.endpoint.ServerImpl does not shut down destination in stop(

[jira] Created: (CXF-1850) org.apache.cxf.endpoint.ServerImpl does not shut down destination in stop() when MultipleEndpointObserver is used.

org.apache.cxf.endpoint.ServerImpl does not shut down destination in stop() when MultipleEndpointObserver is used. -- Key: CXF-1850 URL: https://issues

[jira] Created: (CXF-1777) JAXBDataBinding hard references internal classes from the JAXB Sun RI which are not available in Java 6 any more

JAXBDataBinding hard references internal classes from the JAXB Sun RI which are not available in Java 6 any more Key: CXF-1777 URL: https://issues.apa