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

[Design the new POJO MicroContainer] - Re: StructureContext and candidate annotations

by adrian＠jboss.org

I don't really understand what you are trying to do, but children are described by the ContextInfos of the StructureMetaData. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169016#4169016 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169016

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Pushing correct aspect manager for a deployment

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : . | Another problem is that for scoped deployments I am changing the beans name to something unique and adding an alias annotation containing the bean name. This breaks with the new code in BeanMetaDataDeployer. I will post more on this once I have some more information about what exactly is going on... Why? You'll break all sorts of assumptions related to deployment components the metadata scopes, and reporting incomplete deployments if you do that wrong. It seems to me that you need to take a step backwards to the original problem and explain what you are really trying to solve, rather than try to figure out what has broken because you are hacking at things you shouldn't. :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169014#4169014 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169014

17 years, 8 months

1
0
0 / 0

[Design of JBoss Deployment Framework] - Re: MBean Dependency not working as expected .

by adrian＠jboss.org

"vickyk" wrote : I have the following contents in the MBean deployment descriptor | | | | <?xml version="1.0" encoding="UTF-8"?> | | <server> | | <mbean code="org.jboss.test.jca.mbean.RaDependsOnMe" | | name="jboss.test:test=RaDependsOnMeMBean"> | | <depends>jboss.test:name=test</depends> | | </mbean> | | </server> | | The jboss.test:name=test is not present so I would expect that the RaDependsOnMe not to get registered/available for usage | | But to my surprise I see the MBean jboss.test:test=RaDependsOnMeMBean available from the jmx-console and I am able to call the sayHello() operation from the jmx-console . | | I tried this on Jboss5 , Jboss4.2 and Jboss4.0.5 . | | This looks to me as the bug . | | No. Depends is a contract on the create/start lifecycle not registration in the MBeanServer. To get what you want in JMX, you'd have to introduce something like the MC demand into the jmx xml. | <mbean code="org.jboss.test.jca.mbean.RaDependsOnMe" | name="jboss.test:test=RaDependsOnMeMBean"> | <demand whenRequired="Instantiated">jboss.test:name=test</demand> | </mbean> | Which doesn't currently exist within the -service.xml View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169010#4169010 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169010

17 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: JBCACHE-166 - TreeSet/Map, LinkedHashMap

by manik.surtani＠jboss.com

The problem with a createSortedNode() method on cache is the implicit creation of nodes. So what happens if you do: cache.createSortedNode(/a/b/c, mySorting); where /a exists and is sorted, but /b does not? Does /b get created as a sorted or unsorted node? I guess as long as any assumptions are clearly documented, then we can use that as the only mechanism to create a sorted node. Beyond that, we could use Node.isSorted() and Node.getSortedData(), Node.getSortedChildren() as you suggested, throwing exceptions if Node.isSorted() == false. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169004#4169004 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4169004

17 years, 8 months

1
0
0 / 0

[Design of JBossCache] - Re: JBoss Cache Public API

by manik.surtani＠jboss.com

Ok, will sort it out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168999#4168999 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168999

17 years, 8 months

1
0
0 / 0

[Design of JBoss Deployment Framework] - MBean Dependency not working as expected .

by vickyk

I have the following contents in the MBean deployment descriptor | <?xml version="1.0" encoding="UTF-8"?> | <server> | <mbean code="org.jboss.test.jca.mbean.RaDependsOnMe" | name="jboss.test:test=RaDependsOnMeMBean"> | <depends>jboss.test:name=test</depends> | </mbean> | </server> The jboss.test:name=test is not present so I would expect that the RaDependsOnMe not to get registered/available for usage But to my surprise I see the MBean jboss.test:test=RaDependsOnMeMBean available from the jmx-console and I am able to call the sayHello() operation from the jmx-console . I tried this on Jboss5 , Jboss4.2 and Jboss4.0.5 . This looks to me as the bug . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168997#4168997 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168997

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: StructureContext and candidate annotations

by alesj

"alesj" wrote : | Where MockEARStructureDepolyer then checks in | Module's StructureContext if we have any matching annotation. | In order to do this, I need some way to get a child StructureContext from parent StructureContext: e.g. | private Integer determineType(StructureContext context, VirtualFile archive) throws Exception | { | boolean recognised = context.determineChildStructure(archive); | if (recognised) | { | StructureContext subContext = context.getChildContext(archive); | Set<Class<? extends Annotation>> foundAnnotations = subContext.getFoundAnnotations(); | if (foundAnnotations.contains(Stateless.class)) | return J2eeModuleMetaData.EJB; | } | Where is the best way/place to store this info? While creating new StructureContext? | public StructureContext(VirtualFile root, VirtualFile parent, VirtualFile file, StructureMetaData metaData, VFSStructuralDeployers deployers, StructureContext parentContext) | { | ... | this.parentContext = parentContext; | if (parentContext != null) | { | // ADD CHILD INFO HERE | } | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168987#4168987 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168987

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Pushing correct aspect manager for a deployment

by kabir.khan＠jboss.com

I still do not get what I expect in the MetaData repository, none of the MetaDataRetrievals have a initialised metadataByName property. I noticed something else, before the call to | scopeInfo.setScope(unit.getScope()); | in BeanMetaDataDeployer scopeInfo.scopeKey is | [JVM=THIS, CLASS=org.jboss.beans.metadata.plugins.factory.GenericBeanFactory, INSTANCE=ScopedAlias_13_Factory$ScopedInterceptor, WORK=5644960] | after the call it is | [JVM=THIS, APPLICATION=vfszip:/Users/kabir/sourcecontrol/jboss-head/testsuite/output/lib/aop-scopeddependency-scoped.sar, DEPLOYMENT=vfszip:/Users/kabir/sourcecontrol/jboss-head/testsuite/output/lib/aop-scopeddependency-scoped.sar] | I will take a closer look at your KernelScopeUnitTestCase. Another problem is that for scoped deployments I am changing the beans name to something unique and adding an alias annotation containing the bean name. This breaks with the new code in BeanMetaDataDeployer. I will post more on this once I have some more information about what exactly is going on... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168986#4168986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168986

17 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Pushing correct aspect manager for a deployment

by adrian＠jboss.org

"kabir.khan(a)jboss.com" wrote : I see TestMetaDataBeanDeployer from JBDEPLOY-69 adds the metadata in a different way | The only reason I did it a different way was because the deployers were not fully configured in that test. I modified the test so it sets up the Deployer's MetaDataRepository from the Kernel's MetaDataRepository. The test now uses the mechanism you had originally and passes. | public class TestMetaDataBeanDeployer extends AbstractDeployer | { | public TestMetaDataBeanDeployer() | { | setStage(DeploymentStages.PRE_REAL); | } | | public void deploy(DeploymentUnit unit) throws DeploymentException | { | unit.getMutableMetaData().addMetaData("test", this, TestMetaDataBeanDeployer.class); | } | } | I don't what you are seeing? Can you modify the test to show it? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168985#4168985 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168985

17 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: StructureContext and candidate annotations

by alesj

"adrian(a)jboss.org" wrote : | Having said that I don't see why the getters for DeploymentResourceLoader and AnnotatedEnvironment are abstract. There should be default implementations in the abstract class. | Since the owner class is in deployers-vfs-spi, which doesn't know about the real impls, e.g. DefaultAnnotationEnvironment and VFSDeploymentResourceLoaderImpl. For this I've created additional AbstractVFSStructureDeployer, which has these impls as default. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4168984#4168984 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4168984

17 years, 8 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 2008