[JBoss JIRA] (JBIDE-26634) Hibernate ITests are failing for specific runtimes
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBIDE-26634?page=com.atlassian.jira.plug... ]
Josef Kopriva reassigned JBIDE-26634:
-------------------------------------
Assignee: Josef Kopriva
> Hibernate ITests are failing for specific runtimes
> --------------------------------------------------
>
> Key: JBIDE-26634
> URL: https://issues.redhat.com/browse/JBIDE-26634
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, integration-tests
> Affects Versions: 4.12.0.AM1
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Priority: Major
> Fix For: 4.14.x
>
>
> Some Hibernate ITests are failing for specific runtimes: 3.5, 3.6, 4.0, 4.2, 5.2, 5.3, 5.4.
> {code:java}
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationFileTest.testCreateConfigurationFileWithConsole My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3] 1 min 6 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationFileTest.testCreateConfigurationFile My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3] 1 min 6 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationFileTest.createConfigurationFileFromDatasource My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3] 1 min 8 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationFileTest.testCreateConfigurationFileWithConsole My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4] 1 min 6 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationFileTest.testCreateConfigurationFile My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4] 1 min 6 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationFileTest.createConfigurationFileFromDatasource My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4] 1 min 8 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3] 1 min 12 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3] 1 min 12 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3] 1 min 12 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4] 1 min 12 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4] 1 min 12 sec 1
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4] 1 min 12 sec 1
> org.jboss.tools.hibernate.reddeer.test.HQLEditorTest.testHQLEditor My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.5] 22 sec 1
> org.jboss.tools.hibernate.reddeer.test.HQLEditorTest.testHQLEditor My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.6] 22 sec 1
> org.jboss.tools.hibernate.reddeer.test.HQLEditorTest.testHQLEditor My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 4.2] 21 sec 1
> org.jboss.tools.hibernate.reddeer.test.HQLEditorTest.testHQLEditor My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 4.2] 21 sec 1
> org.jboss.tools.hibernate.reddeer.test.RevengFileTest.testCreateRevengFile My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb 1 min 10 sec 1
> org.jboss.tools.hibernate.reddeer.test.RevengFileTest.testCreateRevengFile My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb 1 min 10 sec 1
> org.jboss.tools.hibernate.reddeer.test.TablesFromJPAEntitiesGeneration.testDDLGeneration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3 use console: true] 26 sec 1
> org.jboss.tools.hibernate.reddeer.test.TablesFromJPAEntitiesGeneration.testDDLGeneration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.3 use console: false] 26 sec 1
> org.jboss.tools.hibernate.reddeer.test.TablesFromJPAEntitiesGeneration.testDDLGeneration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4 use console: true] 26 sec 1
> org.jboss.tools.hibernate.reddeer.test.TablesFromJPAEntitiesGeneration.testDDLGeneration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.4 use console: false] 26 sec 1
> org.jboss.tools.hibernate.reddeer.test.CodeGenerationConfigurationTest.testHibernateGenerateConfigurationWithReveng My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.5] 2 min 29 sec 38
> org.jboss.tools.hibernate.reddeer.test.CodeGenerationConfigurationTest.testHibernateGenerateConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.5] 22 sec 38
> org.jboss.tools.hibernate.reddeer.test.CodeGenerationConfigurationTest.testHibernateGenerateConfigurationWithReveng My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.6] 31 sec 38
> org.jboss.tools.hibernate.reddeer.test.CodeGenerationConfigurationTest.testHibernateGenerateConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.6] 22 sec 38
> org.jboss.tools.hibernate.reddeer.test.CodeGenerationConfigurationTest.testHibernateGenerateConfigurationWithReveng My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 4.0] 35 sec 38
> org.jboss.tools.hibernate.reddeer.test.CodeGenerationConfigurationTest.testHibernateGenerateConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 4.0] 22 sec 38
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.5] 31 sec 38
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.6] 31 sec 38
> org.jboss.tools.hibernate.reddeer.test.ConsoleConfigurationTest.testConsoleConfiguration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 4.0] 31 sec 38
> org.jboss.tools.hibernate.reddeer.test.CriteriaEditorTest.testCriteriaEditorMvn35 My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.5] 27 sec 38
> org.jboss.tools.hibernate.reddeer.test.CriteriaEditorTest.testCriteriaEditorMvn35 My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 3.6] 25 sec 38
> org.jboss.tools.hibernate.reddeer.test.CriteriaEditorTest.testCriteriaEditorMvn35 My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 4.0] 25 sec 38
> org.jboss.tools.hibernate.reddeer.test.TablesFromJPAEntitiesGeneration.testDDLGeneration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.2 use console: true] 26 sec 91
> org.jboss.tools.hibernate.reddeer.test.TablesFromJPAEntitiesGeneration.testDDLGeneration My H2 Driver-Generic JDBC Driver-jdbc:h2:tcp://localhost/sakila-testdb [hibernate 5.2 use console: false]
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by André Dietisheim (Jira)
[ https://issues.redhat.com/browse/JBIDE-25303?page=com.atlassian.jira.plug... ]
André Dietisheim updated JBIDE-25303:
-------------------------------------
retargeting from 4.5.3.AM3 to the next release 4.14.0.Final
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.redhat.com/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.3.AM3, 4.14.0.Final
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> ** -Dfabric8.generator.from=fabric8/s2i-java
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-25303) Server adapter: support hot-deployment on OpenShift for SpringBoot app
by André Dietisheim (Jira)
[ https://issues.redhat.com/browse/JBIDE-25303?page=com.atlassian.jira.plug... ]
André Dietisheim updated JBIDE-25303:
-------------------------------------
Fix Version/s: 4.14.0.Final
> Server adapter: support hot-deployment on OpenShift for SpringBoot app
> ----------------------------------------------------------------------
>
> Key: JBIDE-25303
> URL: https://issues.redhat.com/browse/JBIDE-25303
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.1.Final
> Reporter: Aurélien Pupier
> Assignee: André Dietisheim
> Priority: Major
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.3.AM3, 4.14.0.Final
>
> Attachments: Image+Pasted+at+2018-1-16+10-58.png, docker-explorer-inspect-image.png, fuse-on-openshift.zip, project-deployment-assembly.png, screenshot-1.png, spring-boot-demo.zip
>
>
> currently, Springboot jar projects (such as Fuse Integration Services) are rsynced with a zipped jar file.
> The requirements are:
> - rsync unpacked jar
> - rsync without the jar name as folder
> - it will will work only if springboot devtool are included (so maybe need some dialog guiding user to do i in case it is not activated)
> use case "Develop SpringBoot application deployed on OpenShift as any other applications in JBoss Tools":
> - there is a SpringBoot app deployed on OpenShift
> - the developer want to develop evolution of the SpringBoot app
> -- when he/she modifies the project, the application needs to be automatically updated on OpenShift instance
> -- Remote java debug should be available when the OpenShift server adapter is in debug mode.
> Steps:
> # EXEC: create a project in your OpenShift server (ex. camel-ose-springboot)
> # EXEC: Import project within fuse-on-openshift.zip into your workspace
> # EXEC: open launch configuration and change:
> ** -Dkubernetes.master= so that it first your cdk instance
> ** -Dkubernetes.namespace= to the name of the project that you create in step 1.
> ** -Dfabric8.generator.from=fabric8/s2i-java
> # EXEC: run the launch config (that is included in the project), so that the project gets deployed to OpenShift (cdk)
> # ASSERT: your project in OpenShift now contains a service **camel-ose-springboot-xml**, the pod for it is running.
> # EXEC: in OpenShift Explorer: select this service and create a server adapter for it (*Server Adapter..* in the context menu for the service)
> # ASSERT: server adapter is created and is *[started]*
> # EXEC: in OpenShift Explorer: pick *Pod Log...* in the context menu for the pod of your service)
> # ASSERT: pod log is opened in "Console" view and shows an output with random numbers in the end
> {code}
> simple-route - >>> 455
> simple-route - >>> 695
> simple-route - >>> 935
> {code}
> # EXEC: In Project Explorer: open class MyTransformer and change the transform method
> # ASSERT: "Console" view is opened and shows how the server adapter is publishing the MyTransformer class to the pod
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27019) Show in -> Web console option does not work for CRC 1.3 as there is different end point url for this
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27019?page=com.atlassian.jira.plug... ]
Jeff MAURY updated JBIDE-27019:
-------------------------------
Sprint: devex #179 Jan/Feb 2020
> Show in -> Web console option does not work for CRC 1.3 as there is different end point url for this
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-27019
> URL: https://issues.redhat.com/browse/JBIDE-27019
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.14.0.AM1
> Reporter: Ondrej Dockal
> Assignee: André Dietisheim
> Priority: Critical
> Fix For: 4.14.0.Final
>
>
> Show in -> Web Console does not work for Openshift connection created from CRC 1.3 version as the Server's url (OS 4.2 endpoint - https://api.crc.testing:6443/) does not work for web console access. The correct one is https://console-openshift-console.apps-crc.testing/.
> I got this error stack trace, btw:
> {code}
> eclipse.buildId=12.14.0.AM1-v20200123-0055-B5802
> java.version=11.0.5
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/odockal/workspace_12140AM1-0123/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.core.jobs
> Error
> Mon Jan 27 15:12:23 CET 2020
> An internal error occurred during: "Retrieving console for https://api.crc.testing:6443...".
> com.openshift.restclient.UnsupportedEndpointException: Unable to determine the api endpoint for kind 'ConfigMap'
> at com.openshift.internal.restclient.URLBuilder.buildWithNamespaceInPath(URLBuilder.java:149)
> at com.openshift.internal.restclient.URLBuilder.build(URLBuilder.java:135)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:297)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:271)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:239)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:222)
> at com.openshift.internal.restclient.DefaultClient.get(DefaultClient.java:406)
> at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:93)
> at com.openshift.internal.restclient.capability.server.Console.getOpenShift4ConsoleUrl(Console.java:107)
> at com.openshift.internal.restclient.capability.server.Console.getConsoleUrl(Console.java:64)
> at org.jboss.tools.openshift.core.connection.Connection.getConsoleURL(Connection.java:381)
> at org.jboss.tools.openshift.internal.ui.handler.OpenInWebConsoleHandler.lambda$0(OpenInWebConsoleHandler.java:61)
> at org.eclipse.core.runtime.jobs.Job$1.run(Job.java:164)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27023) JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27023?page=com.atlassian.jira.plug... ]
Jeff MAURY commented on JBIDE-27023:
------------------------------------
What is the scenario to reproduce ?
> JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found
> --------------------------------------------------------------
>
> Key: JBIDE-27023
> URL: https://issues.redhat.com/browse/JBIDE-27023
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.14.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.14.0.Final
>
>
> javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2020-01-28 18:43:13.650
> !MESSAGE An internal error occurred during: "NLS missing message: JAXRSWSTestView_Invoking_WS_Status in: org.jboss.tools.ws.ui.messages.JBossWSUI".
> !STACK 0
> javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found
> at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:135)
> at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264)
> at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:123)
> at javax.xml.ws.spi.FactoryFinder.access$2(FactoryFinder.java:112)
> at javax.xml.ws.spi.FactoryFinder$3.run(FactoryFinder.java:255)
> at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264)
> at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:166)
> at javax.xml.ws.spi.Provider.provider(Provider.java:39)
> at javax.xml.ws.Service.<init>(Service.java:36)
> at javax.xml.ws.Service.create(Service.java:116)
> at org.jboss.tools.ws.jaxws.ui.tester.JAXWSTester2.doTest(JAXWSTester2.java:143)
> at org.jboss.tools.ws.jaxws.ui.view.JAXWSType.handleWSTest(JAXWSType.java:113)
> at org.jboss.tools.ws.ui.views.WebServicesTestView$16.run(WebServicesTestView.java:697)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27023) JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27023?page=com.atlassian.jira.plug... ]
Jeff MAURY updated JBIDE-27023:
-------------------------------
Fix Version/s: 4.14.0.Final
(was: 4.14.x)
Sprint: devex #179 Jan/Feb 2020
> JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found
> --------------------------------------------------------------
>
> Key: JBIDE-27023
> URL: https://issues.redhat.com/browse/JBIDE-27023
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.14.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.14.0.Final
>
>
> javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2020-01-28 18:43:13.650
> !MESSAGE An internal error occurred during: "NLS missing message: JAXRSWSTestView_Invoking_WS_Status in: org.jboss.tools.ws.ui.messages.JBossWSUI".
> !STACK 0
> javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found
> at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:135)
> at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264)
> at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:123)
> at javax.xml.ws.spi.FactoryFinder.access$2(FactoryFinder.java:112)
> at javax.xml.ws.spi.FactoryFinder$3.run(FactoryFinder.java:255)
> at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264)
> at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:166)
> at javax.xml.ws.spi.Provider.provider(Provider.java:39)
> at javax.xml.ws.Service.<init>(Service.java:36)
> at javax.xml.ws.Service.create(Service.java:116)
> at org.jboss.tools.ws.jaxws.ui.tester.JAXWSTester2.doTest(JAXWSTester2.java:143)
> at org.jboss.tools.ws.jaxws.ui.view.JAXWSType.handleWSTest(JAXWSType.java:113)
> at org.jboss.tools.ws.ui.views.WebServicesTestView$16.run(WebServicesTestView.java:697)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27023) JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found
by Ondrej Dockal (Jira)
Ondrej Dockal created JBIDE-27023:
-------------------------------------
Summary: JAXWS - Provider org.apache.axis2.jaxws.spi.Provider not found
Key: JBIDE-27023
URL: https://issues.redhat.com/browse/JBIDE-27023
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.14.0.AM1
Reporter: Ondrej Dockal
Assignee: Jeff MAURY
Fix For: 4.14.x
javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found
{code}
!ENTRY org.eclipse.core.jobs 4 2 2020-01-28 18:43:13.650
!MESSAGE An internal error occurred during: "NLS missing message: JAXRSWSTestView_Invoking_WS_Status in: org.jboss.tools.ws.ui.messages.JBossWSUI".
!STACK 0
javax.xml.ws.spi.FactoryFinder$ConfigurationError: Provider org.apache.axis2.jaxws.spi.Provider not found
at javax.xml.ws.spi.FactoryFinder$2.run(FactoryFinder.java:135)
at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264)
at javax.xml.ws.spi.FactoryFinder.newInstance(FactoryFinder.java:123)
at javax.xml.ws.spi.FactoryFinder.access$2(FactoryFinder.java:112)
at javax.xml.ws.spi.FactoryFinder$3.run(FactoryFinder.java:255)
at javax.xml.ws.spi.FactoryFinder.doPrivileged(FactoryFinder.java:264)
at javax.xml.ws.spi.FactoryFinder.find(FactoryFinder.java:166)
at javax.xml.ws.spi.Provider.provider(Provider.java:39)
at javax.xml.ws.Service.<init>(Service.java:36)
at javax.xml.ws.Service.create(Service.java:116)
at org.jboss.tools.ws.jaxws.ui.tester.JAXWSTester2.doTest(JAXWSTester2.java:143)
at org.jboss.tools.ws.jaxws.ui.view.JAXWSType.handleWSTest(JAXWSType.java:113)
at org.jboss.tools.ws.ui.views.WebServicesTestView$16.run(WebServicesTestView.java:697)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months