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

[Design of JBossCache] - Re: Pass event type to EvictionPolicy.canIgnoreEvents

by bstansberry＠jboss.com

Now that I've got your +1 there is: http://jira.jboss.com/jira/browse/JBCACHE-801 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977015#3977015 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977015

19 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1115 - Automatic detection of Tomcat port

by heiko.braun＠jboss.com

The only problem i see here is the disconnecgt between the MC and the JMX kernel. That particular attribute is managed by the MC. I think it should somehow be populated when the ServiceEndpointManager is initialized and not just bypassed when the WSDL is delivered. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977011#3977011 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977011

19 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBWS-1115 - Automatic detection of Tomcat port

by heiko.braun＠jboss.com

I stumbled across this several times as well. If you come up with a solution that would be perfect. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977010#3977010 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977010

19 years, 6 months

1
0
0 / 0

[Design of JBossCache] - Re: Pass event type to EvictionPolicy.canIgnoreEvents

by manik.surtani＠jboss.com

+1. Is there a JIRA task for this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977009#3977009 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977009

19 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: WS-Eventing and subscription expiration time

by heiko.braun＠jboss.com

Thanks, that's exellent news. Regarding your questions: 1.) I would say the properties should be read/write. 2.) Would you suggest makes perfect sense to me and could be applied to the same patch. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977008#3977008 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977008

19 years, 6 months

1
0
0 / 0

[Design of JBossCache] - Handling JGroups merging in JBoss Cache

by manik.surtani＠jboss.com

JBC currently does not handle JGroups merge events, mainly because there is no clear way of handling this. This is clearly not a concern for caches backed with shared cache loaders, but could lead to inconsistencies in other cases. The biggest problem here is that there is no 'correct' way of handling a merge. The approach proposed is to expose a MergePolicy interface and provide a default implementation (EvictOnMergePolicy?) which evicts the contents of the cache on merge, and allow end users to handle the merge manually. What, typically, would you need to handle a merge, what should this interface contain? BTW, this is for 2.1.0 - see http://jira.jboss.com/jira/browse/JBCACHE-471 View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977004#3977004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977004

19 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - WS-Eventing and subscription expiration time

by maeste

We made the patch for the feature described in this User's forum post: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=90201 I put two configurable properties in SubscriptionManager Mbean. I have two questions before putting the patch on jira: 1) Would you prefer the properties to be read/write or write only? | 2) I noticed jbossws throws an InvalideExpirationTime Excetion when I try to subscribe with an expiration time longer than maxLeaseTime. According to specification (5.4) this exception should be used only when the expiration time is in the past or the expiration duration is zero. I think it should answer with a valid registration forcing expiration time to maxLeaseTime (Specification 3.1). Could I put this fix in the same patch or do you prefer two different patches? | | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977002#3977002 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977002

19 years, 6 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: transaction support in JBossAS 5.0

by mark.little＠jboss.com

Oh, and I assume you have to durably record the mapping between the short-hand notation (long) and the real transaction id. Essentially keep a reference as to where your index (the long) has reached so that, upon failure and recovery, you can continue counting from where you left off (or you risk generating a new mapping using the same counter before half a million years is up ;-). This durable recording is going to impose some overhead: every time you increment the counter you have to record it to disk . Plus, it probably needs to be managed transactionally too. Or did I miss something? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976998#3976998 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976998

19 years, 6 months

1
0
0 / 0

[Design of JBoss Transaction Services] - Re: transaction support in JBossAS 5.0

by mark.little＠jboss.com

Yes, but in TP systems you never take a chance, no matter how small. Plus, I'm sure someone made a similar comment about date fields back in the 1960's and looks what happened come the year 2000! ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976994#3976994 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976994

19 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Application Server Integration Tests

by rachmatowicz＠jboss.com

I looked at the recommendadtions for running tests against the MC (as opposed to JMX) and I feel that pursuing it is the right approach, but perhaps not right at this moment. Given that the MC will replace JMX, running test cases against the MC will have to happen, and not just for JMS tests. Any framework designed should also be applicable to other classes of test cases. At present, even with AB's detailed design sketches, it's not clear ( to me :-( ) how elements common to most test cases should be organised - whether by delegation or through the use of QueueRequestors. I think we should have a detailed design of this new framework, which will essentially supercede JBossTestCase, and agreement on the design, before embarking on such significant changes. Therefore, i'm going to start applying the simplified refactoring today, taking JMS test cases from the jbossmq directory, refactoring them, and placing the refactored versions in jbossmessaging directory. When this is complete, we will have a set of generic JMS tests which will apply to either JMS provider, running in the context of the AS. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3976993#3976993 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3976993

19 years, 6 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 October 2006