March 2008 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: BeanFactory and IoC annotations support

by adrian＠jboss.org

For the simple BeanFactory case (i.e. no factory injection in its constructor), we can add the "bean class" as a related class automatically to the GenericBeanFactoryMetaData View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138734#4138734 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138734

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: BeanFactory and IoC annotations support

by adrian＠jboss.org

Related classes (see the JIRA issue) http://jira.jboss.com/jira/browse/JBMICROCONT-22. i.e. When I deploy my factory or some other container, I also want the dependencies on a given class resolved before the factory is deployed. | <bean name="MainClass" class="com.acme.Main"> | <related>com.acme.Related</related> | </bean> | This was initially raised for AOP where we need to know that com.acme.Main instantiates a com.acme.Related programmatically and that Related has aspects whose dependencies need to be satisifed before we deploy/invoke on Main. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138732#4138732 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138732

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Channel.AUTO_RECONNECT

by bstansberry＠jboss.com

The failure detection protocol on another node considers the node to have failed [1] and the VERIFY_SUSPECT protocol on the coordinator node concurs [2]. The coordinator then publishes a new view that doesn't contain the suspect node. But the node hasn't entirely failed; it begins working again and tries to send messages to the group, of which it is no longer a member. Typically this would be a case of something happening on the node that prevents it responding to FD heartbeat requests for a period. Maybe a 100% CPU situation or something blocking all the threads that pass messages up from the transport protocol. (In JG 2.4 there is just one such thread, so if it gets blocked for a while in the app, the node can be suspected.) [1] Details on the most common failure detection protocols: http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsFD[/url] and [url]http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsFD_SOCK[/url] as well as [url]http://wiki.jboss.org/wiki/Wiki.jsp?page=FDVersusFD_SOCK [2] http://wiki.jboss.org/wiki/Wiki.jsp?page=JGroupsVERIFY_SUSPECT View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138730#4138730 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138730

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - BeanFactory and IoC annotations support

by alesj

Currently we don't do anything with MC IoC annotations on beans that are created by bean factory (e.g. GenericBeanFactory). Handling them in createBean method is too late, since we loose the notion of dependencies, e.g. @Inject(bean="somebean") at that moment we can only do lookup and fail if 'somebean' is not installed, loosing what MC's state machine is all about. We could move annotations lookup in create() and set the dependencies whenRequired state to INSTALLED. But this will again only work if bean attribute is explicitly defined. In the case when bean is created through ConstructorMetaData.factory, there is nothing we can do to avoid problems previously mentioned - no true dependencies. Which road to take? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138728#4138728 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138728

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Shared Transport in JGroups

by clebert.suconic＠jboss.com

I have been testing JGroups 2.6.2 and it is working fine without any problems. However we need to update the configs at JBoss 5/multiplexor before the JBoss 5 release. It currently doesn't have Unicast as I could see. I'm a little confused to what will replace the multiplexor. Whatever it is we need the stack we currently use available on JBAS 5. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138727#4138727 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138727

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Missing class scope in InstantiateAction

by adrian＠jboss.org

"alesj" wrote : "alesj" wrote : But is this the right way? :-) | e.g. do we need some explicit MetaData removal from KernelMetaDataRepository before we change the scope key in ScopeInfo? You need to remove the old context before you change the key and re-register it. See the PreIntallAction or the KernelMetaDataRepository interface. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138722#4138722 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138722

18 years

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Channel.AUTO_RECONNECT

by clebert.suconic＠jboss.com

anonymous wrote : This means if these channels detect they've been shunned (kicked out of the group) they won't automatically disconnect() themselves and then connect() themselves to rejoin the group. Is this intentional? Brian.. in what situation they can be kicked out? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138721#4138721 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138721

18 years

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Implementing JAXB style parsing for aop-mc-int

by kabir.khan＠jboss.com

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: beanfactory injection

by adrian＠jboss.org

"alesj" wrote : "scott.stark(a)jboss.org" wrote : Guess I need to look into how to make the error more informative. | Like I said, and I think Adrian also already mentioned, we need to switch on the xml validation, for tests and real usage. | That would tell you the real problem, 'name' attribute doesn't exist on inject element. | That's a different issue. Turning on xml validation isn't going to help if you construct the BeanMetaData programmatically. We should add something to the "toHumanReadableString()" for the "anonymous inject" to ask whether they intended that it or just forgot to give a bean name. :-) | Bean2TypePool -> injection by interface org.jboss.beans.metadata.spi.factory.BeanFactory (or did you forget to supply a bean name for the injection?) {Installed:** NOT FOUND **} | Otherwise we're going to get lots of FAQs :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138714#4138714 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138714

18 years

1
0
0 / 0

[Design of JCA on JBoss] - Re: JBAS-4662 Implementation details.

by adrian＠jboss.org

The ha behaviours have been rolled into the main jdbc resource adapters. You should NOT need to handle it specially. You do not need seperate metadata for the ha case (it is now just an alias in the xml for backwards compatiblity). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138712#4138712 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138712

18 years

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 March 2008