July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1796) Creating a pooled-connection-factory via the CLI requires confusing syntax

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFLY-1796?page=com.atlassian.jira.plugin.... ] Justin Bertram updated WFLY-1796: --------------------------------- > Creating a pooled-connection-factory via the CLI requires confusing syntax > -------------------------------------------------------------------------- > > Key: WFLY-1796 > URL: https://issues.jboss.org/browse/WFLY-1796 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha3 > Reporter: Justin Bertram > Assignee: Jeff Mesnil > > When creating a pooled-connection factory via the CLI the syntax for the "connector" is confusing. Here is a simple example: > {noformat} > /subsystem=messaging/hornetq-server=default/pooled-connection-factory=my-pooled-connection-factory/:add(connector={"in-vm" => "xyz"}, entries=["java:/MyPooledCF"]) > {noformat} > The "connector" wants a list of name-value pairs, but only the name is taken into consideration. This command results in this XML: > {noformat} > <pooled-connection-factory name="my-pooled-connection-factory"> > <connectors> > <connector-ref connector-name="in-vm"/> > </connectors> > <entries> > <entry name="java:/MyPooledCF"/> > </entries> > </pooled-connection-factory> > {noformat} > I believe this is because {{org.jboss.as.messaging.jms.ConnectionFactoryAttributes.Common#CONNECTOR}} is defined as a {{org.jboss.as.controller.SimpleMapAttributeDefinition}} and it should probably just be a {{org.jboss.as.controller.PrimitiveListAttributeDefinition}} when used in the pooled-connection-factory. -- 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-1796) Creating a pooled-connection-factory via the CLI requires confusing syntax

by Justin Bertram (JIRA)

[ https://issues.jboss.org/browse/WFLY-1796?page=com.atlassian.jira.plugin.... ] Justin Bertram updated WFLY-1796: --------------------------------- Description: When creating a pooled-connection factory via the CLI the syntax for the "connector" is confusing. Here is a simple example: {noformat} /subsystem=messaging/hornetq-server=default/pooled-connection-factory=my-pooled-connection-factory/:add(connector={"in-vm" => "xyz"}, entries=["java:/MyPooledCF"]) {noformat} The "connector" wants a list of name-value pairs, but only the name is taken into consideration. This command results in this XML: {noformat} <pooled-connection-factory name="my-pooled-connection-factory"> <connectors> <connector-ref connector-name="in-vm"/> </connectors> <entries> <entry name="java:/MyPooledCF"/> </entries> </pooled-connection-factory> {noformat} The "xyz" is completely unnecessary. I believe this is because {{org.jboss.as.messaging.jms.ConnectionFactoryAttributes.Common#CONNECTOR}} is defined as a {{org.jboss.as.controller.SimpleMapAttributeDefinition}} and it should probably just be a {{org.jboss.as.controller.PrimitiveListAttributeDefinition}} when used in the pooled-connection-factory. was: When creating a pooled-connection factory via the CLI the syntax for the "connector" is confusing. Here is a simple example: {noformat} /subsystem=messaging/hornetq-server=default/pooled-connection-factory=my-pooled-connection-factory/:add(connector={"in-vm" => "xyz"}, entries=["java:/MyPooledCF"]) {noformat} The "connector" wants a list of name-value pairs, but only the name is taken into consideration. This command results in this XML: {noformat} <pooled-connection-factory name="my-pooled-connection-factory"> <connectors> <connector-ref connector-name="in-vm"/> </connectors> <entries> <entry name="java:/MyPooledCF"/> </entries> </pooled-connection-factory> {noformat} I believe this is because {{org.jboss.as.messaging.jms.ConnectionFactoryAttributes.Common#CONNECTOR}} is defined as a {{org.jboss.as.controller.SimpleMapAttributeDefinition}} and it should probably just be a {{org.jboss.as.controller.PrimitiveListAttributeDefinition}} when used in the pooled-connection-factory. > Creating a pooled-connection-factory via the CLI requires confusing syntax > -------------------------------------------------------------------------- > > Key: WFLY-1796 > URL: https://issues.jboss.org/browse/WFLY-1796 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 8.0.0.Alpha3 > Reporter: Justin Bertram > Assignee: Jeff Mesnil > > When creating a pooled-connection factory via the CLI the syntax for the "connector" is confusing. Here is a simple example: > {noformat} > /subsystem=messaging/hornetq-server=default/pooled-connection-factory=my-pooled-connection-factory/:add(connector={"in-vm" => "xyz"}, entries=["java:/MyPooledCF"]) > {noformat} > The "connector" wants a list of name-value pairs, but only the name is taken into consideration. This command results in this XML: > {noformat} > <pooled-connection-factory name="my-pooled-connection-factory"> > <connectors> > <connector-ref connector-name="in-vm"/> > </connectors> > <entries> > <entry name="java:/MyPooledCF"/> > </entries> > </pooled-connection-factory> > {noformat} > The "xyz" is completely unnecessary. > I believe this is because {{org.jboss.as.messaging.jms.ConnectionFactoryAttributes.Common#CONNECTOR}} is defined as a {{org.jboss.as.controller.SimpleMapAttributeDefinition}} and it should probably just be a {{org.jboss.as.controller.PrimitiveListAttributeDefinition}} when used in the pooled-connection-factory. -- 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-1795) WildFly's favicon.ico is outdated (shows 7 AS instead of WildFly)

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-1795?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-1795: ------------------------------------- Unless the console packages it's own favicon, the one in the welcome content directory is the WildFly icon. > WildFly's favicon.ico is outdated (shows 7 AS instead of WildFly) > ----------------------------------------------------------------- > > Key: WFLY-1795 > URL: https://issues.jboss.org/browse/WFLY-1795 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.0.0.Alpha4 > Reporter: Frank Langelage > Assignee: Heiko Braun > Priority: Minor > > The favicon.ico used for the WildFly console show still "7 AS". > Should be changed to a WildFly icon. -- 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-1795) WildFly's favicon.ico is outdated (shows 7 AS instead of WildFly)

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/WFLY-1795?page=com.atlassian.jira.plugin.... ] Frank Langelage commented on WFLY-1795: --------------------------------------- This one might be a good replacement: http://www.wildfly.org/favicon.ico > WildFly's favicon.ico is outdated (shows 7 AS instead of WildFly) > ----------------------------------------------------------------- > > Key: WFLY-1795 > URL: https://issues.jboss.org/browse/WFLY-1795 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 8.0.0.Alpha4 > Reporter: Frank Langelage > Assignee: Heiko Braun > Priority: Minor > > The favicon.ico used for the WildFly console show still "7 AS". > Should be changed to a WildFly icon. -- 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-1795) WildFly's favicon.ico is outdated (shows 7 AS instead of WildFly)

by Frank Langelage (JIRA)

Frank Langelage created WFLY-1795: ------------------------------------- Summary: WildFly's favicon.ico is outdated (shows 7 AS instead of WildFly) Key: WFLY-1795 URL: https://issues.jboss.org/browse/WFLY-1795 Project: WildFly Issue Type: Bug Components: Web Console Affects Versions: 8.0.0.Alpha4 Reporter: Frank Langelage Assignee: Heiko Braun Priority: Minor The favicon.ico used for the WildFly console show still "7 AS". Should be changed to a WildFly icon. -- 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-1794) CDI JSF apps get WELD-001529 warning

by Stan Silvert (JIRA)

Stan Silvert created WFLY-1794: ---------------------------------- Summary: CDI JSF apps get WELD-001529 warning Key: WFLY-1794 URL: https://issues.jboss.org/browse/WFLY-1794 Project: WildFly Issue Type: Bug Components: CDI / Weld, JSF Affects Versions: 8.0.0.Alpha4 Reporter: Stan Silvert Assignee: Stan Silvert Fix For: 8.0.0.Alpha4 With the latest version of Weld, JSF apps that use CDI now get this warning: {noformat} 14:42:20,862 WARN [org.jboss.weld.Bean] (MSC service thread 1-2) WELD-001529 An InjectionTarget is created for a class org.jboss.as.jsf.injection.weld.WeldApplicationFactory which does not have any appropriate constructor. {noformat} -- 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-1782) ASYNC-tcp tests should have cacheMode set to ASYNC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1782?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1782: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=989543 (was: https://bugzilla.redhat.com/show_bug.cgi?id=989543, https://bugzilla.redhat.com/show_bug.cgi?id=990114) > ASYNC-tcp tests should have cacheMode set to ASYNC > -------------------------------------------------- > > Key: WFLY-1782 > URL: https://issues.jboss.org/browse/WFLY-1782 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 8.0.0.Alpha4 > > > testsuite/integration/clust/pom.xml > <cacheMode>SYNC</cacheMode> is used for SYNC-tcp tests instead of <cacheMode>ASYNC</cacheMode> -- 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-1793) integration tests - allow modules to inherit properties variables

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1793?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-1793: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=990114 > integration tests - allow modules to inherit properties variables > ----------------------------------------------------------------- > > Key: WFLY-1793 > URL: https://issues.jboss.org/browse/WFLY-1793 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: No Release > Reporter: Aleksandar Kostadinov > Assignee: Ondrej Zizka > > Seems like surefire plug-in properties are not inherited by submodules by default. This is a problem as described in bz: > https://bugzilla.redhat.com/show_bug.cgi?id=990114 -- 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-1793) integration tests - allow modules to inherit properties variables

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1793?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1793: ----------------------------------------------- Aleksandar Kostadinov <akostadi(a)redhat.com> made a comment on [bug 990114|https://bugzilla.redhat.com/show_bug.cgi?id=990114] WFLY-1782 is another thing, not sure how it got linked. Linking to WFLY-1793 > integration tests - allow modules to inherit properties variables > ----------------------------------------------------------------- > > Key: WFLY-1793 > URL: https://issues.jboss.org/browse/WFLY-1793 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: No Release > Reporter: Aleksandar Kostadinov > Assignee: Ondrej Zizka > > Seems like surefire plug-in properties are not inherited by submodules by default. This is a problem as described in bz: > https://bugzilla.redhat.com/show_bug.cgi?id=990114 -- 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-1782) ASYNC-tcp tests should have cacheMode set to ASYNC

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1782?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1782: ----------------------------------------------- Aleksandar Kostadinov <akostadi(a)redhat.com> made a comment on [bug 990114|https://bugzilla.redhat.com/show_bug.cgi?id=990114] WFLY-1782 is another thing, not sure how it got linked. Linking to WFLY-1793 > ASYNC-tcp tests should have cacheMode set to ASYNC > -------------------------------------------------- > > Key: WFLY-1782 > URL: https://issues.jboss.org/browse/WFLY-1782 > Project: WildFly > Issue Type: Bug > Components: Clustering, Test Suite > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Minor > Fix For: 8.0.0.Alpha4 > > > testsuite/integration/clust/pom.xml > <cacheMode>SYNC</cacheMode> is used for SYNC-tcp tests instead of <cacheMode>ASYNC</cacheMode> -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2013