jbossws-2.0.2
by Thomas Diesler
Folks,
the jbossws-2.0.2 release is targeted for 01-Nov-2007
Do, 20-Sep-2007: jira freeze
Do, 18-Oct-2007: code freeze
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=87391
We have 25 issues to resolve for that release. Currently the issues are
distributed as follows
Alessio: 1
Darran: 2
Heiko: 6
Richard: 1
Thomas: 8
Unassigned: 7
------------------
Total: 25
Please pickup the unassigned issues.
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years
[Fwd: InfoQ Article on Open Source WS Stacks]
by Thomas Diesler
Hi Folks,
has any of you provided feedback to Stefan Tilkov while I was on
holiday?
cheers
-thomas
-------- Forwarded Message --------
From: Stefan Tilkov <stefan.tilkov(a)innoq.com>
To: Diephouse Dan <dan(a)envoisolutions.com>, Arjen Poutsma
<apoutsma(a)interface21.com>, Paul Fremantle <paul(a)wso2.com>, Thomas
Diesler <thomas.diesler(a)jboss.com>, Arun Gupta <Arun.Gupta(a)sun.com>
Subject: InfoQ Article on Open Source WS Stacks
Date: Wed, 5 Sep 2007 17:59:50 +0200
All,
I am looking to write a piece for InfoQ (http://www.infoq.com) on
open source web services stacks for Java, including Axis2, CXF,
JBossWS, Metro, and Spring WS. My plan is to ask all of you a number
of questions (I hope you all feel that you are the correct person to
talk to, please let me know if you're not).
I'm explicitly not trying to do a "shootout" or evaluation. Rather,
I'm interested in finding out where the philosophy, goals and design
approaches behind the stacks are similar and where they differ.
I will consolidate the answers into a single piece, taking care to
keep it neutral.
The schedule is:
1) Please indicate that you want to participate until the end of the
week, 9 September at the latest (if I don't get a reply, I assume you
don't want to)
2) Please send me your answers to the questions below until the end
of next week (16 September). I suggest you send them only to me, not
to the rest of the list :-) Be sure to keep each answer to 500 words
as an absolute maximum (I will cut and paraphrase and quote wildly,
so don't expect everything you answer will be included verbatim).
3) I'll send you the final draft by September 24 for you to check
whether I have quoted you correctly, and to gather final feedback.
Without further ado, here are the questions:
(1) Can you describe the main design goals of "your" framework? What
do you perceive as its main strengths and unique features?
(2) What's your position on and the framework's support for JCP
standards such as JAX-WS, JAX-RPC, JAXM, JAXB? Why is support for it
included/not included?
(3) What Web services standards do you support, and why are those you
don't support not supported (i.e. do you plan to include them later,
not at all, ...)
(4) What's your position with regards to data binding and the
problems many people associate with it? Do you support native access
to the XML message, an XML/object mapping, or both?
(5) How well do you support interoperability with other WS
implementations, particularly .NET/WCF?
(6) What is your position with regards to REST? Do you offer any kind
of REST support?
(7) What is your framework's maturity? Are there any case studies you
can point to, are there any commercial or open source products that
rely on it?
Thanks!
Stefan Tilkov
InfoQ SOA Editor
--
Stefan Tilkov, http://www.innoq.com/blog/st/
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years
[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack
by palin
Hi Richard,
first of all, just to be clear, I'm not saying clustering rm is a must neither it's easy to implement it. I actually believe it would be very usefull in a real application and that it can be obtained with less pain if the whole rm subsystem it designed keeping it in mind.
So... just a couple of ideas, imho we should open another thread on this in future if needed.
anonymous wrote : * use cookies aware loadbalancer in the front of cluster
| * all your RM endpoints (hosted on cluster nodes) must be cookies aware
Are cookies really needed for rm? In any case the user loadbalancer choice is not our business ;-)
anonymous wrote : * your cluster must be able to replicate the sessions and cookies
| * use clustered database (where RM messages are stored)
For example jboss cache /pojo cache could be used to access and replicate the sessions / rm store on all cluster nodes.
Once again... I'm just wondering if this could be done if the whole system is designed with this issue in mind.
Regarind the original post subject i.e. the RMChannel location:
anonymous wrote : RM subsystem will be hooked to the whole invocation framework, it will consists of handlers, transport wrappers, database based store and other entities. It won't be implemented on the transport layer only.
OK, now I get it. I'll be glad to share ideas about this when you'll think about the server side. I'll think about the handler issue you wrote in the meantime.
Bye
Alessio Soldano
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086663#4086663
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086663
18 years
amberpoint patch in jbossws-2.0.1
by Thomas Diesler
Hi Darran and whoever can answer this,
do you know if the Amberpoint patch is part of the 2.0.1 code base?
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years
[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack
by richard_opalka
"palin" wrote : But there's something that is not clear to me: let's consider the server side (but this also apply on client side), shouldn't the RM subsystem process incoming messages before passing them to the core? (for example to be able to send receive acks) As far as I understand, when you do all the RM processing in the RemotingConnectionImpl, all the core/application work has already been performed (you're ready to send response message, right?)
|
| When working on ws-policy, we thought a bit about ws-rm too, since this is going to use policies. We immagined that we could have ws-rm handlers (set by the ws-policy deployer on both client and server sides) intercepting messages and passing them to RM subsystem. May be this is not the best idea... but you might consider this too ;-)
|
RM subsystem will be hooked to the whole invocation framework, it will consists of handlers, transport wrappers, database based store and other entities. It won't be implemented on the transport layer only.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086566#4086566
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086566
18 years
[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack
by richard_opalka
I'll do the clarification first. What is the RM subsystem for me?
* RM JAXWS handlers communicating with RM store
* RM Channel (as drawn on the picture above) communicating with RM store too (represents reliable transport wrapper for me only)
* RM store (database based persistent store)
* RM sender/receiver used by RM channel and RM handlers too
What is the above picture about? It's only about reliable resending of processed and accepted messages on the transport level. Alessio and Heiko ask me why I decided to put RM channel to the RemotingConnectionImpl and not to the handler?
My answer is: RM sender must be placed on top of transport layer because of his resending capability.
I can't put it to the JAXWS handler. If I would do it, the problem could be with WS-Security (next JAXWS handler that could be in the chain). If I would communicate with transport layer directly from RM handler, WS-Security handler wouldn't be called at all and thus
WS security wouldn't be supported in combination with WS-RM.
Thus what I need is to ensure that all handlers in the handler chain are executed, and then, on transport layer RM channel will accept such completely processed outgoing messages and resend them.
I hope it's now more clear for you now ;-)
Richard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086553#4086553
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086553
18 years
[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack
by richard_opalka
"palin" wrote :
| Just an idea for now... this afternoon I was thinking about cluster with Stefano. Did you consider that a real reliable messaging system is most likely going to be deployed on a clustered environment? (I mean, if you're seeking for reliability... why having a single point of failure using a single host?) IMHO it might be a plus to design the RM implementation keeping this cluster-issue in mind.
|
There's a lot of issues related to the Cluster vs. Web Services.
First of all I need to say that clustered environment is the most suitable for stateless web services. It's because if you have stateless services, you do not need to replicate sessions and cluster manager can forward message to any cluster node of his choice.
The situation becomes complicated if your web service isn't stateless (and each RM enabled endpoint isn't stateless). Imagine the situation you have RM receivers running on multiple cluster nodes. What you can do in such situation? In real life there is the loadbalancer in the front of cluster and if you have the good one it is cookies aware.
Thus the solution for clustered RM environment is:
* use cookies aware loadbalancer in the front of cluster
* all your RM endpoints (hosted on cluster nodes) must be cookies aware
* your cluster must be able to replicate the sessions and cookies
* use clustered database (where RM messages are stored)
* your cluster can't be hidden behind the filewall
If you will meet all these preconditions I don't see the problem to have clustered RM ;-)
Richard
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086524#4086524
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086524
18 years
