November 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBREM-416) create jboss-remoting-client-pda.jar

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-416?page=all ] Tom Elrod updated JBREM-416: ----------------------------- Fix Version/s: 4.0.0.Beta1 (was: 2.2.0.Alpha3 (Bluto)) > create jboss-remoting-client-pda.jar > ------------------------------------ > > Key: JBREM-416 > URL: http://jira.jboss.com/jira/browse/JBREM-416 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 4.0.0.Beta1 > > > Need a remoting client distribution that can run within J2ME environment (PDA to be specific). -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-417) create J2ME compatible socket client invoker

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-417?page=all ] Tom Elrod updated JBREM-417: ----------------------------- Fix Version/s: 4.0.0.Beta1 (was: 2.2.0.Alpha3 (Bluto)) > create J2ME compatible socket client invoker > -------------------------------------------- > > Key: JBREM-417 > URL: http://jira.jboss.com/jira/browse/JBREM-417 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta1 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 4.0.0.Beta1 > > > There are a few API calls in current SocketClientInvoker that is not allowed in J2ME. Need to create an extention of the SocketClientInvoker (maybe MicroSocketClientInvoker?) that will remove these calls so can be used within J2ME environment. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-410) look at adding httpc as http client invoker

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-410?page=all ] Tom Elrod updated JBREM-410: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > look at adding httpc as http client invoker > ------------------------------------------- > > Key: JBREM-410 > URL: http://jira.jboss.com/jira/browse/JBREM-410 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: transport > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > https://nhttpc.dev.java.net/ > NIO HTTP Client > An HTTP client built using JDK 1.4 NIO. Scales to thousands of > concurrent client connections per VM with almost no CPU overhead. > BSD license. > In particular, need to see if has NTLM support -- 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, 6 months

1
0
0 / 0

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

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-505?page=all ] Tom Elrod updated JBREM-505: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > 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 > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > 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

19 years, 6 months

1
0
0 / 0

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

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-398?page=all ] Tom Elrod updated JBREM-398: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > 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 > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > 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

19 years, 6 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBREM-274) add callback methods to the Client API

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-274?page=all ] Tom Elrod resolved JBREM-274. ------------------------------ Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) Resolution: Done See public void addListener(InvokerCallbackHandler callbackhandler, Map metadata) throws Throwable > add callback methods to the Client API > -------------------------------------- > > Key: JBREM-274 > URL: http://jira.jboss.com/jira/browse/JBREM-274 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: callbacks > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > Would like to add methods to the Client class to allow users to call on it to create the callback server and manage internally. Currently, the user has to create their own callback server (via a Connector class) and manage it themselves. Would be much easier from a programming standpoint for the user to just have the Client class to do this automatically. > My initial thought on this is to have this happen when the user adds a callback listener to the Client and the Client would then automatically create the callback server internallly. The user can pass extra metadata if wanted to specify port, etc. Then when the user removes callback listener, if there are no more listeners left, cleanup the callback server. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-315) allow chaining of marshaller/unmarshallers

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-315?page=all ] Tom Elrod updated JBREM-315: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > allow chaining of marshaller/unmarshallers > ------------------------------------------ > > Key: JBREM-315 > URL: http://jira.jboss.com/jira/browse/JBREM-315 > Project: JBoss Remoting > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: marshall > Affects Versions: 1.4.0 final > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > I was thinking of paired marshaller/unmarshaller, which would be > beneficial for more than just this example (compressing payload comes to > mind). Would like to be able to declare a chain of marshallers. For > example: > <marshallers> > <marshaller>org.jboss.remoting.marshall.CompressedMarshaller</marshaller> > <marshaller>org.jboss.remoting.marshall.InvocationMarshaller</marshaller> > <marshaller>org.jboss.remoting.marshall.CountingMarshaller</marshaller> > </marshallers> > <unmarshallers> > <unmarshaller>org.jboss.remoting.marshall.InvocationUnMarshaller</unmarshaller> > <unmarshaller<org.jboss.remoting.marshall.CompressedUnMarshaller</unmarshaller> > of course packaging and order may not be correct in this example. Just > trying to show how would be nice to configure the chain that is used and > that would not require to by symmetrical if didn't want to. > In this example, the CompressedMarshaller would compress the payload, > then write to the InvocationMarshaller, which would write to the > CountingMarshaller, which would then keep track of number of bytes > written and send notifications as was being written. On the server > side, might not need to know number of bytes being read, so would just > have the InvocationUnMarshaller, then CompressedUnMarshaller to > uncompress the 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-453) Send the pre-release jar to the messaging team for testing

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-453?page=all ] Tom Elrod updated JBREM-453: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > Send the pre-release jar to the messaging team for testing > ---------------------------------------------------------- > > Key: JBREM-453 > URL: http://jira.jboss.com/jira/browse/JBREM-453 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ovidiu Feodorov > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > -- 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, 6 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.Beta1 (Bluto) (was: 2.2.0.Alpha3 (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.Beta1 (Bluto) > > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-518) Remove HTTPServerInvoker

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-518?page=all ] Tom Elrod updated JBREM-518: ----------------------------- Fix Version/s: 2.2.0.Beta1 (Bluto) (was: 2.2.0.Alpha3 (Bluto)) > Remove HTTPServerInvoker > ------------------------ > > Key: JBREM-518 > URL: http://jira.jboss.com/jira/browse/JBREM-518 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: transport > Affects Versions: 2.0.0.CR1 (Boon) > Reporter: Tom Elrod > Assigned To: Tom Elrod > Fix For: 2.2.0.Beta1 (Bluto) > > > Need to remove HTTPServerInvoker now that CoyoteInvoker has taken its place. Was deprecated in 2.0.0 (Boon), so can remove it in this release. -- 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, 6 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 November 2006