August 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-3701) Investigate HTTPSManagementInterfaceTestCase.testHTTPS and HTTPSWebConnectorTestCase.testVerifyingConnector failures

by Emmanuel Hugonnet (JIRA)

Emmanuel Hugonnet created WFLY-3701: --------------------------------------- Summary: Investigate HTTPSManagementInterfaceTestCase.testHTTPS and HTTPSWebConnectorTestCase.testVerifyingConnector failures Key: WFLY-3701 URL: https://issues.jboss.org/browse/WFLY-3701 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Web (Undertow) Affects Versions: 9.0.0.Beta1 Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Those tests are failing on Brontes: http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=19132&tab=buil... Need to investigate -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-748) HTTP management API section in the Admin Guide

by Emmanuel Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFLY-748?page=com.atlassian.jira.plugin.s... ] Emmanuel Hugonnet commented on WFLY-748: ---------------------------------------- https://docs.jboss.org/author/display/WFLY9/The+HTTP+management+API has been created > HTTP management API section in the Admin Guide > ---------------------------------------------- > > Key: WFLY-748 > URL: https://issues.jboss.org/browse/WFLY-748 > Project: WildFly > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emmanuel Hugonnet > Fix For: No Release > > > We need a technical guide to the HTTP management API. > The "Management clients" section gives a basic overview. But it should reference a separate section that documents the usage of GET and POST, the URL patterns, the JSON representation of DMR etc. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3670) Flag modules to be loaded in a distinct classloader context

by Wolf-Dieter Fink (JIRA)

[ https://issues.jboss.org/browse/WFLY-3670?page=com.atlassian.jira.plugin.... ] Wolf-Dieter Fink commented on WFLY-3670: ---------------------------------------- I did not meant to have absolute path for resources here. The issue is that if a module is referenced from different applications the module itself is loaded with a unique classloader. So all applications which depends on this module are using the same instance of static members. In case of having a module implementation with such static objects and the application need to have these objects unique for each application the only approach at the moment is to copy the module. The request is to have a flag like "separateClassLoaderPerDependency" - at module.xml level to have a copy for all dependency references - in the application (jboss-deployment-structure or MANIFEST) to have a separate in-memory copy for this application > Flag modules to be loaded in a distinct classloader context > ----------------------------------------------------------- > > Key: WFLY-3670 > URL: https://issues.jboss.org/browse/WFLY-3670 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Wolf-Dieter Fink > Assignee: Jason Greene > > For some use-cases it will be helpful to have a module in a separate classloader (as copy) if it is used from different applications. > An example is if the module includes classes which follow the singleton pattern but the singleton should be per application instead of instance wide. > There are two possiblities to flag that > - within the module.xml > - within the module reference MAIFEST or jboss-deployment-structure.xml -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3700) Optional Module for Camel

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-3700?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-3700: ------------------------------ Fix Version/s: Awaiting Volunteers Assignee: (was: David Lloyd) Component/s: (was: Class Loading) > Optional Module for Camel > ------------------------- > > Key: WFLY-3700 > URL: https://issues.jboss.org/browse/WFLY-3700 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: Any > Reporter: Jeremy Davis > Labels: modules > Fix For: Awaiting Volunteers > > > It would be nice to have an optional module with the necessary jars to run Camel -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3700) Optional Module for Camel

by Jeremy Davis (JIRA)

Jeremy Davis created WFLY-3700: ---------------------------------- Summary: Optional Module for Camel Key: WFLY-3700 URL: https://issues.jboss.org/browse/WFLY-3700 Project: WildFly Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Class Loading Environment: Any Reporter: Jeremy Davis Assignee: David Lloyd It would be nice to have an optional module with the necessary jars to run Camel -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-101) Allow SyslogHandler to automatically try a reconnect

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-101?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated LOGMGR-101: ------------------------------------------- Bugzilla Update: (was: Perform) Bugzilla References: (was: https://bugzilla.redhat.com/show_bug.cgi?id=1125996) > Allow SyslogHandler to automatically try a reconnect > ---------------------------------------------------- > > Key: LOGMGR-101 > URL: https://issues.jboss.org/browse/LOGMGR-101 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.5.2.Final > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{SyslogHandler}} does not attempt to reconnect if the connection is dropped. Some logic around trying a reconnect should be added. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-101) Allow SyslogHandler to automatically try a reconnect

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-101?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated LOGMGR-101: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1125996 > Allow SyslogHandler to automatically try a reconnect > ---------------------------------------------------- > > Key: LOGMGR-101 > URL: https://issues.jboss.org/browse/LOGMGR-101 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.5.2.Final > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{SyslogHandler}} does not attempt to reconnect if the connection is dropped. Some logic around trying a reconnect should be added. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOGMGR-101) Allow SyslogHandler to automatically try a reconnect

by Ingo Weiss (JIRA)

[ https://issues.jboss.org/browse/LOGMGR-101?page=com.atlassian.jira.plugin... ] Ingo Weiss updated LOGMGR-101: ------------------------------ Affects Version/s: 1.5.2.Final Affects: User Experience > Allow SyslogHandler to automatically try a reconnect > ---------------------------------------------------- > > Key: LOGMGR-101 > URL: https://issues.jboss.org/browse/LOGMGR-101 > Project: JBoss Log Manager > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.5.2.Final > Reporter: James Perkins > Assignee: James Perkins > > Currently the {{SyslogHandler}} does not attempt to reconnect if the connection is dropped. Some logic around trying a reconnect should be added. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1069) Add resolve-expressions param to operation read-resource

by Joe Wertz (JIRA)

[ https://issues.jboss.org/browse/WFLY-1069?page=com.atlassian.jira.plugin.... ] Joe Wertz reassigned WFLY-1069: ------------------------------- Assignee: Joe Wertz > Add resolve-expressions param to operation read-resource > -------------------------------------------------------- > > Key: WFLY-1069 > URL: https://issues.jboss.org/browse/WFLY-1069 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Domain Management > Reporter: Michael Voegele > Assignee: Joe Wertz > Labels: expression, read-resource > > When reading a resource remotely, it would be nice to have the possibility to have expressions resolved. > Following does of course not work, as the code runs in a separate jvm. > {code:java} > private void readRecursive(ModelNode modelNode, String modelNodeName, Map<String, Object> map) { > switch (modelNode.getType()) { > ... > case EXPRESSION: > // this would be great but won't work as it runs in a different jvm > // ModelNode expression = modelNode.resolve(); > // readRecursive(expression, modelNodeName, map); > map.put(modelNodeName, modelNode.asString()); > break; > ... > } > {code} > Therefore a param resolve-expressions for the read-resource operation would be good. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3674) In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-3674?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-3674: ------------------------------------ note, description added to [https://docs.jboss.org/author/display/WFLY9/JPA+Reference+Guide#JPARefere...] > In non-transactional entity manager invocation, add extension to defer entity detach until persistence context is closed > ------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3674 > URL: https://issues.jboss.org/browse/WFLY-3674 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 9.0.0.Beta1 > > > For compatibility with earlier JBoss application server versions (5.0/6.0), add an extension that allows the persistence context to last until the referencing persistence context is closed. > For example, in a session method that has no active JTA transaction, entities returned, will not cleared from the persistence context, until the session method completes. This extension is only introduced to allow compatibility with older application server versions. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 11 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 August 2014