Proposal for alternative WSRP transport layer

[julien1]

Chris has issues to make JBossWS working with JDK 1.4 and the JBossWS backport. I am confident that resolving this is just a matter of time.

However this is a showstopper for us and I propose to use another invocation layer that use the same HTTP wire :

1/ Use the WSDL generated objects, make them implement java.io.Serializable
2/ Implement the consumer using jakarta HttpClient
3/ Implement the endpoints using a servlet (or several)

A request is made from the client to the endpoint using :

1/ a specific parameter in the query string : /myendpoint?method=getMarkup

2/ serialise the array of argument in the body of the http request
3/ serialize the response in the http client response

Simply put : make a WSRP RPC without using the SOAP layer.

The benefit is that the client can force the http cookie in order to keep the same client session on the endpoint which is something we need.

Later we can switch back on the SOAP stack.

The benefits we have :

1/ easy to develop
2/ can be used as an alternative layer (even later)
3/ it does not block us until the soap issue is resolved
4/ two person can work in parallel : one on the wsrp invocation, the other on the SOAP stack setup with all the marshalling issues that we will probably have to clear.

Does it make sense ?

[julien1]

BTW it may also be possible to use JBoss remoting with a servlet layer as long as we can get access to to the http request/response to make the request dispatch possible in order to have the session semantics we need.

[thomas.diesler]

I disagree. I need to see what the specific issues he is having - in JIRA.

250+ ws4ee tests pass on the new stack, both in jboss-head and jboss-4.0.x. If he can show me the specifics of this show stoper - he can continue to work with a snapshot that will be available within hours.

I do not even want to talk about a workaround if I don't have a confirmed jira issues that documents the "show stopper"

[julien1]

ok, Chris will follow up for sure on this.

We need that you tag us that release in cvs so we can all use to be consistent ?

[julien1]

I have added a jira task for that http://jira.jboss.com/jira/browse/JBWS-685

[claprun]

The issue is not that there is a "show stopper" per se. The issue is that I haven't been able to deploy the wsrp service using the JBoss WS stack.

Now, this might be due to my lack of familiarity with the stack. Then again, until today, I wasn't able to deploy the stack properly just by itself. The documentation is not very clear as to what is required and the CVS is not helping either.

I am now having problems with deploying the wsrp service but that might come from the code we currently have (which was not developed by me and which I don't fully grasp yet).

I agree with the fact that we need to have a clear understanding of which version of JBoss WS we can use. I also agree with the fact that we should use JBoss WS instead of developing our own invocation framework if at all possible. However, getting everything lined up has so far proved rather frustrating and we cannot afford to spend more than another week to get everything working together.

[julien1]

that is what I call a showstopper.

I just want to avoid that this issue last more than one week from now.

[jason.greene]

Please review my comments that I have sent via email and the corresponding JIRA issues.

Chris may contact either myself or Thomas directly, and we will assist in any way we can.

-Jason