February 2018 - jbossws-issues - Jboss List Archives

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4099?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4099: ---------------------------------- Fix Version/s: jbossws-cxf-5.2.1.Final > JDK10 support > ------------- > > Key: JBWS-4099 > URL: https://issues.jboss.org/browse/JBWS-4099 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.0.Final > Reporter: Jan Blizňák > Fix For: jbossws-cxf-5.2.1.Final > > > With JDK10 release coming within weeks we should enable JBWS to build and test also on this JDK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4099) JDK10 support

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4099?page=com.atlassian.jira.plugin.... ] Jan Blizňák edited comment on JBWS-4099 at 2/20/18 10:38 AM: ------------------------------------------------------------- There are not many changes from JDK9, as a first step it should be enough to activate already existing 'JDK9' profiles with modular arguments, these are in jbossws-parent and jbossws-cxf, just change the enforcer rule to open interval: {code:xml} <jdk>[9,)</jdk> {code} There is also an issue with surefire plugin 2.20.1 not working on JKD10 at the moment, 2.19.1 works for now; fixed in 2.21.0, it will be released soon. was (Author: jbliznak): There are not many changes from JDK9, as a first step it should be enough to activate already existing 'JDK9' profiles with modular arguments, these are in jbossws-parent and jbossws-cxf, just change the enforcer rule to open interval: {code:xml} <jdk>[9,)</jdk> {code} There is also an issue with surefire plugin 2.20.1 not working on JKD10 at the moment, 2.19.1 works for now. > JDK10 support > ------------- > > Key: JBWS-4099 > URL: https://issues.jboss.org/browse/JBWS-4099 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.0.Final > Reporter: Jan Blizňák > > With JDK10 release coming within weeks we should enable JBWS to build and test also on this JDK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4099) JDK10 support

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4099?page=com.atlassian.jira.plugin.... ] Jan Blizňák commented on JBWS-4099: ----------------------------------- There are not many changes from JDK9, as a first step it should be enough to activate already existing 'JDK9' profiles with modular arguments, these are in jbossws-parent and jbossws-cxf, just change the enforcer rule to open interval: {code:xml} <jdk>[9,)</jdk> {code} There is also an issue with surefire plugin 2.20.1 not working on JKD10 at the moment, 2.19.1 works for now. > JDK10 support > ------------- > > Key: JBWS-4099 > URL: https://issues.jboss.org/browse/JBWS-4099 > Project: JBoss Web Services > Issue Type: Feature Request > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.0.Final > Reporter: Jan Blizňák > > With JDK10 release coming within weeks we should enable JBWS to build and test also on this JDK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4099) JDK10 support

by Jan Blizňák (JIRA)

Jan Blizňák created JBWS-4099: --------------------------------- Summary: JDK10 support Key: JBWS-4099 URL: https://issues.jboss.org/browse/JBWS-4099 Project: JBoss Web Services Issue Type: Feature Request Components: jbossws-cxf Affects Versions: jbossws-cxf-5.2.0.Final Reporter: Jan Blizňák With JDK10 release coming within weeks we should enable JBWS to build and test also on this JDK. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4098) Testsuite server logging doesn't work after migration to gmavenplus-plugin

by Jan Blizňák (JIRA)

[ https://issues.jboss.org/browse/JBWS-4098?page=com.atlassian.jira.plugin.... ] Jan Blizňák updated JBWS-4098: ------------------------------ Git Pull Request: https://github.com/jbossws/jbossws-cxf/pull/41 > Testsuite server logging doesn't work after migration to gmavenplus-plugin > -------------------------------------------------------------------------- > > Key: JBWS-4098 > URL: https://issues.jboss.org/browse/JBWS-4098 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Affects Versions: jbossws-cxf-5.2.0.Final > Reporter: Jan Blizňák > Assignee: Jan Blizňák > Priority: Minor > > Setting '-DenableServerLoggingToConsole' property has no effect on testsuite run, it stopped working after gmaven-plugin was migrated to gmavenplus-plugin. It seems the new plugin doesn't pass the commandline parameters the same way the old plugin did. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4098) Testsuite server logging doesn't work after migration to gmavenplus-plugin

by Jan Blizňák (JIRA)

Jan Blizňák created JBWS-4098: --------------------------------- Summary: Testsuite server logging doesn't work after migration to gmavenplus-plugin Key: JBWS-4098 URL: https://issues.jboss.org/browse/JBWS-4098 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Affects Versions: jbossws-cxf-5.2.0.Final Reporter: Jan Blizňák Assignee: Jan Blizňák Priority: Minor Setting '-DenableServerLoggingToConsole' property has no effect on testsuite run, it stopped working after gmaven-plugin was migrated to gmavenplus-plugin. It seems the new plugin doesn't pass the commandline parameters the same way the old plugin did. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4097) JAX-WS Client does not unmarshal array property

by Viral Gohel (JIRA)

Viral Gohel created JBWS-4097: --------------------------------- Summary: JAX-WS Client does not unmarshal array property Key: JBWS-4097 URL: https://issues.jboss.org/browse/JBWS-4097 Project: JBoss Web Services Issue Type: Bug Components: jbossws-cxf Reporter: Viral Gohel The link, https://docs.oracle.com/cd/E19355-01/820-1072/ahiid/index.html it suggests that JAXBElement is required also if there are element nillable="true" and minOccurs="0" or if there are two global elements with the same named xsd:complexType. We always need a client to be regenerated using a jaxbBindings.xml with the option <jaxb:globalBindings generateElementProperty="false" />, the web service client is working. Some of the implementation except CXF, work without having the file, jaxbBindings.xml file. Is that an issue with jbossws-cxf ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4096) Testsuite failures with JDK9 and WFLY 12.0.0.Beta1

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4096?page=com.atlassian.jira.plugin.... ] Alessio Soldano commented on JBWS-4096: --------------------------------------- The failures go away with the upgrade of JBoss Modules from 1.7.0.Beta3 to 1.7.0.Final. > Testsuite failures with JDK9 and WFLY 12.0.0.Beta1 > -------------------------------------------------- > > Key: JBWS-4096 > URL: https://issues.jboss.org/browse/JBWS-4096 > Project: JBoss Web Services > Issue Type: Bug > Reporter: Alessio Soldano > Assignee: R Searls > Priority: Critical > Fix For: jbossws-cxf-5.2.1.Final > > > We have multiple failures when testing jbossws-cxf master against latest WildFly master. > {noformat} > [ERROR] Failures: > [ERROR] JBWS3628TestCase.testWSDL:72->checkPolicyReference:86->Assert.assertTrue:41->Assert.fail:88 WSDL does not contain policy reference to 'WS-Addressing_policy' > [ERROR] SchemaValidationTestCase.testSchemaValidationEndpoint:98->Assert.assertTrue:41->Assert.fail:88 not respect to enumration error is expected > [ERROR] SignEncryptTestCase.testServerSide:134->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testSignEncrypt: javax.xml.ws.soap.SOAPFaultException A security error was encountered when verifying the message]> > [ERROR] SignEncryptTestCase.testServerSideUsingConfigProperties:143->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testSignEncryptUsingConfigProperties: javax.xml.ws.soap.SOAPFaultException A security error was encountered when verifying the message]> > [ERROR] Errors: > [ERROR] PolicyAttachmentTestCase.testEndpointWithCustomWSSEAndWSA:141 » SOAPFault The ... > [ERROR] PolicyAttachmentTestCase.testEndpointWithWSSEAndWSA:112 » SOAPFault The signat... > [ERROR] MultipleClientsSignEncryptTestCase.testAlice:106 Error The signature or decry... > [ERROR] MultipleClientsSignEncryptTestCase.testJohn:126 Error The signature or decryp... > [ERROR] SignEncryptTestCase.testClientSide:114 » SOAPFault The signature or decryption... > [ERROR] SignEncryptTestCase.testClientSideUsingConfigProperties:125 » SOAPFault Unmars... > [ERROR] WSSecurityPolicyExamples22xTestCase.test224:188 » SOAPFault The signature or d... > [ERROR] WSTrustTestCase.testBearer:539 » SOAPFault The signature or decryption was inv... > [ERROR] WSTrustTestCase.testHolderOfKey:482 » SOAPFault The signature or decryption wa... > [INFO] > [ERROR] Tests run: 240, Failures: 4, Errors: 9, Skipped: 1 > {noformat} > {noformat} > [ERROR] Failures: > [ERROR] DefaultSchemaValidationTestCaseForked.testDefaultClientValidation:105->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: testDefaultClientValidation # Error tests: ]> > [ERROR] DefaultSchemaValidationTestCaseForked.testDefaultServerValidation:152->Assert.assertTrue:52->Assert.assertTrue:41->Assert.fail:86 > [INFO] > [ERROR] Tests run: 7, Failures: 2, Errors: 0, Skipped: 0 > {noformat} > {noformat} > [ERROR] Failures: > [ERROR] ClientConfigurationTestCase.testConfigurationChangeOnDispatchInContainer:226->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testConfigurationChangeOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> > [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationFromFileUsingFeatureOnDispatchInContainer:190->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationFromFileUsingFeatureOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> > [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationOnDispatchFromFileInContainer:160->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationOnDispatchFromFile: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> > [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationOnDispatchInContainer:292->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> > [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationOnDispatchUsingFeatureInContainer:306->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationOnDispatchUsingFeature: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> > [ERROR] ClientConfigurationTestCase.testDefaultClientConfigurationOnDispatchInContainer:247->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testDefaultClientConfigurationOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> > [ERROR] Errors: > [ERROR] HttpJAXBTestCase.testProviderDispatch:93 » HTTP > [ERROR] ProviderJAXBTestCase.testProviderDispatch:93 » HTTP > [INFO] > [ERROR] Tests run: 427, Failures: 6, Errors: 2, Skipped: 7 > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4096) Testsuite failures with JDK9 and WFLY 12.0.0.Beta1

by Alessio Soldano (JIRA)

Alessio Soldano created JBWS-4096: ------------------------------------- Summary: Testsuite failures with JDK9 and WFLY 12.0.0.Beta1 Key: JBWS-4096 URL: https://issues.jboss.org/browse/JBWS-4096 Project: JBoss Web Services Issue Type: Bug Reporter: Alessio Soldano Assignee: R Searls Priority: Critical Fix For: jbossws-cxf-5.2.1.Final We have multiple failures when testing jbossws-cxf master against latest WildFly master. {noformat} [ERROR] Failures: [ERROR] JBWS3628TestCase.testWSDL:72->checkPolicyReference:86->Assert.assertTrue:41->Assert.fail:88 WSDL does not contain policy reference to 'WS-Addressing_policy' [ERROR] SchemaValidationTestCase.testSchemaValidationEndpoint:98->Assert.assertTrue:41->Assert.fail:88 not respect to enumration error is expected [ERROR] SignEncryptTestCase.testServerSide:134->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testSignEncrypt: javax.xml.ws.soap.SOAPFaultException A security error was encountered when verifying the message]> [ERROR] SignEncryptTestCase.testServerSideUsingConfigProperties:143->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testSignEncryptUsingConfigProperties: javax.xml.ws.soap.SOAPFaultException A security error was encountered when verifying the message]> [ERROR] Errors: [ERROR] PolicyAttachmentTestCase.testEndpointWithCustomWSSEAndWSA:141 » SOAPFault The ... [ERROR] PolicyAttachmentTestCase.testEndpointWithWSSEAndWSA:112 » SOAPFault The signat... [ERROR] MultipleClientsSignEncryptTestCase.testAlice:106 Error The signature or decry... [ERROR] MultipleClientsSignEncryptTestCase.testJohn:126 Error The signature or decryp... [ERROR] SignEncryptTestCase.testClientSide:114 » SOAPFault The signature or decryption... [ERROR] SignEncryptTestCase.testClientSideUsingConfigProperties:125 » SOAPFault Unmars... [ERROR] WSSecurityPolicyExamples22xTestCase.test224:188 » SOAPFault The signature or d... [ERROR] WSTrustTestCase.testBearer:539 » SOAPFault The signature or decryption was inv... [ERROR] WSTrustTestCase.testHolderOfKey:482 » SOAPFault The signature or decryption wa... [INFO] [ERROR] Tests run: 240, Failures: 4, Errors: 9, Skipped: 1 {noformat} {noformat} [ERROR] Failures: [ERROR] DefaultSchemaValidationTestCaseForked.testDefaultClientValidation:105->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: testDefaultClientValidation # Error tests: ]> [ERROR] DefaultSchemaValidationTestCaseForked.testDefaultServerValidation:152->Assert.assertTrue:52->Assert.assertTrue:41->Assert.fail:86 [INFO] [ERROR] Tests run: 7, Failures: 2, Errors: 0, Skipped: 0 {noformat} {noformat} [ERROR] Failures: [ERROR] ClientConfigurationTestCase.testConfigurationChangeOnDispatchInContainer:226->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testConfigurationChangeOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationFromFileUsingFeatureOnDispatchInContainer:190->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationFromFileUsingFeatureOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationOnDispatchFromFileInContainer:160->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationOnDispatchFromFile: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationOnDispatchInContainer:292->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> [ERROR] ClientConfigurationTestCase.testCustomClientConfigurationOnDispatchUsingFeatureInContainer:306->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testCustomClientConfigurationOnDispatchUsingFeature: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> [ERROR] ClientConfigurationTestCase.testDefaultClientConfigurationOnDispatchInContainer:247->JBossWSTest.assertEquals:332->Assert.assertEquals:144->Assert.assertEquals:115 expected:<[1]> but was:<[# Failed tests: # Error tests: testDefaultClientConfigurationOnDispatch: javax.xml.parsers.FactoryConfigurationError Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found]> [ERROR] Errors: [ERROR] HttpJAXBTestCase.testProviderDispatch:93 » HTTP [ERROR] ProviderJAXBTestCase.testProviderDispatch:93 » HTTP [INFO] [ERROR] Tests run: 427, Failures: 6, Errors: 2, Skipped: 7 {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBWS-4095) Cannot register web service, fails with NullPointerException in DelegateClassLoader

by Alessio Soldano (JIRA)

[ https://issues.jboss.org/browse/JBWS-4095?page=com.atlassian.jira.plugin.... ] Alessio Soldano updated JBWS-4095: ---------------------------------- Assignee: R Searls (was: Alessio Soldano) > Cannot register web service, fails with NullPointerException in DelegateClassLoader > ----------------------------------------------------------------------------------- > > Key: JBWS-4095 > URL: https://issues.jboss.org/browse/JBWS-4095 > Project: JBoss Web Services > Issue Type: Bug > Components: jbossws-cxf > Reporter: Antonio Chirizzi > Assignee: R Searls > Fix For: jbossws-cxf-5.2.1.Final > > > While deploying a EAR application, which contains a WAR which is trying to register a web service, I get the follwing exception: > {code} > 13:53:34,624 INFO [org.jboss.ws.cxf.deployment] (MSC service thread 1-7) JBWS024074: WSDL published to: file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/standalone/data/wsdl/dms-new-ear-services-0.0.8.1.ear/dms-new-war-0.0.7.1.war/BusinessWebServiceService.wsdl > 13:53:34,658 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/ws/jaxws-client/main/jbossws-cxf-client-5.1.9.Final.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar. > 13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-tools-wsdlto-frontend-jaxws-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar. > 13:53:34,659 WARNING [org.apache.cxf.catalog.OASISCatalogManager] (MSC service thread 1-7) Catalog found at jar:file:/home/achirizzi/sandbox/dev/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/apache/cxf/impl/main/cxf-services-ws-discovery-api-3.1.12.jar!/META-INF/jax-ws-catalog.xml but no org.apache.xml.resolver.CatalogManager was found. Check the classpatch for an xmlresolver jar. > 13:53:34,773 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-7) MSC000001: Failed to start service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.subunit."dms-new-ear-services-0.0.8.1.ear"."dms-new-war-0.0.7.1.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of subdeployment "dms-new-war-0.0.7.1.war" of deployment "dms-new-ear-services-0.0.8.1.ear" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > Caused by: javax.xml.parsers.FactoryConfigurationError: Provider __redirected.__DocumentBuilderFactory could not be instantiated: java.lang.NullPointerException > at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:204) > at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:152) > at javax.xml.parsers.FactoryFinder.find(FactoryFinder.java:232) > at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:120) > at com.ibm.wsdl.xml.WSDLReaderImpl.getDocument(WSDLReaderImpl.java:2180) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2390) > at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:2422) > at org.apache.cxf.wsdl11.WSDLManagerImpl.loadDefinition(WSDLManagerImpl.java:238) > at org.apache.cxf.wsdl11.WSDLManagerImpl.getDefinition(WSDLManagerImpl.java:163) > at org.apache.cxf.wsdl11.WSDLServiceFactory.<init>(WSDLServiceFactory.java:85) > at org.apache.cxf.jaxws.ServiceImpl.initializePorts(ServiceImpl.java:217) > at org.apache.cxf.jaxws.ServiceImpl.initialize(ServiceImpl.java:160) > at org.apache.cxf.jaxws.ServiceImpl.<init>(ServiceImpl.java:129) > at org.jboss.wsf.stack.cxf.client.ProviderImpl$JBossWSServiceImpl.<init>(ProviderImpl.java:574) > at org.jboss.wsf.stack.cxf.client.ProviderImpl.createServiceDelegate(ProviderImpl.java:258) > at javax.xml.ws.Service.<init>(Service.java:57) > at com.tullettprebon.dms.tmmalternativeaddress.ws.TMMMarkitWireService.<init>(TMMMarkitWireService.java:60) > at com.tullettprebon.dms.webservices.ReferenceWebService.<init>(ReferenceWebService.java:232) > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at org.jboss.wsf.stack.cxf.configuration.BusHolder.newInstance(BusHolder.java:322) > at org.jboss.wsf.stack.cxf.configuration.BusHolder.configure(BusHolder.java:212) > 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:165) > ... 5 more > Caused by: java.lang.NullPointerException > at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132) > at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147) > at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102) > at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98) > at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103) > at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192) > ... 33 more > {code} > I wasted 3 days trying to find a solution thinking that the problem was in my dependencies with xerces or any other xml resolver. > Then I decided to checkout the code near the root cause: > {code} > Caused by: java.lang.NullPointerException > at org.jboss.ws.common.utils.DelegateClassLoader.getResourceAsStream(DelegateClassLoader.java:132) > at __redirected.__RedirectedUtils.findProviderClassNames(__RedirectedUtils.java:147) > at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:102) > at __redirected.__RedirectedUtils.loadProvider(__RedirectedUtils.java:98) > at __redirected.__DocumentBuilderFactory.<init>(__DocumentBuilderFactory.java:103) > at sun.reflect.GeneratedConstructorAccessor62.newInstance(Unknown Source) > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:423) > at java.lang.Class.newInstance(Class.java:442) > at javax.xml.parsers.FactoryFinder.newInstance(FactoryFinder.java:192) > ... 33 more > {code} > and I think I have fixed a bug in {{jbossws-common-3.1.5}}. > I have downloaded the latest version of {{jbossws-common-master}} from github (with which the problem was still showing). > Then I fixed the class {{org/jboss/ws/common/utils/DelegateClassLoader.java}} changing this: > {code} > /** {@inheritDoc} */ > @Override > public InputStream getResourceAsStream(final String name) > { > InputStream is = parent.getResourceAsStream(name); > return (is == null) ? delegate.getResourceAsStream(name) : is; > } > {code} > to this: > {code} > /** {@inheritDoc} */ > @Override > public InputStream getResourceAsStream(final String name) > { > InputStream is = null; > if (parent != null) > { > is = parent.getResourceAsStream(name); > } > return (is == null) ? delegate.getResourceAsStream(name) : is; > } > {code} > and then built again the jbossws-common jar and replaced the (suspected) faulty one under the WildFly modules. With the new jar the webservice can be registered. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 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 February 2018