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

[Design of JBoss ESB] - Re: Scheduling of services

by mark.little＠jboss.com

I like that option. I think it's more extensible too. However, it sounds like more of a re-working of the architecture would be required to do that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065697#4065697 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065697

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Providing bean name aware feature

by alesj

"alesj" wrote : | Wrapper it is! Can / should I add unmodifiable wrappers to SPI? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065693#4065693 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065693

18 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: Redesigning eviction

by andyredhead

Hi, anonymous wrote : | When is an eviction needed? When we're running out of memory. If memory was infinite, we wouldn't need evictions. | I'm not sure this is the only scenario where an object needs evicting. I think another criteria would be that an object should be evicted when its state has become "stale". Sometimes the logic around what makes "stale state" is going to be so application specific that there could be no expectation that the cache works it out, however there are plenty of occasions where a broad-brush approach such as "objects under this sub-branch get evicted after X minutes". I have a couple of applications in production where JBossCache is used as a 2nd level cache for Hibernate and a time based eviction policy suits the application very well. I guess the point of this post is: 1) Pointing out that memory consumption is not the only driver for eviction 2) A simple policy (with simple configuration) will suite "real world" applications just fine, making it overly complicated to do easy stuff would be painful for us "simple users" (well, me anyway ;) 3) As what's there kind of works, perhaps the effort that would go into this would be better off put into something else for now (like standardising the AOP framework for the pojo cache, even better to be standardising on the JBOss AOP framework so that those of us who are tied to using the appserver don't have to learn another AOP framework or worry about how a different AOP framework will interact with JBoss AOP thats already being used in other parts of their applications...) Cheers, Andy View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065672#4065672 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065672

18 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Scheduling of services

by tfennelly

To add another twist to this.... What I was thinking re scheduling was to have a "ScheduledEventProvider" (e.g. <sevent-provider> that generates scheduled events). With that, you could then have a "ScheduledEventListener" (<sevent-listener>) which listens to the <sevent-provider>. The <sevent-listener> could be configured with a MessageComposer in the same way all (or at least some) of the other listeners can be configured with a composer (org.jboss.soa.esb.listeners.message.MessageComposer impl) that does whatever is needed. So, taking the WSListener as an example, it would actually be implemented as a MessageComposer that sits on a <sevent-listener> and when triggered (asked to "compose"), it goes off and makes the SOAP invocation and uses the result to compose the org.jboss.soa.esb.message.Message payload to be processed by the service pipeline (or whatever). Just another option :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065671#4065671 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065671

18 years, 8 months

1
0
0 / 0

[Design of JBoss internal QA (Test Suite)] - Testsuite Failures

by ambika

Hi, I am trying to run the testsuite of jboss 4.2.0 on a hpux platform. I have installed the jboss bin from the zip. Following is the error message for most of the testcases. Suite: org.jboss.test.aop.test.AOPUnitTestCase Test: unknown Type: error Exception: java.lang.SecurityException Message: Failed to authenticate principal=null, securityDomain=jmx-console Suite: org.jboss.test.cache.bean.MBeanUnitTestCase Test: testReplicatedPutTx Type: error Exception: javax.naming.NameNotFoundException Message: ejb not bound Suite: org.jboss.test.cache.test.aop.CacheObjectMBeanUnitTestCase Test: testBinding Type: error Exception: javax.naming.NameNotFoundException Message: test not bound Do i need to change any files? Regards, Ambika View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065663#4065663 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065663

18 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ProfileService aspects are no longer being applied

by scott.stark＠jboss.org

"kabir.khan(a)jboss.com" wrote : Just to decipher :-) | | If the currently woven/proxied class matches the interface in a pointcut expression, and no methods match, you want some error to be reported? | anonymous wrote : | | Correct. | | | | "kabir.khan(a)jboss.com" wrote : | | | But maybe using an annotation might be more robust? AFAICR we do not currently support checking annotations inherited from interface methods, but if desired that should be pretty simple to add | | Its not possible as in this case there are an unknown number of Deployers (the interface in the pointcut) and the Deployer interface is the only contract. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065613#4065613 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065613

18 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ProfileService aspects are no longer being applied

by kabir.khan＠jboss.com

Just to decipher :-) If the currently woven/proxied class matches the interface in a pointcut expression, and no methods mattch, you want some error to ne reported? That is probably possible. But maybe using an annotation might be more robust? AFAICR we do not currently support checking annotations inherited from interface methods, but if desired that should be pretty simple to add View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065606#4065606 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065606

18 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ProfileService aspects are no longer being applied

by scott.stark＠jboss.org

That does bring up the question of whether there could be type checking on an aspect. If you could say that the pointcut expression must match the given interface signature this error could be reported. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065604#4065604 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065604

18 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: ProfileService aspects are no longer being applied

by scott.stark＠jboss.org

Never mind. I did not realize the Deployer interface methods had changed that much. There are no longer any prepare/commit deploy/undeploy methods. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065603#4065603 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065603

18 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: Redesigning eviction

by galder.zamarreno＠jboss.com

Separating what to do with nodes that are evicted, such as deleting them from memory or passivating them has given us flexibility. Same should be done for what nnnn suggested. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065599#4065599 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065599

18 years, 8 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 July 2007