September 2008 - jboss-remoting-issues

[JBoss JIRA] Created: (JBREM-1026) Add service metadata

by David Lloyd (JIRA)

Add service metadata -------------------- Key: JBREM-1026 URL: https://jira.jboss.org/jira/browse/JBREM-1026 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api Reporter: David Lloyd Fix For: 3.0.0-M3 A RequestHandlerSource (aka a forwarded service) needs methods to query static metadata, such as: 1) The presence or absence of ordering guarantees across the total path 2) Security information about the total path (encryption strength for example) 3) Path information (like a traceroute, for cost as well as diagnostic information; could include link cost, transport type & version, etc) 4) Possibly authentication information about the total path It should be possible to add new metadata types later on without interfering with backwards compatibility. So lack of a given metadata type must be considered to be possibly indicative of an older version along the path. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1031) Add jboss-classloading.xml descriptors to artifacts

by David Lloyd (JIRA)

Add jboss-classloading.xml descriptors to artifacts --------------------------------------------------- Key: JBREM-1031 URL: https://jira.jboss.org/jira/browse/JBREM-1031 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 3.0.0.Beta1 The jboss-classloading.xml descriptor is necessary for proper AS5 deployment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1036) Integrate new marshalling framework

by David Lloyd (JIRA)

Integrate new marshalling framework ----------------------------------- Key: JBREM-1036 URL: https://jira.jboss.org/jira/browse/JBREM-1036 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta1 Use pluggable externalizers for stream replacement, replacing the old marker object code. Work out something for marshaller negotiation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1020) Release 2.2.2.SP10

by Ron Sigal (JIRA)

Release 2.2.2.SP10 ------------------ Key: JBREM-1020 URL: https://jira.jboss.org/jira/browse/JBREM-1020 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP10 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1037) CLONE [JBREM-1006] - SOA MTOM bug points to bug in Remoting codebase

by Ron Sigal (JIRA)

CLONE [JBREM-1006] - SOA MTOM bug points to bug in Remoting codebase --------------------------------------------------------------------- Key: JBREM-1037 URL: https://jira.jboss.org/jira/browse/JBREM-1037 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.2.SP7, 2.4.0.GA (Pinto) Environment: SOA 4.3.0 CP02 CR3 Reporter: Ron Sigal Assignee: Ron Sigal Priority: Minor Fix For: 2.4.0.SP1 (Pinto) SOA-568 and JBESB-1803 point to a potential bug in the HttpUnmarshaller code shipped with EAP 4.3.0 CP01. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBREM-839) Remoting Endpoint Connector Resource Adapter

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-839?page=com.atlassian.jira.plug... ] David Lloyd updated JBREM-839: ------------------------------ Fix Version/s: 3.1.0.Beta1 (was: 3.0.0.Beta1) > Remoting Endpoint Connector Resource Adapter > -------------------------------------------- > > Key: JBREM-839 > URL: https://jira.jboss.org/jira/browse/JBREM-839 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Fix For: 3.1.0.Beta1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBREM-1030) Release 2.4.0.SP2

by Ron Sigal (JIRA)

Release 2.4.0.SP2 ----------------- Key: JBREM-1030 URL: https://jira.jboss.org/jira/browse/JBREM-1030 Project: JBoss Remoting Issue Type: Release Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.4.0.SP2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-1035) Convert marshalling to use the jboss-marshalling API

by David Lloyd (JIRA)

Convert marshalling to use the jboss-marshalling API ---------------------------------------------------- Key: JBREM-1035 URL: https://jira.jboss.org/jira/browse/JBREM-1035 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBREM-1009) Streaming should work with packet-based channels as well as stream-based channels

by David Lloyd (JIRA)

Streaming should work with packet-based channels as well as stream-based channels --------------------------------------------------------------------------------- Key: JBREM-1009 URL: http://jira.jboss.com/jira/browse/JBREM-1009 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Components: r3 api Reporter: David Lloyd Assigned To: David Lloyd Fix For: 3.0.0-M3 OutputStreams and Writers are trivially implemented using streams - writes to the remote object are simply propagated across to channel. Other types of streams are more difficult to implement this way. InputStream for example has two types of messages - a data chunk and an exception chunk. Because of this, some basic framing is necessary; with only support for streams, this framing must take place within the stream handler which is a pain to implement. So, a stream serializer should be able to register itself as a byte stream handler (using a StreamChannel) or a message stream handler (using a MessageChannel). -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBREM-917) Switch to Remoting 3.x in JBossAS; deprecate 2.x and earlier

by David Lloyd (JIRA)

[ https://jira.jboss.org/jira/browse/JBREM-917?page=com.atlassian.jira.plug... ] David Lloyd updated JBREM-917: ------------------------------ Fix Version/s: 3.1.0.GA (was: 3.0.0.GA) > Switch to Remoting 3.x in JBossAS; deprecate 2.x and earlier > ------------------------------------------------------------ > > Key: JBREM-917 > URL: https://jira.jboss.org/jira/browse/JBREM-917 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: David Lloyd > Fix For: 3.1.0.GA > > > Master bug to hold all issues that prevent inclusion of Remoting 3 - based transports for various services in JBossAS. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 3 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 September 2008