[jira] Reopened: (CXF-1779) exclude non-serializable property to JBI NormalizedMessage
[ https://issues.apache.org/jira/browse/CXF-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reopened CXF-1779: --- exclude non-serializable property to JBI NormalizedMessage -- Key: CXF-1779 URL: https://issues.apache.org/jira/browse/CXF-1779 Project: CXF Issue Type: Bug Affects Versions: 2.0.8, 2.1.2 Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.0.9, 2.1.3, 2.2 this will fix https://issues.apache.org/activemq/browse/SM-1537 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1779) exclude non-serializable property to JBI NormalizedMessage
[ https://issues.apache.org/jira/browse/CXF-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang resolved CXF-1779. --- Resolution: Fixed exclude non-serializable property to JBI NormalizedMessage -- Key: CXF-1779 URL: https://issues.apache.org/jira/browse/CXF-1779 Project: CXF Issue Type: Bug Affects Versions: 2.0.8, 2.1.2 Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.0.9, 2.1.3, 2.2 this will fix https://issues.apache.org/activemq/browse/SM-1537 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (CXF-1780) float's and double's negative infinity is incorrectly marshalled/unmarshalled as positive infinity
float's and double's negative infinity is incorrectly marshalled/unmarshalled as positive infinity -- Key: CXF-1780 URL: https://issues.apache.org/jira/browse/CXF-1780 Project: CXF Issue Type: Bug Components: CORBA Binding Affects Versions: 2.1.2 Reporter: Matteo Vescovi Fix For: 2.1.3 Floats with value Float.NEGATIVE_INFINITY or doubles with value Double.NEGATIVE_INFINITY are incorrectly marshalled/unmarshalled as positive infinity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1662) wsdl2java should check if using -p is safe to use
[ https://issues.apache.org/jira/browse/CXF-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean O'Callaghan resolved CXF-1662. --- Resolution: Fixed http://svn.apache.org/viewvc?rev=691237view=rev wsdl2java should check if using -p is safe to use - Key: CXF-1662 URL: https://issues.apache.org/jira/browse/CXF-1662 Project: CXF Issue Type: Improvement Components: Tooling Reporter: Daniel Kulp Assignee: Sean O'Callaghan If a wsdl has schemas in multiple namespaces and you use -p package to map everything to one package, the result won't work with jaxb. We need to detect that and output a bunch of warnings about it. Each schema needs it's own package. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (CXF-1340) wsdl2java overwrites objectFactory methods if multiple service classes are in the same package, causes value type inheritance problems
[ https://issues.apache.org/jira/browse/CXF-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean O'Callaghan reassigned CXF-1340: - Assignee: Sean O'Callaghan wsdl2java overwrites objectFactory methods if multiple service classes are in the same package, causes value type inheritance problems -- Key: CXF-1340 URL: https://issues.apache.org/jira/browse/CXF-1340 Project: CXF Issue Type: Bug Components: Tooling Affects Versions: 2.0.3, 2.1 Environment: Windows XP, eclipse Reporter: Incognito Assignee: Sean O'Callaghan Attachments: cxf-issue-objectFactory.zip If you have two wsdl-based services, who's wsdl2java output is in the same package, the outputted objectFactory retains only the most recent service's methods. For example: Given two wsdl files, CarService.wsdl and UserService.wsdl; if one executes the wsdl2java binary with both services; with CarService first and UserService second, and with both service classes being output in package org.example.api, then only one objectFactory.java class will be created. First, objectFactory will be created with the objects for CarService.wsdl, and then it will be overwritten with UserService.wsdl's objects. It just so happens that in this scenario, if the former service contains an object that is abstract, that is, that it contains types that inherit via wsdl's extension keyword, AND methods for creating instances of CarService.wsdl's outputted java are NOT present in objectFactory.java, then CXF does not include type information in the SOAP messages. For example: given an alternate CarService.wsdl with the following types: complexType name=Car abstract=true ... /complexType complexType name=Jeep extension base=Car ... /extension /complexType If CarService.wsdl also had a method called getCarById, and wsdl2java output 2 java classes: getCarById.java and getCarByIdResponse.java, AND wsdl2java on UserService.wsdl was executed AFTER it was executed on CarService (resulting in an objectFactory without create methods for getCar*), then CXF will send SOAP messages like the following soap getCarByIdResponse !-- type information here would mistakenly be missing -- ... /getCarByIdResposne /soap The ultimate result is that if a project has more than 1 service being output in the same package AND if more than 1 type in those two services use type extension, then CXF will have problems marshalling those classes because it will end up leaving out the type information for all classes not included in the ObjectFactory. One alternative would be to have the wsdl2java classes be output to multiple packages. If the different services shared types, this would result in duplicated code in each service. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1780) float's and double's negative infinity is incorrectly marshalled/unmarshalled as positive infinity
[ https://issues.apache.org/jira/browse/CXF-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1780. -- Resolution: Fixed Assignee: Daniel Kulp float's and double's negative infinity is incorrectly marshalled/unmarshalled as positive infinity -- Key: CXF-1780 URL: https://issues.apache.org/jira/browse/CXF-1780 Project: CXF Issue Type: Bug Components: CORBA Binding Affects Versions: 2.1.2 Reporter: Matteo Vescovi Assignee: Daniel Kulp Fix For: 2.1.3 Attachments: infinity_patch.diff Floats with value Float.NEGATIVE_INFINITY or doubles with value Double.NEGATIVE_INFINITY are incorrectly marshalled/unmarshalled as positive infinity. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1769) Nillable schema elements in WSDL cause XmlSchemaException
[ https://issues.apache.org/jira/browse/CXF-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1769. -- Resolution: Fixed Fix Version/s: 2.1.3 2.0.9 Assignee: Daniel Kulp (was: Benson Margulies) I added some code to the jaxb databinding on trunk to workaround a bug in JAXB for this. That's why it's working there. Nillable schema elements in WSDL cause XmlSchemaException - Key: CXF-1769 URL: https://issues.apache.org/jira/browse/CXF-1769 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Affects Versions: 2.1.2 Reporter: John Hite Assignee: Daniel Kulp Fix For: 2.0.9, 2.1.3 Attachments: build.xml, HelloWorld.wsdl A WSDL with a nillable schema element, e.g. element name=sayHelloResponse complexType sequence element name=output type=xsd:string minOccurs=0 maxOccurs=1 nillable=true / /sequence /complexType /element can be used to generate a JAX-WS front end, but when trying to recreate the WSDL via reflection, the following exception is thrown: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: urn:example-helloworld Steps to reproduce: 1. Use WSDLToJava to generate a JAXWS frontend from the provided WSDL. 2. Use JavaToWS to generate a new WSDL from the generated JAXWS frontend. If you remove the 'nillable=true' from the wsdl, then this error goes away. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1777) JAXBDataBinding hard references internal classes from the JAXB Sun RI which are not available in Java 6 any more
[ https://issues.apache.org/jira/browse/CXF-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies resolved CXF-1777. --- Resolution: Invalid The problem isn't that anything moved. The problem is that the version of JAXB in the 1.6 JRE is not new enough. See the notes I added to: http://cwiki.apache.org/confluence/display/CXF/FAQ 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.apache.org/jira/browse/CXF-1777 Project: CXF Issue Type: Bug Components: JAXB Databinding Affects Versions: 2.1.1 Environment: Sun JDK 1.6.0_06 Reporter: Gyorgy Orban The following classes have been moved to a new internal package in Java 6: com.sun.xml.bind.marshaller.NamespacePrefixMapper; com.sun.xml.bind.v2.ContextFactory; com.sun.xml.bind.v2.runtime.JAXBContextImpl; JAXBDataBinding has hard reference to them. It causes issues when running CXF on Sun JDK 1.6.0_06 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1772) Generated WSDL has a char
[ https://issues.apache.org/jira/browse/CXF-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627764#action_12627764 ] Benson Margulies commented on CXF-1772: --- This is not a feature of Aegis at this time. You will have to work with the type mapping object to change the object. There's no mechanism in the XML type mapping system for this. However, if this is non-conforming, we should just fix it to use string. Generated WSDL has a char - Key: CXF-1772 URL: https://issues.apache.org/jira/browse/CXF-1772 Project: CXF Issue Type: Bug Components: Aegis Databinding Affects Versions: 2.1.1 Reporter: Nathan Deckard My .aegis.xml mappings are not overriding a char that is showing up in the generated WSDL. The char is causing SOAPUI to error out because char does not exist in the http://schemas.xmlsoap.org/soap/encoding/ schema. NathansCharImpl.aegis.xml: ?xml version=1.0 encoding=UTF-8? !-- For Aegis mappings -- aegis:mappings xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:aegis=http://cwiki.apache.org/CXF20DOC/aegis-databinding.data/aegis; schemaLocation=http://cwiki.apache.org/CXF20DOC/aegis-databinding.data/aegis.xsd; aegis:mapping aegis:property name=myCharacter componentType=org.apache.cxf.aegis.type.basic.CharacterType typeName=xsd:string/ aegis:method name=getMyCharacter return-type componentType=org.apache.cxf.aegis.type.basic.CharacterType typeName=xsd:string/ /aegis:method /aegis:mapping /aegis:mappings @WebService @Features(features = org.apache.cxf.feature.LoggingFeature) public interface NathansCharacter { public abstract Character getMyCharacter(); public abstract void setMyCharacter(Character myCharacter); } @WebService (endpointInterface = com.clearingcorp.riskmanagement.ws.NathansCharacter) @Features(features = org.apache.cxf.feature.LoggingFeature) public class NathansCharacterImpl implements NathansCharacter { private Character myCharacter; public Character getMyCharacter() { return myCharacter; } public void setMyCharacter(Character myCharacter) { this.myCharacter = myCharacter; } } bean id=nathansCharacterServiceImpl class=com.clearingcorp.riskmanagement.ws.NathansCharacterImpl/ jaxws:endpoint id=myCharacterServiceEndpoint implementorClass=com.clearingcorp.riskmanagement.ws.NathansCharacterImpl implementor=#nathansCharacterServiceImpl address=/myCharacterService jaxws:serviceFactory ref bean=jaxws-and-aegis-service-factory/ /jaxws:serviceFactory /jaxws:endpoint bean id=aegisBean class=org.apache.cxf.aegis.databinding.AegisDatabinding scope=prototype/ bean id=jaxws-and-aegis-service-factory class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean scope=prototype property name=dataBinding ref=aegisBean/ property name=serviceConfigurations list bean class=org.apache.cxf.jaxws.support.JaxWsServiceConfiguration/ bean class=org.apache.cxf.aegis.databinding.XFireCompatibilityServiceConfiguration/ bean class=org.apache.cxf.service.factory.DefaultServiceConfiguration/ /list /property /bean The error from SOAPUI: Fri Aug 29 14:55:49 CDT 2008:ERROR:org.apache.xmlbeans.XmlException: http://localhost:7003/riskmanagement-wsserver/myCharacterService?wsdl:0: error: src-resolve: type '[EMAIL PROTECTED]://schemas.xmlsoap.org/soap/encoding/' not found. org.apache.xmlbeans.XmlException: http://localhost:7003/riskmanagement-wsserver/myCharacterService?wsdl:0: error: src-resolve: type '[EMAIL PROTECTED]://schemas.xmlsoap.org/soap/encoding/' not found. at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.xmlbeans.XmlBeans.compileXsd(XmlBeans.java:553) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.buildSchemaTypes(SchemaUtils.java:266) at
[jira] Commented: (CXF-1772) Generated WSDL has a char
[ https://issues.apache.org/jira/browse/CXF-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627771#action_12627771 ] Daniel Kulp commented on CXF-1772: -- Comment #1: at this point, we definitely shouldn't be mapping anything into the soap-enc namespace. We don't really support soap-encoding at this point (Dain added SOME support into aegis, but it's not really hooked up yet). Thus, that definitely needs to be fixed. Comment #2: it would probably be a good idea to map char into a simpleType restriction of string with maxLength=1: simpleType name=Character restriction base=string maxLength value=1/ minLength value=1/ /restriction /simpleType Generated WSDL has a char - Key: CXF-1772 URL: https://issues.apache.org/jira/browse/CXF-1772 Project: CXF Issue Type: Bug Components: Aegis Databinding Affects Versions: 2.1.1 Reporter: Nathan Deckard My .aegis.xml mappings are not overriding a char that is showing up in the generated WSDL. The char is causing SOAPUI to error out because char does not exist in the http://schemas.xmlsoap.org/soap/encoding/ schema. NathansCharImpl.aegis.xml: ?xml version=1.0 encoding=UTF-8? !-- For Aegis mappings -- aegis:mappings xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:aegis=http://cwiki.apache.org/CXF20DOC/aegis-databinding.data/aegis; schemaLocation=http://cwiki.apache.org/CXF20DOC/aegis-databinding.data/aegis.xsd; aegis:mapping aegis:property name=myCharacter componentType=org.apache.cxf.aegis.type.basic.CharacterType typeName=xsd:string/ aegis:method name=getMyCharacter return-type componentType=org.apache.cxf.aegis.type.basic.CharacterType typeName=xsd:string/ /aegis:method /aegis:mapping /aegis:mappings @WebService @Features(features = org.apache.cxf.feature.LoggingFeature) public interface NathansCharacter { public abstract Character getMyCharacter(); public abstract void setMyCharacter(Character myCharacter); } @WebService (endpointInterface = com.clearingcorp.riskmanagement.ws.NathansCharacter) @Features(features = org.apache.cxf.feature.LoggingFeature) public class NathansCharacterImpl implements NathansCharacter { private Character myCharacter; public Character getMyCharacter() { return myCharacter; } public void setMyCharacter(Character myCharacter) { this.myCharacter = myCharacter; } } bean id=nathansCharacterServiceImpl class=com.clearingcorp.riskmanagement.ws.NathansCharacterImpl/ jaxws:endpoint id=myCharacterServiceEndpoint implementorClass=com.clearingcorp.riskmanagement.ws.NathansCharacterImpl implementor=#nathansCharacterServiceImpl address=/myCharacterService jaxws:serviceFactory ref bean=jaxws-and-aegis-service-factory/ /jaxws:serviceFactory /jaxws:endpoint bean id=aegisBean class=org.apache.cxf.aegis.databinding.AegisDatabinding scope=prototype/ bean id=jaxws-and-aegis-service-factory class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean scope=prototype property name=dataBinding ref=aegisBean/ property name=serviceConfigurations list bean class=org.apache.cxf.jaxws.support.JaxWsServiceConfiguration/ bean class=org.apache.cxf.aegis.databinding.XFireCompatibilityServiceConfiguration/ bean class=org.apache.cxf.service.factory.DefaultServiceConfiguration/ /list /property /bean The error from SOAPUI: Fri Aug 29 14:55:49 CDT 2008:ERROR:org.apache.xmlbeans.XmlException: http://localhost:7003/riskmanagement-wsserver/myCharacterService?wsdl:0: error: src-resolve: type '[EMAIL PROTECTED]://schemas.xmlsoap.org/soap/encoding/' not found. org.apache.xmlbeans.XmlException: http://localhost:7003/riskmanagement-wsserver/myCharacterService?wsdl:0: error: src-resolve: type '[EMAIL PROTECTED]://schemas.xmlsoap.org/soap/encoding/' not found. at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at
[jira] Assigned: (CXF-1772) Generated WSDL has a char
[ https://issues.apache.org/jira/browse/CXF-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies reassigned CXF-1772: - Assignee: Benson Margulies Generated WSDL has a char - Key: CXF-1772 URL: https://issues.apache.org/jira/browse/CXF-1772 Project: CXF Issue Type: Bug Components: Aegis Databinding Affects Versions: 2.1.1 Reporter: Nathan Deckard Assignee: Benson Margulies My .aegis.xml mappings are not overriding a char that is showing up in the generated WSDL. The char is causing SOAPUI to error out because char does not exist in the http://schemas.xmlsoap.org/soap/encoding/ schema. NathansCharImpl.aegis.xml: ?xml version=1.0 encoding=UTF-8? !-- For Aegis mappings -- aegis:mappings xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:aegis=http://cwiki.apache.org/CXF20DOC/aegis-databinding.data/aegis; schemaLocation=http://cwiki.apache.org/CXF20DOC/aegis-databinding.data/aegis.xsd; aegis:mapping aegis:property name=myCharacter componentType=org.apache.cxf.aegis.type.basic.CharacterType typeName=xsd:string/ aegis:method name=getMyCharacter return-type componentType=org.apache.cxf.aegis.type.basic.CharacterType typeName=xsd:string/ /aegis:method /aegis:mapping /aegis:mappings @WebService @Features(features = org.apache.cxf.feature.LoggingFeature) public interface NathansCharacter { public abstract Character getMyCharacter(); public abstract void setMyCharacter(Character myCharacter); } @WebService (endpointInterface = com.clearingcorp.riskmanagement.ws.NathansCharacter) @Features(features = org.apache.cxf.feature.LoggingFeature) public class NathansCharacterImpl implements NathansCharacter { private Character myCharacter; public Character getMyCharacter() { return myCharacter; } public void setMyCharacter(Character myCharacter) { this.myCharacter = myCharacter; } } bean id=nathansCharacterServiceImpl class=com.clearingcorp.riskmanagement.ws.NathansCharacterImpl/ jaxws:endpoint id=myCharacterServiceEndpoint implementorClass=com.clearingcorp.riskmanagement.ws.NathansCharacterImpl implementor=#nathansCharacterServiceImpl address=/myCharacterService jaxws:serviceFactory ref bean=jaxws-and-aegis-service-factory/ /jaxws:serviceFactory /jaxws:endpoint bean id=aegisBean class=org.apache.cxf.aegis.databinding.AegisDatabinding scope=prototype/ bean id=jaxws-and-aegis-service-factory class=org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean scope=prototype property name=dataBinding ref=aegisBean/ property name=serviceConfigurations list bean class=org.apache.cxf.jaxws.support.JaxWsServiceConfiguration/ bean class=org.apache.cxf.aegis.databinding.XFireCompatibilityServiceConfiguration/ bean class=org.apache.cxf.service.factory.DefaultServiceConfiguration/ /list /property /bean The error from SOAPUI: Fri Aug 29 14:55:49 CDT 2008:ERROR:org.apache.xmlbeans.XmlException: http://localhost:7003/riskmanagement-wsserver/myCharacterService?wsdl:0: error: src-resolve: type '[EMAIL PROTECTED]://schemas.xmlsoap.org/soap/encoding/' not found. org.apache.xmlbeans.XmlException: http://localhost:7003/riskmanagement-wsserver/myCharacterService?wsdl:0: error: src-resolve: type '[EMAIL PROTECTED]://schemas.xmlsoap.org/soap/encoding/' not found. at org.apache.xmlbeans.impl.schema.SchemaTypeSystemCompiler.compile(SchemaTypeSystemCompiler.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.xmlbeans.XmlBeans.compileXmlBeans(XmlBeans.java:667) at org.apache.xmlbeans.XmlBeans.compileXsd(XmlBeans.java:553) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.buildSchemaTypes(SchemaUtils.java:266) at com.eviware.soapui.impl.wsdl.support.xsd.SchemaUtils.loadSchemaTypes(SchemaUtils.java:179) at com.eviware.soapui.impl.wsdl.support.wsdl.WsdlContext.loadDefinitions(WsdlContext.java:264) at
[jira] Assigned: (CXF-1778) Memory leak occurs in specific cases when WS-Addressing feature is enabled
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp reassigned CXF-1778: Assignee: Daniel Kulp Memory leak occurs in specific cases when WS-Addressing feature is enabled -- Key: CXF-1778 URL: https://issues.apache.org/jira/browse/CXF-1778 Project: CXF Issue Type: Bug Components: WS-* Components Affects Versions: 2.2 Reporter: Maciej Kwiecien Assignee: Daniel Kulp Priority: Critical Attachments: cxf-ws-addr-memory-leak.zip, histoConnectionRefused.log, histoEchoServerWithoutWsAddr.log I observed memory leak (OOM thrown) in following situations: 1.WS-Addressing enabled on client and server side. When server stops responding (connection refused on client side) client memory usage is increasing until OOM is thrown. 2.WS-Addressing enabled only on client side, server provide service without WS-Addressing feature (or WS-Addressing configuration is incorrect). Client memory heap is building up even faster than in first case. I will provide a sample application and more detailed description how to reproduce bug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1777) JAXBDataBinding hard references internal classes from the JAXB Sun RI which are not available in Java 6 any more
[ https://issues.apache.org/jira/browse/CXF-1777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627783#action_12627783 ] Daniel Kulp commented on CXF-1777: -- As a quick update, I've re-run the entire build and testsuite with 1.6.0_07 and all the tests pass and such. 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.apache.org/jira/browse/CXF-1777 Project: CXF Issue Type: Bug Components: JAXB Databinding Affects Versions: 2.1.1 Environment: Sun JDK 1.6.0_06 Reporter: Gyorgy Orban The following classes have been moved to a new internal package in Java 6: com.sun.xml.bind.marshaller.NamespacePrefixMapper; com.sun.xml.bind.v2.ContextFactory; com.sun.xml.bind.v2.runtime.JAXBContextImpl; JAXBDataBinding has hard reference to them. It causes issues when running CXF on Sun JDK 1.6.0_06 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1778) Memory leak occurs in specific cases when WS-Addressing feature is enabled
[ https://issues.apache.org/jira/browse/CXF-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1778. -- Resolution: Fixed Memory leak occurs in specific cases when WS-Addressing feature is enabled -- Key: CXF-1778 URL: https://issues.apache.org/jira/browse/CXF-1778 Project: CXF Issue Type: Bug Components: WS-* Components Affects Versions: 2.1.2 Reporter: Maciej Kwiecien Assignee: Daniel Kulp Priority: Critical Fix For: 2.1.3 Attachments: cxf-ws-addr-memory-leak.zip, histoConnectionRefused.log, histoEchoServerWithoutWsAddr.log I observed memory leak (OOM thrown) in following situations: 1.WS-Addressing enabled on client and server side. When server stops responding (connection refused on client side) client memory usage is increasing until OOM is thrown. 2.WS-Addressing enabled only on client side, server provide service without WS-Addressing feature (or WS-Addressing configuration is incorrect). Client memory heap is building up even faster than in first case. I will provide a sample application and more detailed description how to reproduce bug. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1656) PolicyEngineImpl Memory Improvement
[ https://issues.apache.org/jira/browse/CXF-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1656. -- Resolution: Fixed PolicyEngineImpl Memory Improvement --- Key: CXF-1656 URL: https://issues.apache.org/jira/browse/CXF-1656 Project: CXF Issue Type: Improvement Components: WS-* Components Affects Versions: 2.1.1, 2.0.7 Reporter: Bharath Ganesh Assignee: Daniel Kulp Fix For: 2.1.3 PolicyEngineImpl maintains a clientEndpointInfos map to keep the EndpointPolicies for client endpoints. An entry added to this map (while a client comes in) is removed only when the server endpoint is stopped. This leads to very high memory usage when there are frequent getPort() Calls. This can be can be reduced by maintaining a weak reference to the client EndpointInfo's. [Make clientEndpointInfoMap a weakhashmap] This would mean that after the lifetime of a single client port, all its data structures would be cleared. We need to explore more on this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1334) remove eclipse-plugin module
[ https://issues.apache.org/jira/browse/CXF-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1334. -- Resolution: Fixed Fix Version/s: 2.2 Assignee: Daniel Kulp remove eclipse-plugin module Key: CXF-1334 URL: https://issues.apache.org/jira/browse/CXF-1334 Project: CXF Issue Type: Task Affects Versions: 2.0.3 Reporter: Bozhong Lin Assignee: Daniel Kulp Fix For: 2.2 As Eclipse STP project no long needs this stuff -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1771) WstxUnexpectedCharException when returning a String from a CXF SOAP service containing specific characters (used with CXF client)
[ https://issues.apache.org/jira/browse/CXF-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1771. -- Resolution: Invalid Fix Version/s: Invalid Resolving as Invalid as this kind of matches the normal JAXB behavior. JAXB allows creation of XML/SOAP messages that are not valid per the schema. (like lists of not correct length, nillables or missing elements when they are required, etc) If you need strict compliance, it does allow validation to be turned on. WstxUnexpectedCharException when returning a String from a CXF SOAP service containing specific characters (used with CXF client) - Key: CXF-1771 URL: https://issues.apache.org/jira/browse/CXF-1771 Project: CXF Issue Type: Bug Affects Versions: 2.1.2 Reporter: Martijn Brinkers Fix For: Invalid If my SOAP service returns a String that contains control characters and the service is consumed by a CXF client a com.ctc.wstx.exc.WstxUnexpectedCharException is being thrown. It's easy to duplicate (in my setup) by modifying one line of the CXF 2.1.2 sample samples/java_first_jaxws: public String sayHiToUser(User user) { System.out.println(sayHiToUser called); users.put(users.size() + 1, user); return Hello + user.getName() + '\27'; = add '\27' to the String being returned } Now when you start the client sample the following exception is being thrown: INFO: Interceptor has thrown exception, unwinding now org.apache.cxf.interceptor.Fault: Unmarshalling Error: Illegal character ((CTRL-CHAR, code 23)) at [row,col {unknown-source}]: [1,161] at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:552) at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:465) at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:105) at org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:102) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220) at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:449) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2029) at org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1865) at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:66) at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:593) at org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:62) at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:220) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:296) at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:242) at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73) at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:178) at $Proxy42.sayHiToUser(Unknown Source) at demo.hw.client.Client.main(Client.java:56) Caused by: javax.xml.bind.UnmarshalException - with linked exception: [com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character ((CTRL-CHAR, code 23)) at [row,col {unknown-source}]: [1,161]] at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.handleStreamException(UnmarshallerImpl.java:422) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:360) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:337) at org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshall(JAXBEncoderDecoder.java:537) ... 17 more Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Illegal character ((CTRL-CHAR, code 23)) at [row,col {unknown-source}]: [1,161] at com.ctc.wstx.sr.StreamScanner.throwInvalidSpace(StreamScanner.java:650) at com.ctc.wstx.sr.BasicStreamReader.readTextPrimary(BasicStreamReader.java:4554) at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2886) at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1019) at org.apache.cxf.staxutils.DepthXMLStreamReader.next(DepthXMLStreamReader.java:220) at com.sun.xml.bind.v2.runtime.unmarshaller.StAXStreamConnector.bridge(StAXStreamConnector.java:225) at com.sun.xml.bind.v2.runtime.unmarshaller.UnmarshallerImpl.unmarshal0(UnmarshallerImpl.java:358) ... 19 more Exception in thread main
[jira] Resolved: (CXF-1730) The Exception handling if it is thrown from a RequestHandler is not correct i guess.
[ https://issues.apache.org/jira/browse/CXF-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1730. -- Resolution: Fixed Fix Version/s: 2.1.2 Assignee: Daniel Kulp Confirmed fixed in 2.1.2. The Exception handling if it is thrown from a RequestHandler is not correct i guess. Key: CXF-1730 URL: https://issues.apache.org/jira/browse/CXF-1730 Project: CXF Issue Type: Bug Components: REST Affects Versions: 2.1.2 Environment: Windows XP, jdk1.6, Apache Tomcat 6.0.16 Reporter: Frank Ittermann Assignee: Daniel Kulp Fix For: 2.1.2 Hello again i' ve used an implementation of RequestHandler to perform authentication stuff. So if the Authentication failed a RuntimeException is thrown. I've also wrote a ExceptionMapper implementation to transform occurred Exception into Http Status codes. If the RuntimeException from the Authentication was thrown than this is translated to an HTTP 403 status code. But this Http status code is not send as response. This sends a 200 status code. After a time of debugging i found the code that is responsible for that. The processResponse method of the org.apache.cxf.jaxrs.interceptor.JAXRSOutInterceptor work not correct is guess. Because code with the following code block this methods ends. OperationResourceInfo operation = (OperationResourceInfo)exchange.get(OperationResourceInfo.class .getName()); if (operation == null) { return; } because the operation variable is null. The code after this is responsible to but the Response from the ExceptionMapper class into the message object so that i received a 403 http status code. I've searched the code again and i found the code block how put the OperationResourceInfo into the Exchange object. That is done by the processRequest method of the org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor class. But before the OperationResourceInfo object is putted in the registered ResourceHandler are called see the code block below. for (ProviderInfoRequestHandler sh : shs) { Response response = sh.getProvider().handleRequest(message, resource); if (response != null) { message.getExchange().put(Response.class, response); return; } } I guess the code how put in the OperationresourceInfo object could be performed before the RequestHandlers are called maybe? Or it's forbidden to throw a Runtimeexception inside the RequestHandler ? I've also tried to return an Response object from the RequestHandler but the effect was the same it never arrives the client. It received also the Response object with http code 200. The CXF framework is great and very flexible good work. The opportunities to register own code is very great. Good work. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CXF-1390) Upgrade to Spring 2.5
[ https://issues.apache.org/jira/browse/CXF-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-1390. -- Resolution: Fixed Fix Version/s: 2.2 Assignee: Daniel Kulp Trunk (2.2) is now using 2.5.4.(2.1.x uses 2.0.8 by default, but is tested with 2.5.4 in IONA) Upgrade to Spring 2.5 - Key: CXF-1390 URL: https://issues.apache.org/jira/browse/CXF-1390 Project: CXF Issue Type: Bug Components: Core Affects Versions: 2.0.3 Reporter: Dan Diephouse Assignee: Daniel Kulp Fix For: 2.2 Attachments: cxf-spring-demo.war, cxf-spring-error.war, cxf-spring-error_stacktrace.rtf CXF doesn't work correctly on Spring 2.5. For instance, you get this: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'jrulesService': Unsatisfied dependency expressed through constructor argument with index 2 of type [org.apache.cxf.jaxws.JaxWsServerFactoryBean]: Ambiguous constructor argument types - did you specify the correct bean references as constructor arguments? (What ever happened to the famed backward compatability!? :-) *sigh*) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (CXF-1779) exclude non-serializable property to JBI NormalizedMessage
[ https://issues.apache.org/jira/browse/CXF-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12627897#action_12627897 ] Freeman Fang commented on CXF-1779: --- also need exclude Map or Collection property as well which entry may not be serializable http://svn.apache.org/viewvc?rev=691508view=rev for 2.0.x http://svn.apache.org/viewvc?rev=691510view=rev for 2.1.x http://svn.apache.org/viewvc?rev=691511view=rev for trunk exclude non-serializable property to JBI NormalizedMessage -- Key: CXF-1779 URL: https://issues.apache.org/jira/browse/CXF-1779 Project: CXF Issue Type: Bug Affects Versions: 2.0.8, 2.1.2 Reporter: Freeman Fang Assignee: Freeman Fang Fix For: 2.0.9, 2.1.3, 2.2 this will fix https://issues.apache.org/activemq/browse/SM-1537 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.