February 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2783) EmbeddedContainerConfiguration does not validate correctly

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2783?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-2783: ------------------------------ Component/s: Test Suite > EmbeddedContainerConfiguration does not validate correctly > ---------------------------------------------------------- > > Key: WFLY-2783 > URL: https://issues.jboss.org/browse/WFLY-2783 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Test Suite > Affects Versions: 8.0.0.CR1 > Reporter: Markus von Rüden > Priority: Minor > > I experimented a bit with arquillian and the embedded wildfly container. > However, durinng startup I am getting this exception: > {code} > java.lang.RuntimeException: JBAS011137: Cannot load module org.jboss.vfs from: local module loader @3a55b9b (finder: local module finder @5d211efb (roots: /home/username/dev/arquillian-tutorial/null/modules)) > {code} > So I took a deeper look at class > org.jboss.as.arquillian.container.embedded.EmbeddedContainerConfiguration located in "wildfly/arquillian/embedded" > The validate method there seems to have a validation problem: > {code} > @Override > public void validate() throws ConfigurationException { > super.validate(); > Validate.configurationDirectoryExists(jbossHome, "jbossHome '" + jbossHome + "' must exist"); > Validate.configurationDirectoryExists(jbossHome, "modulePath '" + modulePath + "' must exist"); > Validate.configurationDirectoryExists(jbossHome, "bundlePath '" + bundlePath + "' must exist"); > } > {code} > It checks jbossHome three times. But I assume it should check jbossHome, bundleHome and moduleHome instead. > I am not sure if the Exception and the validation-implementation are associated with each other in any way, but the validate() method looks wrong to me :) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2887) Build fail due to CalendarBasedTimeoutTestCase on OSX 7u51

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-2887?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-2887. ----------------------------- Resolution: Duplicate Issue duplicates WFLY-2881 > Build fail due to CalendarBasedTimeoutTestCase on OSX 7u51 > ---------------------------------------------------------- > > Key: WFLY-2887 > URL: https://issues.jboss.org/browse/WFLY-2887 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.CR1 > Reporter: Cody Lerum > > Cannot build from master (d7d7a1f) on OSX due to following failure > {code} > ------------------------------------------------------- > T E S T S > ------------------------------------------------------- > Running org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptorTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.316 sec - in org.jboss.as.ejb3.component.stateful.StatefulSessionSynchronizationInterceptorTestCase > Running org.jboss.as.ejb3.concurrency.EJBReadWriteLockTest > Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.012 sec - in org.jboss.as.ejb3.concurrency.EJBReadWriteLockTest > Running org.jboss.as.ejb3.deployment.processors.ViewInterfacesTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.02 sec - in org.jboss.as.ejb3.deployment.processors.ViewInterfacesTestCase > Running org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase > Tests run: 14, Failures: 0, Errors: 0, Skipped: 7, Time elapsed: 3.227 sec - in org.jboss.as.ejb3.subsystem.Ejb3SubsystemUnitTestCase > Running org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase > Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.786 sec <<< FAILURE! - in org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase > testCalendarBasedTimeout(org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase) Time elapsed: 0.785 sec <<< FAILURE! > java.lang.AssertionError: Cuba Standard Time > at org.junit.Assert.fail(Assert.java:88) > at org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.testWithStartInThePast(CalendarBasedTimeoutTestCase.java:496) > at org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutTestCase.testCalendarBasedTimeout(CalendarBasedTimeoutTestCase.java:95) > Running org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutWithDifferentTimeZoneTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in org.jboss.as.ejb3.timer.schedule.CalendarBasedTimeoutWithDifferentTimeZoneTestCase > Running org.jboss.as.ejb3.timer.schedule.CalendarUtilTestCase > Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in org.jboss.as.ejb3.timer.schedule.CalendarUtilTestCase > Running org.jboss.as.ejb3.timer.schedule.RangeValueTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in org.jboss.as.ejb3.timer.schedule.RangeValueTestCase > Results : > Failed tests: > CalendarBasedTimeoutTestCase.testCalendarBasedTimeout:95->testWithStartInThePast:496 Cuba Standard Time > Tests run: 31, Failures: 1, Errors: 0, Skipped: 7 > {code} > Environment > {code} > mbp:jboss-as codylerum$ mvn install -rf :wildfly-ejb3 -XX > Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 09:22:22-0600) > Maven home: /usr/local/Cellar/maven/3.1.1/libexec > Java version: 1.7.0_51, vendor: Oracle Corporation > Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "10.9.1", arch: "x86_64", family: "mac" > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-679) Arquillian Managed Container does not honor configured ports

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-679?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar resolved WFLY-679. ------------------------------ Fix Version/s: 8.0.0.Final (was: Awaiting Volunteers) Resolution: Done This was fixed some time ago. > Arquillian Managed Container does not honor configured ports > ------------------------------------------------------------ > > Key: WFLY-679 > URL: https://issues.jboss.org/browse/WFLY-679 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Karel Piwko > Fix For: 8.0.0.Final > > > When starting a managed container, following configuration is not used by Arquillian: > {code} > <container qualifier="container" default="true"> > <configuration> > <property name="jbossHome">target/jbossas-2</property> > <property name="managementPort">19999</property> > <property name="jmxPort">1190</property> > <property name="httpPort">8180</property> > <property name="startupTimeoutInSeconds">180</property> > </configuration> >  > <protocol type="jmx-as7"> > <configuration> > <property name="executionType">REMOTE</property> > </configuration> > </protocol> > </container> > {code} > The standalone container is always started on default ports, e.g. 9999, 1099, 8080. > The ports are defined in standalone.xml and it seems difficult to change them without touching the file. See > http://community.jboss.org/thread/168140 for related question. > This makes customization of the test runs with managed containers difficult and for clusters even more difficult. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1657) Facilitate the use of groovy java ee

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1657?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1657: ------------------------------ Fix Version/s: Awaiting Volunteers > Facilitate the use of groovy java ee > ------------------------------------ > > Key: WFLY-1657 > URL: https://issues.jboss.org/browse/WFLY-1657 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 8.0.0.Alpha1, 8.0.0.Alpha2 > Reporter: Gilliard Cordeiro > Fix For: Awaiting Volunteers > > > disregard GroovyObject interface when read interfaces of the bean. > Thus POGO (Plain Old Groovy Objects) can be non-interface session beans. > It is a EJB feature (https://java.net/jira/browse/EJB_SPEC-108), but until the specification does not possess it, could be a feature of WildFly -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1020) Add DeploymentModulePermission

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1020?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1020: ------------------------------ Component/s: Server > Add DeploymentModulePermission > ------------------------------ > > Key: WFLY-1020 > URL: https://issues.jboss.org/browse/WFLY-1020 > Project: WildFly > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Server > Reporter: David Lloyd > Assignee: David Lloyd > > Add a permission which governs the ability of a deployment to load a specific module. The permission should be checked at deploy time for every explicitly added module dependency. > It may also be wise to automatically add permissions for each implicit module as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1005) Upgrade to joda time 2.1

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1005?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1005: ------------------------------ Component/s: Build System > Upgrade to joda time 2.1 > ------------------------ > > Key: WFLY-1005 > URL: https://issues.jboss.org/browse/WFLY-1005 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: Build System > Environment: - > Reporter: Wouter Oet > > JBoss AS 7.1.1 ships with Joda-time 1.6.2, however the newer version 2.1 is available and contains bugfixes and improvements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-910) Using an annotation from a private api module does not result in a warning

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-910?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated WFLY-910: ----------------------------- Component/s: Class Loading > Using an annotation from a private api module does not result in a warning > -------------------------------------------------------------------------- > > Key: WFLY-910 > URL: https://issues.jboss.org/browse/WFLY-910 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading > Reporter: Carlo de Wolf > > If an user deployment uses an annotation from a module that is marked as private there is no warning being emitted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-910) Using an annotation from a private api module does not result in a warning

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-910?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar updated WFLY-910: ----------------------------- Affects Version/s: JBoss AS7 7.2.0.Final > Using an annotation from a private api module does not result in a warning > -------------------------------------------------------------------------- > > Key: WFLY-910 > URL: https://issues.jboss.org/browse/WFLY-910 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading > Affects Versions: JBoss AS7 7.2.0.Final > Reporter: Carlo de Wolf > > If an user deployment uses an annotation from a module that is marked as private there is no warning being emitted. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-854) Grails app load with Jboss 7

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-854?page=com.atlassian.jira.plugin.s... ] Tomaz Cerar resolved WFLY-854. ------------------------------ Fix Version/s: 8.0.0.Final Resolution: Done This should be fixed in WildFly 8, given that we dont ship OSGI subsystem anymore. > Grails app load with Jboss 7 > ---------------------------- > > Key: WFLY-854 > URL: https://issues.jboss.org/browse/WFLY-854 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: Grails 1.3.4 and 2.0 > Reporter: David Pugh > Fix For: 8.0.0.Final > > Attachments: MANIFEST.MF > > > When deploying any Grails 1.3.4 or 2.0 project with Jboss 7 final version, the Grails project deploys properly but > the gsp pages in the project will not actually be loaded by the Jboss server. > There are not errors listed in the server log. > I am aware of this bug https://issues.jboss.org/browse/AS7-2941, which of course displays errors, > but with the new 7.1.0 final versions no errors are displayed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1006) Upgrade XOM to 1.2.10

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-1006?page=com.atlassian.jira.plugin.... ] Tomaz Cerar updated WFLY-1006: ------------------------------ Summary: Upgrade XOM to 1.2.10 (was: Upgrade XOM to 1.2.7) > Upgrade XOM to 1.2.10 > --------------------- > > Key: WFLY-1006 > URL: https://issues.jboss.org/browse/WFLY-1006 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: XML Frameworks > Reporter: Júlio Pires > Assignee: Tomaz Cerar > Fix For: 8.0.1.Final > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2014