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

[Design the new POJO MicroContainer] - Re: Fine grained action aware interfaces (JBMICROCONT-134)

by adrian＠jboss.org

"bkeh12" wrote : Hi,adrian | Where are you ? | alesj wrote : Currently all interfaces extend KernelControllerContextAware, which is convenient for simple awareness, but might not be that useful in all cases. | Do you agree this! | Can talk to us, please. Personally, I have little interest in this feature. :-) I think it is an anti-pattern of IOC for the "POJO" to implement container interfaces. I understand that sometimes it is useful, but only for people that are trying to "extend" the container without modifying the container itself, e.g. using AOP to add the interface as a mixin so you can pick and choose which beans get certain processing. Without more concrete usecases of these features it is difficult to come to any conclusion on what this api should really look like. The only reason I added it in the first place was because it mirrored the MBeanRegistration interface from JMX. The whole question then became more complicated when the "JMX Introduction" aspect couldn't decide whether it wanted be invoked at construction or configuration. :-) So we extended the api such that you could get a callback on any of the state transitions. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002883#4002883 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002883

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Why SingletonSchemaResolverFactory?

by adrian＠jboss.org

"alesj" wrote : I used this 'hack' to temp add new Spring schema: | | | public void setUp() throws Exception | | { | | SchemaBindingResolver resolver = SingletonSchemaResolverFactory.getInstance().getSchemaBindingResolver(); | | DefaultSchemaResolver defaultSchemaResolver = (DefaultSchemaResolver) resolver; | | defaultSchemaResolver.addSchemaInitializer("urn:jboss:spring-beans:2.0", new SpringSchemaInitializer()); | | defaultSchemaResolver.addSchemaLocation("urn:jboss:spring-beans:2.0", "mc-spring-beans_2_0.xsd"); | | super.setUp(); | | } | | | | But I agree with you. The Spring one (and other known ones) should be added to the singleton. If the initializer class is not in the classpath, it will ignore it. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002875#4002875 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002875

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Why SingletonSchemaResolverFactory?

by adrian＠jboss.org

There is an MBean/POJO that can be deployed to add schemas at runtime. The singleton is just a mechanism to setup "known ones" automatically. i.e. factory settings. There is a post about it somewhere in the JBossXB forum. If search worked I could find it for you. :-) e.g. | <bean name="Schemas" class="org.jboss.xb.binding.sunday.unmarshalling.SchemaResolverConfig"> | |  | <property name="SchemaInitializers"> | urn:somenamespace=some.class.name | </property> | |  | <property name="SchemaLocations"> | urn:somenamespace=schema/some.xsd | </property> | |  | <property name="ParseAnnotations"> | urn:somenamespace=false | </property> | </bean> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002874#4002874 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002874

19 years, 2 months

1
0
0 / 0

[Design of POJO Server] - Re: SerializableDeploymentRepository notions

by bill.burke＠jboss.com

I'm thinking of: | DeploymentContext.getAttachments().addAttachment(key, value, List<VirtualFile> metaSources); | Then, when getAttachment() is called, DC scans and checks to see if that attachment should be killed. Also, there should be additional methods on DeploymentContext: | | getAttachments(); | getManagedObjects(); | | These attachments would actually be serialized with the profile while getTransientAttachments() would not. If i'm being too obvious, then apologies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002873#4002873 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002873

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Plan to improve CMS integration

by julien＠jboss.com

"roy.russo(a)jboss.com" wrote : Nesting fixes the slowness and identity problems, but the CMSAdmin still doesn't show any directories. ok, I'll look into that tonight. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002870#4002870 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002870

19 years, 2 months

1
0
0 / 0

[Design of EJB 3.0] - Re: EJBTHREE-615 still present in Embedded-ALPHA9

by bill.burke＠jboss.com

We've totally scrapped Embedded EJB3 and started the Embedded JBoss project based on JBoss 5 kernel. New Embedded JBoss will be full featured. Most features of regular jboss should be available in embedded. If you want to testdrive, checkout head SVN. its in the jboss-head/embedded directory. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002867#4002867 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002867

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: ManagedProperty changes

by adrian＠jboss.org

Fair enough. The only reason for requiring a ManagedObject was that I thought the ManagedObject would be part of the identity. i.e. two properties with the same values but belonging to different managed objects would be different. See the "equals" implementation. It is generally desirable to have an immutable identity, i.e. no setManagedObject() If the properties are going to have a standalone identity then it is not an issue. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002858#4002858 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002858

19 years, 2 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Recent changes Microcontainer

by adrian＠jboss.org

"alesj" wrote : Using KernelConfigFactory to get KernelConfig (which can provide this)? | | Putting KernelConfig instance into Configurator? | It's a 'loop' usage. Looks wrong. | | I see we are already using KernelConfig as a parameter. | Doing it the same here (adding it as a parameter in resolveProperty method)? | If I do this (just tried), then almost every method in Configurator needs it. Yuck. | | Any other ways / ideas? | It is the KernelConfigurator that has this information. The problem is that the current code uses a static singleton as a delegate AbstractKernelConfigurator -> Configurator so one way to fix would be to move the code to the AbstractKernelConfigurator that needs kernel specific config. Perhaps a simpler solution is to expose the TypeInfoFactory on the TypeInfo interface. You would then be able to do | TypeInfoFactory typeInfoFactory = beanInfo.getClassInfo().getTypeInfoFactory(); | TypeInfo typeInfo = typeInfoFactory.getTypeInfo(name, classLoader); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002844#4002844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002844

19 years, 2 months

1
0
0 / 0

[Design of JBoss Portal] - Re: Plan to improve CMS integration

by roy.russo＠jboss.com

Nexting fixes the slowness and identity problems, but the CMSAdmin still doesn't show any directories. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002842#4002842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002842

19 years, 2 months

1
0
0 / 0

[Design of JBoss jBPM] - JMS Example in 3.2 Beta

by jeffdelong

There is a JMS Example (examples/jms) in the 3.2 Beta, however it does not appear to be complete. Can anyone provide more information on this example, as I am looking to do something very similar for the ESB project. Thanks, Jeff View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4002838#4002838 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4002838

19 years, 2 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