October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4701) JaasSecurityDomain doesn't handle encrypted truststore passwords properly

by Stefan Guilhen (JIRA)

JaasSecurityDomain doesn't handle encrypted truststore passwords properly ------------------------------------------------------------------------- Key: JBAS-4701 URL: http://jira.jboss.com/jira/browse/JBAS-4701 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.5.GA Reporter: Stefan Guilhen Assigned To: Stefan Guilhen Fix For: JBossAS-4.2.2.GA, JBossAS-4.0.5.GA As described in support case 00017949, the user cannot set an encrypted password for the truststore in the same way he does for the keystore. The application server fails to start when the encrypted truststore password is used, displaying the following exception: java.io.IOException: Keystore was tampered with, or password was incorrect. -- 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

16 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCOMMON-36) ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method.

by Vicky Kak (JIRA)

ExternalContext needs pass proxy interface set to the Proxy.newProxyInstance(loader, interfaces, handler); in createProxyContext method. ---------------------------------------------------------------------------------------------------------------------------------------- Key: JBCOMMON-36 URL: http://jira.jboss.com/jira/browse/JBCOMMON-36 Project: JBoss Common Issue Type: Bug Security Level: Public (Everyone can see) Components: common-core, common-old Affects Versions: 1.0.0.GA Reporter: Vicky Kak Assigned To: Vicky Kak Fix For: 2.2.2.GA, 2.0.6.GA, 1.2.2.GA, 1.0.5.GA In the ExternalContext Classes.getAllInterfaces(ifaces, ctx.getClass()); can populate the ifaces with the duplicate Interface entries . When the ifaces with duplicate Interface entries is passed to the Proxy.newProxyInstance(loader, interfaces, handler); it results in the exception >>java.lang.IllegalArgumentException: repeated interface: -- 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

16 years, 11 months

2
10
0 / 0

[JBoss JIRA] Closed: (JBAS-1292) SFSB session replication

by Jason T. Greene (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1292?page=all ] Jason T. Greene closed JBAS-1292. --------------------------------- Resolution: Out of Date > SFSB session replication > ------------------------ > > Key: JBAS-1292 > URL: http://jira.jboss.com/jira/browse/JBAS-1292 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Bela Ban > Assigned To: Jason T. Greene > Original Estimate: 10 weeks > Remaining Estimate: 10 weeks > > - Issues: who instrument the user-specified object? Can it be done transparently? > - SFSB has states defined already and user declared it as "clusterable", can we > declare the fields object as "advisable" at runtime. Meaning, deployer will know > this bean is clusterable and it will "delegate" it to JBossAop to declare all > the bean state classes to be "advisable". Then JBossCacheAop will add the interceptor > at run time. Check with Bill on this feature. > - Check modified field and do fine-grained replication only -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAOP-107) The different types of classloader integration for AOP belong in the related release not jboss-head

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-107?page=comments#action_12384444 ] Kabir Khan commented on JBAOP-107: ---------------------------------- asintegration/org.jboss.aop.asintegration.jboss5 should be moved into the AS 5 source tree, once that has the MC upgraded to 2.0.0.Beta5 > The different types of classloader integration for AOP belong in the related release not jboss-head > --------------------------------------------------------------------------------------------------- > > Key: JBAOP-107 > URL: http://jira.jboss.com/jira/browse/JBAOP-107 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 2.0.0.alpha4 > Reporter: Adrian Brock > Assigned To: Kabir Khan > Priority: Minor > Fix For: 2.0.0.CR1 > > > The JBoss classloading integration with JBossAOP should be managed by JBoss release, > not by the aop/aspects modules in jboss-head. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-107) The different types of classloader integration for AOP belong in the related release not jboss-head

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ] Kabir Khan updated JBAOP-107: ----------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.CR2) > The different types of classloader integration for AOP belong in the related release not jboss-head > --------------------------------------------------------------------------------------------------- > > Key: JBAOP-107 > URL: http://jira.jboss.com/jira/browse/JBAOP-107 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 2.0.0.alpha4 > Reporter: Adrian Brock > Assigned To: Kabir Khan > Priority: Minor > Fix For: 2.0.0.CR1 > > > The JBoss classloading integration with JBossAOP should be managed by JBoss release, > not by the aop/aspects modules in jboss-head. -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-209) Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-209?page=all ] Kabir Khan updated JBAOP-209: ----------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.CR2) > Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent. > ------------------------------------------------------------------------------------ > > Key: JBAOP-209 > URL: http://jira.jboss.com/jira/browse/JBAOP-209 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 1.3.5 > Reporter: Bill Burke > Assigned To: Bill Burke > Priority: Minor > Fix For: 2.0.0.CR1 > > -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-253) Before release, submit the jar to the Messaging team for testing

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ] Kabir Khan updated JBAOP-253: ----------------------------- Fix Version/s: 2.0.0.CR1 (was: 2.0.0.CR2) > Before release, submit the jar to the Messaging team for testing > ---------------------------------------------------------------- > > Key: JBAOP-253 > URL: http://jira.jboss.com/jira/browse/JBAOP-253 > Project: JBoss AOP > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Kabir Khan > Priority: Minor > Fix For: 2.0.0.CR1 > > -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-209) Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent.

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-209?page=all ] Kabir Khan updated JBAOP-209: ----------------------------- Fix Version/s: 2.0.0.CR2 (was: 2.0.0.beta2) > Change any usage of java.rmi.MarshalledObject with JBoss Serialization's equivalent. > ------------------------------------------------------------------------------------ > > Key: JBAOP-209 > URL: http://jira.jboss.com/jira/browse/JBAOP-209 > Project: JBoss AOP > Issue Type: Feature Request > Affects Versions: 1.3.5 > Reporter: Bill Burke > Assigned To: Bill Burke > Priority: Minor > Fix For: 2.0.0.CR2 > > -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-253) Before release, submit the jar to the Messaging team for testing

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-253?page=all ] Kabir Khan updated JBAOP-253: ----------------------------- Fix Version/s: 2.0.0.CR2 (was: 2.0.0.beta2) > Before release, submit the jar to the Messaging team for testing > ---------------------------------------------------------------- > > Key: JBAOP-253 > URL: http://jira.jboss.com/jira/browse/JBAOP-253 > Project: JBoss AOP > Issue Type: Task > Reporter: Ovidiu Feodorov > Assigned To: Kabir Khan > Priority: Minor > Fix For: 2.0.0.CR2 > > -- 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

16 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAOP-107) The different types of classloader integration for AOP belong in the related release not jboss-head

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-107?page=all ] Kabir Khan updated JBAOP-107: ----------------------------- Fix Version/s: 2.0.0.CR2 (was: 2.0.0.beta2) > The different types of classloader integration for AOP belong in the related release not jboss-head > --------------------------------------------------------------------------------------------------- > > Key: JBAOP-107 > URL: http://jira.jboss.com/jira/browse/JBAOP-107 > Project: JBoss AOP > Issue Type: Task > Affects Versions: 2.0.0.alpha4 > Reporter: Adrian Brock > Assigned To: Kabir Khan > Priority: Minor > Fix For: 2.0.0.CR2 > > > The JBoss classloading integration with JBossAOP should be managed by JBoss release, > not by the aop/aspects modules in jboss-head. -- 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

16 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007