January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-874) CLONE -HTTP Client invoker doesn't throw exceptions when using the sslservlet protocol [JBREM-871]

by Ron Sigal (JIRA)

CLONE -HTTP Client invoker doesn't throw exceptions when using the sslservlet protocol [JBREM-871] -------------------------------------------------------------------------------------------------- Key: JBREM-874 URL: http://jira.jboss.com/jira/browse/JBREM-874 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Components: transport Affects Versions: 2.4.0.Beta1 (Pinto), 2.2.2.GA_CP01 Reporter: Jay Howell Assigned To: Ron Sigal Fix For: 2.2.2.SP4 In the HTTP Client Invoker, the only server side exceptions that get thrown are for the servlet protocol only... and also have to be servlet exceptions... The code from the client that throws the exception is inside of this if block.... i// now check for error response and throw exception unless configured to not do so if(responseCode >= 400 || ("servlet".equals(getLocator().getProtocol()) && result instanceof InvocationResponse && ((InvocationResponse) result).getResult() instanceof ServletThrowable)) { -- 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, 3 months

1
3
0 / 0

[JBoss JIRA] Updated: (JBREM-47) Dynamic classloading

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-47?page=all ] Ron Sigal updated JBREM-47: --------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > Dynamic classloading > -------------------- > > Key: JBREM-47 > URL: http://jira.jboss.com/jira/browse/JBREM-47 > Project: JBoss Remoting > Issue Type: Feature Request > Components: general > Affects Versions: 1.0.1 beta > Reporter: Tom Elrod > > Need ability for dynamic classloading to satisfy two needs. The first, is when an ejb lookup is done, and if do not have the class on the client, can download the client classes for remoting. This is much more efficient than having to serialize all these classes (as there may be many and may not even know what they are until runtime). Also, would like to add the ability for client or server to pass implementation for interfaces across the wire and if the other side does not have those classes, can load them. Once particular case when this might be needed is if using JMX sub-system, client could create custom QueryExp? implementation and pass to the server, and the server could load that class and perform the query. Will require security around this. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-159) Patch to enable JRockit 5.0 to work with JBoss Remoting

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-159?page=all ] Ron Sigal updated JBREM-159: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) > Patch to enable JRockit 5.0 to work with JBoss Remoting > ------------------------------------------------------- > > Key: JBREM-159 > URL: http://jira.jboss.com/jira/browse/JBREM-159 > Project: JBoss Remoting > Issue Type: Patch > Components: general > Affects Versions: 2.2.2.GA > Reporter: Jeff Haynie > Priority: Minor > > org.jboss.remoting.detection.multicast.MulticaseDetector$Listener.run, changed: > try > { > listen(p, buf); > } > catch (Exception ex) > to: > try > { > listen(p, buf); > p.setLength(buf.length); > } > catch (Exception ex) > org.jboss.remoting.loading.ClassUtil.serialize, changed body of the method from: > java.io.ByteArrayOutputStream bos=new java.io.ByteArrayOutputStream(); > java.io.ObjectOutputStream oos=new java.io.ObjectOutputStream(bos); > oos.writeObject(obj); > oos.flush(); > bos.flush(); > byte buf[]=bos.toByteArray(); > bos=null; > oos=null; > return buf; > to: > java.io.ByteArrayOutputStream bos=new java.io.ByteArrayOutputStream(); > java.io.ObjectOutputStream oos=new java.io.ObjectOutputStream(bos); > oos.writeObject(obj); > oos.flush(); > bos.flush(); > oos.close(); > bos.close(); > byte buf[]=bos.toByteArray(); > bos=null; > oos=null; > return buf; -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-154) pluggable server resolver in client

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-154?page=all ] Ron Sigal updated JBREM-154: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > pluggable server resolver in client > ----------------------------------- > > Key: JBREM-154 > URL: http://jira.jboss.com/jira/browse/JBREM-154 > Project: JBoss Remoting > Issue Type: Feature Request > Components: general > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Priority: Minor > > Per forum thread http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3883462#3883462, need ability for the remoting client to have a pluggable way to resolve a server endpoint. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-142) better configuration for stream server

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-142?page=all ] Ron Sigal updated JBREM-142: ---------------------------- Fix Version/s: 2.4.1.Beta (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > better configuration for stream server > -------------------------------------- > > Key: JBREM-142 > URL: http://jira.jboss.com/jira/browse/JBREM-142 > Project: JBoss Remoting > Issue Type: Feature Request > Components: stream > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Priority: Minor > Fix For: 2.4.1.Beta > > > The stream server does have basic configuration for transport, host, and port via system properties (see JBREM-125), but needs better alternative for configuration. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-344) support for NTLM authentication

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-344?page=all ] Ron Sigal updated JBREM-344: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > support for NTLM authentication > ------------------------------- > > Key: JBREM-344 > URL: http://jira.jboss.com/jira/browse/JBREM-344 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-398) bring AOP Remoting under JBossRemoting project

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-398?page=all ] Ron Sigal updated JBREM-398: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > bring AOP Remoting under JBossRemoting project > ---------------------------------------------- > > Key: JBREM-398 > URL: http://jira.jboss.com/jira/browse/JBREM-398 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Reporter: Tom Elrod > > Need to bring AOP Remoting under the JBossRemoting project for further development and maintenance. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-385) Need to pull the legacy invokers into remoting

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-385?page=all ] Ron Sigal updated JBREM-385: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Assignee: (was: Tom Elrod) > Need to pull the legacy invokers into remoting > ---------------------------------------------- > > Key: JBREM-385 > URL: http://jira.jboss.com/jira/browse/JBREM-385 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Scott M Stark > > The org.jboss.invocation.* package has dependencies on remoting, and it should just be moved into the remoting project as the legacy remoting impl. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-505) convert jndi to use remoting for transport

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-505?page=all ] Ron Sigal updated JBREM-505: ---------------------------- Fix Version/s: (was: 2.4.0.Beta1 (Pinto)) Affects Version/s: External_issues Assignee: (was: Tom Elrod) > convert jndi to use remoting for transport > ------------------------------------------ > > Key: JBREM-505 > URL: http://jira.jboss.com/jira/browse/JBREM-505 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: External_issues > Reporter: Tom Elrod > > Need to convert jndi to use remoting as transport. Ties in with JBREM-424. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-800) Adjust timout values to avoid cruisecontrol failures

by Ron Sigal (JIRA)

Adjust timout values to avoid cruisecontrol failures ---------------------------------------------------- Key: JBREM-800 URL: http://jira.jboss.com/jira/browse/JBREM-800 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4.0.Beta1 (Pinto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.4.0.Beta1 (Pinto) It seems that some tests fail on cruisecontrol because a busy machine causes timout deadlines to be missed. For example, http://cruisecontrol.jboss.com/cc/artifacts/jboss-remoting-testsuite-1.4/... This issue will be an umbrella issue to cover adjusting timeout values. If a test continues to fail despite updated timeout values, it will need a JIRA issue of its own. -- 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, 3 months

1
4
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 2008