[jira] [Commented] (CXF-2796) maven build fails once after clean but then succeeds
[ https://issues.apache.org/jira/browse/CXF-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014457#comment-13014457 ] Piotr Klimczak commented on CXF-2796: - Same problem :( I will try to take a closer look at this during this weekend (i hope). So please wait for further informations. cxf-codegen-plugin-markers] [DEBUG] Checking for symlink: File's canonical path: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/jaxws File's absolute path with canonical parent: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/jaxws [INFO] Deleting directory: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/jaxws [DEBUG] Checking for symlink: File's canonical path: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/classes File's absolute path with canonical parent: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/classes [INFO] Deleting directory: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/classes [DEBUG] Checking for symlink: File's canonical path: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target File's absolute path with canonical parent: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target [INFO] Deleting directory: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target [DEBUG] Checking for symlink: File's canonical path: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/cxf-codegen-plugin-markers File's absolute path with canonical parent: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/cxf-codegen-plugin-markers [DEBUG] Skipping non-existing directory: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/classes [DEBUG] Skipping non-existing directory: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/test-classes [DEBUG] Skipping non-existing directory: /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/site [INFO] [INFO] --- cxf-codegen-plugin:2.4.0-SNAPSHOT:wsdl2java (Default Contract) @ kgapi-contract-test --- [DEBUG] Configuring mojo org.apache.cxf:cxf-codegen-plugin:2.4.0-SNAPSHOT:wsdl2java from plugin realm ClassRealm[plugin>org.apache.cxf:cxf-codegen-plugin:2.4.0-SNAPSHOT, parent: sun.misc.Launcher$AppClassLoader@6d6f0472] [DEBUG] Configuring mojo 'org.apache.cxf:cxf-codegen-plugin:2.4.0-SNAPSHOT:wsdl2java' with basic configurator --> [DEBUG] (f) classesDirectory = /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/classes [DEBUG] (f) disableDependencyScan = false [DEBUG] (f) disableDirectoryScan = false [DEBUG] (f) fork = false [DEBUG] (f) javaExecutable = /opt/sun-jdk-1.6.0.24/jre/bin/java [DEBUG] (f) localRepository =id: local url: file:///home/kokete/.m2/repository/ layout: none [DEBUG] (f) markerDirectory = /home/kokete/workspace/kgapi/kgapi-contracts/kgapi-contract-test/target/cxf-codegen-plugin-markers [DEBUG] (f) mavenSession = org.apache.maven.execution.MavenSession@d3c9557 [DEBUG] (f) pluginArtifacts = [org.apache.cxf:cxf-codegen-plugin:maven-plugin:2.4.0-SNAPSHOT:, org.apache.maven.shared:maven-artifact-resolver:jar:1.0:compile, org.codehaus.plexus:plexus-utils:jar:2.0.5:compile, org.codehaus.plexus:plexus-archiver:jar:1.2:compile, org.codehaus.plexus:plexus-io:jar:1.0.1:compile, org.apache.cxf:cxf-tools-common:jar:2.4.0-SNAPSHOT:compile, org.apache.velocity:velocity:jar:1.6.4:compile, commons-collections:commons-collections:jar:3.2.1:compile, commons-lang:commons-lang:jar:2.6:compile, oro:oro:jar:2.0.8:compile, wsdl4j:wsdl4j:jar:1.6.2:compile, com.sun.xml.bind:jaxb-xjc:jar:2.1.13:compile, com.sun.xml.bind:jaxb-impl:jar:2.1.13:compile, org.apache.cxf:cxf-api:jar:2.4.0-SNAPSHOT:compile, org.apache.neethi:neethi:jar:3.0.0-SNAPSHOT:compile, org.apache.cxf:cxf-rt-core:jar:2.4.0-SNAPSHOT:compile, org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile, org.apache.cxf:cxf-tools-wsdlto-core:jar:2.4.0-SNAPSHOT:compile, org.apache.cxf:cxf-tools-validator:jar:2.4.0-SNAPSHOT:compile, org.apache.cxf:cxf-common-utilities:jar:2.4.0-SNAPSHOT:compile, org.apache.ws.xmlschema:xmlschema-core:jar:2.0:compile, org.codehaus.woodstox:woodstox-core-asl:jar:4.1.1:compile, org.codehaus.woodstox:stax2-api:jar:3.1.1:compile, org.apache.cxf:cxf-tools-wsdlto-databinding-jaxb:jar:2.4.0-SNAPSHOT:compile, org.apache.cxf:cxf-tools-wsdlto-frontend-jaxws:jar:2.4.0-SNAPSHOT:compile, xml-resolver:xml-resolver:jar:1.2:compile, org.springframework:spring-core:jar:3.0.5.RELEASE:compile, org.springframework:spring-asm:jar:3.0.5.RELEASE:compile, commons-logging:commons-logging:jar:1.1.1:compile, org.springframework:spring-beans:jar:3.0.5.RELEASE:compile, org.springframework:spring-context:jar:3.0.5.RELEASE:compile, org.sp
[jira] [Commented] (CXF-2796) maven build fails once after clean but then succeeds
[ https://issues.apache.org/jira/browse/CXF-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014499#comment-13014499 ] raisercostin commented on CXF-2796: --- You might want to take a look here http://stackoverflow.com/questions/3832414/classcastexception-in-casting-dtmmanagerdefault-into-dtmmanager-during-maven-jaxb/5147175#5147175 "The solution is to search for all dependencies on Xalan and xercesImpl in the classpath . These dependencies should be excluded." So is a classpath issue, and might be reproduced if the jars have a specific order, and some registred components for working with xml goes in a specific order. > maven build fails once after clean but then succeeds > > > Key: CXF-2796 > URL: https://issues.apache.org/jira/browse/CXF-2796 > Project: CXF > Issue Type: Bug > Components: Build system >Affects Versions: 2.2.7 > Environment: java version "1.6.0_18" > OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8-0ubuntu1) > OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) >Reporter: Bruce Edge > Labels: build, maven > Fix For: NeedMoreInfo > > > When I run: > mvn clean install > It fails with this traceback: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault > cannot be cast to org.apache.xml.dtm.DTMManager > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: > java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot > be cast to org.apache.xml.dtm.DTMManager > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: > java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot > be cast to org.apache.xml.dtm.DTMManager > at > org.apache.cxf.maven_plugin.WSDL2JavaMojo.callWsdl2Java(WSDL2JavaMojo.java:409) > at > org.apache.cxf.maven_plugin.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:361) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > ... 17 more > Caused by: org.apache.cxf.tools.common.ToolException: > java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot > be cast to org.apache.xml.dtm.DTMManager > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:279) > at > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86) > at > org.apache.cxf.maven_plugin.WSDL2JavaMojo.callWsdl2Java(WSDL2JavaMojo.java:406) > ... 20 more > Caused by: java.lang.ClassCastException: > org.apache.
[jira] [Commented] (CXF-2796) maven build fails once after clean but then succeeds
[
https://issues.apache.org/jira/browse/CXF-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014505#comment-13014505
]
Piotr Klimczak commented on CXF-2796:
-
I can confirm that removing described dependencies have solved the problem.
But the sad thing is, that adding simple dependency like:
org.apache.cxf
cxf-rt-ws-security
${cxf.version}
where ${cxf.version} is a servicemix features parent property will BLOW your
cxf-codegen-plugin.
So i guess this is why it is better idea to place you wsdl/xsd files in
separated project :)
Thanks!
> maven build fails once after clean but then succeeds
>
>
> Key: CXF-2796
> URL: https://issues.apache.org/jira/browse/CXF-2796
> Project: CXF
> Issue Type: Bug
> Components: Build system
>Affects Versions: 2.2.7
> Environment: java version "1.6.0_18"
> OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8-0ubuntu1)
> OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode)
>Reporter: Bruce Edge
> Labels: build, maven
> Fix For: NeedMoreInfo
>
>
> When I run:
> mvn clean install
> It fails with this traceback:
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault
> cannot be cast to org.apache.xml.dtm.DTMManager
> [INFO]
>
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException:
> java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot
> be cast to org.apache.xml.dtm.DTMManager
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException:
> java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot
> be cast to org.apache.xml.dtm.DTMManager
> at
> org.apache.cxf.maven_plugin.WSDL2JavaMojo.callWsdl2Java(WSDL2JavaMojo.java:409)
> at
> org.apache.cxf.maven_plugin.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:361)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.apache.cxf.tools.common.ToolException:
> java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot
> be cast to org.apache.xml.dtm.DTMManager
> at
> org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:279)
> at
> org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113)
> at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86)
> at
> org.apache.cxf.maven_plugin.WSDL2JavaMojo.callWsdl2Java(WSDL2JavaMojo.java:406)
> ... 20 more
> Caused by: java.lang.ClassCastException:
> org.apache.xml.dtm.ref.DTMManagerDefault
[jira] [Resolved] (CXF-3427) JMSContinuation should be thread safe
[ https://issues.apache.org/jira/browse/CXF-3427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang resolved CXF-3427. --- Resolution: Fixed Fix Version/s: 2.3.4 2.4 > JMSContinuation should be thread safe > - > > Key: CXF-3427 > URL: https://issues.apache.org/jira/browse/CXF-3427 > Project: CXF > Issue Type: Bug > Components: Transports >Reporter: Willem Jiang >Assignee: Willem Jiang >Priority: Minor > Fix For: 2.4, 2.3.4 > > > As the doResume() method of JMSContinuation could be invoked in different > thread as the same time, it should be synchronized. > Also, some boolean flag (isNew, isPending, isResumed) need to be made > volatile. > We also need to update the JettyContinuationWrapper and Servlet3Continuation > for boolean flag. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-2256) Implement the SOAP over TCP standard supported by Metro and WCF(via plugin)
[ https://issues.apache.org/jira/browse/CXF-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014568#comment-13014568 ] G.W.G.K.N.Udayanga commented on CXF-2256: - Hello; I am G.W.G.K.N.Udayanga a fouth year(final year) student from the dept of computer science & Engineering,university of moratuwa,Sri Lanka.I am interested in doing this project for gsoc 2011.Can you give some references relevant to this project and can i know about the mentor for this project? > Implement the SOAP over TCP standard supported by Metro and WCF(via plugin) > --- > > Key: CXF-2256 > URL: https://issues.apache.org/jira/browse/CXF-2256 > Project: CXF > Issue Type: Task > Components: Transports >Reporter: Krzysztof Wilkos > Labels: gsoc2011 > > Implement the SOAP optimized TCP transport developed by Sun and supported by > Metro and WCF (via an external plugin). The spec is available at: > http://java.sun.com/webservices/reference/apis-docs/soap-tcp-v1.0.pdf The > optimized transport would support using a stateful fastinfoset grammar to > optimize the transmissions increasing performance. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-3434) Blueprint coloc feature
Blueprint coloc feature --- Key: CXF-3434 URL: https://issues.apache.org/jira/browse/CXF-3434 Project: CXF Issue Type: New Feature Components: OtherDatabindings Affects Versions: 2.4 Reporter: Edstrom Johan Priority: Minor Fix For: 2.4 Patch attached for blueprint coloc feature. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3434) Blueprint coloc feature
[ https://issues.apache.org/jira/browse/CXF-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edstrom Johan updated CXF-3434: --- Attachment: Blueprint_coloc_feature_.patch > Blueprint coloc feature > --- > > Key: CXF-3434 > URL: https://issues.apache.org/jira/browse/CXF-3434 > Project: CXF > Issue Type: New Feature > Components: OtherDatabindings >Affects Versions: 2.4 >Reporter: Edstrom Johan >Priority: Minor > Fix For: 2.4 > > Attachments: Blueprint_coloc_feature_.patch > > > Patch attached for blueprint coloc feature. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-3435) catalog.cat files are pointing to wrong xsd schemas
catalog.cat files are pointing to wrong xsd schemas --- Key: CXF-3435 URL: https://issues.apache.org/jira/browse/CXF-3435 Project: CXF Issue Type: Bug Components: WS-* Components Affects Versions: 2.4 Reporter: Aki Yoshida Priority: Trivial Fix For: 2.4 This problem is trivial and occurs only in the current trunk. In 2.3.x, the local versions of various ws xsd schemas were available at /common/schemas/src/main/resources/schemas/wsdl/. In trunk, the location of the schemas seems to have moved to /api/src/main/resources/schemas/wsdl/. However, the catalog.cat files for rt/ws/rm and rt/ws/addr have not been updated with this new location. Consequently, the local schema retrieval is not working and the ws/rm build tries to fetch the external public schema at http://schemas.xmlsoap.org/ws/2004/08/addressing for the addressing schema. Just updating the catalog.cat files will solve this problem. I'm attaching the patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3435) catalog.cat files are pointing to wrong xsd schemas
[ https://issues.apache.org/jira/browse/CXF-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aki Yoshida updated CXF-3435: - Attachment: trunk_20110401.txt patch for schema location path changes in catalog.cat > catalog.cat files are pointing to wrong xsd schemas > --- > > Key: CXF-3435 > URL: https://issues.apache.org/jira/browse/CXF-3435 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 2.4 >Reporter: Aki Yoshida >Priority: Trivial > Fix For: 2.4 > > Attachments: trunk_20110401.txt > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > This problem is trivial and occurs only in the current trunk. > In 2.3.x, the local versions of various ws xsd schemas were available at > /common/schemas/src/main/resources/schemas/wsdl/. > In trunk, the location of the schemas seems to have moved to > /api/src/main/resources/schemas/wsdl/. > However, the catalog.cat files for rt/ws/rm and rt/ws/addr have not been > updated with this new location. > Consequently, the local schema retrieval is not working and the ws/rm build > tries to fetch the external public schema at > http://schemas.xmlsoap.org/ws/2004/08/addressing for the addressing schema. > Just updating the catalog.cat files will solve this problem. > I'm attaching the patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3388) Expose CXF JMX MBeans as the JAX-RS resources
[ https://issues.apache.org/jira/browse/CXF-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014801#comment-13014801 ] Travis commented on CXF-3388: - I would like to participate in this mission as from the wonderful gsoc. I have good experiences in using cxf for ws outbound call and good practices in inbound server. I think it's amazing if I could have this opportunity to make a further step. I am a student in US. > Expose CXF JMX MBeans as the JAX-RS resources > - > > Key: CXF-3388 > URL: https://issues.apache.org/jira/browse/CXF-3388 > Project: CXF > Issue Type: New Feature > Components: Management >Reporter: Sergey Beryozkin > Labels: gsoc, gsoc2011 > > The JAX-RS application exposing CXF JMX MBeans over HTTP needs to be added to > the rt/management-web component. > This application should follow the best ideas expressed in the following blog > entry : > http://blogs.sun.com/jmxnetbeans/entry/restful_access_to_jmx_instrumentation1 > A more complete list of links is here: > http://mail-archives.apache.org/mod_mbox/cxf-users/201102.mbox/%3c2443d95470d8d8449b8cf1984400858702600...@exchange2.corp.ebates.com%3E > See also > http://mail-archives.apache.org/mod_mbox/cxf-users/201102.mbox/%3c2443d95470d8d8449b8cf19844008587034ed...@exchange2.corp.ebates.com%3E -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-3436) Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean
[ https://issues.apache.org/jira/browse/CXF-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Laskowski updated CXF-3436: - Attachment: CXF-3436.patch > Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean > > > Key: CXF-3436 > URL: https://issues.apache.org/jira/browse/CXF-3436 > Project: CXF > Issue Type: Improvement > Components: Documentation >Reporter: Jacek Laskowski >Priority: Trivial > Attachments: CXF-3436.patch > > > A patch to add 'new' amongst other fixes in the javadoc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-3436) Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean
Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean Key: CXF-3436 URL: https://issues.apache.org/jira/browse/CXF-3436 Project: CXF Issue Type: Improvement Components: Documentation Reporter: Jacek Laskowski Priority: Trivial Attachments: CXF-3436.patch A patch to add 'new' amongst other fixes in the javadoc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CXF-3434) Blueprint coloc feature
[ https://issues.apache.org/jira/browse/CXF-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp reassigned CXF-3434: Assignee: Daniel Kulp > Blueprint coloc feature > --- > > Key: CXF-3434 > URL: https://issues.apache.org/jira/browse/CXF-3434 > Project: CXF > Issue Type: New Feature > Components: OtherDatabindings >Affects Versions: 2.4 >Reporter: Edstrom Johan >Assignee: Daniel Kulp >Priority: Minor > Fix For: 2.4 > > Attachments: Blueprint_coloc_feature_.patch > > > Patch attached for blueprint coloc feature. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CXF-3435) catalog.cat files are pointing to wrong xsd schemas
[ https://issues.apache.org/jira/browse/CXF-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp reassigned CXF-3435: Assignee: Daniel Kulp > catalog.cat files are pointing to wrong xsd schemas > --- > > Key: CXF-3435 > URL: https://issues.apache.org/jira/browse/CXF-3435 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 2.4 >Reporter: Aki Yoshida >Assignee: Daniel Kulp >Priority: Trivial > Fix For: 2.4 > > Attachments: trunk_20110401.txt > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > This problem is trivial and occurs only in the current trunk. > In 2.3.x, the local versions of various ws xsd schemas were available at > /common/schemas/src/main/resources/schemas/wsdl/. > In trunk, the location of the schemas seems to have moved to > /api/src/main/resources/schemas/wsdl/. > However, the catalog.cat files for rt/ws/rm and rt/ws/addr have not been > updated with this new location. > Consequently, the local schema retrieval is not working and the ws/rm build > tries to fetch the external public schema at > http://schemas.xmlsoap.org/ws/2004/08/addressing for the addressing schema. > Just updating the catalog.cat files will solve this problem. > I'm attaching the patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CXF-3436) Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean
[ https://issues.apache.org/jira/browse/CXF-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp reassigned CXF-3436: Assignee: Daniel Kulp > Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean > > > Key: CXF-3436 > URL: https://issues.apache.org/jira/browse/CXF-3436 > Project: CXF > Issue Type: Improvement > Components: Documentation >Reporter: Jacek Laskowski >Assignee: Daniel Kulp >Priority: Trivial > Attachments: CXF-3436.patch > > > A patch to add 'new' amongst other fixes in the javadoc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-2796) maven build fails once after clean but then succeeds
[ https://issues.apache.org/jira/browse/CXF-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-2796. -- Resolution: Not A Problem Fix Version/s: (was: NeedMoreInfo) I'm going to resolve this as it's determined to be an issue with a 3rd party library that we really don't have control over. That libary is excludable for the most part. > maven build fails once after clean but then succeeds > > > Key: CXF-2796 > URL: https://issues.apache.org/jira/browse/CXF-2796 > Project: CXF > Issue Type: Bug > Components: Build system >Affects Versions: 2.2.7 > Environment: java version "1.6.0_18" > OpenJDK Runtime Environment (IcedTea6 1.8) (6b18-1.8-0ubuntu1) > OpenJDK 64-Bit Server VM (build 14.0-b16, mixed mode) >Reporter: Bruce Edge > Labels: build, maven > > When I run: > mvn clean install > It fails with this traceback: > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault > cannot be cast to org.apache.xml.dtm.DTMManager > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: > java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot > be cast to org.apache.xml.dtm.DTMManager > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) > at > org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:616) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.MojoExecutionException: > java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot > be cast to org.apache.xml.dtm.DTMManager > at > org.apache.cxf.maven_plugin.WSDL2JavaMojo.callWsdl2Java(WSDL2JavaMojo.java:409) > at > org.apache.cxf.maven_plugin.WSDL2JavaMojo.execute(WSDL2JavaMojo.java:361) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) > ... 17 more > Caused by: org.apache.cxf.tools.common.ToolException: > java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot > be cast to org.apache.xml.dtm.DTMManager > at > org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:279) > at > org.apache.cxf.tools.common.toolspec.ToolRunner.runTool(ToolRunner.java:103) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:113) > at org.apache.cxf.tools.wsdlto.WSDLToJava.run(WSDLToJava.java:86) > at > org.apache.cxf.maven_plugin.WSDL2JavaMojo.callWsdl2Java(WSDL2JavaMojo.java:406) > ... 20 more > Caused by: java.lang.ClassCastException: > org.apache.xml.dtm.ref.DTMManagerDefault cannot be cast to > org.apache.xml.dtm.DTMManager > at org.apache.xml.dtm.DTMManager.newInstance(DTMManager.java:137) > at org.apache.xpath.XPathContext.(XPathContext.java:102) > at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:207) > at org.apache
[jira] [Resolved] (CXF-3416) Have wsdl2java generate a constructor that sets all fields
[ https://issues.apache.org/jira/browse/CXF-3416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3416. -- Resolution: Won't Fix Fix Version/s: Invalid I'm going to mark this "Won't Fix". This is really a JAXB/XJC issue. HOWEVER, there exists and XJC plugin that can already do this: http://java.net/projects/jaxb2-commons/pages/value-constructor That plugin can be used along with CXF's wsdl2java tooling to accomplish this. > Have wsdl2java generate a constructor that sets all fields > -- > > Key: CXF-3416 > URL: https://issues.apache.org/jira/browse/CXF-3416 > Project: CXF > Issue Type: Improvement > Components: Soap Binding >Reporter: Dobes Vandermeer > Fix For: Invalid > > > Be nice to have the data classes generated by wsdl2java so that you can > construct them easily, either by having a constructor to fill in all the > fields or have the setters return "this" so you can chain them together. > Otherwise constructing a tree objects becomes quite a lot of work. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-3413) IndexOutOfBoundsException in DocLiteralInInterceptor
[
https://issues.apache.org/jira/browse/CXF-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13014837#comment-13014837
]
Daniel Kulp commented on CXF-3413:
--
While the error message is not ideal, the soap message does not match the
schema and thus should fail. The schema says the soap:Body should have a
single child called GeneratePreviewResponse which your message does not.
> IndexOutOfBoundsException in DocLiteralInInterceptor
>
>
> Key: CXF-3413
> URL: https://issues.apache.org/jira/browse/CXF-3413
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.3.3
>Reporter: Andreas Gudian
>
> I am receiving the following response from a web service that I call using
> CXF 2.3.3:
> {code:xml}
>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:xml="http://www.w3.org/XML/1998/namespace";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding";>
> xmlns:xsd1="http://www.xxx.yy/zzz/types/";>-1
> http://www.xxx.yy/zzz/types/";>Some Status
> Message
> http://www.xxx.yy/zzz/types/";>
>
>
> {code}
> This results in the following exception:
> {code}
> java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:188)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:755)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2335)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2193)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2037)
> 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:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> at $Proxy43.myWebserviceOperation(Unknown Source)
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3434) Blueprint coloc feature
[ https://issues.apache.org/jira/browse/CXF-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3434. -- Resolution: Fixed > Blueprint coloc feature > --- > > Key: CXF-3434 > URL: https://issues.apache.org/jira/browse/CXF-3434 > Project: CXF > Issue Type: New Feature > Components: OtherDatabindings >Affects Versions: 2.4 >Reporter: Edstrom Johan >Assignee: Daniel Kulp >Priority: Minor > Fix For: 2.4 > > Attachments: Blueprint_coloc_feature_.patch > > > Patch attached for blueprint coloc feature. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3435) catalog.cat files are pointing to wrong xsd schemas
[ https://issues.apache.org/jira/browse/CXF-3435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3435. -- Resolution: Fixed > catalog.cat files are pointing to wrong xsd schemas > --- > > Key: CXF-3435 > URL: https://issues.apache.org/jira/browse/CXF-3435 > Project: CXF > Issue Type: Bug > Components: WS-* Components >Affects Versions: 2.4 >Reporter: Aki Yoshida >Assignee: Daniel Kulp >Priority: Trivial > Fix For: 2.4 > > Attachments: trunk_20110401.txt > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > This problem is trivial and occurs only in the current trunk. > In 2.3.x, the local versions of various ws xsd schemas were available at > /common/schemas/src/main/resources/schemas/wsdl/. > In trunk, the location of the schemas seems to have moved to > /api/src/main/resources/schemas/wsdl/. > However, the catalog.cat files for rt/ws/rm and rt/ws/addr have not been > updated with this new location. > Consequently, the local schema retrieval is not working and the ws/rm build > tries to fetch the external public schema at > http://schemas.xmlsoap.org/ws/2004/08/addressing for the addressing schema. > Just updating the catalog.cat files will solve this problem. > I'm attaching the patch. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3436) Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean
[ https://issues.apache.org/jira/browse/CXF-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3436. -- Resolution: Fixed Fix Version/s: 2.3.4 2.4 > Javadoc fixes for o.a.c.jaxws.JaxWsServerFactoryBean > > > Key: CXF-3436 > URL: https://issues.apache.org/jira/browse/CXF-3436 > Project: CXF > Issue Type: Improvement > Components: Documentation >Reporter: Jacek Laskowski >Assignee: Daniel Kulp >Priority: Trivial > Fix For: 2.4, 2.3.4 > > Attachments: CXF-3436.patch > > > A patch to add 'new' amongst other fixes in the javadoc -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CXF-3413) IndexOutOfBoundsException in DocLiteralInInterceptor
[
https://issues.apache.org/jira/browse/CXF-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp reassigned CXF-3413:
Assignee: Daniel Kulp
> IndexOutOfBoundsException in DocLiteralInInterceptor
>
>
> Key: CXF-3413
> URL: https://issues.apache.org/jira/browse/CXF-3413
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.3.3
>Reporter: Andreas Gudian
>Assignee: Daniel Kulp
>
> I am receiving the following response from a web service that I call using
> CXF 2.3.3:
> {code:xml}
>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:xml="http://www.w3.org/XML/1998/namespace";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding";>
> xmlns:xsd1="http://www.xxx.yy/zzz/types/";>-1
> http://www.xxx.yy/zzz/types/";>Some Status
> Message
> http://www.xxx.yy/zzz/types/";>
>
>
> {code}
> This results in the following exception:
> {code}
> java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:188)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:755)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2335)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2193)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2037)
> 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:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> at $Proxy43.myWebserviceOperation(Unknown Source)
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3130) Aegis throws (and throws up) when an ExceptionInInitializerError happens while introspecting
[ https://issues.apache.org/jira/browse/CXF-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Kulp resolved CXF-3130. -- Resolution: Fixed Fix Version/s: (was: 2.4) 2.3.2 > Aegis throws (and throws up) when an ExceptionInInitializerError happens > while introspecting > > > Key: CXF-3130 > URL: https://issues.apache.org/jira/browse/CXF-3130 > Project: CXF > Issue Type: Bug > Components: Aegis Databinding >Affects Versions: 2.3.0, 2.2.11 >Reporter: Benson Margulies >Assignee: Benson Margulies > Fix For: 2.3.2 > > > org.apache.cxf.aegis.type.java5.AnnotationReader, the function 'load' > carefully traps ClassNotFoundException to allow it to just float along past > problems with classes that are referenced in services. However, there might > also be an ExceptionInInitializerError, and those pass through. > In both cases, logging+returning null seems appropriate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3413) IndexOutOfBoundsException in DocLiteralInInterceptor
[
https://issues.apache.org/jira/browse/CXF-3413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-3413.
--
Resolution: Fixed
Fix Version/s: 2.3.4
Stuck a better error message in there.
> IndexOutOfBoundsException in DocLiteralInInterceptor
>
>
> Key: CXF-3413
> URL: https://issues.apache.org/jira/browse/CXF-3413
> Project: CXF
> Issue Type: Bug
>Affects Versions: 2.3.3
>Reporter: Andreas Gudian
>Assignee: Daniel Kulp
> Fix For: 2.3.4
>
>
> I am receiving the following response from a web service that I call using
> CXF 2.3.3:
> {code:xml}
>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:xml="http://www.w3.org/XML/1998/namespace";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
> http://www.w3.org/2003/05/soap-envelope";
> xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding";>
> xmlns:xsd1="http://www.xxx.yy/zzz/types/";>-1
> http://www.xxx.yy/zzz/types/";>Some Status
> Message
> http://www.xxx.yy/zzz/types/";>
>
>
> {code}
> This results in the following exception:
> {code}
> java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
> at java.util.ArrayList.RangeCheck(ArrayList.java:547)
> at java.util.ArrayList.get(ArrayList.java:322)
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:188)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:755)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2335)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2193)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2037)
> 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:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> at $Proxy43.myWebserviceOperation(Unknown Source)
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-3395) cxf transfer hashmap can't be chinese word
[
https://issues.apache.org/jira/browse/CXF-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Kulp resolved CXF-3395.
--
Resolution: Fixed
Fix Version/s: 2.3.4
I'm going to close this as it seems to be a compiler encoding issue with
compiling the code, not really CXF. I did update the examples to make sure
they all are compiled as UTF-8 instead of platform encoding.
> cxf transfer hashmap can't be chinese word
> --
>
> Key: CXF-3395
> URL: https://issues.apache.org/jira/browse/CXF-3395
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
>Affects Versions: 2.3.3
> Environment: spring 3.0+dwr3.0+jdk5+tomcat6
>Reporter: kakashi
>Priority: Critical
> Fix For: 2.3.4
>
>
> hi cxf team:
>i use cxf2.3.3 in my project,and i tansfer the hashmap through cxf client
> to server(i use the example of apache-cxf-2.3.2,the java_first_jaxws project
> in official promulgate package) .firstly it run normally,but when i put some
> chinese word(not englist word) to hashmap
>i modify the HelloWorldImpl.java(the official example project
> file,java_first_jaxws is the project name) function just like this:
> HelloWorldImpl.java
> public Map getUsers() {
> Map usersForMap = new LinkedHashMap();
> //汉字bug 中文 bug
> usersForMap.put(1, new UserImpl("yhb汉字bug")); //-->when total english
> word,it run ok,when some chinese word here the cxf tell error to me.
> usersForMap.put(2, new UserImpl("wybl"));
> System.out.println("getUsers called");
> return usersForMap;
> }
>
>it' seem the marshal and unmarshal crash and tell fllow error(englisth
> word in hashmap seem runs ok):
> org.apache.cxf.interceptor.Fault: Marshalling Error: null
> at
> org.apache.cxf.jaxb.JAXBEncoderDecoder.unmarshalWithBridge(JAXBEncoderDecoder.java:327)
> at org.apache.cxf.jaxb.io.DataReaderImpl.read(DataReaderImpl.java:124)
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.getPara(DocLiteralInInterceptor.java:251)
> at
> org.apache.cxf.interceptor.DocLiteralInInterceptor.handleMessage(DocLiteralInInterceptor.java:127)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:255)
> at org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:755)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:2335)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:2193)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:2037)
> 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:516)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:313)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:265)
> at org.apache.cxf.frontend.ClientProxy.invokeSync(ClientProxy.java:73)
> at
> org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:124)
> at $Proxy61.getMapByCXFDocument(Unknown Source)
> at com.webservice.cxf.CxfSoapAction.runWebService(CxfSoapAction.java:77)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:592)
> at
> org.directwebremoting.impl.DefaultRemoter$1.doFilter(DefaultRemoter.java:740)
> at
> org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:744)
> at
> org.directwebremoting.impl.DefaultRemoter.execute(DefaultRemoter.java:593)
> at
> org.directwebremoting.dwrp.BaseCallHandler.handle(BaseCallHandler.java:90)
> at
> org.directwebremoting.servlet.UrlProcessor.handle(UrlProcessor.java:120)
> at org.directwebremoting.servlet.DwrServlet.doPost(DwrServlet.java:141)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
