September 2008 - jbossws-issues - Jboss List Archives

[JBoss JIRA] Created: (JBWS-2042) Rewrite WS-RM protocol messages de/serialization

by Richard Opalka (JIRA)

Rewrite WS-RM protocol messages de/serialization ------------------------------------------------ Key: JBWS-2042 URL: http://jira.jboss.com/jira/browse/JBWS-2042 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 WS-RM protocol message de/serialization: * will be based on Input/Output streams -- 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

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2044) Rewrite Server side file system based RM store

by Richard Opalka (JIRA)

Rewrite Server side file system based RM store ---------------------------------------------- Key: JBWS-2044 URL: http://jira.jboss.com/jira/browse/JBWS-2044 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 Server side RMStore: * will store RMProxy registered endpoints * will store exchanged messages * will store sequence metadata -- 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

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2041) Rewrite RMDeploymentAspect

by Richard Opalka (JIRA)

Rewrite RMDeploymentAspect -------------------------- Key: JBWS-2041 URL: http://jira.jboss.com/jira/browse/JBWS-2041 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 RMDeploymentAspect: * will de/register endpoint with RMProxy * will provide QoS policy description to be ensured by RMProxy -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2043) Refactor server side RM handler to be used by RMReceiver

by Richard Opalka (JIRA)

Refactor server side RM handler to be used by RMReceiver -------------------------------------------------------- Key: JBWS-2043 URL: http://jira.jboss.com/jira/browse/JBWS-2043 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 RMServerHandler: * will be refactored to behave like message Filter * will be used by RMReceiver -- 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

14 years, 10 months

3
4
0 / 0

[JBoss JIRA] Created: (JBWS-2039) Rewrite RMReceiver to survive server restarts and handle QoS correctly

by Richard Opalka (JIRA)

Rewrite RMReceiver to survive server restarts and handle QoS correctly ---------------------------------------------------------------------- Key: JBWS-2039 URL: http://jira.jboss.com/jira/browse/JBWS-2039 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 RMReceiver * will use RMStore to re/store messages, states, sequences * will use RMEndpointInvoker to invoke remote or local endpoints * will ensure AtLeastOnce, AtMostOnce, ExactlyOnce, InOrder delivery quality * will have registered callback to RMProxy (to listen for endpoints de/registered events) and will persist this information * will be well tested via automatic tests -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2040) Implement RMEndpointInvoker

by Richard Opalka (JIRA)

Implement RMEndpointInvoker --------------------------- Key: JBWS-2040 URL: http://jira.jboss.com/jira/browse/JBWS-2040 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 RMEndpointInvoker: * will be used from RMReceiver * will be able to handle local/remote endpoint invocations * will use addressing logical address for informations -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2038) Implement un/secured RM Proxy

by Richard Opalka (JIRA)

Implement un/secured RM Proxy ----------------------------- Key: JBWS-2038 URL: http://jira.jboss.com/jira/browse/JBWS-2038 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 RMProxy: * will implement Provider (standard Webservice endpoint) * will handle only registered endpoints * will have WS-Security handler in handlers chain (applies to secured RMProxy only) * will implement MBean (to enable endpoints register themselves through JMX) * will do WSDL rewriting * will be reusable (users can use default one that will be part of JBossWS or setup their own) * will delegate to RMReceiver -- 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

14 years, 10 months

3
5
0 / 0

[JBoss JIRA] Created: (JBWS-2037) Rewrite server side RM implementation to ensure HA and QoS

by Richard Opalka (JIRA)

Rewrite server side RM implementation to ensure HA and QoS ---------------------------------------------------------- Key: JBWS-2037 URL: http://jira.jboss.com/jira/browse/JBWS-2037 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 RM on server side must be HA and must survive server restarts -- 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

14 years, 10 months

3
6
0 / 0

[JBoss JIRA] Created: (JBWS-2046) Move WS-Security and WS-RM handlers stuff to transport layer

by Richard Opalka (JIRA)

Move WS-Security and WS-RM handlers stuff to transport layer ------------------------------------------------------------ Key: JBWS-2046 URL: http://jira.jboss.com/jira/browse/JBWS-2046 Project: JBoss Web Services Issue Type: Task Security Level: Public (Everyone can see) Components: jbossws-native Reporter: Richard Opalka Assigned To: Richard Opalka Fix For: jbossws-native-2.0.5 -- 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

14 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBWS-2324) jbossws client Port isn't 3ad safe

by Stefano Maestri (JIRA)

jbossws client Port isn't 3ad safe ----------------------------------- Key: JBWS-2324 URL: https://jira.jboss.org/jira/browse/JBWS-2324 Project: JBoss Web Services Issue Type: Feature Request Security Level: Public (Everyone can see) Components: jbossws-native Affects Versions: jbossws-native-3.0.3 Reporter: Stefano Maestri While Service is 3ad safe, Port isn't. I'm referring to client part. It's a problem to achieve better performance in a concurrent environments like Wise/ESB. While it's still possible to invoke Service.getPort() for each call it still not achieve good performance since getPort isn't so fast doing a lot of things under the hood. AFAIK referential implementation have Port 3ad safe and not Service, that would be good for our purpose, since Service.getPort would be good to be invoked in a 3adLocal manner and then Ports cached and reused. -- 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

14 years, 10 months

5
11
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-issues September 2008