July 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4669) Port ClusteredSingleSignOn testNoAuthSingleSignOn test to trunk

by Brian Stansberry (JIRA)

Port ClusteredSingleSignOn testNoAuthSingleSignOn test to trunk --------------------------------------------------------------- Key: JBAS-4669 URL: http://jira.jboss.com/jira/browse/JBAS-4669 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Test Suite Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.0.CR1 Port from Branch_4_2. -- 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

17 years, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-4616) NamingContext lookupLink() does not acquire stub to server Naming service

by Brian Stansberry (JIRA)

NamingContext lookupLink() does not acquire stub to server Naming service ------------------------------------------------------------------------- Key: JBAS-4616 URL: http://jira.jboss.com/jira/browse/JBAS-4616 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Naming Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.0.GA, JBossAS-5.0.0.Beta2, JBossAS-4.0.5.GA Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.Beta3 org.jnp.interfaces.NamingContext.lookupLink(Name) does not invoke the checkRef() method before invoking on the stub to the server-side Naming object. The checkRef() method is what actually contacts the JNDI server to download the stub.. Result of this is an NPE will be thrown if an earlier call hasn't downloaded the stub before lookupLink() is called. -- 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

17 years, 12 months

1
8
0 / 0

[JBoss JIRA] Created: (JBMETA-79) determineResolvedJndiName for a 2x ejb home returns

by Scott M Stark (JIRA)

determineResolvedJndiName for a 2x ejb home returns ---------------------------------------------------- Key: JBMETA-79 URL: https://jira.jboss.org/jira/browse/JBMETA-79 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.0.0.Beta30 Reporter: Scott M Stark Assignee: Scott M Stark Fix For: 1.0.0.CR1 If one calls JBossEnterpriseBeanMetaData.determineResolvedJndiName(String) with an ejb2x remote home iface, for an TestBean ejb in an appclient_dep_compat12_13.ear, the resulting home jndi name is appclient_dep_compat12_13/TestBean rather than the appclient_deploy_compat12_13_TestBean jndiName that has been specified via the xml descriptor/metadata. The logic for remote homes is wrong for ejb2x deployments. -- 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

17 years, 12 months

1
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1626) Meta data and text search feature of repository

by Michael Neale (JIRA)

Meta data and text search feature of repository ----------------------------------------------- Key: JBRULES-1626 URL: http://jira.jboss.com/jira/browse/JBRULES-1626 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.7 Reporter: Michael Neale Assigned To: Jervis Liu Fix For: 5.0.0-M1 -- 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

17 years, 12 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBAS-2870) Separate the HA aspect from the invoker proxy

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-2870?page=com.atlassian.jira.plug... ] Brian Stansberry updated JBAS-2870: ----------------------------------- Fix Version/s: Backlog (was: JBossAS-5.0.0.CR2) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) Unscheduling this for AS 5.0.0. It's a major rework of legacy code. > Separate the HA aspect from the invoker proxy > --------------------------------------------- > > Key: JBAS-2870 > URL: https://jira.jboss.org/jira/browse/JBAS-2870 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: Backlog > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Comment from Scott Stark (http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3926369#3926369) > HA proxy invokers like JRMPInvokerProxyHA should not exist. The only difference between an ha proxy and regular proxy would be an interceptor that selected from the available targets and set the invocation proxy such that the common Invoker proxy was told the transport proxy to use. Even an unclustered proxy could have a recover/ha sematic like blocking until the server is availble with this configuration. HA is an aspect that should not be embedded in the transport specific proxy. -- 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

17 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5798) Management interface for ModClusterService

by Brian Stansberry (JIRA)

Management interface for ModClusterService ------------------------------------------ Key: JBAS-5798 URL: https://jira.jboss.org/jira/browse/JBAS-5798 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: JBossAS-5.1.0.CR1 Define the management attributes and operations. -- 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

17 years, 12 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3019) Add support for CRL validation to the certificate based login modules

by Mohammed Ali (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-3019?page=com.atlassian.jira.plug... ] Mohammed Ali commented on JBAS-3019: ------------------------------------ Please add support for this at the earliest possible > Add support for CRL validation to the certificate based login modules > --------------------------------------------------------------------- > > Key: JBAS-3019 > URL: https://jira.jboss.org/jira/browse/JBAS-3019 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Reporter: Scott M Stark > Assignee: Anil Saldhana > > We need to add support for validating certificates against certificate revocation lists (CRLs). -- 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

17 years, 12 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMDR-29) AnnotatedElementMetaDataLoader should allow annotations to be retrieved for non-public methods/constructors

by Adrian Brock (JIRA)

AnnotatedElementMetaDataLoader should allow annotations to be retrieved for non-public methods/constructors ----------------------------------------------------------------------------------------------------------- Key: JBMDR-29 URL: https://jira.jboss.org/jira/browse/JBMDR-29 Project: JBoss MetaData Repository Issue Type: Bug Components: Loader Affects Versions: JBossMDR-2.0.0.Beta15 Reporter: Adrian Brock Assignee: Adrian Brock Fix For: JBossMDR-2.0.0.CR1 Instead of using Class.getMethod/Constructor it should use the ReflectionsUtils.findMethod/Constructor -- 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

17 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCOMMON-60) file URI and URLs not properly handled in property editors

by Adrian Brock (JIRA)

file URI and URLs not properly handled in property editors ---------------------------------------------------------- Key: JBCOMMON-60 URL: https://jira.jboss.org/jira/browse/JBCOMMON-60 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core (2.x) Affects Versions: 2.2.7.GA Reporter: Adrian Brock Assignee: Adrian Brock Fix For: 2.2.8.GA If you use property editors to inject file urls they are not properly handled in terms of encoding. e.g. file:/some/path%20withspaces gets translated into file:/some/path%25%20withspaces by the Strings.toURI/URL methods when it is trying to turn them into absolute paths. The String passed into makeURL/URIFromFileSpec needs to be decoded before it is turned into a file and later converted back to a URL/URI -- 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

17 years, 12 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5791) JBossMQ ReadTask in UIL2 could block until socket timeout

by Takayoshi Kimura (JIRA)

JBossMQ ReadTask in UIL2 could block until socket timeout --------------------------------------------------------- Key: JBAS-5791 URL: https://jira.jboss.org/jira/browse/JBAS-5791 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMS (JBossMQ) Affects Versions: JBossAS-4.2.3.GA Reporter: Takayoshi Kimura Assignee: Adrian Brock This is similar to JBPAPP-685, but in ReadTask. The in.readByte() call in ReadTask won't be interrupted when the thread is interrupted. When this happened the connection.close() call in client won't return until socket timeout, 2 min by default. Since it's blocking socket, we can't use short timeout approach applied for WriteTask. The only way to interrupt ReadTask is to call Socket.close() or close() on InputStream underlying socket. -- 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

17 years, 12 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 July 2008