May 2009 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: OnDemand as an aspect

by alesj

"david.lloyd(a)jboss.com" wrote : What's the use case? | Any service that might be potential On_Demand activator. e.g. let's say we have a cmd line console (which we do btw ;-)) I don't wanna instantiate all the stuff unless somebody actually uses it == connects to it's ssh SocketServer. I would only install ssh deamon, while wrapping the Socket initalization logic with MC's On_Demand activation mechanism. This would then trigger full install of all other needed beans. But this means my code must know MC, no matter how simple we make the mechanism, is still too intrusive and users will never wanna depend on MC api. Which makes complete sense, as we always preach how transparent it should be to use IoC. And any other service that would serve as an activatior would have to do the same, which means a lot of copy/pasting, depending on the api that might even change (although it's a spi). "david.lloyd(a)jboss.com" wrote : | To me it makes more sense to restrict our usage of on-demand beans to deployments that are only activated if a user deployment consumes it declaratively (in other words, beans depend on beans; methods do not depend on beans). | That too. But that's the job of a profile service. Here we're talking fine grained stuff, and ctor, method, field invocation makes a valid activation use case. "david.lloyd(a)jboss.com" wrote : | Also, and I only speak for myself here, I'm personally really hesitant to invest more into AOP, given that AOP appears to be at least one key source of the performance problems that we have right now. | Afaic this is not really investing into AOP, it's investing into aspects. Or how else are you gonna make this transparent? I doesn't need to be AOP at the end, if you're not calling dynamic proxies AOP. We should provide a set of aspect, helpers, ... which could then be applied how ever the users want. But with having tight AOP integration already in MC, and it's not gonna go away any time soon, we might as well provide this AOP based approach out-of-the-box. Same way we do @JMX, @JndiBinding and Anil's @Password. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228845#4228845 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228845

15 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components

by jaikiran

"richard.opalka(a)jboss.com" wrote : | Why? JBossWS depends on EJB3 components. I don't see the reason why we should hide this dependency? We want and we need to be notified about EJB3 deployer changes. Ignore my previous comments :) I was wrong. Carlo explained to me that, it's EJB3 which should control the reference resolvers. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228840#4228840 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228840

15 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: ESB 4.6 tasks for consideration

by Kevin.Conner＠jboss.com

Any suggestions for monitoring improvements? http://www.jboss.org/index.html?module=bb&op=viewtopic&t=154908 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228833#4228833 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228833

15 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Improvements to monitoring

by Kevin.Conner＠jboss.com

We are now using JON to provide our monitoring facilities, what do you think of this? Which monitoring features would you like to see included/removed/improved in the next release of the project? Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228832#4228832 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228832

15 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Failure on ReplicationAwareJMSServerControlWrapperTest

by clebert.suconic＠jboss.com

All failures we have now are related to the connection issues we have already reported: http://hudson.qa.jboss.com/hudson/view/JBM%202/job/JBM2-tests/lastBuild/t... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228830#4228830 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228830

15 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Re: ESB 4.6 tasks for consideration

by Kevin.Conner＠jboss.com

Alternative registry implementations. http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228828 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228829#4228829 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228829

15 years, 8 months

1
0
0 / 0

[Design of JBoss ESB] - Alternative registry implementations

by Kevin.Conner＠jboss.com

We have had a number of requests to provide an alternative to scout/juddi as our registry. What issue would you want to see addressed by alternative registries? Which technologies would you wish us to support? Kev View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228828#4228828 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228828

15 years, 8 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: All sorts of failures with JDK 1.6

by clebert.suconic＠jboss.com

Maybe we should all switch to JDK 1.6. JDK 1.5 EOL is October 30, 2009: http://java.sun.com/products/archive/eol.policy.html View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228826#4228826 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228826

15 years, 8 months

1
0
0 / 0

[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components

by richard.opalka＠jboss.com

"jaikiran" wrote : | I did not find the definition for the org.jboss.ejb3.EjbReferenceResolver bean within that jbossws-deployer-jboss-beans.xml. Does this mean that JBossWS will rely on EJB3 deployer jboss-beans.xml to deploy an EjbReferenceResolver? :) | Exactly "jaikiran" wrote : | I would recommend that you define your own EjbReferenceResolver (with a unique MC bean name) within JBossWS to ensure that any changes to the EJB3 deployer will not affect JBossWS. | Why? JBossWS depends on EJB3 components. I don't see the reason why we should hide this dependency? We want and we need to be notified about EJB3 deployer changes. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228820#4228820 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228820

15 years, 8 months

1
0
0 / 0

[Design of JBoss Identity] - Re: WS-Trust Integration in JBoss Identity

by anil.saldhana＠jboss.com

Alessio/Stefan, let us keep this communication channel (namely this thread) active. Going forward, we need to be in proper sync with the multitude of SOAP stacks, xml binding libraries and internal JDK WS/xml stacks (starting JDK6) all playing havoc. The key here is to be in sync and proper documentation. :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228813#4228813 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228813

15 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2009