December 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Feedback on JBossWS/CXF integration of WS-RM

by thomas.diesler＠jboss.com

I just sent this to the CXF dev forum anonymous wrote : | Hi Folks, | | over the last couple of days I tried to integrate CXF's WS-RM implementation with JBossWS. Last summer, we announced that JBossWS would provide a pluggable WS framework (see the links below) that would allow JBoss customers to run CXF as the preferred WS implementation in JBoss. | | JBossWS supports CXF as a pluggable WS framework | http://netzooid.com/blog/2007/07/02/jbossws-supports-cxf-as-a-pluggable-w... | | JBossWS supports pluggable Web Service stacks | http://www.jboss.org/index.html?module=bb&op=viewtopic&t=112417 | | We have setup a common testsuite for JAX-WS endpoints and clients that we test against (JBossWS) Native, Metro and CXF. In a nutshell, the integration of cxf-2.0.3 looks promising with only a few outstanding issues | | Resolve JBoss common jax-ws testsuite issues | https://issues.apache.org/jira/browse/CXF-1243 | | The next thing I tried was to integrate CXF's WS-RM implementation. In essence I tried to setup JAX-WS RPC/Document endpoints that I configured to use RM. On the client side I tried to stick to standard JAX-WS API as much as I could. The issues that I encountered on the way are aggregated here | | Resolve JBossWS/CXF WS-RM integration issues | http://issues.apache.org/jira/browse/CXF-1328 | | some of them have workarounds, others not. What I currently have are endpoints that reject non RM messages, but choke on RM messages because of [CXF-1321]. The client seems to work ok for Document but not for RPC [CXF-1322] | | Ideally, I would like to get this work completed early next year. Perhaps there is somebody available, who I could contact to discuss what I should expect in terms of working functionality and how to get things working in an integrated environment. | | As a result I would write a step by step guide on howto enable a JAX-WS endpoint for RM [CXF-1311]. | | Have a good holiday & cheers | -thomas | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4115010#4115010 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4115010

17 years

3
2
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by richard.opalka＠jboss.com

"thomas.diesler(a)jboss.com" wrote : | I propose to get the initial implementation going first. Then we investigate the pros/cons of a standalone decoupled RM implementation. IMO RM Sender/Receiver must be decoupled from client proxy/endpoint. However I was following just three goals when writing this first RM prototype: * finish it till the end of this year * provide the functional test suite covering all scenarios from Microsoft interop * cover the WS-Security combinations too "thomas.diesler(a)jboss.com" wrote : After all, if a RM implementation cannot provide reliable messaging (because of its coupling) - it is pointless to use it from the customer point of view ;-) Again, you're absolutely right and I'm happy you're diving into RM dilemma too because our communication about it becomes meaningful ;-) I'm figuring out this pointless RM implementation, but it's not final solution. It's just first prototype that works. But there's still a lot of work to make it better and more meaningful not only from customer point of view. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114983#4114983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114983

17 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by thomas.diesler＠jboss.com

Thanks. I propose to get the initial implementation going first. Then we investigate the pros/cons of a standalone decoupled RM implementation. After all, if a RM implementation cannot provide reliable messaging (because of its coupling) - it is pointless to use it from the customer point of view ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114974#4114974 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114974

17 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by richard.opalka＠jboss.com

"thomas.diesler(a)jboss.com" wrote : | Using your implementation, would it (eventually) be possible to deploy the RM Sender/Receiver as separate HA components (i.e. on dedicated boxes)? No with the current version of prototype :-( View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114971#4114971 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114971

17 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by richard.opalka＠jboss.com

"thomas.diesler(a)jboss.com" wrote : | | On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is coupled with the Endpoint, it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is only available if the Endpoint is available, the client might as well talk to the Endpoint directly. | | Using your implementation, would it (eventually) be possible to deploy the RM Sender/Receiver as separate HA components (i.e. on dedicated boxes)? Hi Thomas, you're absolutely right. The fact that both RM Sender / Receiver are coupled with client proxy/endpoint defeat the purpose of RM. The reason I decided to provide the initial prototype this way was to support WS-Security as well. If we will want to support WS-Security and decouple both RM Sender / Receiver we need to move WS-Security one level lower (that is to move it from handler to transport marshallers). Other option is to forget about WS-RM + WS-Security combination and to decouple the RM Sender/Receiver. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114969#4114969 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114969

17 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by thomas.diesler＠jboss.com

Hi Richard, while working with the RM implementation I was wondering about the Quality of Service (QoS) aspect of WS-RM. In my understanding the RM Sender/Receiver must be high available (HA) components such that the Client can (always) communicate with the RM Sender and likewise the RM Sender can always communicate with the RM Receiver. | Client <--> RM Sender <-------> RM Receiver <--> Endpoint | QoS QoS | On the contrary, if the RM Sender is coupled with the client proxy or the RM Receiver is coupled with the Endpoint, it would in my opinion defeat the purpose of RM. In other words, if the RM Receiver is only available if the Endpoint is available, the client might as well talk to the Endpoint directly. Using your implementation, would it (eventually) be possible to deploy the RM Sender/Receiver as separate HA components (i.e. on dedicated boxes)? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114954#4114954 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114954

17 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by thomas.diesler＠jboss.com

anonymous wrote : | Other possible option that comes in my mind is to don't close sequences at all, because this step isn't required by RM protocol. Closing the sequence is optional protocol operation. | This seems reasonable, with the option to use proprietary API when needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114950#4114950 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114950

17 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by richard.opalka＠jboss.com

Hi Folks, I'm refactoring current WS-RM code base to remove proprietary user API completely. However there is the problem with closing the sequences. How to detect when to close the sequences? The only reasonable point for me is to register the JVM shutdown hook, However this won't work in our test suites (because deployed webservices are undeployed from server before JUnit test exit). I see that Sun's metro uses proprietary api too to close the sequences. See: http://blogs.sun.com/enterprisetechtips/entry/testing_interoperability_be... Other possible option that comes in my mind is to don't close sequences at all, because this step isn't required by RM protocol. Closing the sequence is optional protocol operation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114707#4114707 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114707

17 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Prototype Ready for Preview

by thomas.diesler＠jboss.com

Thanks Richard, well done. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114542#4114542 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114542

17 years

1
0
0 / 0

[Design of JBoss Web Services] - WS-RM Prototype Ready for Preview

by richard.opalka＠jboss.com

Hi Team/Community, WS-RM Prototype is ready and available for preview. The WS-RM test suite is executed against real endpoints and combinations with WS-Security are covered as well. For documentation take a look here: http://jbws.dyndns.org/mediawiki/index.php?title=WS_Reliable_Messaging To execute the test suite, just type: ./build.sh -Dtest=jaxws/wsrm test on commandline. Please review the tests provided in the test suite and provide your feedback, comments, criticism to this forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114305#4114305 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114305

17 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbossws-dev December 2007