[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-tabpanelfocusedCommentId=13280856#comment-13280856 ] Ulhas Bhole commented on CXF-4329: -- Looks like there are other issues as well. I tried

[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-tabpanelfocusedCommentId=13280857#comment-13280857 ] Ulhas Bhole commented on CXF-4329: -- I think I commented too quickly. I forgot to copy over

[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-tabpanelfocusedCommentId=13277845#comment-13277845 ] Ulhas Bhole commented on CXF-4289: -- I will take a look into it and apply patch soon.

[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-tabpanelfocusedCommentId=13277865#comment-13277865 ] Ulhas Bhole commented on CXF-4228: -- Can you elaborate more on RandomValueProvider? You mean

[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-tabpanelfocusedCommentId=13277868#comment-13277868 ] Ulhas Bhole commented on CXF-4237: -- Hi Glen, It's a good idea but will it not cause more

[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-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-tabpanelfocusedCommentId=13001766#comment-13001766 ] Ulhas Bhole commented on CXF-3374: -- Merged fix to 2.3.x and trunk. 2.3.x-fixes :

[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

[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-tabpanelfocusedCommentId=12993572#comment-12993572 ] Ulhas Bhole commented on CXF-3329: -- Can you attach a sample idl file? I wouldn't mind

[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] 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] 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] 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-tabpanelfocusedCommentId=12632192#action_12632192 ] Ulhas Bhole commented on CXF-1805: -- Hi Seumas, The problem is appearing due to copying of

[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

[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] 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-tabpanelfocusedCommentId=12616410#action_12616410 ] Ulhas Bhole commented on CXF-1701: -- Sending. Sending

[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-tabpanelfocusedCommentId=12616411#action_12616411 ] Ulhas Bhole commented on CXF-1704: -- Sending. Sending

[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

[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] 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

[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-tabpanelfocusedCommentId=12608509#action_12608509 ] Ulhas Bhole commented on CXF-1652: -- Further analysis suggest that the jettyHTTPDestination's