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

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Tests for JBoss MQ message counter functionality

by genman

Actually, I shouldn't have said it was very bad, as an HTML table is pretty nice for say, an operations team to view from the JMX console, but it doesn't really work in any other context, namely for machine parsing or putting it in a spreadsheet. It would be much more useful to have something like an XML element that could be more easily transformed. Something that should be fixed is that historical continues to accumulate in memory, and older data should be removed after some time (say, a month). And I believe the default configuration should have this set to a reasonable default. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999680#3999680 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999680

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Move search filter

by kukeltje

I disagree (as stated before), but a hide/show button is prefered (would that qualify as move them away ;-)) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999670#3999670 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999670

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: Last chance for any changes to the 2.0.0 API

by genman

A few last minute comments: 1. putIfNull -> putIfAbsent, See http://java.sun.com/j2se/1.5.0/docs/api/java/util/concurrent/ConcurrentMa... . People might get confused with "null" versus absent. 2. Remove the print* methods in NodeSPI. Or at least document them. Consider creating a separate util class to print a node. 3. removeChildDirect(Fqn) and removeChildDirect(Object) is a little confusing, since Fqn is a subtype of Object. I would probably suggest just having one or the other. 4. Some of the NodeSPI data methods appear to be just convenience methods and aren't strictly necessary given that getDataDirect() returns an externally modifiable map. For instance, clearDataDirect() really just is the same as NodeSPI.getDataDirect().clear(). So, it would be nice to understand the reason for these extra methods. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999669#3999669 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999669

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Add/Modify/List users in console

by kukeltje

this is already in a jira issue View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999665#3999665 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999665

19 years, 3 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Change user names in console

by kukeltje

+1 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999663#3999663 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999663

19 years, 3 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: resolveClass and annotateClass

by clebert.suconic＠jboss.com

I will verify about the annotateClass calls. Sorry about the delay answering this... I got messed up with my mail box.. probably didn't see the notification. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999651#3999651 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999651

19 years, 3 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: Cleanup of project, move to maven, svn?

by clebert.suconic＠jboss.com

I don't have any objections... I just didn't have time to do it before. Ruel had created a Maven build for jboss-serialization when he was working on maven scripts. It should be in good shape but I haven't tested it recently. .. talking about this new xml output stream... you are considering using jboss-serialization to serialize objects into XML format? Did I understand that correctly? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999650#3999650 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999650

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: Channel creation - mux vs. old style

by bstansberry＠jboss.com

Worse than I thought. Even if there is a exception in step 1 above, we catch the exception and try to create a channel from an old style config. If the JChannelFactory has been injected into the config, that's a clear sign it's meant to be used, so any failure should propagate. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999645#3999645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999645

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Channel creation - mux vs. old style

by bstansberry＠jboss.com

I think we are trying too hard not to fail in startService() if there is an issue with the mux configuration. We do this: 1) If a JChannelFactory has been injected into the config, use it and propagate any exception. 2) If no JChannelFactory is injected, but there is a mux service ObjectName in the config, try to find a mux service in JMX and use it to create the channel. 3) If there is an error in #2, but there is an old-style channel config, use that to create the channel 4) If there is no old-style config, use the default properties to create the channel. Three points: 1) #4 above is bogus. If they configured for mux and didn't specify an old-style config, failure to find the mux service should lead to an exception, not to a fallback on some default. The default properties should only be used if nothing else is configured. I'm going to change that. 2) Trying to find the channel in JMX is suspect, at least in JBoss AS where it can be dependency injected (even in 4.x). Manik put a comment in CacheImpl about that. 3) If we decide to keep the JMX lookup, if it fails, should we log a warn and fall back to the old style config, as in step 3 above, or rather throw an exception? (This is an irrelevant issue if we get rid of the JMX lookup). (NOTE: please don't get rid of the JMX lookup yet, as I still need it in the AS integration. Want to get rid of the need for it, but haven't yet.) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999644#3999644 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999644

19 years, 3 months

1
0
0 / 0

[Design of JBossCache] - Re: PojoCache uses a special node factory

by genman

One thing that I took a look at was the GUID used for some Pojo node data. The GUID itself can be divided into two parts. One is the machine/VM instance ID and the other is the per machine unique ID. Admittedly, this wouldn't help contention... NodeFactory should probably come from the RegionManager. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999643#3999643 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999643

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