November 2006 - jboss-dev-forums - Jboss List Archives

by mmieszek

Tom suggested that I could work on creating web unit tests for the web application. There's pemding issue for this on JIRA: http://jira.jboss.com/jira/browse/JBPM-269 I would like to discuss the subject. Tom, you wrote in March that you started the work. I have some questions: Can it be used as a base for futher development? For which branch should the tests be developed? Is there any policy or approach to writing web unit tests that I should follow? David, AFAIK you are refactoring the applications. Do you have any comments? As the web app is changing fast I think we should work closely on it. Kind regards, Marcin View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988170#3988170 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988170

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1178 implementation trouble

by maeste

Issue created: http://jira.jboss.com/jira/browse/JBWS-1399 and patch attached :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988167#3988167 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988167

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by timfox

"clebert" wrote : | We might need a design session to discuss what we have accomplished though. | Yes we should definitely do this ASAP so we can evaulate where we are and what remains to be done. When does America come back after Thanksgiving? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988159#3988159 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988159

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: DLQ implemented

by timfox

Ok, I am going to merge this into TRUNK before we forget. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988155#3988155 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988155

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JAXRPC / JAXWS terminology

by thomas.diesler＠jboss.com

anonymous wrote : | As part of my work in JBCTS-414 and the eventual SPI, I have refactored | the metadata builders. This also included renaming them to match this | terminology change. I also have split them into separate packages so | that each deployment type can eventually be pluggable. | Yes, this is good. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988154#3988154 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988154

19 years, 4 months

1
0
0 / 0

[Design of JBoss Web Services] - JAXRPC / JAXWS terminology

by thomas.diesler＠jboss.com

Jason sais: In order to avoid confusion, I think it is important that we stop referring to JAX-RPC deployments as "JSR-109 deployments". It's not really correct since JSR-109 governs EE integration for both JAX-WS and JAX-RPC. Instead, we should just call them "JAX-RPC deployments" Also, I think it is important that we make a clear distinction between JAX-WS and JSR-181. We should refer to the annotated endpoints that are in JBossWS 2.0.x as "JAX-WS endpoints", and only use the term "JSR-181 endpoints" to refer to the old JAX-RPC based preview technology that was in 1.0.x. So these two changes leave us with the following deployment types JAX-WS - 2.0.x JSR-181 - 1.0.x only JAX-RPC - 1.0.x and 2.0.x This usage of terminology should be consistent in both our code and documentation. As part of my work in JBCTS-414 and the eventual SPI, I have refactored the metadata builders. This also included renaming them to match this terminology change. I also have split them into separate packages so that each deployment type can eventually be pluggable. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988153#3988153 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988153

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by timfox

Ok, so it looks like good progress is being made on failover :) What is there left to do? My understanding is the remaining pieces are: Load balancing policy for determining which server to initially connect to. (Re-use from remoting). Mechanism for propagating changes in the client side server list from the server to the client when a jgroups view change occurs. I.e. when a new node joins / leaves. (Do we re-use from remoting here too?) "Valve" functionality to stall any activity on connections when server failover is occurring. Replaying of delivered messages to the ServerConmsumerEndpoint so the delivery list can be recreated. Anything else? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988152#3988152 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988152

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by timfox

"clebert.suconic(a)jboss.com" wrote : | Now... viewAccept will perform a failOver if a view is changed. I still need to add some logic to have only one server accepting the failOver but that is pretty easy. | The most trivial way of doing this is to define a failover node F of a failed node A as the node to the right (or left, it doesn't matter) of the failed node in the jgroups view. Also need to think of the view as a "ring". E.g. if the jgroups view has addresses: A B C D E then node A fails over to node B, node B fails over to node C, node C fails onto node D, node D fails onto node E, node E fails onto node A Questions: Is this sufficient for our needs? Is there any sense in supporting multiple failover nodes for a single node? Or does that make no sense? Should the policy really be pluggable? (Probably yes) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988150#3988150 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988150

19 years, 4 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ControllerStates sequential flow for dependent Contexts

by alesj

The bean / state will 'go' as far as you let him to go - applying the deployment mode, defined state, dependencies, demand, ... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988131#3988131 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988131

19 years, 4 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Server side HA and failover

by timfox

"clebert.suconic(a)jboss.com" wrote : I've created a new class called LeaveClusterRequest. | This request is sent over the cluster when PostOffice.stop is called. | Yep, that's the way to do it for now, as discussed. While chatting with Bela at JBW, he said he's going to look at extending the JGroups API so we can have the information of whether the node crashed or not directly. Although this won't be available for a while though. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3988130#3988130 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3988130

19 years, 4 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums November 2006