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

[Design the new POJO MicroContainer] - Re: Field injection tests

by alesj

"scott.stark(a)jboss.org" wrote : Field/method injection of beans from a custom BeanFactory using a bounded pool with both successful injection, and failure due to no pooled instances available. | Can you write this down in API or xml? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138119#4138119 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138119

18 years

1
0
0 / 0

[Design of JBoss Build System] - Re: Shared Parent POM for dependencyManagement

by scott.stark＠jboss.org

Trying to do a mvn compile from the jbossas trunk I'm failing to find org.jboss.jbossas:jboss-as-component-matrix:pom:5.0.0-SNAPSHOT: | Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository | | org.jboss.jbossas:jboss-as-component-matrix:pom:5.0.0-SNAPSHOT | | from the specified remote repositories: | central (http://repo1.maven.org/maven2), | repository.jboss.org (http://repository.jboss.org/maven2), | snapshots.jboss.org (http://snapshots.jboss.org/maven2) | | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:197) | at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:73) | at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:526) | ... 18 more | I don't see this under http://snapshots.jboss.org/maven2/org/jboss/jbossas/. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138116#4138116 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138116

18 years

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP-MC-INT Beta Release

by adrian＠jboss.org

I see 8 failures using tests-no-weave | | Results : | | Tests in error: | | Tests run: 1353, Failures: 0, Errors: 8, Skipped: 0 | I'll go with that as a base line. Let's get this to no errors for the next beta. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138115#4138115 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138115

18 years

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP-MC-INT Beta Release

by kabir.khan＠jboss.com

| [junit] Running org.jboss.test.microcontainer.test.MicrocontainerAllTestCase | [junit] Tests run: 1156, Failures: 9, Errors: 54, Time elapsed: 30.546 sec | [junit] Test org.jboss.test.microcontainer.test.MicrocontainerAllTestCase FAILED | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138114#4138114 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138114

18 years

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: AOP-MC-INT Beta Release

by kabir.khan＠jboss.com

I have reverted the tests in trunk to work as they did in the previous release. I have run the non-secure versions of the tests and the not woven ones pass 100%. For the woven ones I am seeing some failures in MicrocontainerAllTestCase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138113#4138113 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138113

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Field injection tests

by scott.stark＠jboss.org

Field/method injection of beans from a custom BeanFactory using a bounded pool with both successful injection, and failure due to no pooled instances available. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138112#4138112 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138112

18 years

1
0
0 / 0

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

by scott.stark＠jboss.org

"adrian(a)jboss.org" wrote : | It's deliberately "not as integrated as it could be". | Because I want you to be able to write your own BeanMetaDataFactory | to do whatever you like, e.g. see the VFSClassLoaderFactory in the new classloaders. | | If you can't write your own then theres something wrong with the rest of the api. ;-) | | The beanfactory/GenericBeanMetaDataFactory is just an example that happens | to live in the MC codebase and xml namespace. :-) Yes, but we are talking about different apis. The BeanFactory which creates instances and BeanMetaDataFactory which provides collections of BeanMetaData. Maybe BeanFactory is no longer preferred and the beanfactoryType description in bean-deployer_2_0.xsd referring to GenericBeanFactory is out of date. I see the GenericBeanMetaDataFactory is annotated as the beanfactoryType as well. It seems both notions are needed, a BeanMetaDataFactory describes a collection of interrelated beans, the BeanFactory controls how instances are obtained. A javaee container has a BeanMetaDataFactory for its container/aspects, and a BeanFactory for obtaining instances. Back to my other question about the benefit of a beanfactory (as in BeanFactory) vs a ctor factory, its a semantic difference only from the point of view of who is actually creating bean instances. The mc deployer InstantiateAction has a one instance to one BeanMetaData view. I need a container notion where the state machine dependencies represented by the BeanMetaData collections end up injecting an instance that is a function of the "key" type for the bean and pooling policy. I guess this can be encapsulated in the injection value metadata, but its a bit abstract still. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138101#4138101 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138101

18 years

1
0
0 / 0

[Design of JBoss Web Services] - Re: Integration metro

by heiko.braun＠jboss.com

I was going through all the libs that come with the cvs checkout and replacing the shared ones with repository downloads. This includes looking at the manifest and identifying the corresponding version. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138086#4138086 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138086

18 years

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Generics again

by alesj

"adrian(a)jboss.org" wrote : | Like I said before, generics is not a way to avoid having to write a cast. | Its for telling the compiler what you are doing. | | I just upgraded to your latest test code in jboss-reflect which uses generics | yet there are 60 errors due to "unsafe type usage". | You mean BeanInfoUtilTestCase and the SetGetHook hack? Yup, almost the same mistake as FromContext. :-( It's the 'middle' nested beans that are the root of the problem, since I've hacked them to work with sub's. I think the original idea was generic OK. :-) "adrian(a)jboss.org" wrote : | Try using eclipse (with all the generics warnings turned on) | if you can't get IDEA to run -XLint from the JDK compiler. | | That way you'll learn how to correctly use generics. | Hmm, I think it's not that horrible, since apart from FromContext I don't remember any other generic hack that I've introduced in the main code. Perhaps a few tests might also be questionable ... But yeah, why not, I'll turn this on. In IDEA, definitely not in Eclipse. ;-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138080#4138080 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138080

18 years

1
0
0 / 0

[Design of EJB 3.0] - @SecurityDomain changes from AS42 to AS5

by alessio.soldano＠jboss.com

Hi, I was recently taking a look at some failing tests of JBossWS on JBoss AS 5.0 (http://jbws.dyndns.org:8180/hudson/job/Native-Core-AS-5.0.0/33/testReport... for instance). The problem seems to me that we're using the org.jboss.annotation.security.SecurityDomain to declare the security domain to be used, while the AS5 ejb3 aop interceptor (should be Ejb3AuthenticationInterceptorv2, right?) looks for the new org.jboss.ejb3.annotation.SecurityDomain. So no authentication actually happens. Of course using the new annotation make the test pass on AS5, but our testsuite is supposed to work on different containers; so we were wondering if you have any interesting suggestion about this or since AS 5 is a major release we can't do nothing else than using different annotations for different containers. Are there real differences among the two annotations, or is it really a package refactoring only? Thank you View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138079#4138079 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4138079

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