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

[QA of JBoss Portal] - Re: SSO Unit Testing

by sohil.shah＠jboss.com

yeah. that sounds fine. I will create a very simple servlet based web application that uses the authentication mechanism of Portal and use that to test. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065093#4065093 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065093

18 years, 8 months

1
0
0 / 0

[QA of JBoss Portal] - Re: SSO Unit Testing

by julien＠jboss.com

I would prefer to use a simpler servlet as it decouples the feature from the portal and does not introduce a dependency of the test case on the portal configuration structure. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065076#4065076 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065076

18 years, 8 months

1
0
0 / 0

[Design of AOP on JBoss (Aspects/JBoss)] - Re: Optimizing genrated advisors

by kabir.khan＠jboss.com

The answer AFAIK is that there is no exact answer. Enough iterations for the JVM to run about 10 seconds should do I think View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065065#4065065 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065065

18 years, 8 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: Problem with -agentLib:jbossAgent

by clebert.suconic＠jboss.com

You are probably not using JVM 1.5. And as far as I know JBoss 3.2.3 doesn't support JVM 1.5. So this is probably right (that you are using JVM 1.4, which doesn't support the -agentlib paramter) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065053#4065053 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065053

18 years, 8 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - HAServiceMBeanSupport.callMethodOnPartition() doesn't return

by JerryGauth

I've been examining HAServiceMBeanSupport before modifying it for JBAS-4277. One observation is that HAServiceMBeanSupport.callMethodOnPartition() doesn't return results (e.g., return is void), even thoughthe underlying API call (ClusterPartition.callMethodOnCluster) does return results. Is this an oversight or by design? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065045#4065045 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065045

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Providing bean name aware feature

by alesj

"adrian(a)jboss.org" wrote : | I said don't do it, to which you responded "I'll do it anyway. ;-) | I can deny it and delete/edit the post. :-) But the 'mea culpa' would stay and haunt me ... anonymous wrote : | The point is that the internal MetaData model remains clean. | | The only thing you are changing internally is the "inject metadata" to allow | it to get things from the context instead of another bean. | | You can do whatever tricks you like with the xml and annotations to remove | any boiler plate as long it produces the same metadata underneath. | | There's a number of other areas where such a "shorthand" would be useful. | Yup. This is what it should have been done in the first place. :-( I'll ditch my crap and rewrite this to the upper features. If there is a bean attribute on the element as well, should I do the actual bean context lookup and perform the fromContext on that context? And for all the other cases - e.g. type and fromContext - throw exception? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065039#4065039 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065039

18 years, 8 months

1
0
0 / 0

[Design of POJO Server] - Re: Running with the full featured profile service

by scott.stark＠jboss.org

With the latest profileservice-beans.xml the profileservice config is starting up. I do see an error related to the hasingleton deployer, but it does not affect the ProfileServiceUnitTestCase. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065021#4065021 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065021

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Annotation features

by alesj

Since there is a really increasing demand for annotation usage with MC configuration, I think we should _finally_ provide a generic MC beans annotations handling. There are already some annotations present, but I think their lookup is scattered all over the place. I also went through some old posts which just touch on the topic of annotations: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=89400 http://www.jboss.org/index.html?module=bb&op=viewtopic&t=88620&postdays=0... http://www.jboss.org/index.html?module=bb&op=viewtopic&t=88613&postdays=0... There are some pointers to use the ClassInfo/BeanInfo: anonymous wrote : | The inspection should come from "reflection abstraction" | in the container module which is integrated via the | Configurator/BeanInfo. But is looks like this is not yet fully implemented: anonymous wrote : | 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. | Regarding the scattering: 1) I've started with a simple annotation handling with AnnotationDependencyBuilder and DependencyFactory(Lookup), but this is not yet enabled - DependencyBuilder is not pluged in. There was a question about using a chain of DependencyBuilders, but that's where it stopped. - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=107268 2) But on the other hand I'm doing a whole annotation lookup through MetaDataRepository in PreInstallAction. 3) And I do a straight annotation lookup via BeanInfo in LifecycleAction. I like the AnnotationDependencyBuilder with DependencyFactory approach - ok, some weak caching is missing and some other features - but if we are able to provide a generic annotation handling that way ... I guess some of the actual annotation handling will/is depending on the ControllerState we are in - specially regarding classes being present and actual bean instantiation with beanfactory. Perhaps doing DependencyBuilders depending on the state? Is changing the BeanMetaData legal when handling annotations? Or we need to do the cloning before this? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4065013#4065013 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4065013

18 years, 8 months

1
0
0 / 0

[Design of Security on JBoss] - Re: Security is broken in JBoss Head

by adrian＠jboss.org

Thanks! :-) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064986#4064986 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064986

18 years, 8 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Providing bean name aware feature

by adrian＠jboss.org

"alesj" wrote : "adrian(a)jboss.org" wrote : I thought I said not to add that xml config? | | You're not listening to any of my objections on this which has just led to all | | sorts of hacks and stupid configurations. | | | Yup. | I did respond I'll do them both though. :-( | I said don't do it, to which you responded "I'll do it anyway. ;-) | The thing is people - like ThomasD - want to write as little code as possible to get name injected. | Yes that is the annotation. anonymous wrote : | So that I don't screw it up for the Nth time, what should we use then? :-) | We just need a way to say I want to inject some metadata from the context. There could be other things in future like: | @Inject(fromContext="metadata") | void setMetaData(MetaData md); | | @Inject(fromContext="scope") | void setScope(Scope scope); | Though I doubt they will get used that often. More likely would be the GUID when it has been implemented. Injecting the name is probably not what people want anyway if the name exists in multiple scopes/deployments. | @Inject(fromContext="id") | void setID(Object id); | "adrian(a)jboss.org" wrote : | 3) The idea of hardwiring "setName" into the microcontainer code | as some kind of default is just stupid. | e.g. What if the bean already uses the "name" property for something else? You should be aware that setName is not used for bean name, and you actually set name-method attribute. Yes, but this is not what we want the annotation to look like. The XML should reasonably match the annotation in structure and features. If you're talking about ease of use then you can always have an alternative annotation/xml element that means the same thing as the long winded injection. e.g. | @BeanName // == @Inject(fromContext="name") | public void setName(String name); | | <property name="name"><bean-name/></property> | or even | <bean-name property="name"/> | Both of the xml examples above could be parsed to the real PropertyMetaData | <property name="name"><inject fromContext="name"/></property> | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4064983#4064983 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4064983

18 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 July 2007