February 2007 - jboss-dev-forums - Jboss List Archives

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

by clebert.suconic＠jboss.com

Well... do as you wish... I would prefer a separate table.. (1 to 1 relationship) or the extra fields. Composed fields are worse than these extra fields IMO. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011615#4011615 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011615

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

by timfox

Also if don't get rid of them now, it will be very hard to do so later on. Since people may have written other systems / processes which rely on them. I don't want to be in a situation where we end up with a crappy schema we have to live with for ever. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011614#4011614 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011614

19 years, 2 months

1
0
0 / 0

[Design of JBoss Web Services] - Text nodes in SOAP messages

by alex.guizar＠jboss.com

In the TCK, the test case saaj/api/javax_xml_soap/SOAPElement contains two tests about adding text nodes to different SOAPElement subtypes, namely SOAPBody and SOAPHeader. Neither the specification nor the API documents are clear on which SOAPElement subtypes accept Text nodes. The TCK requires that SOAPBodies always accept Text nodes, whereas SOAPHeaders must accept them only if the protocol is SOAP 1.1. Apart from that, I saw our SOAPEnvelopeImpl class overrides addTextNode() to signal it is not legal to attach Text nodes to it. However, one can still add a Text node by invoking the DOM method appendChild(). How should we treat Text nodes? AFAICS there are three approaches in increasing order of effort: 1) Accept them in general, unless the TCK requires otherwise 2) Behave as the RI does 3) Scan the SOAP specifications and XML Schemas, as well as the Basic Profiles for explicit requirements or implicit clues View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011613#4011613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011613

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

by timfox

The thing is, JBoss Messaging is supposed to be a generic messaging system. Currently the DB schema has a depenency on JMS, which is wrong. If we support AMQP for example, are we going to add 10 more fields AMQP_Fluxfactory, AMQP_WibbleQuotient etc? I don't think so. All the generic properties will still be columns, e.g. delivery count, blah blah View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011611#4011611 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011611

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

by clebert.suconic＠jboss.com

These fields are Nullable anyway now. I just don't like the idea of composed fields on the DB. I prefer having the DB self documented. Maybe it's something I inherited from the days I was a consultant working with business systems. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011610#4011610 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011610

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

by jeffdelong

Might this information be useful to a human that is looking at messages that are sitting in a queue? It would be easier to read from a table than from the message header. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011609#4011609 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011609

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

by timfox

If we're going to allow for them being null in the future may as well get rid of them now. I don't want a load of garbage in the db. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011607#4011607 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011607

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JMS specific columns in DB

by clebert.suconic＠jboss.com

You will probably need to store the header on the database anyway, right? I guess putting this to a single field is not going to eliminate the dependency anyway as you still need the information. Those fields are nullable anyway... if using any other protocol in the future we could just keep them NULL. Maybe if you want to separate things you could add the word JMS_ to these fields then it's clear what they are for. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011605#4011605 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011605

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: http://jira.jboss.org/jira/browse/JBMESSAGING-808 - Fail

by timfox

One idea: When retrying a send (or a send transaction) after failover, you could add a flag in the request (checkForDuplicates = true). On the server side, when it processes the request, if this flag is true, then before inserting the messages, you can check in the database to see if the messages already exist (pm.referenceExists()) and if so, you silently ignore the request. This isn't perfect, and doesn't cope with the case where the message is acked before the duplicate arrives, but to deal with that we need duplicate message detection via a cache or something. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011583#4011583 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011583

19 years, 2 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: http://jira.jboss.org/jira/browse/JBMESSAGING-808 - Fail

by clebert.suconic＠jboss.com

"timfox" wrote : Ah right. | I was thinking you were retrying on the same partial queue. That's what I was expecting.. only the failedOver queue being used on the new server. But then I discovered the message being delivered somewhere I was not expecting. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4011582#4011582 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4011582

19 years, 2 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 February 2007