October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-168) InjectionTarget.postConstruct is not called for EJB's

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-168?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-168: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > InjectionTarget.postConstruct is not called for EJB's > ----------------------------------------------------- > > Key: WFLY-168 > URL: https://issues.jboss.org/browse/WFLY-168 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.CR1 > > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-224) Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*"

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-224?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-224: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add allowed values for attribute "cache-type" in "/subsystem=security/security-domain=*" > ---------------------------------------------------------------------------------------- > > Key: WFLY-224 > URL: https://issues.jboss.org/browse/WFLY-224 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management, Security > Affects Versions: 8.0.0.Alpha1 > Reporter: Harald Pehl > Priority: Minor > Fix For: 8.0.0.CR1 > > > The attribute "cache-type" in "/subsystem=security/security-domain=*" can either be "default" or "infinispan". Please add the allowed value to the resource description. > In order to generate the UI based on the management model, it is essential that information like this is present. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-211) Expose client socket binding config through CLI connect configs

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-211?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-211: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Expose client socket binding config through CLI connect configs > --------------------------------------------------------------- > > Key: WFLY-211 > URL: https://issues.jboss.org/browse/WFLY-211 > Project: WildFly > Issue Type: Enhancement > Components: CLI > Reporter: Brian Stansberry > Assignee: Alexey Loubyansky > Fix For: 8.0.0.CR1 > > > Once AS7-6277 is done, continue exposing the client bind socket config to CLI users. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-215) Clustering tests leave a hanging instance if they are run in opposite order

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-215?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-215: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Clustering tests leave a hanging instance if they are run in opposite order > --------------------------------------------------------------------------- > > Key: WFLY-215 > URL: https://issues.jboss.org/browse/WFLY-215 > Project: WildFly > Issue Type: Enhancement > Components: Clustering, Test Suite > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 8.0.0.CR1 > > > Interestingly, if the tests are run in the opposite order i.e. alphabetically, one server instance remains running and doesn't shut down. > I have used a workaround for now > {code} > +  > + <runOrder>reversealphabetical</runOrder> > {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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-214) Consider logging "Number of cluster members" on view change like is done at server startup

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-214?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-214: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Consider logging "Number of cluster members" on view change like is done at server startup > ------------------------------------------------------------------------------------------ > > Key: WFLY-214 > URL: https://issues.jboss.org/browse/WFLY-214 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > Fix For: 8.0.0.CR1 > > > See https://community.jboss.org/message/754829#754829 > Could we just do the same as for the startup? -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-217) Strict location check of persistence.xml deployments

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-217?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-217: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Strict location check of persistence.xml deployments > ---------------------------------------------------- > > Key: WFLY-217 > URL: https://issues.jboss.org/browse/WFLY-217 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Reporter: Bartosz Baranowski > Assignee: Scott Marlow > Priority: Minor > Fix For: 8.0.0.CR1 > > > As of: https://github.com/jbossas/jboss-as/commit/38815193011fba624170a7d938118e... it is possible to deploy persistence.xml from invalid location: > As per JPA spec(https://docs.jboss.org/author/display/AS71/JPA+Reference+Guide), valid locations are: > - an EJB-JAR file > - the WEB-INF/classes directory of a WAR file > - a jar file in the WEB-INF/lib directory of a WAR file > - a jar file in the EAR library directory > - an application client jar file -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-207) Add start/stop operations to hornetq-server resource

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-207?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-207: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Add start/stop operations to hornetq-server resource > ---------------------------------------------------- > > Key: WFLY-207 > URL: https://issues.jboss.org/browse/WFLY-207 > Project: WildFly > Issue Type: Enhancement > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 8.0.0.CR1 > > > Currently it is not possible to start/stop a hornetq-server resource without removing or adding it. > For HornetQ replicated nodes, it'd be useful to be able to start/stop the node (runtime operations) without changing its configuration. That'd be necessary to restart replicated backup servers that have fallen back -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-228) TS: Migrate from Surefire to Failsafe maven plugin.

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-228?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-228: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > TS: Migrate from Surefire to Failsafe maven plugin. > --------------------------------------------------- > > Key: WFLY-228 > URL: https://issues.jboss.org/browse/WFLY-228 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Jakub Senko > Fix For: 8.0.0.CR1 > > Attachments: AS7-failsafe-surefire.html.zip > > > Surefire aims at unit testing. > Failsafe, unlike Surefire, binds to two build phases - integration-tests and verify. > That not only moves test execution to the correct phase, but also brings possibility to test several issues present in the testsuite - like skipping successive Surefire executions in a single module if former fails (not affected by -fae). > -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-209) Move ClientConfigurationImpl factory methods into ModelControllerClientConfiguration

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-209?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-209: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > Move ClientConfigurationImpl factory methods into ModelControllerClientConfiguration > ------------------------------------------------------------------------------------ > > Key: WFLY-209 > URL: https://issues.jboss.org/browse/WFLY-209 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Priority: Minor > Fix For: 8.0.0.CR1 > > > ClientConfigurationImpl includes a bunch of static factory methods that would fit better in a Factory class in the ModelControllerClientConfiguration interface. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-205) AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-205?page=com.atlassian.jira.plugin.s... ] Jason Greene updated WFLY-205: ------------------------------ Fix Version/s: 8.0.0.CR1 (was: 8.0.0.Beta1) > AttributeDefinition validateOperation should convert all expression strings to ModelType.EXPRESSION > --------------------------------------------------------------------------------------------------- > > Key: WFLY-205 > URL: https://issues.jboss.org/browse/WFLY-205 > Project: WildFly > Issue Type: Enhancement > Components: Domain Management > Reporter: Brian Stansberry > Fix For: 8.0.0.CR1 > > > AttributeDefinition.validateOperation currently only converts a string to an expression if the attribute supports expressions. It should convert any time it sees the syntax. This way if a STRING attribute that doesn't support expressions finds one, it will reject it instead of accepting it as a raw string. > Scheduling for 7.3 out of concern this may break things in 7.2 without time to notice/adapt. -- 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

11 years, 3 months

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 October 2013