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

[Design the new POJO MicroContainer] - Re: enums, generics and other animals

by alesj

"adrian(a)jboss.org" wrote : | Also, even for things like ControllerState you can create a helper class. | e.g. | | | public interface MicrocontainerConstants | | { | | String CREATE = "Create"; | | String INSTANTIATED = "Instantiated"; | | } | | | | That way people can reference the constants in their annotations | instead of suffering from typos for the common values. ;-) I though using interfaces to get access to constants was anti-pattern. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134848#4134848 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134848

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: enums, generics and other animals

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : If they are used by the annotations then they should be in the api. | Even the AutowireType? | Moving it out of spi? Yes. If it is used by the annotations then people need it to compile. Also, even for things like ControllerState you can create a helper class. e.g. | public interface MicrocontainerConstants | { | String CREATE = "Create"; | String INSTANTIATED = "Instantiated"; | } | | That way people can reference the constants in their annotations | instead of suffering from typos for the common values. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134847#4134847 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134847

18 years, 1 month

1
0
0 / 0

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

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : | Does that sound about right, or do you think I should get rid of some more types? Only if you think it causes you a problem. It is the elements that are the important thing since when you xsd:redefine they will become entry points into your schema so you don't want them in the common schema. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134844#4134844 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134844

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: enums, generics and other animals

by alesj

"adrian(a)jboss.org" wrote : If they are used by the annotations then they should be in the api. Even the AutowireType? Moving it out of spi? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134843#4134843 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134843

18 years, 1 month

1
0
0 / 0

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

by adrian＠jboss.org

Correct. Everything except the top level elements. I'd actually call the schema something like: jboss-beans-common-2.0.xsd You probably want to sync with Ales since he has a similar requirement for the policy xsd. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134842#4134842 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134842

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: enums, generics and other animals

by adrian＠jboss.org

If they are used by the annotations then they should be in the api. We should really look to move all the annotations (MC, Managed, etc.) to the jboss-integration project as seperate subprojects so people can consume just them for compiles as they need them No need to do this straightaway though. You'll conflict with what I'm doing if you do that now. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134840#4134840 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134840

18 years, 1 month

1
0
0 / 0

[Design of POJO Server] - Re: Another startup time regression

by dimitris＠jboss.org

I switched my local AS5 copy to AOP 'snapshot" and see a 20% improvement :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134839#4134839 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134839

18 years, 1 month

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

I'm trying to decide which types and groups to put into mc-common_1_0.xsd. The easy way is to put everything apart from: deploymentType beanType beanFactoryType lazyType Does that sound about right, or do you think I should get rid of some more types? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134835#4134835 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134835

18 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: enums, generics and other animals

by alesj

Where to keep all this enums? Since they are now scattered all over the place: ControllerMode --> org.jboss.dependency.spi // OK, this one is here to stay FromContext --> org.jboss.beans.metadata.plugins AutowireType --> org.jboss.beans.metadata.spi InjectOption --> org.jboss.beans.metadata.api.annotations The idea with annotations was to keep them in an 'api' package + have separate artifact for them, so user can use just that for his beans. And since now both, beans metadata and annotations, use the same enums, we should find some appropriate place. :-) Perhaps org.jboss.beans.metadata.api.enums? But there is the AutowireType which is part of spi? :-( Moving all but that one there? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134825#4134825 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134825

18 years, 1 month

1
0
0 / 0

[Design of JBossXB] - Re: Attributes problem

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | In the generic case (like the map's key/value) we don't have this option so we need | to "synthesize it" during the parsing. | I guess an alternative would be to create more parsing artifacts, something like: | public class MapEntry | { | public Holder key; | public Holder value; | } | | @BeanAdapter(HolderAdapterFactroy.class) | public class Holder | { | @XmlAttribute(name="replace") | boolean replace; | | ValueMetaData value; | | @XmlValue | public String string; | | //etc. | } | Then write some code in HolderAdapter.getValue() that tries to figure out what to return based on what to do based on what has been set. But this isn't very declarative and is only usable in the MC's map context rather than generically when others hit the same/similar problem. It's also a lot more code to write and maintain. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4134814#4134814 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4134814

18 years, 1 month

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