December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4009) Cannot externalise camel-cdi & deltaspike

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4009?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4009: ----------------------------- Fix Version/s: 9.0.0.Final > Cannot externalise camel-cdi & deltaspike > ----------------------------------------- > > Key: WFLY-4009 > URL: https://issues.jboss.org/browse/WFLY-4009 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Affects Versions: 8.1.0.Final > Reporter: Thomas Diesler > Assignee: Stuart Douglas > Fix For: 9.0.0.Final > > > Currently, there is a webapp deployed as part of the camel subsystem that contains > * camel-cdi > * deltaspike-core-api > * deltaspike-core-impl > * deltaspike-cdictrl-api > Generally it seems that every webapp needs to package these in order for camel-cdi to work. We would however like to replace these embedded jars with references to the already existing modules. > GitHub Issue: https://github.com/tdiesler/wildfly-camel/issues/15 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4267) Add Archetype integration test for HTML5 archetype

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4267?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4267: ----------------------------- Fix Version/s: 9.0.0.Final > Add Archetype integration test for HTML5 archetype > -------------------------------------------------- > > Key: WFLY-4267 > URL: https://issues.jboss.org/browse/WFLY-4267 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3739) Change Arquillian containers to launch the process using the launcher API in core

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3739?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3739: ----------------------------- Fix Version/s: 9.0.0.Final > Change Arquillian containers to launch the process using the launcher API in core > --------------------------------------------------------------------------------- > > Key: WFLY-3739 > URL: https://issues.jboss.org/browse/WFLY-3739 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: James Perkins > Assignee: James Perkins > Fix For: 9.0.0.Final > > > WildFly Core now includes a launcher API to generate the commands and optionally launch a WildFly process. Arquillian should be changed to use this API rather than relying on creating the commands and the process on it's own. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3014) jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3014?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3014: ----------------------------- Fix Version/s: 9.0.0.Final > jboss-web schema not hosted at http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd > --------------------------------------------------------------------------------- > > Key: WFLY-3014 > URL: https://issues.jboss.org/browse/WFLY-3014 > Project: WildFly > Issue Type: Feature Request > Affects Versions: 8.0.0.Final > Environment: Not applicable > Reporter: Ray DeCampo > Assignee: ehsavoie Hugonnet > Priority: Minor > Labels: xml, xml_schema > Fix For: 9.0.0.Final > > > The docs/schema/jboss-web_8_0.xsd file included with WildFly 8.0.0.Final indicates that the schema location is http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd. However, that URI does not return the schema file but a 404 instead (see http://www.jboss.org/j2ee/schema/ for a listing of the files there). > The file should be hosted where the schema document indicates or the schema should be updated to reflect the proper URI of the schema. Without it third party tools cannot assist in ensuring that the XML is well-formed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-2401) org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2401?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-2401: ----------------------------- Fix Version/s: 9.0.0.Final > org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase fails > -------------------------------------------------------------- > > Key: WFLY-2401 > URL: https://issues.jboss.org/browse/WFLY-2401 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Beta1 > Environment: Solaris SPARC 10, Oracle Java 1.7.0_45 > Reporter: Frank Langelage > Assignee: Emanuel Muckenhuber > Fix For: 9.0.0.Final > > Attachments: org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase.txt > > > Running a build of current sources with complete testsuite this test is failing with > testReadAttributeWildcards(org.jboss.as.test.smoke.mgmt.BasicOperationsUnitTestCase) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1783) IIOPNamingTestCase is failing when run on IBM JDK

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1783?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1783: ----------------------------- Fix Version/s: 9.0.0.Final > IIOPNamingTestCase is failing when run on IBM JDK > ------------------------------------------------- > > Key: WFLY-1783 > URL: https://issues.jboss.org/browse/WFLY-1783 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 8.0.0.Alpha3 > Environment: ibm jdk > Reporter: Ondra Chaloupka > Assignee: Ondra Chaloupka > Fix For: 9.0.0.Final > > > Testcase org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingTestCase is failing when is run on IBM JDK with message > Unable to load class: org.jboss.as.test.integration.ejb.iiop.naming._IIOPNamingHome_Stub > The stack trace: > {code} > java.lang.ClassCastException: Unable to load class: org.jboss.as.test.integration.ejb.iiop.naming._IIOPNamingHome_Stub > at com.ibm.rmi.javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:356) > at javax.rmi.PortableRemoteObject.narrow(PortableRemoteObject.java:148) > at org.jboss.as.test.integration.ejb.iiop.naming.IIOPNamingTestCase.testIIOPNamingInvocation(IIOPNamingTestCase.java:65) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.jboss.arquillian.junit.Arquillian$6$1.invoke(Arquillian.java:270) > at org.jboss.arquillian.container.test.impl.execution.LocalTestExecuter.execute(LocalTestExecuter.java:60) > at sun.reflect.GeneratedMethodAccessor43.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115) > at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67) > at org.jboss.arquillian.container.test.impl.execution.ClientTestExecuter.execute(ClientTestExecuter.java:53) > at sun.reflect.GeneratedMethodAccessor13.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createContext(ContainerEventController.java:142) > at org.jboss.arquillian.container.test.impl.client.ContainerEventController.createTestContext(ContainerEventController.java:129) > at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createTestContext(TestContextHandler.java:89) > at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createClassContext(TestContextHandler.java:75) > at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.test.impl.TestContextHandler.createSuiteContext(TestContextHandler.java:60) > at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:90) > at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:88) > at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135) > at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.test(EventTestRunnerAdaptor.java:111) > at org.jboss.arquillian.junit.Arquillian$6.evaluate(Arquillian.java:263) > at org.jboss.arquillian.junit.Arquillian$4.evaluate(Arquillian.java:226) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$5.evaluate(Arquillian.java:240) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.jboss.arquillian.junit.Arquillian$2.evaluate(Arquillian.java:185) > at org.jboss.arquillian.junit.Arquillian.multiExecute(Arquillian.java:314) > at org.jboss.arquillian.junit.Arquillian.access$100(Arquillian.java:46) > at org.jboss.arquillian.junit.Arquillian$3.evaluate(Arquillian.java:199) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:147) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:234) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:133) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:114) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) > at java.lang.reflect.Method.invoke(Method.java:611) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:188) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:166) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:86) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:101) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:74) > {code} > The reason seem to be that the stubs are not generated. As I found there is no option to force jdk generate stubs on the fly (oracle jdk knows -Dcom.sun.CORBA.ORBUseDynamicStub=true) and the generation of stubs have to be done manually e.g. with rmic tool. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1648) Access control response inconsistencies

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1648?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1648: ----------------------------- Fix Version/s: 9.0.0.Final > Access control response inconsistencies > --------------------------------------- > > Key: WFLY-1648 > URL: https://issues.jboss.org/browse/WFLY-1648 > Project: WildFly > Issue Type: Task > Components: Domain Management > Reporter: Heiko Braun > Assignee: Kabir Khan > Fix For: 9.0.0.Final > > > See > a) https://gist.github.com/heiko-braun/5932594 > b) https://gist.github.com/heiko-braun/5932604 > Questions: > - in b) line 35: Why is there an additional nested "result" element? > - in b) line 99: Why is the "access-control" element empty? > (both cases need top be compared with a. ) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1035) jboss-javaee6-webapp-archetype : upgrade hibernate-jpamodelgen and hibernate-jpa-2.0-api for .factorypath

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-1035?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-1035: ----------------------------- Fix Version/s: 9.0.0.Final > jboss-javaee6-webapp-archetype : upgrade hibernate-jpamodelgen and hibernate-jpa-2.0-api for .factorypath > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-1035 > URL: https://issues.jboss.org/browse/WFLY-1035 > Project: WildFly > Issue Type: Enhancement > Reporter: Fred Bricon > Assignee: Pete Muir > Fix For: 9.0.0.Final > > Attachments: factorypath.pdf > > > hibernate-jpamodelgen has version 1.1.1.Final, and version 1.2.0.Final is available. > hibernate-jpa-2.0-api has version 1.0.0.Final, and version 1.0.1.Final is available. > I'll attach a screenshot to illustrate the current settings for .factorypath. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3944) Broken integration between messaging subsystem and jgroups subsystem

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3944?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-3944: ----------------------------- Fix Version/s: 9.0.0.Final > Broken integration between messaging subsystem and jgroups subsystem > -------------------------------------------------------------------- > > Key: WFLY-3944 > URL: https://issues.jboss.org/browse/WFLY-3944 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Brian Stansberry > Assignee: Paul Ferraro > Priority: Critical > Fix For: 9.0.0.Final > > > The integration between messaging and jgroups is currently broken. My guess is this was due to recent changes in clustering. > To reproduce it change the bg-group1 element in standalone-full-ha.xml to replace the socket-binding element with the following: > {code} > <jgroups-stack>udp</jgroups-stack> > <jgroups-channel>hq-bg</jgroups-channel> >  > {code} > At boot this appears in the logs: > {code} > 10:00:58,707 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging"), > ("hornetq-server" => "default") > ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.jgroups.stack.udp]"]} > 10:00:58,930 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report > WFLYCTL0184: New missing/unsatisfied dependencies: > service jboss.jgroups.stack.udp (missing) dependents: [service jboss.messaging.default] > {code} > WFLY-3943 is about the lack of testing of this integration, -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4191) Provide cheatsheet.xml for Kitchensink Quickstarts

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4191?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-4191: ----------------------------- Fix Version/s: 9.0.0.Final > Provide cheatsheet.xml for Kitchensink Quickstarts > -------------------------------------------------- > > Key: WFLY-4191 > URL: https://issues.jboss.org/browse/WFLY-4191 > Project: WildFly > Issue Type: Enhancement > Reporter: Rafael Benevides > Assignee: Rafael Benevides > Labels: quickstart, quickstarts > Fix For: 9.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017