September 2007 - jbossws-dev - Jboss List Archives

[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack

by heiko.braun＠jboss.com

Maybe i need to look at the code. But i was thinking similiar. My first impression was, that RM uses a cleanly seperated subsystem, with jbossws dispatching to it (or registering a callback on the server side). Let the dispatch point be handler or whatever fits into the picture. Could it be that you require fine grained control over the transport? I.e. dealing with return codes and continuation? Is that the reason you chose the RemotingConnectionImpl.java? Another drawback is that the RemotingConnection is only available on the client side. How is the server side dealing with it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086478#4086478 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086478

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: Adding jbossws-spi to maven

by heiko.braun＠jboss.com

Yes 1.0.0.GA is the right one. The higher version numbers are actually earlier ones, when the spi codebase did still live with the core. It used to inherit the core version number with every release. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086475#4086475 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086475

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack

by palin

Hi Richard, I've just taken a look at both your private branch code and this post ;-) "richard_opalka" wrote : 1.) Yes, the model of the SENDER and RECEIVER should be similar. I've just draw the client side, but you can imagine similar mechanism on the server side too. Just for clear in present I'm mainly focusing on the client side. OK, as a matter of fact speaking of RM, client side and server side do a lot of things the same way. anonymous wrote : 2.) I was playing games and doing some experiments with JBossWS client side invocation framework and was looking for the most suitable place to put the RM SENDER in. I have implemented dummy sender and executed all the JBossWS tests on all JBoss AS version against this dummy sender. The result of my experiment is in SVN repository (in my branch). | You can find this dummy sender implementation in RemotingConnectionImpl.java. 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 ;-) anonymous wrote : I'm expecting another questions, comments, criticism and opinions from you guys ;-) 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. Bye Alessio Soldano View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086397#4086397 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086397

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Adding jbossws-spi to maven

by scott.stark＠jboss.org

To factor out some of the jbossas metadata into the https://svn.jboss.org/repos/jbossas/projects/metadata project, requires getting the jbossws-spi jar into maven2 repo to be able to build the metadata project. I'm going to put the 1.0.0.GA release out today, as that is what is being pulled in by the current jbossws version included in the build-thirdparty.xml. However, I see later versions in the jboss repo 2.0.0.GA/ 2.1.0.Beta1/ Is the 1.0.0.GA release what should be getting pulled into jbossas5? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086303#4086303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086303

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Wise 1.0 released

by maeste

We are proud to announce the first public release of Wise. Thanks a lot to all for the help in these months. You can find the public announcement on TSS: http://www.theserverside.com/news/thread.tss?thread_id=46933 feedbacks are welcome. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085980#4085980 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085980

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack

by richard_opalka

1.) Yes, the model of the SENDER and RECEIVER should be similar. I've just draw the client side, but you can imagine similar mechanism on the server side too. Just for clear in present I'm mainly focusing on the client side. 2.) I was playing games and doing some experiments with JBossWS client side invocation framework and was looking for the most suitable place to put the RM SENDER in. I have implemented dummy sender and executed all the JBossWS tests on all JBoss AS version against this dummy sender. The result of my experiment is in SVN repository (in my branch). You can find this dummy sender implementation in RemotingConnectionImpl.java. If you would like to explain something we can communicate it also e.g. via Skype. I'm expecting another questions, comments, criticism and opinions from you guys ;-) Richard View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085894#4085894 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085894

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-RM Sender/Receiver Location Within JBossWS Stack

by heiko.braun＠jboss.com

Nice ascii art. * Does a RM CHANNEL model the sender as well as the receiver side? * "I decided that the most suitable place to put RM CHANNEL to is the RemotingConnectionImpl class." Sorry, i dont understand this part. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085519#4085519 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085519

17 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - WS-RM Sender/Receiver Location Within JBossWS Stack

by thomas.diesler＠jboss.com

Richard sais: RM SENDER AND RECEIVER LOCATION WITHIN JBOSSWS STACK RM Sender and Receiver must operate on top of the transport layer so they are able to create and close new transport connections. RM Sender and Receiver are RM entities which goal is to ensure message delivery and reliability according to the specified RM policy. The expected model of RM sender/receiver is: * It will be a separate thread responsible for accepting/returning messages from/to JBossWS messaging layer * It will persist all messages going through it * It will query messages in the RM store against specific conditions * It will create RM tasks and put it to the RM task queue when re/send is necessary Picture of the client side follows (RM RECEIVER is similar): | | +-----------------------------------------------------------------------------------+ | | RM CHANNEL | | +---+ | | | | | | +-----------+ +---------+ | | | J | send(request) | | put(RM request) | | | | | B |------------------->| |------------------->| RM | | | | O | | | RM SENDER | | TASKS | | | | S | return response | | return RM response | QUEUE | | | | S |<-------------------| |<---------+ | | | | | W | | +-----------+ | +---------+ | | | S | | | A | | | | | | | | | +----------+ | | | | M | | | | | | | | | E | | write(request) | query | read(request) | | | | | S | | write(response) | | read(resposne) | | take RM task | | | S | | | | | | | | | A | | V | | | | | | G | | +-----------+ +---|------|------------------------+ | | | I | | | | | | | RM THREAD POOL | | | | N | | | RM STORE | | | V | | | | G | | | | | +----------+ +----------+ | | | | | | +-----------+ | | Thread 1 | ... | Thread N | | | | | L | | | +----------+ +----------+ | | | | A | | | A | | | | | Y | | +---|------|------------------------+ | | | E | | | | | | | R | | read(response)| | write(request) | | | | | | | | | +---+ | +----|------|------------------------+ | | | | | V | | +---+ | | | | +-----------------------+ | | | | | | | | | Output Stream |-------->| N | | | | | +-----------------------+ | | | E | | | | | | | | T | | | | | REMOTING TRANSPORT | | | W | | | | | | | | O | | | | +---------------------+ | | | R | | | | | Input Stream |<-----------------| K | | | | +---------------------+ | | | | | | | | | +---+ | | +------------------------------------+ | | | | | +-----------------------------------------------------------------------------------+ | | Definitions: NETWORK - Intranet or Internet network JBOSSWS MESSAGING LAYER - JBossWS messaging layer RM CHANNEL - is responsible for message acceptance from the JBOSSWS MESSAGING LAYER. Since this time this channel is responsible for reliable message delivery and will comunicate with JBOSSWS MESSAGING LAYER accordingly (i.e. ensuring message in order delivery etc ...) RM STORE - is responsible for persistent operations. It must be able to: * write message and its associated metadata, * read the message and its associated metadata, * query the messages in the store according to the specified criteria NOTE 1: Messages and their metadata must be fully de/serializable without dependency on the context class loader. That means all messages will be de/serialized before putting them to the RM STORE. NOTE 2: Messages and their metadata will be de/serialized in the same thread that initiated the invocation because of the heavy use of ThreadLocals in the JBossWS invocation framework. (However this requirement could be fixed by removing the ThreadLocal dependency) RM TASKS QUEUE - holds RM tasks identified by the RM SENDER/RECEIVER that have to be send to the transport layer RM THREAD POOL - holds RM threads that are responsible for doing the tasks stored in the RM TASKS QUEUE and execute them against REMOTING TRANSPORT NOTE: All this is about messages acceptance from the JBossWS messaging layer and ensuring the reliable delivery to the network and than back to the mesaging layer. It is not about the RM message creation on the SOAP layer. SOAP headers related to the WS-RM specification will be handled on higher level. IMPLEMENTATION LOCATION: I decided that the most suitable place to put RM CHANNEL to is the RemotingConnectionImpl class. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4085504#4085504 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4085504

17 years, 3 months

1
0
0 / 0

Re: Integrating apache-cxf

by Thomas Diesler

Hi Dan, yes, that's good. To enable the excluded tests you need to modify the exclude file in src/test/resources -thomas On Fri, 2007-08-24 at 11:02 -0400, Daniel Kulp wrote: > Thomas, > > OK. With your latest changes and renaming my jbossas dir to > just "trunk" (and updating the ant.properties files to reflect that), I > now have it successfully deployed. An > ant tests-main tests-smoke > now successfully runs 16 tests. > > I assume that means I'm up and running. That's a good start. :-) > > Next question: how do I now run the tests that are failing? If I try > something like: > ant -Dtest=jaxws/samples/logicalhandler test > > (taken from http://jira.jboss.org/jira/browse/JBWS-1753) > it doesn't run anything. > > > Thanks! > Dan > > > > On Friday 24 August 2007, Thomas Diesler wrote: > > Hi Daniel, > > > > thanks for your effort - please stay with me ... > > > > On Thu, 2007-08-23 at 16:35 -0400, Daniel Kulp wrote: > > > Thomas, > > > > > > On Tuesday 21 August 2007, Thomas Diesler wrote: > > > > as promised some days back, I changed the jbossws-cxf build system > > > > such that we can now integrate an arbitrary Apache-CXF snapshot. > > > > Please see > > > > > > > > http://jbws.dyndns.org/mediawiki/index.php?title=Building_From_Sou > > > >rce# Checkout_and_build_JBossWS-CXF > > > > > > > > for details. > > > > > > I've been trying to follow these instructions and haven't seemed to > > > gotten anywhere. > > > > > > First off: building the jbossas module doesn't work with those > > > instructions. It seems to download all the thirdpart stuff to > > > jbossas/../thirdparty, but then it tries to find some jars in > > > jbossas/thirdparty. > > > > This is bizarre and yes you are right. It seems that the checkout > > directory cannot be called 'jbossas'. I updated the page to use the > > default checkout name. > > > > > I worked around this by adding > > > a -Dproject.thirdparty=/path/to/thirdparty flag when I called > > > build.sh. That needs to be documented on that page or (preferably) > > > the build needs to be updated so it actually works. > > > > > > Second: when I run JBoss, I see: > > > 16:20:18,614 INFO [NativeServerConfig] JBoss Web Services - Native > > > > > > Fine. However, when I then go into the cxf build dir and run the > > > deploy, i now get all kinds of errors in jboss due to /jbossws > > > already being there. From that point on, jboss is completely > > > screwed. I cannot even shutdown jboss and restart. All kinds of > > > errrors occur on restart. I pretty much have to wipe out the > > > jbossas output dir and rebuild. > > > > > > I then tried to build jbossas, then "undeploy" the native stuff and > > > deploying the CXF stuff before running the run.sh. I then get: > > > *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required > > > State:Actual State} > > > > > > WSCXFDeploymentAspectInstallerEJB > > > -> WSDeploymentAspectManagerEJB{Configured:** NOT FOUND **} > > > -> WSDeploymentAspectInstallerEJB{Start:** NOT FOUND **} > > > -> WSDeploymentAspectInstallerEJB{Create:** NOT FOUND **} > > > > > > WSCXFDeploymentAspectInstallerPostJSE > > > -> WSDeploymentAspectInstallerPostJSE{Start:** NOT FOUND **} > > > -> WSDeploymentAspectManagerPostJSE{Configured:** NOT FOUND **} > > > -> WSDeploymentAspectInstallerPostJSE{Create:** NOT FOUND **} > > > > > > WSCXFDeploymentAspectInstallerPreJSE > > > -> WSDeploymentAspectInstallerPreJSE{Start:** NOT FOUND **} > > > -> WSDeploymentAspectManagerPreJSE{Configured:** NOT FOUND **} > > > -> WSDeploymentAspectInstallerPreJSE{Create:** NOT FOUND **} > > > > > > WSEndpointRegistry > > > -> WSMBeanServerLocator{Configured:** NOT FOUND **} > > > > > > WSServerConfig > > > -> WSMBeanServerLocator{Configured:** NOT FOUND **} > > > > > > > > > If I try to run the tests in that state, the test fails and I see: > > > > > > 16:29:52,175 ERROR [[TestEndpoint]] Allocate exception for servlet > > > TestEndpoint > > > java.lang.ClassCastException: > > > org.jboss.test.ws.jaxws.samples.asynchronous.TestEndpointBean > > > > > > That wouldn't be a CXF issue. > > > > Yes, you need to undeploy jbossws-native first. I updated the page to > > that respect. Yesterday I also fixed a bug where undeploy-jboss50 > > would incorrectly remove the container integration as well. This was > > the cause of the errors you describe above. > > > > > Basically, I'm completely stuck. Can you PLEASE provide some > > > better instructions on how to get it running. > > > > Yes of course. I updated the page with feedback from this thread. > > > > > I know pretty much nothing > > > about JBoss (or most any other J2EE app server for that matter), so > > > there really needs to be very good instructions as well as some > > > indication of what to I should expect to see on the consoles so I > > > know it's working correctly (or incorrectly as the case may be). > > > > Done. > > > > > Thanks! > > > Dan > > > > > > > The current situation is that the last cxf binary release (2.0) > > > > passes 16 out of 109 jaxws tests from our general jaxws test > > > > suite. Native and Metro pass all. CXF trunk does not build in > > > > hudson. > > > > > > > > http://jbws.dyndns.org:8180/hudson/ > > > > > > > > I individually looked at all failing tests and tried to identify > > > > the problems. Respective jira issues are created here > > > > > > > > http://jira.jboss.org/jira/secure/IssueNavigator.jspa?reset=true&m > > > >ode= > > > > hide&pid=12310050&sorter/order=DESC&sorter/field=priority&resoluti > > > >on=-1 &component=12311066 > > > > > > > > I also mirrored these jira issues in the Apache CXF bug tracking > > > > system. The next natural step would be to decide which bug > > > > tracking system to use (I don't have a strong preference - either > > > > would work for me). > > > > > > > > When this has been agreed on, jira developer rights should be > > > > setup such that the teams can assign issues to each other. On our > > > > end that would be me initially. Would you be able to name a person > > > > that I can assign issues to and work with to get these integration > > > > issues resolved in a timely manner? > > > > > > > > If there is anything else you require, please let me know. > > > > > > > > cheers > > > > -thomas > > > > > > > > PS: I'll be available until the end of this week. Then I'll be on > > > > holiday until Mon,17-Sep. During that period Heiko Braun will take > > > > over. > > > -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 3 months

1
0
0 / 0

jbossws hudson QA environment

by Thomas Diesler

Hi Ryan, I would like to bring the jbossws hudson QA environment http://jbws.dyndns.org:8180/hudson/ to the general jboss QA infrastructure. Ideally, we would like to have a dedicated box where we can setup and maintain our QA ourselves. Whats your take on this? cheers -thomas -- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Thomas Diesler Web Service Lead JBoss, a division of Red Hat xxxxxxxxxxxxxxxxxxxxxxxxxxxx

17 years, 3 months

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 September 2007