January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBREM-674) add test case for client exiting correctly

by Tom Elrod (JIRA)

add test case for client exiting correctly ------------------------------------------ Key: JBREM-674 URL: http://jira.jboss.com/jira/browse/JBREM-674 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: general Reporter: Tom Elrod Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) Per Tim Fox: Suggestion: Create a test in the remoting test suite which creates a remoting client in it's own vm, does some stuff then tries to exit cleanly. If it can't then the test fails. This would catch any similar issues in the future if people add timers without remembering to make them daemon. (We're going to add a test in the JBM test suite anyway for 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-621) Add Pagination to SortableTable (the iterators support skipping already)

by Michael Neale (JIRA)

Add Pagination to SortableTable (the iterators support skipping already) ------------------------------------------------------------------------ Key: JBRULES-621 URL: http://jira.jboss.com/jira/browse/JBRULES-621 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-625) restoring a version should update comment plus increment version number

by Michael Neale (JIRA)

restoring a version should update comment plus increment version number ----------------------------------------------------------------------- Key: JBRULES-625 URL: http://jira.jboss.com/jira/browse/JBRULES-625 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-787) Documentation: Add a chapter on extending JBoss Cache

by Manik Surtani (JIRA)

Documentation: Add a chapter on extending JBoss Cache ----------------------------------------------------- Key: JBCACHE-787 URL: http://jira.jboss.com/jira/browse/JBCACHE-787 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.0.0 With sections on: 1) The SPI interface 2) How to write your custom cache loader 3) How to write your custom eviction policy 4) How to write your custom transaction manager lookup 5) How to write your custom cache listener -- 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

19 years, 3 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-622) SortableTable to encapsulate model rendering code

by Michael Neale (JIRA)

SortableTable to encapsulate model rendering code ------------------------------------------------- Key: JBRULES-622 URL: http://jira.jboss.com/jira/browse/JBRULES-622 Project: JBoss Rules Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Michael Neale Assigned To: Michael Neale -- 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

19 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-612) NPE on asserting facts before reading rules with retract

by Justine Hlista (JIRA)

NPE on asserting facts before reading rules with retract -------------------------------------------------------- Key: JBRULES-612 URL: http://jira.jboss.com/jira/browse/JBRULES-612 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.5 Environment: Windows XP, JDK 1.5.0_07 Reporter: Justine Hlista Assigned To: Mark Proctor I have a scenario that asserts two simple facts, then reads a rule file, then fires the rules. One of the rules retracts one of the facts, then modifies another object. An NPE results when things are run as in the attached files. However, if the rule file is read first, then the facts are asserted, there is no NPE. Alternatively, if the second rule, the consequence of which retracts one of the facts, is modified so that the retract is the last statement in the consequence, then the NPE does not occur, even if the facts are asserted before the rules are read. -- 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

19 years, 3 months

3
5
0 / 0

[JBoss JIRA] Updated: (JBREM-63) Get rid of the legacy configuration that embeds xml parsing

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-63?page=all ] Tom Elrod updated JBREM-63: ---------------------------- Fix Version/s: 2.2.0.Beta2 (Boon) (was: 2.2.0.Beta1 (Bluto)) Affects: [Documentation (Ref Guide, User Guide, etc.), Compatibility/Configuration] (was: [Compatibility/Configuration, Documentation (Ref Guide, User Guide, etc.)]) Priority: Blocker (was: Critical) > Get rid of the legacy configuration that embeds xml parsing > ----------------------------------------------------------- > > Key: JBREM-63 > URL: http://jira.jboss.com/jira/browse/JBREM-63 > Project: JBoss Remoting > Issue Type: Task > Affects Versions: 1.0.1 beta > Reporter: Scott M Stark > Assigned To: Tom Elrod > Priority: Blocker > Fix For: 2.2.0.Beta2 (Boon) > > > I see that the org.jboss.remoting.transport.Connector is using the legacy mechanism of using an Element configuration as an attribute and doing the xml parsing within the code. This needs to be removed and replaced with JBossXB constructs. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-298) Need ability to add transport specific info to invocation payload

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-298?page=all ] Tom Elrod updated JBREM-298: ----------------------------- Fix Version/s: 2.2.0.Beta2 (Boon) (was: 2.2.0.Beta1 (Bluto)) > Need ability to add transport specific info to invocation payload > ----------------------------------------------------------------- > > Key: JBREM-298 > URL: http://jira.jboss.com/jira/browse/JBREM-298 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: transport > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Assigned To: Ron Sigal > Fix For: 2.2.0.Beta2 (Boon) > > > Specific example would be to add ssl client cert from the ssl socket to the invocation payload. -- 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-521) Organize configuration of client side socket/server socket factories and server side socket/server socket factories.

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-521?page=all ] Tom Elrod updated JBREM-521: ----------------------------- Fix Version/s: 2.2.0.Beta2 (Boon) (was: 2.2.0.Beta1 (Bluto)) > Organize configuration of client side socket/server socket factories and server side socket/server socket factories. > -------------------------------------------------------------------------------------------------------------------- > > Key: JBREM-521 > URL: http://jira.jboss.com/jira/browse/JBREM-521 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Alpha3 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.0.Beta2 (Boon) > > > JBREM-520 concerns organizing configuration of socket factories and sever socket factories in the context of a Connector. This issue concerns the more general problem of organizing the configuration of factories in the contexts of both Clients and Connectors. There are two aspects of configuration through the Client: > 1) configuration of socket factories used by client invokers, and > 2) configuration of server socket factories used by server invokers in callback Connectors created by calls to Client.addListener(). > and these need to be aligned with the two aspects of configuration through the Connector: > 1) configuration of server socket factories used by server invokers, and > 2) configuration of socket factories used by callback client invokers created on the server side in response to calls to Client.addListener(). > For example, there should be a Client.setServerInvoker() 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

19 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-522) When Client.addListener() creates a callback Connector for an SSL transport, the SSLServerSocket should be put in client mode.

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-522?page=all ] Tom Elrod updated JBREM-522: ----------------------------- Fix Version/s: 2.2.0.Beta2 (Boon) (was: 2.2.0.Beta1 (Bluto)) > When Client.addListener() creates a callback Connector for an SSL transport, the SSLServerSocket should be put in client mode. > ------------------------------------------------------------------------------------------------------------------------------ > > Key: JBREM-522 > URL: http://jira.jboss.com/jira/browse/JBREM-522 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Alpha3 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > Fix For: 2.2.0.Beta2 (Boon) > > > Just as ServerInvokerCallbackHandler configures callback client invoker SSLSocketFactorys to put their SSLSockets in server mode, Client should configure callback server invoker SSLServerSocketFactorys to put their SSLServerSockets in client mode. > This is the inverse of JBREM-368/JBREM-491. > It is also related to JBREM-521. -- 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

19 years, 3 months

1
0
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 2007