October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5650) Upgrade JBoss Marshalling to 1.3.16.GA

by Scott Marlow (JIRA)

Scott Marlow created AS7-5650: --------------------------------- Summary: Upgrade JBoss Marshalling to 1.3.16.GA Key: AS7-5650 URL: https://issues.jboss.org/browse/AS7-5650 Project: Application Server 7 Issue Type: Feature Request Components: Build System Reporter: Scott Marlow Assignee: Paul Gier Fix For: 7.2.0.Alpha1 -- 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

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] (AS7-5689) Fix JBossWS Remote Deployer AS7 resource leaks

by Richard Opalka (JIRA)

Richard Opalka created AS7-5689: ----------------------------------- Summary: Fix JBossWS Remote Deployer AS7 resource leaks Key: AS7-5689 URL: https://issues.jboss.org/browse/AS7-5689 Project: Application Server 7 Issue Type: Bug Components: Web Services Affects Versions: 7.1.3.Final (EAP) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) -- 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

13 years, 9 months

1
2
0 / 0

[JBoss JIRA] (AS7-5153) Add sun.awt to sun.jdk module

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/AS7-5153?page=com.atlassian.jira.plugin.s... ] David Lloyd resolved AS7-5153. ------------------------------ Fix Version/s: 7.2.0.Alpha1 7.1.4.Final (EAP) Resolution: Done > Add sun.awt to sun.jdk module > ----------------------------- > > Key: AS7-5153 > URL: https://issues.jboss.org/browse/AS7-5153 > Project: Application Server 7 > Issue Type: Feature Request > Components: Class Loading > Environment: When using Oracle jre > Reporter: Michael Procopio > Assignee: David Lloyd > Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) > > > We have code which extends sun.awt.DisplayChangedListener, and yes we know that it is documented by Oracle as a internal only interface; however, our developers maintain they have no other way to make their code run properly. Since sun.awt is not considered a system package our users run into problems when using Jboss 7.1. And yes we realize that the user can code Djboss.modules.system.pkgs in her conf file; however, that's one more thing to keep track of. And sun.awt really is a system package when using the Oracle JRE. > -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5050) Expose javax.annotation.processing in system module

by Julien Viet (JIRA)

Julien Viet created AS7-5050: -------------------------------- Summary: Expose javax.annotation.processing in system module Key: AS7-5050 URL: https://issues.jboss.org/browse/AS7-5050 Project: Application Server 7 Issue Type: Bug Components: Class Loading Affects Versions: 7.1.1.Final Reporter: Julien Viet Assignee: David Lloyd Priority: Minor The path javax.annotation.processing is not exposed and break applications that needs it. Adding <path name="javax/annotation/processing"/> to api/main/modules.xml solves the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
5
0 / 0

[JBoss JIRA] (JBMESSAGING-1937) Allow server side message time-to-live to override any value provided by a client

by Doug Grove (JIRA)

Doug Grove created JBMESSAGING-1937: --------------------------------------- Summary: Allow server side message time-to-live to override any value provided by a client Key: JBMESSAGING-1937 URL: https://issues.jboss.org/browse/JBMESSAGING-1937 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Reporter: Doug Grove Priority: Optional The customer wishes to be able to have a message timeout (time-to-live) specified on the server in the destination configuration. This value would be used for the message time-to-live regardless of what value is provided by the client. -- 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

13 years, 9 months

1
1
0 / 0

[JBoss JIRA] (AS7-5692) Upgrade JGroups to 3.2.0.CR1

by Paul Ferraro (JIRA)

Paul Ferraro created AS7-5692: --------------------------------- Summary: Upgrade JGroups to 3.2.0.CR1 Key: AS7-5692 URL: https://issues.jboss.org/browse/AS7-5692 Project: Application Server 7 Issue Type: Component Upgrade Components: Clustering Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 7.2.0.Alpha1 -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-52) Add option to WriterHandler to collapse repeated messages

by David Lloyd (JIRA)

David Lloyd created LOGMGR-52: --------------------------------- Summary: Add option to WriterHandler to collapse repeated messages Key: LOGMGR-52 URL: https://issues.jboss.org/browse/LOGMGR-52 Project: JBoss Log Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.4.0.Beta1 The WriterHandler could have a time interval configured wherein a repeated message would be collapsed. The last message would be stored in a field for comparison along with a nanoTime tag (the timestamp on the message is not adequate because the clock can have skew or be reset completely at any time). If the current message string equals the last message string, and collapsing is enabled, then instead of logging the message, a count is incremented. If the current message is not equal, then the stored message is logged with a tag indicating the number of repeats (i18n?) and then the next submitted message is logged. -- 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

13 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-5402) upgrade netty to 3.4.5.Final

by Jeff Mesnil (JIRA)

Jeff Mesnil created AS7-5402: -------------------------------- Summary: upgrade netty to 3.4.5.Final Key: AS7-5402 URL: https://issues.jboss.org/browse/AS7-5402 Project: Application Server 7 Issue Type: Component Upgrade Components: JMS, Web Services Affects Versions: 7.1.2.Final (EAP) Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1 When I upgraded HornetQ to 2.2.19.Final, I did not update Netty to the same version that HornetQ requires (from 3.2.6.Final to 3.4.5.Final). What's more, with this version, Netty changeed its groupId in Maven from org.jboss.netty to io.netty. HornetQ is not the only component that depends on Netty (jbossws uses it too) and I am not sure jbossws is ready to update its version of Netty. Since the groupId of Netty changed, I propose to add a new module io.netty and upgrade its Netty versiontto 3.4.5.Final. HornetQ modules will then depend on that module. I will *not* change the current org.jboss.netty module (that is used by jbossws) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

1
5
0 / 0

[JBoss JIRA] (AS7-5160) Support for static resources from /META-INF/resources from JBoss Module

by Kirk Rasmussen (JIRA)

Kirk Rasmussen created AS7-5160: ----------------------------------- Summary: Support for static resources from /META-INF/resources from JBoss Module Key: AS7-5160 URL: https://issues.jboss.org/browse/AS7-5160 Project: Application Server 7 Issue Type: Feature Request Components: Class Loading Affects Versions: 7.1.1.Final Reporter: Kirk Rasmussen Assignee: David Lloyd It would be a nice extension to support loading Servlet 3.0 style fragements for static resources from JBoss modules. For example, for sharing static resources from Vaadin with multiple WAR files (2MB of static files) could be avoided: {code:xml} <jboss-deployment-structure> <deployment> <dependencies> <module name="vaadin.static"> <imports> <include path="META-INF**" /> </imports> </module> </dependencies> </deployment> </jboss-deployment-structure> {code} The module above would contain web static resources in /META-INF/resources/. This doesn't currently work unfortunately. When the JAR contained in the Module is embedded in the WAR file it works fine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
3
0 / 0

[JBoss JIRA] (AS7-4970) Upgrade JBoss Logging

by Juergen Zimmermann (JIRA)

Juergen Zimmermann created AS7-4970: --------------------------------------- Summary: Upgrade JBoss Logging Key: AS7-4970 URL: https://issues.jboss.org/browse/AS7-4970 Project: Application Server 7 Issue Type: Feature Request Components: Remoting Affects Versions: 7.1.2.Final (EAP) Reporter: Juergen Zimmermann Assignee: David Lloyd jboss-remoting 3.2.7 is using these versions in pom.xml which are not up-to-date: * logging.version: 3.1.0.GA -> 3.1.1.GA * logging-tools.version: 1.0.0.GA -> 1.0.2.GA * logmanager.version: 1.2.0.GA -> 1.3.1.GA -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
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 October 2012