November 2015 - jbossws-issues - Jboss List Archives

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3959: --------------------------------------- well, then I really need to try the SwitchYard app and figure out how to get it back working. The change that is affecting you is most likely this https://github.com/jbossws/jbossws-cxf/commit/fcf95cb4c718187945074eab0e1... , which was a fix to JBWS-3941 / JBEAP-857. Will work on this next week. > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Tomohisa igarashi (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Tomohisa igarashi commented on JBWS-3959: ----------------------------------------- Tried cherry-picking it over 5.1.0.Final and replaced jbossws-cxf-server jar, then I got this {code} JBWS022092: Could not resolve content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/LibraryTypes.xsd in deployment {code} vfs:/ is ommitted? I guess vfs:/ is needed to resolve this file via ClassLoader#getResource() > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3959: --------------------------------------- mmmh... I've just spotted something in the code that might be the culprit, perhaps you can try pulling this fix: https://github.com/jbossws/jbossws-cxf/commit/e109e4daa84a68b0b6db2e7864b... ? > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3959: ---------------------------------- Assignee: Alessio Soldano > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Tomohisa igarashi (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Tomohisa igarashi commented on JBWS-3959: ----------------------------------------- Here is the application, but it's a SwitchYard application and need to setup SwitchYard on top of EAP/WildFly. Plus WildFly10 support is still under development. https://github.com/jboss-switchyard/switchyard/tree/master/quickstarts/de... This is the WSDL file importing LibraryTypes.xsd: https://github.com/jboss-switchyard/switchyard/blob/master/quickstarts/de... And the LibraryTypes.xsd is in same path: https://github.com/jboss-switchyard/switchyard/blob/master/quickstarts/de... Does it help? > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > Fix For: jbossws-cxf-5.2.0.Final > > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3959: --------------------------------------- Any chance you can provide a reproducer for this or better clarify what you mean with "The importing XSD file in a same jar" condition and hence how should I build up a deployment jar to reproduce the issue? > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > Fix For: jbossws-cxf-5.2.0.Final > > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3959: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.0.Final > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > Fix For: jbossws-cxf-5.2.0.Final > > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3957) publishWsdlImports writes WSDL-XML files with wrong characterset under Windows

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3957?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-3957: --------------------------------------- Martin, I've patched the AbstractWSDLFilePublisher as shown at https://github.com/jbossws/jbossws-common/commit/88dc3e05a00164adb0fb782c... . I believe that should solve your problem, but it would be great if you could check / try the fix. Besides that, few comments on the discussion above: * JSR 109 actually requires us to write the published wsdl to the disk too (there few TCK tests covering this) * you're right in saying that publish to disk could be performed in a more efficient way, as basically when there're xsd imports within imported wsdl, the imported wsdl is written and re-read again; feel free to send a patch/improvement for that and/or open up a jira * wsdl4j looks to be in EOL mode (or dead, call it as you want), I've had bad luck too in the past proposing patches. > publishWsdlImports writes WSDL-XML files with wrong characterset under Windows > ------------------------------------------------------------------------------ > > Key: JBWS-3957 > URL: https://issues.jboss.org/browse/JBWS-3957 > Project: JBoss Web Services > Issue Type: Bug > Environment: WildFly 9, Windows 7 with default Java file.encoding Cp1252. > Reporter: Martin Both > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > I would like to deploy a WebService but I get an exception. The WSDL XSD file contains an german character 'ä'. See: > Here is the part of the XSD: > <xs:simpleType name="Teilnehmerart"> > <xs:restriction base="xs:string"> > <xs:enumeration value="Privat"></xs:enumeration> > <xs:enumeration value="Geschäftlich"></xs:enumeration> > </xs:restriction> > </xs:simpleType> > The JBoss class org.jboss.ws.common.utils.AbstractWSDLFilePublisher > writes the imported WSDL file using a FileWriter at line 166 + 167. > FileWriter fw = new FileWriter(targetFile); > wsdlWriter.writeWSDL(subdef, fw); > In a next step this file is read again and results in an exception: > Invalid byte 2 of 3-byte UTF-8 sequence. > This is because the file is written in Cp1252 enconding together with an XML prolog > UTF-8 encoding. That is crazy and cannot work. > A workaround would be to set the Java file.encoding to UTF-8 but that is not what I want. > There are two solutions: > I think it is better to create a binary OutputStream instead of creating a FileWriter. > The wsdlWriter offers two methods! The method with OutputStream argument would always write XML files using a UTF-8 encoding. > An other way to fix that would be a bug fix to WSDL4J 1.6.3. > The WSDL4J method com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Definition wsdlDef, Writer sink) does map default Java file.encoding to "UTF-8". That is sometimes wrong. > The class com.ibm.wsdl.util.xml.DOM2Writer should have an XmlEncodingMapping from "Cp1252" to "Windows-1252". That would fix the problem also. But I think it would be better to use always UTF-8 with the OutputStream method. > Best regards > Martin Both -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3957) publishWsdlImports writes WSDL-XML files with wrong characterset under Windows

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-3957?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-3957: ---------------------------------- Assignee: Alessio Soldano (was: Jim Ma) > publishWsdlImports writes WSDL-XML files with wrong characterset under Windows > ------------------------------------------------------------------------------ > > Key: JBWS-3957 > URL: https://issues.jboss.org/browse/JBWS-3957 > Project: JBoss Web Services > Issue Type: Bug > Environment: WildFly 9, Windows 7 with default Java file.encoding Cp1252. > Reporter: Martin Both > Assignee: Alessio Soldano > Fix For: jbossws-cxf-5.2.0.Final > > > I would like to deploy a WebService but I get an exception. The WSDL XSD file contains an german character 'ä'. See: > Here is the part of the XSD: > <xs:simpleType name="Teilnehmerart"> > <xs:restriction base="xs:string"> > <xs:enumeration value="Privat"></xs:enumeration> > <xs:enumeration value="Geschäftlich"></xs:enumeration> > </xs:restriction> > </xs:simpleType> > The JBoss class org.jboss.ws.common.utils.AbstractWSDLFilePublisher > writes the imported WSDL file using a FileWriter at line 166 + 167. > FileWriter fw = new FileWriter(targetFile); > wsdlWriter.writeWSDL(subdef, fw); > In a next step this file is read again and results in an exception: > Invalid byte 2 of 3-byte UTF-8 sequence. > This is because the file is written in Cp1252 enconding together with an XML prolog > UTF-8 encoding. That is crazy and cannot work. > A workaround would be to set the Java file.encoding to UTF-8 but that is not what I want. > There are two solutions: > I think it is better to create a binary OutputStream instead of creating a FileWriter. > The wsdlWriter offers two methods! The method with OutputStream argument would always write XML files using a UTF-8 encoding. > An other way to fix that would be a bug fix to WSDL4J 1.6.3. > The WSDL4J method com.ibm.wsdl.xml.WSDLWriterImpl.writeWSDL(Definition wsdlDef, Writer sink) does map default Java file.encoding to "UTF-8". That is sometimes wrong. > The class com.ibm.wsdl.util.xml.DOM2Writer should have an XmlEncodingMapping from "Cp1252" to "Windows-1252". That would fix the problem also. But I think it would be better to use always UTF-8 with the OutputStream method. > Best regards > Martin Both -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBWS-3959) schema import failure - JBWS022092: Could not resolve vfs%3A/content...

by Tomohisa igarashi (JIRA)

[ https://issues.jboss.org/browse/JBWS-3959?page=com.atlassian.jira.plugin.... ] Tomohisa igarashi updated JBWS-3959: ------------------------------------ Description: The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. {code} &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl ..... (snip) ..... Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) ... 11 more Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) ... 24 more {code} was: The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode (%3A=>:) is not processed for the XSD path. {code} &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl ..... (snip) ..... Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) ... 11 more Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) ... 24 more {code} > schema import failure - JBWS022092: Could not resolve vfs%3A/content... > ----------------------------------------------------------------------- > > Key: JBWS-3959 > URL: https://issues.jboss.org/browse/JBWS-3959 > Project: JBoss Web Services > Issue Type: Bug > Affects Versions: jbossws-cxf-5.1.0.Final > Reporter: Tomohisa igarashi > > The importing XSD file in a same jar can't be resolved during WSDL publishing. I hit this issue on WildFly10 CR4/JBossWS 5.1.0.Final, and this sample application is working fine on EAP6/WildFly8.0. > On EAP6/WildFly8.0, the xsd path starts with "vfs:/content" at ResourceResolverImpl#resolve(), but on WF10 it's "vfs%3A/content". It seems like the required decode ("%3A"=>":") is not processed for the XSD path. > {code} > &#27;[0m&#27;[31m16:39:41,215 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.jboss.msc.service.StartException in service jboss.deployment.unit."switchyard-demo-library-2.1.0-SNAPSHOT.jar".SwitchYardService: org.switchyard.component.soap.WebServicePublishException: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > ..... (snip) ..... > Caused by: java.lang.RuntimeException: JBWS024076: Service {urn:switchyard-quickstart-demo:library:1.0}SuggestionService, cannot publish wsdl to: /home/tomo/workspace/SwitchYard/switchyard/release/jboss-as7/wildfly/dist/target/jboss-switchyard/wildfly-10.0.0.CR4/standalone/data/wsdl/suggestion.deployment/vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/SuggestionService.wsdl > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:113) > 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.ws.common.deployment.DeploymentAspectManagerImpl.deploy(DeploymentAspectManagerImpl.java:118) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.doDeploy(EndpointPublisherImpl.java:163) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:114) > at org.jboss.as.webservices.publish.EndpointPublisherImpl.publish(EndpointPublisherImpl.java:107) > at org.switchyard.as7.extension.ws.JBossWSEndpoint.publish(JBossWSEndpoint.java:103) > at org.switchyard.as7.extension.ws.JBossWSEndpointPublisher.publish(JBossWSEndpointPublisher.java:89) > ... 11 more > Caused by: java.io.IOException: JBWS022092: Could not resolve vfs%3A/content/switchyard-demo-library-2.1.0-SNAPSHOT.jar/META-INF/LibraryTypes.xsd in deployment suggestion.deployment > at org.jboss.ws.common.deployment.ResourceResolverImpl.resolve(ResourceResolverImpl.java:128) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:234) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:259) > at org.jboss.ws.common.utils.AbstractWSDLFilePublisher.publishSchemaImports(AbstractWSDLFilePublisher.java:263) > at org.jboss.wsf.stack.cxf.deployment.WSDLFilePublisher.publishWsdlFiles(WSDLFilePublisher.java:98) > ... 24 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 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 November 2015