August 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3943) Move all test util classes in wsi-bp-tests to JBossWSTest

by Jim Ma (JIRA)

Jim Ma created JBWS-3943: ---------------------------- Summary: Move all test util classes in wsi-bp-tests to JBossWSTest Key: JBWS-3943 URL: https://issues.jboss.org/browse/JBWS-3943 Project: JBoss Web Services Issue Type: Enhancement Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.0.Beta1 Reporter: Jim Ma Assignee: Jim Ma Fix For: jbossws-cxf-5.2.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3938) Upgrade to Apache CXF 3.1.3

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3938?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3938: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.0.Final (was: jbossws-cxf-5.1.0.Final) > Upgrade to Apache CXF 3.1.3 > --------------------------- > > Key: JBWS-3938 > URL: https://issues.jboss.org/browse/JBWS-3938 > Project: JBoss Web Services > Issue Type: Task > Components: jbossws-cxf > Reporter: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3942) Upgrade to Apache CXF 3.1.2-jbossorg-1

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3942: ------------------------------------- Summary: Upgrade to Apache CXF 3.1.2-jbossorg-1 Key: JBWS-3942 URL: https://issues.jboss.org/browse/JBWS-3942 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-5.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3941) Failure on writing wsdl to disk

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3941?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3941: ---------------------------------- Description: {noformat} 11:42:58,272 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl address=http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService implementor=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl serviceName={http://test.jbws3792/}JBWS3792WSService portName={http://test.jbws3792/}JBWS3792WSPort annotationWsdlLocation=http://bar:8080/jbws3792-external-wsdl/jbws3792.wsdl wsdlLocationOverride=http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl mtomEnabled=false 11:42:58,282 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://test.jbws3792/}JBWS3792WSService from WSDL: http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl 11:42:58,306 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService 11:42:58,312 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jbws3792-ws-impl.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: JBWS024076: Service {http://test.jbws3792/}JBWS3792WSService, cannot publish wsdl to: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:109) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.publishContractToFilesystem(EndpointImpl.java:148) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:85) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543) at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:231) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) ... 5 more Caused by: java.io.FileNotFoundException: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl (The filename, directory name, or volume label syntax is incorrect) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at java.io.FileOutputStream.<init>(FileOutputStream.java:162) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.writeDocument(WSDLFilePublisher.java:176) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:81) ... 14 more {noformat} was: 11:42:58,272 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl address=http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService implementor=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl serviceName={http://test.jbws3792/}JBWS3792WSService portName={http://test.jbws3792/}JBWS3792WSPort annotationWsdlLocation=http://bar:8080/jbws3792-external-wsdl/jbws3792.wsdl wsdlLocationOverride=http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl mtomEnabled=false 11:42:58,282 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://test.jbws3792/}JBWS3792WSService from WSDL: http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl 11:42:58,306 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService 11:42:58,312 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jbws3792-ws-impl.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: JBWS024076: Service {http://test.jbws3792/}JBWS3792WSService, cannot publish wsdl to: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:109) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.publishContractToFilesystem(EndpointImpl.java:148) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:85) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543) at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:231) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) ... 5 more Caused by: java.io.FileNotFoundException: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl (The filename, directory name, or volume label syntax is incorrect) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at java.io.FileOutputStream.<init>(FileOutputStream.java:162) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.writeDocument(WSDLFilePublisher.java:176) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:81) ... 14 more > Failure on writing wsdl to disk > ------------------------------- > > Key: JBWS-3941 > URL: https://issues.jboss.org/browse/JBWS-3941 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.0.Final > > > {noformat} > 11:42:58,272 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl > address=http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService > implementor=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl > serviceName={http://test.jbws3792/}JBWS3792WSService > portName={http://test.jbws3792/}JBWS3792WSPort > annotationWsdlLocation=http://bar:8080/jbws3792-external-wsdl/jbws3792.wsdl > wsdlLocationOverride=http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl > mtomEnabled=false > 11:42:58,282 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://test.jbws3792/}JBWS3792WSService from WSDL: http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl > 11:42:58,306 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService > 11:42:58,312 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jbws3792-ws-impl.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.RuntimeException: JBWS024076: Service {http://test.jbws3792/}JBWS3792WSService, cannot publish wsdl to: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:109) > at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.publishContractToFilesystem(EndpointImpl.java:148) > at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:85) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255) > at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543) > at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:231) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97) > at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59) > at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) > ... 5 more > Caused by: java.io.FileNotFoundException: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl (The filename, directory name, or volume label syntax is incorrect) > at java.io.FileOutputStream.open0(Native Method) > at java.io.FileOutputStream.open(FileOutputStream.java:270) > at java.io.FileOutputStream.<init>(FileOutputStream.java:213) > at java.io.FileOutputStream.<init>(FileOutputStream.java:162) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.writeDocument(WSDLFilePublisher.java:176) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:81) > ... 14 more > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3941) Failure on writing wsdl to disk

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3941: ------------------------------------- Summary: Failure on writing wsdl to disk Key: JBWS-3941 URL: https://issues.jboss.org/browse/JBWS-3941 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: jbossws-cxf-5.1.0.Final 11:42:58,272 INFO [org.jboss.ws.cxf.metadata] (MSC service thread 1-3) JBWS024061: Adding service endpoint metadata: id=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl address=http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService implementor=org.jboss.test.ws.jaxws.cxf.jbws3792.wsImpl.JBWS3792WSImpl serviceName={http://test.jbws3792/}JBWS3792WSService portName={http://test.jbws3792/}JBWS3792WSPort annotationWsdlLocation=http://bar:8080/jbws3792-external-wsdl/jbws3792.wsdl wsdlLocationOverride=http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl mtomEnabled=false 11:42:58,282 INFO [org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-3) Creating Service {http://test.jbws3792/}JBWS3792WSService from WSDL: http://localhost:8080/jbws3792-external-wsdl/jbws3792.wsdl 11:42:58,306 INFO [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-3) Setting the server's publish address to be http://localhost:8080/jbws3792-ws-impl/JBWS3792WSService 11:42:58,312 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jbws3792-ws-impl.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jbws3792-ws-impl.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154) at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.RuntimeException: JBWS024076: Service {http://test.jbws3792/}JBWS3792WSService, cannot publish wsdl to: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:109) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.publishContractToFilesystem(EndpointImpl.java:148) at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:85) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:255) at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:543) at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:231) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:97) at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:59) at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147) ... 5 more Caused by: java.io.FileNotFoundException: W:\workspace\eap-7x-jbossws-testsuite-windows\52dc560b\build\jboss-eap-7.0\standalone\data\wsdl\jbws3792-ws-impl.war\http:\localhost:8080\jbws3792-external-wsdl\jbws3792.wsdl (The filename, directory name, or volume label syntax is incorrect) at java.io.FileOutputStream.open0(Native Method) at java.io.FileOutputStream.open(FileOutputStream.java:270) at java.io.FileOutputStream.<init>(FileOutputStream.java:213) at java.io.FileOutputStream.<init>(FileOutputStream.java:162) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.writeDocument(WSDLFilePublisher.java:176) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:81) ... 14 more -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3870) Imported schemas in weird places in deployments causes issues

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3870?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3870: ---------------------------------- Fix Version/s: jbossws-cxf-5.1.0.Final (was: jbossws-cxf-5.2.0.Final) > Imported schemas in weird places in deployments causes issues > ------------------------------------------------------------- > > Key: JBWS-3870 > URL: https://issues.jboss.org/browse/JBWS-3870 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: R Searls > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.1.0.Final > > Attachments: schemasInWeirdPlaceFromSrc.zip > > > There is a customer that has placed their WSDL files under > WEB-INF/classes/wsdl rather than just WEB-INF/wsdl. They then put > their WSDL under a subdirectory of that folder, say "thewsdl". Then > that WSDL references other schemas in other subdirectories at the same > level as the WSDL's subdirectory. Like this: > WEB-INF/ > classes/ > wsdl/ > thewsdl/ > the-actual-wsdl.wsdl > schemas/ > some-schema.xsd > When this gets deployed, all the imported schemas fall outside the > deployment's data/wsdl folder when they are written to the filesystem. > Like this: > standalone/ > data/ > wsdl/ > myDeployment.war/ > <wsdl would go here> > schemas/ > some-schema.xsd > This can cause weird concurrency issues if multiple deployment > processor threads happen to be processing separate webservices where > each have WSDLs that happen to import schemas with the same schemaLocation > attribute. In the above scenario, the schemaLocation would include a > ".." since the WSDL would be in its own subfolder. > The code that writes these files to disk is here > Line 224: > https://anonsvn.jboss.org/repos/jbossws/common/tags/jbossws-common-2.3.1.... > Line 190: > https://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.3.... > The problem is that WSDLFilePublisher.getPublishLocation() cuts off > subfolders that the WSDL is under in this particular scenario, so when > the schemaLocation that has ".." in it is appended to the WSDL path, > it will write the schema outside the deployment's data/wsdl/ folder. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3870) Imported schemas in weird places in deployments causes issues

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3870?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3870: --------------------------------------- OK, the issue is fixed, but needs Apache CXF 3.1.3 to be available (basically the CXF-6552 changes) for passing the testcase. > Imported schemas in weird places in deployments causes issues > ------------------------------------------------------------- > > Key: JBWS-3870 > URL: https://issues.jboss.org/browse/JBWS-3870 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: R Searls > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > Attachments: schemasInWeirdPlaceFromSrc.zip > > > There is a customer that has placed their WSDL files under > WEB-INF/classes/wsdl rather than just WEB-INF/wsdl. They then put > their WSDL under a subdirectory of that folder, say "thewsdl". Then > that WSDL references other schemas in other subdirectories at the same > level as the WSDL's subdirectory. Like this: > WEB-INF/ > classes/ > wsdl/ > thewsdl/ > the-actual-wsdl.wsdl > schemas/ > some-schema.xsd > When this gets deployed, all the imported schemas fall outside the > deployment's data/wsdl folder when they are written to the filesystem. > Like this: > standalone/ > data/ > wsdl/ > myDeployment.war/ > <wsdl would go here> > schemas/ > some-schema.xsd > This can cause weird concurrency issues if multiple deployment > processor threads happen to be processing separate webservices where > each have WSDLs that happen to import schemas with the same schemaLocation > attribute. In the above scenario, the schemaLocation would include a > ".." since the WSDL would be in its own subfolder. > The code that writes these files to disk is here > Line 224: > https://anonsvn.jboss.org/repos/jbossws/common/tags/jbossws-common-2.3.1.... > Line 190: > https://anonsvn.jboss.org/repos/jbossws/stack/cxf/tags/jbossws-cxf-4.3.3.... > The problem is that WSDLFilePublisher.getPublishLocation() cuts off > subfolders that the WSDL is under in this particular scenario, so when > the schemaLocation that has ".." in it is appended to the WSDL path, > it will write the schema outside the deployment's data/wsdl/ folder. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3940) Update and migrate wsi bp tests suite with arquillian and new test utilties

by Jim Ma (JIRA)

Jim Ma created JBWS-3940: ---------------------------- Summary: Update and migrate wsi bp tests suite with arquillian and new test utilties Key: JBWS-3940 URL: https://issues.jboss.org/browse/JBWS-3940 Project: JBoss Web Services Issue Type: Enhancement Components: jbossws-cxf Affects Versions: jbossws-cxf-5.1.0.Beta1 Reporter: Jim Ma Fix For: jbossws-cxf-5.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3939) Provide testcase for WS-Eventing (WS-RA)

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3939: ------------------------------------- Summary: Provide testcase for WS-Eventing (WS-RA) Key: JBWS-3939 URL: https://issues.jboss.org/browse/JBWS-3939 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf, ws-eventing Reporter: Alessio Soldano Fix For: jbossws-cxf-5.2.0.Final WS-Eventing is included in Apache CXF since many months. We should add a testcase in JBossWS and possibly look at improvements needed for a real world use. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3938) Upgrade to Apache CXF 3.1.3

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-3938: ------------------------------------- Summary: Upgrade to Apache CXF 3.1.3 Key: JBWS-3938 URL: https://issues.jboss.org/browse/JBWS-3938 Project: JBoss Web Services Issue Type: Task Components: jbossws-cxf Reporter: Alessio Soldano Fix For: jbossws-cxf-5.1.0.Final -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues August 2015