October 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5706) 1.5.0 doesn't seem to load on IE7

by Heiko Braun (JIRA)

Heiko Braun created AS7-5706: -------------------------------- Summary: 1.5.0 doesn't seem to load on IE7 Key: AS7-5706 URL: https://issues.jboss.org/browse/AS7-5706 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.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

13 years, 9 months

2
10
0 / 0

[JBoss JIRA] (AS7-2334) Web Console: Eager clustering checkbox enabled/disabled

by Jim Tyrrell (Created) (JIRA)

Web Console: Eager clustering checkbox enabled/disabled ------------------------------------------------------- Key: AS7-2334 URL: https://issues.jboss.org/browse/AS7-2334 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Jim Tyrrell Assignee: Heiko Braun Out of the box this probably should be checked by default so you get the typical in the past JGroups messages in the logging showing that clustering between two instances has occurred. -- 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

6
7
0 / 0

[JBoss JIRA] (AS7-4344) Cannot execute deploy operation from within activation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4344: ----------------------------------- Summary: Cannot execute deploy operation from within activation Key: AS7-4344 URL: https://issues.jboss.org/browse/AS7-4344 Project: Application Server 7 Issue Type: Sub-task Components: OSGi, Server Reporter: Thomas Diesler -- 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
2
0 / 0

[JBoss JIRA] (AS7-4615) Define a database of system modules

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4615: ----------------------------------- Summary: Define a database of system modules Key: AS7-4615 URL: https://issues.jboss.org/browse/AS7-4615 Project: Application Server 7 Issue Type: Task Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler The OSGi configuration supports ModuleIdentifiers. So for example {code} <capability name="javax.transaction.api"/> {code} references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider. If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime). -- 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
9
0 / 0

[JBoss JIRA] (AS7-5051) Allow EE deployments to define dependency requirements with OSGi metadata

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5051: ----------------------------------- Summary: Allow EE deployments to define dependency requirements with OSGi metadata Key: AS7-5051 URL: https://issues.jboss.org/browse/AS7-5051 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler This essentially means that you can put OSGi metadata into an EE deployment manifest, which essentially makes it an OSGi bundle. Deployment unit processing should be such that the EE bundle gets resolved according to it's defined capabilities/requirements. Subsystem processors should not need to care whether the Module was created as a result of OSGi resolution or by the ModuleSpecProcessor. This task is complete when we can do this with the EE core technologies (i.e. webapp, ejb3, cdi) -- 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
6
0 / 0

[JBoss JIRA] (JBRULES-3635) Can we change the encoding used in Drools by default encoding to be configured?

by 大伟张 (JIRA)

大伟张 created JBRULES-3635: ----------------------------- Summary: Can we change the encoding used in Drools by default encoding to be configured? Key: JBRULES-3635 URL: https://issues.jboss.org/browse/JBRULES-3635 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: 大伟张 Assignee: Mark Proctor Can we change the encoding used in Drools by default encoding to be configured? bacause i want to use chinese charset in rule content, according to the current Mechanism of drools, i need to change system default encoding to UTF-8 or other supporting the Chinese character set, it will make impact to whole system, So we hope Drools can support set encoding. like follow method: {code:title=ByteArrayResource.java|borderStyle=solid} public Reader getReader() throws IOException { return new InputStreamReader( getInputStream()); //here can we support config encoding //return new InputStreamReader( getInputStream(), "UTF-8" ); } {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

13 years, 9 months

1
7
0 / 0

[JBoss JIRA] (JBCL-181) Cache getResources in all layers

by Ales Justin (Created) (JIRA)

Cache getResources in all layers -------------------------------- Key: JBCL-181 URL: https://issues.jboss.org/browse/JBCL-181 Project: JBoss ClassLoader Issue Type: Enhancement Components: ClassLoader Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.4.0.Alpha1 -- 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-5703) cli LinebreaksTestCase relies on environment JBOSS_HOME

by Cheng Fang (JIRA)

Cheng Fang created AS7-5703: ------------------------------- Summary: cli LinebreaksTestCase relies on environment JBOSS_HOME Key: AS7-5703 URL: https://issues.jboss.org/browse/AS7-5703 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.1.3.Final (EAP) Reporter: Cheng Fang Assignee: Alexey Loubyansky When building jboss-as and running tests, I'm seeing the following error from cli tests: Tests in error: org.jboss.as.cli.parsing.test.LinebreaksTestCase: Failed to parse /Users/cfang/as/bin/jboss-cli.xml The path points to my existing jboss installation, which could be a different version from what I'm building and testing in my jboss-as workspace. When my existing jboss is 7.2, or 5, 6, the cli test failed. Maybe the test should reset or unset JBOSS_HOME in its surefire plugin configuration. -- 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
3
0 / 0

[JBoss JIRA] (SECURITY-702) Release PicketBox 4.0.14.Final

by Stefan Guilhen (JIRA)

Stefan Guilhen created SECURITY-702: --------------------------------------- Summary: Release PicketBox 4.0.14.Final Key: SECURITY-702 URL: https://issues.jboss.org/browse/SECURITY-702 Project: PicketBox Issue Type: Task Security Level: Public (Everyone can see) Components: JBossSX, Security SPI Reporter: Stefan Guilhen Assignee: Stefan Guilhen -- 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] (JBMESSAGING-1935) The MessagingClusterHealthMBean does not provide JMX otifications

by Doug Grove (JIRA)

Doug Grove created JBMESSAGING-1935: --------------------------------------- Summary: The MessagingClusterHealthMBean does not provide JMX otifications Key: JBMESSAGING-1935 URL: https://issues.jboss.org/browse/JBMESSAGING-1935 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.4.8.SP5 Reporter: Doug Grove The MessagingClusterHealthMBean effectively shuts down JBoss Messaging on certain error conditions. Loss of connectivity to the database is one such condition. JMX notification of stop and start events should be provided so that management tools can be made aware of these events and take appropriate action. -- 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
4
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