January 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-1254) Should support SASL ANONYMOUS mechanism

by Ron Sigal (JIRA)

Should support SASL ANONYMOUS mechanism --------------------------------------- Key: JBREM-1254 URL: https://jira.jboss.org/browse/JBREM-1254 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: security Affects Versions: 3.1.0.Beta2 Reporter: Ron Sigal Fix For: 3.1.0.Beta3 Currently, creating a connection to a peer requires authenticating the user through an available SASL mechanism. The SASL provider from Sun supports, for example, CRAM-MD5 and DIGEST-MD5, which require the use of user names and passwords. The ANONYMOUS mechanism would allow the creation of connections without authentication. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBREM-918) Make JRPP resilient against connection failure

by David Lloyd (JIRA)

Make JRPP resilient against connection failure ---------------------------------------------- Key: JBREM-918 URL: http://jira.jboss.com/jira/browse/JBREM-918 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: r3 JRPP Reporter: David Lloyd Fix For: 3.0.0-M3 If a JRPP connection is dropped, it should be possible to re-establish the connection and resume the session, without the loss of any in-flight requests/contexts/services/etc. As a corollary, it might be worth exploring having more than one connection in a "bundle" to help parallelize the transit load and avoid head-of-line bottleneck problems. Perhaps it is worth looking into multihoming as well. Note that this looks a lot like a list of features that SCTP already has... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (JBREM-1190) Change logging to conform to standard

by David Lloyd (JIRA)

Change logging to conform to standard ------------------------------------- Key: JBREM-1190 URL: https://jira.jboss.org/jira/browse/JBREM-1190 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.1.0.GA Change logging to adhere to JBossAS standard. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-833) HTTP Transport Implementation

by David Lloyd (JIRA)

HTTP Transport Implementation ----------------------------- Key: JBREM-833 URL: http://jira.jboss.com/jira/browse/JBREM-833 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
9
0 / 0

[JBoss JIRA] Created: (JBREM-839) Remoting Endpoint Connector Resource Adapter

by David Lloyd (JIRA)

Remoting Endpoint Connector Resource Adapter -------------------------------------------- Key: JBREM-839 URL: http://jira.jboss.com/jira/browse/JBREM-839 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
4
0 / 0

[JBoss JIRA] Created: (JBREM-917) Switch to Remoting 3.x in JBossAS; deprecate 2.x and earlier

by David Lloyd (JIRA)

Switch to Remoting 3.x in JBossAS; deprecate 2.x and earlier ------------------------------------------------------------ Key: JBREM-917 URL: http://jira.jboss.com/jira/browse/JBREM-917 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.0.0.GA Master bug to hold all issues that prevent inclusion of Remoting 3 - based transports for various services in JBossAS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBREM-1194) SSL simulation mode

by David Lloyd (JIRA)

SSL simulation mode ------------------- Key: JBREM-1194 URL: https://jira.jboss.org/jira/browse/JBREM-1194 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core: remote Reporter: David Lloyd Fix For: 3.1.0.CR1 A session should be configured to be able to act as if SSL were in force even if it isn't. This allows SSL to be offloaded to appliances. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1197) JASPI/JBossSX Server Authentication Provider

by David Lloyd (JIRA)

JASPI/JBossSX Server Authentication Provider -------------------------------------------- Key: JBREM-1197 URL: https://jira.jboss.org/jira/browse/JBREM-1197 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 core Reporter: David Lloyd Fix For: 3.1.0.CR1 Provide an implementation of ServerAuthenticationProvider which integrates with JBossAS using one of the available APIs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-908) Make stream detectors pluggable

by David Lloyd (JIRA)

Make stream detectors pluggable ------------------------------- Key: JBREM-908 URL: http://jira.jboss.com/jira/browse/JBREM-908 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api, r3 core Reporter: David Lloyd Fix For: Remoting 3 M3 Right now there's just a fixed singleton list with just the default detector. See org.jboss.cx.remoting.core.CoreSession. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2822) process does not deploy if default gateway branch does not have condition

by Anurag Aggarwal (JIRA)

process does not deploy if default gateway branch does not have condition ------------------------------------------------------------------------- Key: JBRULES-2822 URL: https://jira.jboss.org/browse/JBRULES-2822 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-process Affects Versions: 5.1.0.M2 Reporter: Anurag Aggarwal Assignee: Mark Proctor If a process has gateway and the default branch of gateway - the process can not be build by the knowledgebase the error message is "Could not find variable '" + variableName + "' for constraint '" + descr.getText() + "'" ) ); it is coming from call sequence - SplitNodeBuilder:69, MVELReturnValueEvaluatorBuilder:61 The samples, BPMN2-ExclusiveSplitDefault.xml and BPMN2-InclusiveSplitDefault.xml also fail to build -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
7
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 January 2011