[JBoss JIRA] (WFLY-1442) Web console branding across community and product versions
by Harald Pehl (JIRA)
[ https://issues.jboss.org/browse/WFLY-1442?page=com.atlassian.jira.plugin.... ]
Harald Pehl commented on WFLY-1442:
-----------------------------------
Backport looks good
> Web console branding across community and product versions
> -----------------------------------------------------------
>
> Key: WFLY-1442
> URL: https://issues.jboss.org/browse/WFLY-1442
> Project: WildFly
> Issue Type: …
[View More]Feature Request
> Components: Web Console
> Reporter: Harald Pehl
> Assignee: Harald Pehl
> Labels: console_1.5.4
>
> Define a way to specify the branding for the web console across different community and product versions. The name and version used for the branding should be read from the {{product-name}} and {{product-version}} attributes of the root DMR resource. Regarding the logo there are different options:
> # Use a unique logo for the web console across all community and products / versions
> # Choose between a community (WildFly) and a product logo (RedHat)
> # Hold up all logos for any community / product version in the HAL release stream and choose dynamically.
--
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
[View Less]
11 years, 8 months
[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JASSIST-187?page=com.atlassian.jira.plugi... ]
Scott Marlow resolved JASSIST-187.
----------------------------------
Resolution: Out of Date
[~chiba] must of fixed this already, marking out of date.
> Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux
> ---------------------------------------------------------------------------------------
>
> Key: JASSIST-187
> …
[View More] URL: https://issues.jboss.org/browse/JASSIST-187
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.16.0-GA, 3.16.1-GA, 3.17.0-GA
> Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error
> Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error
> Reporter: Alexander Zinin
> Assignee: Scott Marlow
> Fix For: 3.18.0-GA
>
> Attachments: javassist-test.rar, javassist-test.zip
>
>
> It will be difficult to describe what the error.
> I will attach source code that reproduce error.
> If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value.
> Running on Windows:
> 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1
> Running on Linux:
> 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null
> 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!!
> Bug appeared in version 3.16.0.
--
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
[View Less]
11 years, 8 months
[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JASSIST-187?page=com.atlassian.jira.plugi... ]
Scott Marlow commented on JASSIST-187:
--------------------------------------
I rebuilt the attached test with 3.18.0-GA and the regression appears to be fixed (with Java 1.6.0_31). To verify, I built again with 3.17.1-GA and could reproduce again.
Output is here http://pastebin.com/bR3bj6m7
I'm going to close this issue as fixed in 3.18.0-GA.
> Hibernate + inherited entity with getId …
[View More]overrided + Different behavior in Win and Linux
> ---------------------------------------------------------------------------------------
>
> Key: JASSIST-187
> URL: https://issues.jboss.org/browse/JASSIST-187
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.16.0-GA, 3.16.1-GA, 3.17.0-GA
> Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error
> Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error
> Reporter: Alexander Zinin
> Assignee: Shigeru Chiba
> Attachments: javassist-test.rar, javassist-test.zip
>
>
> It will be difficult to describe what the error.
> I will attach source code that reproduce error.
> If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value.
> Running on Windows:
> 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1
> Running on Linux:
> 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null
> 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!!
> Bug appeared in version 3.16.0.
--
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
[View Less]
11 years, 8 months
[JBoss JIRA] (JASSIST-187) Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/JASSIST-187?page=com.atlassian.jira.plugi... ]
Scott Marlow updated JASSIST-187:
---------------------------------
Fix Version/s: 3.18.0-GA
Assignee: Scott Marlow (was: Shigeru Chiba)
> Hibernate + inherited entity with getId overrided + Different behavior in Win and Linux
> ---------------------------------------------------------------------------------------
>
> Key: JASSIST-187
> URL: …
[View More]https://issues.jboss.org/browse/JASSIST-187
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.16.0-GA, 3.16.1-GA, 3.17.0-GA
> Environment: Windows 7 x64 Oracle JVM x86/x64 1.6.37 - no error
> Linux Ubuntu x64 Oracle JVM x64 1.6.37 - error
> Reporter: Alexander Zinin
> Assignee: Scott Marlow
> Fix For: 3.18.0-GA
>
> Attachments: javassist-test.rar, javassist-test.zip
>
>
> It will be difficult to describe what the error.
> I will attach source code that reproduce error.
> If you have hibernate entity with overrided getId() method, in hibernate session this method returns null instead of correct value.
> Running on Windows:
> 2012-12-16 17:33:19,332 INFO ru.zinin.service.SomeServiceImpl :44 - ID = 1
> Running on Linux:
> 2012-12-16 17:41:47,772 INFO ru.zinin.service.SomeServiceImpl :44 - ID = null
> 2012-12-16 17:41:47,772 ERROR ru.zinin.service.SomeServiceImpl :46 - ID IS NULL!!!
> Bug appeared in version 3.16.0.
--
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
[View Less]
11 years, 8 months
[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-…
[View More]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
[View Less]
11 years, 8 months
[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 …
[View More]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
[View Less]
11 years, 8 months
[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 "…
[View More]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
[View Less]
11 years, 8 months