August 2006 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Bean instantiate order with contextual injection

by adrian＠jboss.org

"adrian(a)jboss.org" wrote : | Why would you be looking up the @Inject from the | AbstractDependencyValueMetaData (ADVM)? | It is a property of the class/method. | With the annotation approach it is your job to create/add an ADVM to the metadata. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964991#3964991 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964991

19 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bean instantiate order with contextual injection

by adrian＠jboss.org

"alesj" wrote : | But what about actual @Inject in class annotation? | Where to look/inspect class for them - to add dependency 'demand' items - how to get bean class from AbstractDependencyValueMetaData? | | ... | | How to add specific code about @Inject annotation into AnnotationMetaData.visit() - through children? | I don't understand either of these questions. Why would you be looking up the @Inject from the AbstractDependencyValueMetaData (ADVM)? It is a property of the class/method. AnnotationMetaData.visit() is used to process | <bean> | <annotation>... | Which AFAIK, (Kabir may know better) isn't properly integrated except when AOP is used. i.e. The Bean/ClassInfo is not updated with the annotation overrides. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964990#3964990 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964990

19 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bean instantiate order with contextual injection

by adrian＠jboss.org

If it gets complicated, it is probably better to turn into a first "delegate" object to avoid polluting the AbstractKernelController. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964987#3964987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964987

19 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bean instantiate order with contextual injection

by adrian＠jboss.org

"alesj" wrote : | | Where to hold such information? | Where you hold it now, e.g.: protected Map<Class, ClassContext> contextsByClass = CollectionsFactory.createConcurrentReaderMap(); private class ClassConext { private Set contexts; // other info } View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964986#3964986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964986

19 years, 7 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: Mustang Serialization problems.

by clebert.suconic＠jboss.com

This has to do the way JBossRemoting is solving classLoader operations. I believe JBossRemoting is aways doing loader.loadClass, and on JVM 1.6 it's supposed to aways do a Class.forName(..,...,classLoader). So.. it is some inconsistent change documented on compatibility issues on the JVM 1.6. We will have to change some code to work on JVM 1.6. As for the serialization type... on UnifiedInvoker you can add the parameter type to serialization parameter type="serialization" value="jboss" Take a look on Remoting documentation for the exact parameter name (I have such a bad memory :-)... and look for your UnifiedInvoker configuration. For EJB3 I believe is under ejb3.deployer directory. (If it wasn't changed recenlty) If you can't find I can do a quick research for you. Let me know on that case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964984#3964984 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964984

19 years, 7 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: Why JBossSerialization doesn't work on JRockit 1.4

by clebert.suconic＠jboss.com

I forgot to mention also they have changed something on JRockit's code for this to work. I haven't tested yet, but we will need a recent JRockit JVM for this to work. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964982#3964982 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964982

19 years, 7 months

1
0
0 / 0

[Design of JBoss Serialization] - Re: Why JBossSerialization doesn't work on JRockit 1.4

by clebert.suconic＠jboss.com

Henrik Stahi from BEA pointed me out this JIRA from XPath: http://jira.codehaus.org/browse/XSTR-311 Which is the same issue we had with BEA. I guess we will be able to run JBossSerialization with JRockit 1.4 with few changes. Looking at XPath's issue, the only difference is the way I'm acquiring Unsafe field. I will test it right away. Clebert Suconic View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964981#3964981 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964981

19 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bean instantiate order with contextual injection

by alesj

"adrian(a)jboss.org" wrote : | The best you can do (in general) is remember that a | contextual injection was done and if another candidate | appears after the fact then issue a warning. | Where to hold such information? anonymous wrote : assuming you are talking about annotations That too (see below). But what about actual @Inject in class annotation? Where to look/inspect class for them - to add dependency 'demand' items - how to get bean class from AbstractDependencyValueMetaData? anonymous wrote : | AbstractKernelController.preprocessMetaData() | is where this gets done (assuming you are talking about annotations). | However when we do classloading dependencies, some of this | will have to move to the DescribeAction such that we know | the class exists. How to add specific code about @Inject annotation into AnnotationMetaData.visit() - through children? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964979#3964979 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964979

19 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bean property inspection and actual injection

by adrian＠jboss.org

The inspection should come from "reflection abstraction" in the container module which is integrated via the Configurator/BeanInfo. The other parts of the injection is just mapping this to the context name via the new dependeny item which will then get used in the AbstractDependencyValueMetaData. Also your package names are wrong. Everything should be either under "spi" (contract - definitions) or "plugins" (implemementation details/choices) Injection is not a part of the general contract. It is a part of one possible implementation of the contract, i.e. the xml or AbstractDependencyValueMetaData The general contract is just the ValueMetaData and MetaDataVisitor. I do intend in future to define a proper contract such that you can more easily "write your own dependency". See other threads in this forum. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964976#3964976 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964976

19 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Bean instantiate order with contextual injection

by adrian＠jboss.org

"alesj" wrote : | I must probably put in a 'demand' of my property's class ... and for each context instantiation I supply all implementings classes? | | But what if there actually are more then one such matching bean - I would probably get the one that is first instantiated injected, discarting the fact that more matching bean can occur. | anonymous wrote : | | | | In general that is an unsolvable problem with hot deployment. | | | | You can solve it to the "first order" by requiring that any bean | | with a contextual injection waits for those without to be deployed. | | | | But then those beans with contextual injections may | | introduce extra matches, i.e. "second order". | | | | Try to solve the "second order" problem like the first leads | | to "third order" problems. | | | | The best you can do (in general) is remember that a | | contextual injection was done and if another candidate | | appears after the fact then issue a warning. | | | | anonymous wrote : | | | What about @Inject meta data? | | | Where to do the inspection and add dependency items? | | | | | | | AbstractKernelController.preprocessMetaData() | | is where this gets done (assuming you are talking about annotations). | | However when we do classloading dependencies, some of this | | will have to move to the DescribeAction such that we know | | the class exists. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3964972#3964972 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3964972

19 years, 7 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 August 2006