[JBoss JIRA] (WFLY-5052) NoClassDefFoundError at JAX-WS webservice deployment
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5052?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5052.
----------------------------
> NoClassDefFoundError at JAX-WS webservice deployment
> ----------------------------------------------------
>
> Key: WFLY-5052
> URL: https://issues.jboss.org/browse/WFLY-5052
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 9.0.1.Final
> Reporter: Gregory Lardiere
> Assignee: Alessio Soldano
> Fix For: 10.0.0.Beta1
>
> Attachments: SampleWS.war, SampleWS.zip
>
>
> The exception *java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaAllMember* is thrown when deploying a JAX-WS webservice :
> {code}
> 2015-08-04 16:32:18,222 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."SampleWS.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."SampleWS.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "SampleWS.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NoClassDefFoundError: org/apache/ws/commons/schema/XmlSchemaAllMember
> at org.apache.cxf.common.xmlschema.SchemaCollection.addCrossImports(SchemaCollection.java:315)
> at org.apache.cxf.common.xmlschema.SchemaCollection.addCrossImportsType(SchemaCollection.java:307)
> at org.apache.cxf.common.xmlschema.SchemaCollection.addOneSchemaCrossImports(SchemaCollection.java:252)
> at org.apache.cxf.common.xmlschema.SchemaCollection.addCrossImports(SchemaCollection.java:236)
> at org.apache.cxf.jaxb.JAXBSchemaInitializer.buildExceptionType(JAXBSchemaInitializer.java:605)
> at org.apache.cxf.jaxb.JAXBSchemaInitializer.checkForExistence(JAXBSchemaInitializer.java:326)
> at org.apache.cxf.jaxb.JAXBSchemaInitializer.begin(JAXBSchemaInitializer.java:150)
> at org.apache.cxf.service.ServiceModelVisitor.visitOperation(ServiceModelVisitor.java:120)
> at org.apache.cxf.service.ServiceModelVisitor.walk(ServiceModelVisitor.java:74)
> at org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:403)
> at org.apache.cxf.service.factory.AbstractServiceFactoryBean.initializeDataBindings(AbstractServiceFactoryBean.java:86)
> at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass(ReflectionServiceFactoryBean.java:467)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.buildServiceFromClass(JaxWsServiceFactoryBean.java:712)
> at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.initializeServiceModel(ReflectionServiceFactoryBean.java:527)
> at org.apache.cxf.wsdl.service.factory.ReflectionServiceFactoryBean.create(ReflectionServiceFactoryBean.java:261)
> at org.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsServiceFactoryBean.java:215)
> at org.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(AbstractWSDLBasedEndpointFactory.java:102)
> at org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:159)
> at org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:211)
> at org.apache.cxf.jaxws.EndpointImpl.getServer(EndpointImpl.java:456)
> at org.apache.cxf.jaxws.EndpointImpl.doPublish(EndpointImpl.java:334)
> at org.jboss.wsf.stack.cxf.deployment.EndpointImpl.doPublish(EndpointImpl.java:79)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:251)
> at org.apache.cxf.jaxws.EndpointImpl.publish(EndpointImpl.java:539)
> at org.jboss.wsf.stack.cxf.configuration.NonSpringBusHolder.configure(NonSpringBusHolder.java:119)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.startDeploymentBus(BusDeploymentAspect.java:120)
> at org.jboss.wsf.stack.cxf.deployment.aspect.BusDeploymentAspect.start(BusDeploymentAspect.java:66)
> at org.jboss.as.webservices.deployers.AspectDeploymentProcessor.deploy(AspectDeploymentProcessor.java:73)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> Caused by: java.lang.ClassNotFoundException: org.apache.ws.commons.schema.XmlSchemaAllMember from [Module "org.apache.cxf:main" from local module loader @14899482 (finder: local module finder @21588809 (roots: /tmp/wildfly-9.0.1.Final/modules,/tmp/wildfly-9.0.1.Final/modules/system/layers/base))]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> ... 34 more
> {code}
> Replacing xmlschema-core-2.0.2.jar with xmlschema-core-2.2.1.jar fixes this problem.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-4871) Upgrade to Hibernate Search 5.3.0.Final
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4871?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4871.
----------------------------
> Upgrade to Hibernate Search 5.3.0.Final
> ---------------------------------------
>
> Key: WFLY-4871
> URL: https://issues.jboss.org/browse/WFLY-4871
> Project: WildFly
> Issue Type: Component Upgrade
> Components: JPA / Hibernate
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 10.0.0.Alpha5
>
>
> The main reason for this upgrade is that some changes are needed in modules structure between Hibernate Search 5.2 to 5.3.
> Wildfly is currently using HS 5.2 but will require >=5.4 to be compatible with Hibernate ORM 5.
> So applying this intermediate step towards HS 5.3 will make the Hibernate ORM 5 pull request easier.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-4925) Admin in Monitor role can execute test-connection-in-pool op
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4925?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4925.
----------------------------
> Admin in Monitor role can execute test-connection-in-pool op
> ------------------------------------------------------------
>
> Key: WFLY-4925
> URL: https://issues.jboss.org/browse/WFLY-4925
> Project: WildFly
> Issue Type: Bug
> Components: JCA
> Affects Versions: 10.0.0.Alpha5
> Reporter: Brian Stansberry
> Assignee: Jesper Pedersen
> Fix For: 10.0.0.Alpha6
>
>
> This should not work, as the Monitor role is not allowed to do anything that modifies any state:
> {code}
> [standalone@localhost:9990 data-source=ExampleDS] :test-connection-in-pool{roles=Monitor}
> {
> "outcome" => "success",
> "result" => [true]
> }
> {code}
> I believe the problem is PoolOperations L75:
> {code}
> final ServiceController<?> managementRepoService = context.getServiceRegistry(false).getService(
> ConnectorServices.MANAGEMENT_REPOSITORY_SERVICE);
> {code}
> The parameter to context.getServiceRegistry(...) must be 'true' if the operation is going to use the returned service registry to perform any form of state modification. So I believe all the PoolOperation subclasses should provide a param to PoolOperation's constructor that can be used to set this value. I believe in all subclasses except DumpQueuedThreadInPool this param should be 'true'.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-4532) Clean up jboss-as-web_2_*.xsd schemas
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-4532?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-4532.
----------------------------
> Clean up jboss-as-web_2_*.xsd schemas
> -------------------------------------
>
> Key: WFLY-4532
> URL: https://issues.jboss.org/browse/WFLY-4532
> Project: WildFly
> Issue Type: Sub-task
> Components: Web (Undertow)
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 9.0.0.CR2, 10.0.0.Alpha1
>
>
> The last jboss-as-web schema included in a community release is jboss-as-web_2_0.xsd
> JBoss EAP contains both jboss-as-web_2_1.xsd and jboss-as-web_2_2.xsd
> I believe something was mistakenly added to the 2.1 schema in EAP, this was forward ported to WildFly - then the change to 2.1 was reverted in EAP and a 2.2 schema added.
> Version 2.1 and 2.2 of the schemas need porting from EAP to WildFly and the parsers updated to support them accordingly.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months
[JBoss JIRA] (WFLY-5320) Jacorb :migrate operation does not return migration-warnings
by Kabir Khan (JIRA)
[ https://issues.jboss.org/browse/WFLY-5320?page=com.atlassian.jira.plugin.... ]
Kabir Khan closed WFLY-5320.
----------------------------
> Jacorb :migrate operation does not return migration-warnings
> ------------------------------------------------------------
>
> Key: WFLY-5320
> URL: https://issues.jboss.org/browse/WFLY-5320
> Project: WildFly
> Issue Type: Task
> Components: IIOP
> Affects Versions: 10.0.0.CR1
> Reporter: Ondra Chaloupka
> Assignee: Tomasz Adamski
> Fix For: 10.0.0.CR1
>
> Attachments: standalone-full.tomig.inital.xml
>
>
> If I run migrate operation on jacorb subsystem the result of the operation is
> {code}
> /subsystem=jacorg:migrate()
> {
> "outcome" => "success",
> "result" => undefined
> }
> {code}
> But the result should be
> {code}
> {
> "outcome" => "success",
> "result" => {"migration-warnings" => []}
> }
> {code}
> Try the same with messaging or web subsystem
> {code}
> /subsystem=web:migrate()
> {
> "outcome" => "success",
> "result" => {"migration-warnings" => []}
> {code}
> To reproduce
> - compile latest wildfly from github
> - use the attached file standalone-full.tomig.inital.xml
> - {{./bin/standalone.sh -c standalone-full.tomig.initial.xml --admin-only}}
> - ./bin/jboss-cli.sh -c --controller=remote://localhost:9999
> - /subsystem=jacorb:migrate()
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 7 months