July 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1686) Use HAL release stream version number in console footer

by Harald Pehl (JIRA)

[ https://issues.jboss.org/browse/WFLY-1686?page=com.atlassian.jira.plugin.... ] Harald Pehl commented on WFLY-1686: ----------------------------------- Found a solution by generating the console version info using the SPIProcessor. This way HAL can override the version. > Use HAL release stream version number in console footer > ------------------------------------------------------- > > Key: WFLY-1686 > URL: https://issues.jboss.org/browse/WFLY-1686 > Project: WildFly > Issue Type: Feature Request > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > > Currently the version number of the Core Console is displayed in the footer of the Admin Console. This should be changed to the version number of the HAL Release Stream. There can be more than one HAL Release Stream based on one Core Console Version: > {code} > Core Console 1.5.4.Final --> HAL Release Stream 1.5.4.Final > --> HAL Release Stream 1.5.5.Final > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-209) NoSuchMethodException when traiting a legacy class without a default constructor

by Davide Sottara (JIRA)

Davide Sottara created DROOLS-209: ------------------------------------- Summary: NoSuchMethodException when traiting a legacy class without a default constructor Key: DROOLS-209 URL: https://issues.jboss.org/browse/DROOLS-209 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.CR1, 5.5.0.Final Reporter: Davide Sottara Assignee: Mark Proctor Fix For: 5.5.1.Final, 6.0.0.CR2 Trait Wrappers for legacy classes expect the default constructor to be present. If not, an exception is raised. -- 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, 9 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: ------------------------------------- That's the one I see in in the WildFly code base. > 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, 9 months

1
0
0 / 0

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

by Justin Bertram (JIRA)

Justin Bertram created WFLY-1796: ------------------------------------ Summary: 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, 9 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: --------------------------------- > 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, 9 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, 9 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, 9 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, 9 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, 9 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, 9 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 July 2013