February 2007 - jboss-jira - Jboss List Archives

[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

18 years, 7 months

3
10
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

18 years, 7 months

2
5
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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBREM-539) add sslservlet procotol

by Tom Elrod (JIRA)

add sslservlet procotol ----------------------- Key: JBREM-539 URL: http://jira.jboss.com/jira/browse/JBREM-539 Project: JBoss Remoting Issue Type: Feature Request 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) Need to add sslservlet as there is no way to currently have a ssl deployed servlet invoker without this distinction. This will require use of HTTPSClientInvoker on the client side. Would also be nice to do a check internally to make sure that servlet is available and log an error if is not (maybe within start() method), since is only way to really know if servlet deployed within web container properly. -- 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

18 years, 7 months

2
4
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

18 years, 7 months

2
3
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

18 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

18 years, 7 months

2
4
0 / 0

[JBoss JIRA] Created: (SECURITY-16) Inject options on AuthorizationManagerService

by Anil Saldhana (JIRA)

Inject options on AuthorizationManagerService --------------------------------------------- Key: SECURITY-16 URL: http://jira.jboss.com/jira/browse/SECURITY-16 Project: JBoss Security Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0 AuthorizationManagerService can have an injection of options that can then be passed on to the various pluggable Authorization Managers. Each of the Authorization Managers can have an optional setOptions method. -- 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

18 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-4087) SFSB.getCallerPrincipal() from before- and afterCompletion

by Alexey Loubyansky (JIRA)

SFSB.getCallerPrincipal() from before- and afterCompletion ---------------------------------------------------------- Key: JBAS-4087 URL: http://jira.jboss.com/jira/browse/JBAS-4087 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: EJB2 Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Alexey Loubyansky Assigned To: Anil Saldhana One should be able to call ctx.getCallerPrincipal() from SFSB's afterBegin, before- and afterCompletion. See "7.6.1 Operations Allowed in the Methods of a Stateful Session Bean Class" of the EJB2.1 spec. -- 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

18 years, 7 months

2
3
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

18 years, 7 months

4
3
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 February 2007