May 2008 - jboss-remoting-issues - Jboss List Archives

[JBoss JIRA] Reopened: (JBREM-221) remove physical inclusion of docbook support directories

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-221?page=all ] Ron Sigal reopened JBREM-221: ----------------------------- > remove physical inclusion of docbook support directories > -------------------------------------------------------- > > Key: JBREM-221 > URL: http://jira.jboss.com/jira/browse/JBREM-221 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Priority: Optional > > Included style and support directory under root docs directory. These are large in size and should either require checkoout of docbook-support project (as suggested on wiki) and point to that or find another solution that does not require getting these upon standard JBossRemoting checkout. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-221) remove physical inclusion of docbook support directories

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-221?page=all ] Ron Sigal updated JBREM-221: ---------------------------- Fix Version/s: (was: 2.4.0.GA (Pinto)) Removed fix version. > remove physical inclusion of docbook support directories > -------------------------------------------------------- > > Key: JBREM-221 > URL: http://jira.jboss.com/jira/browse/JBREM-221 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Priority: Optional > > Included style and support directory under root docs directory. These are large in size and should either require checkoout of docbook-support project (as suggested on wiki) and point to that or find another solution that does not require getting these upon standard JBossRemoting checkout. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-221) remove physical inclusion of docbook support directories

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-221?page=all ] Ron Sigal closed JBREM-221. --------------------------- Resolution: Done > remove physical inclusion of docbook support directories > -------------------------------------------------------- > > Key: JBREM-221 > URL: http://jira.jboss.com/jira/browse/JBREM-221 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Priority: Optional > > Included style and support directory under root docs directory. These are large in size and should either require checkoout of docbook-support project (as suggested on wiki) and point to that or find another solution that does not require getting these upon standard JBossRemoting checkout. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-373) clean up lease handling on server side

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-373?page=all ] Ron Sigal closed JBREM-373. --------------------------- Resolution: Won't Fix > clean up lease handling on server side > -------------------------------------- > > Key: JBREM-373 > URL: http://jira.jboss.com/jira/browse/JBREM-373 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Priority: Minor > > In issue JBREM-372, put in a hack for cleaning up lease map within the ServerInvoker where would pass the clientLeases variable from ServerInvoker to the constructor of Lease. Then when LeaseTimerTask fired and event that client was dead, would remove itself from the ServerInvoker's lease map (by client id). > Should not have to pass in the lease map from ServerInvoker. Maybe better approach would be to have ServerInvoker add itself as listener, so when the connection failure event fired, it would be notified and remove the lease from the clientLeases map itself. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-302) remote dynamic marshall loading not working on linux

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-302?page=all ] Ron Sigal updated JBREM-302: ---------------------------- Fix Version/s: 2.4.1.Beta (was: 2.4.0.GA (Pinto)) > remote dynamic marshall loading not working on linux > ---------------------------------------------------- > > Key: JBREM-302 > URL: http://jira.jboss.com/jira/browse/JBREM-302 > Project: JBoss Remoting > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: marshall > Affects Versions: 1.4.0 beta > Environment: Linux, JDK 1.4 > Reporter: Tom Elrod > Priority: Minor > Fix For: 2.4.1.Beta > > Attachments: SocketMarshallerLoadingTestCase-out.txt > > > The following test cases fail on Linux (and not on Windows): > org.jboss.test.remoting.marshall.dynamic.remote.http.HTTPMarshallerLoadingTestCase > org.jboss.test.remoting.marshall.dynamic.remote.socket.SocketMarshallerLoadingTestCase > Test output for SocketMarshallerLoadingTestCase attached, but says that server can not find the class: > org.jboss.test.remoting.marshall.dynamic.remote.socket.TestObject > However, confirmed that this class is within the jboss-remoting-loading-tests.jar, which is being set on the classpath (as shown in the output log). -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-373) clean up lease handling on server side

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-373?page=all ] Ron Sigal updated JBREM-373: ---------------------------- Fix Version/s: (was: 2.4.0.GA (Pinto)) > clean up lease handling on server side > -------------------------------------- > > Key: JBREM-373 > URL: http://jira.jboss.com/jira/browse/JBREM-373 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Priority: Minor > > In issue JBREM-372, put in a hack for cleaning up lease map within the ServerInvoker where would pass the clientLeases variable from ServerInvoker to the constructor of Lease. Then when LeaseTimerTask fired and event that client was dead, would remove itself from the ServerInvoker's lease map (by client id). > Should not have to pass in the lease map from ServerInvoker. Maybe better approach would be to have ServerInvoker add itself as listener, so when the connection failure event fired, it would be notified and remove the lease from the clientLeases map itself. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-221) remove physical inclusion of docbook support directories

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-221?page=all ] Ron Sigal closed JBREM-221. --------------------------- Resolution: Won't Fix Remoting 3 will be mavenized. > remove physical inclusion of docbook support directories > -------------------------------------------------------- > > Key: JBREM-221 > URL: http://jira.jboss.com/jira/browse/JBREM-221 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Priority: Optional > Fix For: 2.4.0.GA (Pinto) > > > Included style and support directory under root docs directory. These are large in size and should either require checkoout of docbook-support project (as suggested on wiki) and point to that or find another solution that does not require getting these upon standard JBossRemoting checkout. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-139) need automated test for servlet server invoker

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-139?page=all ] Ron Sigal updated JBREM-139: ---------------------------- Fix Version/s: 2.4.1.Beta (was: 2.4.0.GA (Pinto)) > need automated test for servlet server invoker > ---------------------------------------------- > > Key: JBREM-139 > URL: http://jira.jboss.com/jira/browse/JBREM-139 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.2.0 final > Reporter: Tom Elrod > Priority: Minor > Fix For: 2.4.1.Beta > > > Tests for servlet invoker is manual since have to deploy servlet-invoker.war to jboss in order for it to work. Need to figure out if there > is an easy automated way to do this (since would currently require JBossAS, don't think realistic to run as unit test for JBossRemoting > test run). -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-116) Create public and implementors javadoc

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-116?page=all ] Ron Sigal updated JBREM-116: ---------------------------- Fix Version/s: (was: 2.4.0.GA (Pinto)) > Create public and implementors javadoc > -------------------------------------- > > Key: JBREM-116 > URL: http://jira.jboss.com/jira/browse/JBREM-116 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.0.2 final > Reporter: Tom Elrod > > Need to produce javadoc for public API and for implementation API (which is subject to change). One idea would be to create seperate packages for the actual implementations, such as for the transports and marshallers, so will be easier to identify what is public and what is implementation. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-116) Create public and implementors javadoc

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-116?page=all ] Ron Sigal closed JBREM-116. --------------------------- Resolution: Won't Fix > Create public and implementors javadoc > -------------------------------------- > > Key: JBREM-116 > URL: http://jira.jboss.com/jira/browse/JBREM-116 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.0.2 final > Reporter: Tom Elrod > > Need to produce javadoc for public API and for implementation API (which is subject to change). One idea would be to create seperate packages for the actual implementations, such as for the transports and marshallers, so will be easier to identify what is public and what is implementation. -- 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

15 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues May 2008