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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Valve on HAAspect (Repost)

by clebert.suconic＠jboss.com

I have just committed ValveAspect, as an extension of HAAspect. I want to have a design session with developers about this. if something is not right I can refactor it later. I could change this to use the aspect's XML, but from my point of view it would complicate another side of things (like how to get the ConnectinDelegate from any Delegate, and how to get the proper Valve in place). Right now I'm adding the Aspect to the stack using the API. This is to control the instantiation of ValveAspect, and also we will only install the aspect on clustered connection factories. We could play with two stacks, but the instantiation needs also to be taken in consideration. If we use plain pointcuts it will require us to aways navigate to ConnectionState/ConnectionDelegate from any given Delegate what would probably make the aspect use some ifdefs. (we can discuss this over a design session) As you can see I have also created an abstract type Valve, which encapsulates synchronized blocks and notifies. It's a very simple class but I liked the way I did, encapsulating the logic over there. (org.jboss.jms.util.Valve). It's a functionality so basic that I wondered if anyone else ever implemented such thing (probably yes). Another point is about ValveAspect extending HAAspect. I could move everything to HAAspect but it looked too messy when I had it only in one class. First because HAAspect exists per ConnectionFactory, while ValveAspect exists per Connection, and the use cases are a little bit different. ValveAspect will call failover in a connection, but it will block simultaneous calls. I have also moved the ConnectionListener into ValveAspect as I don't want simultaneous failover calls captured by try..catch or Remoting Lease. I still have a failure on ValveTest, but it's not caused by the Valve itself. The multi-thread has made the case a little bit worse, so we will have to investigate this independently of the valve development. Something about the Message is not on the channel (Paging support) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994471#3994471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994471

19 years, 3 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Valve on HAAspect

by clebert.suconic＠jboss.com

I have just committed ValveAspect, as an extension of HAAspect. I want to have a design session with you guys about this. if something is not right I can refactor it later. (Give me the chance to do it please ;-) ) I could change this to use the aspect's XML, but from my point of view it would complicate another side of things (like how to get the ConnectinDelegate from any Delegate, and how to get the proper Valve in place). Right now I'm adding the Aspect to the stack using the API. This is to control the instantiation of ValveAspect, and also we will only install the aspect on clustered connection factories. We could play with two stacks, but the instantiation needs also to be taken in consideration. If we use plain pointcuts it will require us to aways navigate to ConnectionState/ConnectionDelegate from any given Delegate what would probably make the aspect use some ifdefs. (we can discuss this over a design session) As you can see I have also created an abstract type Valve, which encapsulates synchronized blocks and notifies. It's a very simple class but I liked the way I did, encapsulating the logic over there. (org.jboss.jms.util.Valve). It's a functionality so basic that I wondered if anyone else ever implemented such thing (probably yes). Another point is about ValveAspect extending HAAspect. I could move everything to HAAspect but it looked too messy when I had it only in one class. First because HAAspect exists per ConnectionFactory, while ValveAspect exists per Connection, and the use cases are a little bit different. ValveAspect will call failover in a connection, but it will block simultaneous calls. I have also moved the ConnectionListener into ValveAspect as I don't want simultaneous failover calls captured by try..catch or Remoting Lease. I still have a failure on ValveTest, but it's not caused by the Valve itself. The multi-thread has made the case a little bit worse, so we will have to investigate this independently of the valve development. Something about the Message is not on the channel (Paging support) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994471#3994471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994471

19 years, 3 months

1
0
0 / 0

[Design of JBoss Web Services] - JBWS-1260 - Naming for anonymous types.

by darran.lofthouse＠jboss.com

I am currently working on JBWS-1260, I have a set of 27 different WSDLs that I have put through wscompile and I am then putting through wstools to compare the generated artifacts. I think this is a bug with wscompile but I just wanted to check before I override the generated descriptor from wscompile. The following is the input message: - | <element name='lookup' type='tns:Person'/> | | <complexType name='Person'> | <sequence> | <element name='Name'> | <complexType> | <attribute name='postcode' type='string'/> | </complexType> | </element> | </sequence> | </complexType> | When we create the java-xml mapping we map it using the following anonymous qname: - <anonymous-type-qname xmlns:typeNS='http://test.jboss.org/ws/jbws1260/types'>typeNS:>Person>Name</anonymous-type-qname> wscompile maps it as: - <root-type-qname xmlns:typeNS="http://test.jboss.org/ws/jbws1260/types">typeNS:lookup-Name</root-type-qname> View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994463#3994463 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994463

19 years, 3 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: Runtime profiler - linux 64

by clebert.suconic＠jboss.com

I have tried it with 64 and didn't have a problem. Are you using the download package from labs page? (the newest version?) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994434#3994434 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994434

19 years, 3 months

1
0
0 / 0

[Design of POJO Server] - Re: Moving forward with the profile service mgmt api

by scott.stark＠jboss.org

Yes, but I need to get the PS using a deployment repository that holds the modified deployment metadata to effectively test this. That is what I hope to get done this weekend. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994419#3994419 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994419

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Exception with Mysql during deployment

by kukeltje

- wrong forum - incomplete post (no code tags used) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994414#3994414 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994414

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: Serialization Compatibility Tests

by pavel.tsekov＠redhat.com

I added the news files to the Branch_JBossCache_1_4_0 branch. I also modified the build.xml to include a new target - "compat-tests". Now I'd like to create a database and add a test for it. Which releases are we going to test against ? Where should we keep the database ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994403#3994403 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994403

19 years, 3 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Other IoC containers support

by alesj

"alex.loubyansky(a)jboss.com" wrote : I tried to load this XSD w/o xml.xsd in the classpath and there was no problem. There was also no resource resolution. Commit or send me a testcase if it's still a problem. Funny, at first I again had problems - my test case failing, so I again added xml.xsd, but I tried it now - without xml.xsl - and it works like you said. But now I get different exception, which is bugging me for a while now: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=97354 I'm going through the XB code - which source code branch is used with current XB binaries used in MC? So that debuging code matches. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994402#3994402 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994402

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: deploying to jboss in development

by tom.baeyens＠jboss.com

look in jboss/configuration/build.xml for creating a jboss installation you can shoot all other specific questions in this forum. i know we should document this better, but that is a work in progress View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994393#3994393 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994393

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: deploying to jboss in development

by falazar

How exactly does that work? Can we get some stuff updated in the Wiki as well, or some good instructions. I go the new CVS compiling but a little confused on what to deploy and how to deploy it. James Ratcliff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994357#3994357 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994357

19 years, 3 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 December 2006