[jira] [Commented] (CXF-5124) Combination of @WebFault and @XmlType annotations leads to invalid XSD (WSDL)

[ https://issues.apache.org/jira/browse/CXF-5124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830758#comment-13830758 ] Ulhas Bhole commented on CXF-5124: -- Can you provide a small testcase to reproduce this issu

[jira] [Commented] (CXF-5125) Inconsistent namespace/element name qualification in SoapBody in normal vs. fault return message.

[ https://issues.apache.org/jira/browse/CXF-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13830757#comment-13830757 ] Ulhas Bhole commented on CXF-5125: -- Can you attach small testcase to reproduce this issue?

[jira] [Commented] (CXF-4329) Service using simple frontend with JAXB binding causes a ClassNotFoundException when started in Karaf

[ https://issues.apache.org/jira/browse/CXF-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280857#comment-13280857 ] Ulhas Bhole commented on CXF-4329: -- I think I commented too quickly. I forgot to copy over

[jira] [Commented] (CXF-4329) Service using simple frontend with JAXB binding causes a ClassNotFoundException when started in Karaf

[ https://issues.apache.org/jira/browse/CXF-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280856#comment-13280856 ] Ulhas Bhole commented on CXF-4329: -- Looks like there are other issues as well. I tried wit

[jira] [Commented] (CXF-4237) Remove true/false flags from purely binary WSDL2Java options

[ https://issues.apache.org/jira/browse/CXF-4237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277868#comment-13277868 ] Ulhas Bhole commented on CXF-4237: -- Hi Glen, It's a good idea but will it not cause more c

[jira] [Commented] (CXF-4228) DefaultValueProvider and WSDL Schema element default

[ https://issues.apache.org/jira/browse/CXF-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277865#comment-13277865 ] Ulhas Bhole commented on CXF-4228: -- Can you elaborate more on RandomValueProvider? You mean

[jira] [Assigned] (CXF-4289) Coping Request SOAP Headers to Fault response

[ https://issues.apache.org/jira/browse/CXF-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole reassigned CXF-4289: Assignee: Ulhas Bhole > Coping Request SOAP Headers to Fault response > -

[jira] [Commented] (CXF-4289) Coping Request SOAP Headers to Fault response

[ https://issues.apache.org/jira/browse/CXF-4289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13277845#comment-13277845 ] Ulhas Bhole commented on CXF-4289: -- I will take a look into it and apply patch soon. Rega

[jira] Resolved: (CXF-3374) CXF Service Builder fails if the binding is imported from different file and has different target namespace than one imported into.

[ https://issues.apache.org/jira/browse/CXF-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole resolved CXF-3374. -- Resolution: Fixed Fix Version/s: 2.3.4 2.4 > CXF Service Builder fails if the b

[jira] Commented: (CXF-3374) CXF Service Builder fails if the binding is imported from different file and has different target namespace than one imported into.

[ https://issues.apache.org/jira/browse/CXF-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001766#comment-13001766 ] Ulhas Bhole commented on CXF-3374: -- Merged fix to 2.3.x and trunk. 2.3.x-fixes : http://sv

[jira] Created: (CXF-3374) CXF Service Builder fails if the binding is imported from different file and has different target namespace than one imported into.

CXF Service Builder fails if the binding is imported from different file and has different target namespace than one imported into. --- Key: CXF-3374

[jira] Commented: (CXF-3319) idl2wsdl defines XSD types multiple times in wsdl.

[ https://issues.apache.org/jira/browse/CXF-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12997238#comment-12997238 ] Ulhas Bhole commented on CXF-3319: -- Fix rev.: 2.3.x-fixes: http://svn.apache.org/viewvc?rev

[jira] Resolved: (CXF-3319) idl2wsdl defines XSD types multiple times in wsdl.

[ https://issues.apache.org/jira/browse/CXF-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole resolved CXF-3319. -- Resolution: Fixed Fix Version/s: 2.2.13 > idl2wsdl defines XSD types multiple times in wsdl. > --

[jira] Commented: (CXF-3329) idl2wsdl: attributes of structs with the same name as a type do not show up in XSD

[ https://issues.apache.org/jira/browse/CXF-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994414#comment-12994414 ] Ulhas Bhole commented on CXF-3329: -- I had a initial look at the code and some debugging on

[jira] Commented: (CXF-3329) idl2wsdl: attributes of structs with the same name as a type do not show up in XSD

[ https://issues.apache.org/jira/browse/CXF-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993572#comment-12993572 ] Ulhas Bhole commented on CXF-3329: -- Can you attach a sample idl file? I wouldn't mind havin

[jira] Updated: (CXF-3319) idl2wsdl defines XSD types multiple times in wsdl.

[ https://issues.apache.org/jira/browse/CXF-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole updated CXF-3319: - Attachment: cxf-3319-trunk.patch cxf-3319-2.3.x.patch Attached are the patch files for the

[jira] Updated: (CXF-3319) idl2wsdl defines XSD types multiple times in wsdl.

[ https://issues.apache.org/jira/browse/CXF-3319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole updated CXF-3319: - Attachment: duplicateAttribute.idl > idl2wsdl defines XSD types multiple times in wsdl. >

[jira] Created: (CXF-3319) idl2wsdl defines XSD types multiple times in wsdl.

idl2wsdl defines XSD types multiple times in wsdl. --- Key: CXF-3319 URL: https://issues.apache.org/jira/browse/CXF-3319 Project: CXF Issue Type: Bug Components: Tooling Affects

[jira] Resolved: (CXF-1805) Use of Content-Type in JMS Header not in line with JMS specification

[ https://issues.apache.org/jira/browse/CXF-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole resolved CXF-1805. -- Resolution: Fixed Fix Version/s: 2.2 2.1.3 2.0.9 Fixed the p

[jira] Commented: (CXF-1805) Use of Content-Type in JMS Header not in line with JMS specification

[ https://issues.apache.org/jira/browse/CXF-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12632192#action_12632192 ] Ulhas Bhole commented on CXF-1805: -- Hi Seumas, The problem is appearing due to copying of P

[jira] Assigned: (CXF-1805) Use of Content-Type in JMS Header not in line with JMS specification

[ https://issues.apache.org/jira/browse/CXF-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole reassigned CXF-1805: Assignee: Ulhas Bhole > Use of Content-Type in JMS Header not in line with JMS specification > --

[jira] Resolved: (CXF-1742) JMS Conduit Pooled Session Recycling

[ https://issues.apache.org/jira/browse/CXF-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole resolved CXF-1742. -- Resolution: Fixed Fix Version/s: 2.0.9 2.1.2 Fixed now and will be available in

[jira] Assigned: (CXF-1742) JMS Conduit Pooled Session Recycling

[ https://issues.apache.org/jira/browse/CXF-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole reassigned CXF-1742: Assignee: Ulhas Bhole > JMS Conduit Pooled Session Recycling > >

[jira] Resolved: (CXF-1704) Service w/JMS transport should support non-jndi destinationName and destinationStyle

[ https://issues.apache.org/jira/browse/CXF-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole resolved CXF-1704. -- Resolution: Fixed > Service w/JMS transport should support non-jndi destinationName and > destinationSty

[jira] Commented: (CXF-1704) Service w/JMS transport should support non-jndi destinationName and destinationStyle

[ https://issues.apache.org/jira/browse/CXF-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616411#action_12616411 ] Ulhas Bhole commented on CXF-1704: -- Sending. Sending rt/transports/jms/src/m

[jira] Resolved: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

[ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole resolved CXF-1701. -- Resolution: Fixed > JMS Transport Configuration in a WSDL file is not parsed > --

[jira] Commented: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

[ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616410#action_12616410 ] Ulhas Bhole commented on CXF-1701: -- Sending. Sending rt/transports/jms/src/m

[jira] Assigned: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

[ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole reassigned CXF-1701: Assignee: Ulhas Bhole > JMS Transport Configuration in a WSDL file is not parsed > --

[jira] Assigned: (CXF-1704) Service w/JMS transport should support non-jndi destinationName and destinationStyle

[ https://issues.apache.org/jira/browse/CXF-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole reassigned CXF-1704: Assignee: Ulhas Bhole > Service w/JMS transport should support non-jndi destinationName and > destin

[jira] Updated: (CXF-1701) JMS Transport Configuration in a WSDL file is not parsed

[ https://issues.apache.org/jira/browse/CXF-1701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole updated CXF-1701: - Remaining Estimate: 0h Original Estimate: 0h This behaviour is intentional. Client, Server and Session

[jira] Resolved: (CXF-1676) oneway request followed by two-way request fails while using JMS Transport.

[ https://issues.apache.org/jira/browse/CXF-1676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulhas Bhole resolved CXF-1676. -- Resolution: Fixed Issue is fixed now. > oneway request followed by two-way request fails while using JMS

[jira] Created: (CXF-1676) oneway request followed by two-way request fails while using JMS Transport.

oneway request followed by two-way request fails while using JMS Transport. Key: CXF-1676 URL: https://issues.apache.org/jira/browse/CXF-1676 Project: CXF Issue Ty

[jira] Commented: (CXF-1652) CXF Decoupled Endpoints are not getting cleaned up properly even after bus.Shutdown() in org.apache.cxf.systest.ws.rm.SequenceTest.

[ https://issues.apache.org/jira/browse/CXF-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608509#action_12608509 ] Ulhas Bhole commented on CXF-1652: -- Further analysis suggest that the jettyHTTPDestination's

[jira] Created: (CXF-1652) CXF Decoupled Endpoints are not getting cleaned up properly even after bus.Shutdown() in org.apache.cxf.systest.ws.rm.SequenceTest.

CXF Decoupled Endpoints are not getting cleaned up properly even after bus.Shutdown() in org.apache.cxf.systest.ws.rm.SequenceTest. --- Key: CXF-1652