July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-538) update remoting dist build to break out transports into individual jars

by Tom Elrod (JIRA)

update remoting dist build to break out transports into individual jars ----------------------------------------------------------------------- Key: JBREM-538 URL: http://jira.jboss.com/jira/browse/JBREM-538 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Because of JBREM-496 would like to have several binaries output from the dist build. Need one that includes everything from remoting. Then need ones for the transports (including one just for the client). So might look like: jboss-remoting-all.jar jboss-remoting-core.jar jboss-remoting-socket.jar jboss-remoting-socket-client.jar jboss-remoting-http.jar jboss-remoting-http-client.jar and so forth. -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-544) http client invoker (for http, https, servlet, and sslservlet) needs to handle exceptions in same manner as other transport implementations

by Tom Elrod (JIRA)

http client invoker (for http, https, servlet, and sslservlet) needs to handle exceptions in same manner as other transport implementations ------------------------------------------------------------------------------------------------------------------------------------------- Key: JBREM-544 URL: http://jira.jboss.com/jira/browse/JBREM-544 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) All the other transport clients will throw an exception from the Client.invoke() method when an error occurs. However, the http client invoker currently does not. This is a problem in that can not deliver on no api changes when changing transports. However, there is a need (by the web services group) to have the exception NOT thrown. So need to provide option for both behaviors. -- 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, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBREM-540) need to make servlet-invoker.war part of remoting distribution

by Tom Elrod (JIRA)

need to make servlet-invoker.war part of remoting distribution -------------------------------------------------------------- Key: JBREM-540 URL: http://jira.jboss.com/jira/browse/JBREM-540 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) -- 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, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-542) change how remoting servlet finds servlet invoker

by Tom Elrod (JIRA)

change how remoting servlet finds servlet invoker ------------------------------------------------- Key: JBREM-542 URL: http://jira.jboss.com/jira/browse/JBREM-542 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Currently the servlet deployed within servlet-invoker.war uses the servlet server invoker's JMX Object name (provide within the init-param of web.xml) to lookup the servlet server invoker to make calls upon. This is limited in that requires JMX be available within the web container. Althought this will probably be available in most J2EE app servers, might not be in other web container only deployments. Need to remove this restriction. -- 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, 7 months

3
10
0 / 0

[JBoss JIRA] Created: (JBREM-545) setting of the bind address within MulticastDetector not working

by Tom Elrod (JIRA)

setting of the bind address within MulticastDetector not working ---------------------------------------------------------------- Key: JBREM-545 URL: http://jira.jboss.com/jira/browse/JBREM-545 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: detection Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) If set the bind address within the MultiplexDetector, it does not actually bind the MultiplexSocket to that address. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-536) turn off host verification when doing push callback from server using same ssl config as server

by Tom Elrod (JIRA)

turn off host verification when doing push callback from server using same ssl config as server ----------------------------------------------------------------------------------------------- Key: JBREM-536 URL: http://jira.jboss.com/jira/browse/JBREM-536 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: security Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) Since will not have the ServerinvokerCallbackHandler pick up ssl config from the server when creating push callback client back to callback server, will need to turn off host verification as well as setting the client mode (which is already being done). -- 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, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (JBREM-535) add config to force use of remote invoker instead of local

by Tom Elrod (JIRA)

add config to force use of remote invoker instead of local ---------------------------------------------------------- Key: JBREM-535 URL: http://jira.jboss.com/jira/browse/JBREM-535 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.0.0.Beta2 (Boon) Reporter: Tom Elrod Assigned To: Tom Elrod Fix For: 2.0.0.CR1 (Boon) With the change to having InvokerLocator.BYVALUE config use local invoker and cloning of value instead of using remote invoker (see JBREM-320), now need a specific config for forcing use of remote invoker instead of local even when in same jvm. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3445) Testcase for UTF-8 support with FORM Authentication

by Anil Saldhana (JIRA)

Testcase for UTF-8 support with FORM Authentication --------------------------------------------------- Key: JBAS-3445 URL: http://jira.jboss.com/jira/browse/JBAS-3445 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-4.0.6.CR1 User says: ======================================================== I have run into as well using JBoss 4.0.3SP1 (and 4.0.4GA). In my Web Applications, I can login with English usernames and passwords just fine. But when I try to login with a Russian or Chineese username, the login always fails. >From the tracing I've done, it seems the username is getting converted to ISO-8859-1, and that's why it's failing. I've done all the "standard" things to make our pages UTF-8, and this does work on every page except the login page. Something about "j_security_check" is ignoring UTF-8 and forcing a conversion to "ISO-8859-1". ========================================================= -- 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, 7 months

4
3
0 / 0

[JBoss JIRA] Created: (JBAS-3400) JaasSecurityManagerService can show security provider/JCA algorithm information

by Anil Saldhana (JIRA)

JaasSecurityManagerService can show security provider/JCA algorithm information ------------------------------------------------------------------------------- Key: JBAS-3400 URL: http://jira.jboss.com/jira/browse/JBAS-3400 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Security Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Sohil Shah Priority: Optional Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1, JBossAS-3.2.8.SP2 It may be useful to determine the security providers and the various JCA algorithms installed in the JDK. So, add two methods to the JaasSecurityManagerService as follows: - showProviders() - getAlgorithm(String serviceName) If the serviceName is null, show all the possible JCA service names. Here is a partial tested code, that you may want to adapt: ====================================================================================== import java.security.*; import java.util.*; public class A { public static void main(String[] args) { Provider[] providers = Security.getProviders(); for(int i = 0; i < providers.length; i++) { System.out.println("Provider="+providers[i].toString()); } System.out.println("Printing JCA Algorithm Information"); printJCAAlgorithm("Cipher"); printJCAAlgorithm("Signature"); printJCAAlgorithm("KeyFactory"); printJCAAlgorithm("SecretKeyFactory"); printJCAAlgorithm("AlgorithmParameters"); printJCAAlgorithm("MessageDigest"); printJCAAlgorithm("Mac"); } private static void printJCAAlgorithm(String sName) { System.out.println("Printing "+sName); Set md2 = Security.getAlgorithms(sName); System.out.println(sName + " set length="+md2.size()); Iterator md2iter = md2.iterator(); while(md2iter.hasNext()) { System.out.println(md2iter.next().toString()); } } } ==================================================================================== The output is: asaldhana~/testSecurity>java -cp . -Djava.security.manager A Provider=SUN version 1.5 Provider=SunRsaSign version 1.5 Provider=SunJSSE version 1.5 Provider=SunJCE version 1.5 Provider=SunJGSS version 1.0 Provider=SunSASL version 1.5 Printing JCA Algorithm Information Printing Cipher Cipher set length=13 ARCFOUR PBEWITHSHA1ANDDESEDE DESEDEWRAP PBEWITHMD5ANDTRIPLEDES DESEDE RSA AESWRAP AES PBEWITHMD5ANDDES BLOWFISH DES RC2 PBEWITHSHA1ANDRC2_40 Printing Signature Signature set length=9 SHA256WITHRSA NONEWITHDSA .... Make the changes in HEAD. I will port it to Branch_4_0 and Branch_3_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

16 years, 7 months

5
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-716) Performance benchmarking for PojoCache 2.0

by Ben Wang (JIRA)

Performance benchmarking for PojoCache 2.0 ------------------------------------------ Key: JBCACHE-716 URL: http://jira.jboss.com/jira/browse/JBCACHE-716 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Fix For: 2.0.0 Since we have goe thru dramatic refacotring of internal code, we should perform another benchmark to optimize the code. -- 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, 7 months

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006