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

[Design of JBossCache] - Re: Eviction redesign

by mircea.markus

anonymous wrote : Re: XML configuration, I also propose dropping defaultPolicyClass and defaultEventQueueSize from the eviction element since there is a default element within the eviction element to denote settings for the default region defaultPolicyClass and defaultEventQueueSize are a convenient way of specifying default values for subregions, i.e. if a region is missing "policyClass" attribute. which is mandatory, then it would take the value from "defaultPolicyClass". On the other hand, the "" region is a syntactic sugar for "" which doesn't have to do with specifying default values (it might not even be present). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170365#4170365 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170365

17 years, 7 months

1
0
0 / 0

[Design of JBoss Profiler] - Re: challenge loading jboss-profiler on EAP 4.3

by rodgerca

Thanks I already read the readme.txt from start to finish. It can be a little confusing. I got the error because I put jboss-profiler-connectors in the %JBOSS_HOME%/bin directory. The profiler is working on the server side now. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170359#4170359 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170359

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MDR doesn't work on annotated privates (Repost)

by adrian＠jboss.org

"wolfc" wrote : anonymous wrote : | | My concern would be whether AOP needs to also use annotations on the | | method during the invocation and so know to use this Signature? | Not right now, because the EJB3 container sets up a manual interceptor chain. In future this chain should also come from aop.xml, then it might become a problem. | | Note that both web container & client container have so far been left out of scope. | That's not what I meant. If the method is enhanced using an AOP aspect, it may want access to the annotations, e.g. | @PostConstruct | @LogCalls(level=Leves.TRACE) | private void postConstruct() {} | | @Aspect | public CallLogging | { | public Object invoke(MethodInvocation invocation) throws Throwable | { | // This effectively does | // advisor.getMetaData().getComponentMetaData(new MethodSignature(invocation.getMethod())).getAnnotation(LogCalls.class) | LogCalls logCalls = invocation.getAnnotation(LogCalls.class); | | // Impl | doLog(logCalls, invocation); | } | } | Which would kind of work as it currently stands (since it doesn't validate the method). The "kind of" is because it is not intended to work, and wouldn't work if you don't use the constructor with the Method in it. If you don't pass the Method object, it has to search for the Method and will instead find the one in Sub.class. anonymous wrote : Is there a Jira for the new method signature? No JIRA, since we haven't decided what the proper solution is yet. As I see it there are currently two possible solutions: 1) Your's which is to introduce a new Signature, but this is going to be non-transparent to users, at least it doesn't interfere with more normal usages. 2) Morph MethodSignature to understand the "optional" class as part of the key. But this would complicate the equals()/hashCode() used to store and retrieve component metadata, e.g. Instance level metadata populated from the xml It would no longer be a simple get/put() semantic which would make writing MetaDataLoaders overly complicated and error prone. Callers who don't use the Method constructor would still have to know/pass the declaring class when constructing the signature to get the super method. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170354#4170354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170354

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MDR doesn't work on annotated privates

by adrian＠jboss.org

"wolfc" wrote : anonymous wrote : | | My concern would be whether AOP needs to also use annotations on the | | method during the invocation and so know to use this Signature? | Not right now, because the EJB3 container sets up a manual interceptor chain. In future this chain should also come from aop.xml, then it might become a problem. | | Note that both web container & client container have so far been left out of scope. | That's not what I meant. If the method is enhanced using an AOP aspect, it may want access to the annotations, e.g. | @PostConstruct | @LogCalls(level=Leves.TRACE) | private void postConstruct() {} | | @Aspect | public CallLogging | { | public Object invoke(MethodInvocation invocation) throws Throwable | { | // This effectively does | // advisor.getMetaData().getComponentMetaData(new MethodSignature(invocation.getMethod())).getAnnotation(LogCalls.class) | LogCalls logCalls = invocation.getAnnotation(LogCalls.class); | | // Impl | doLog(logCalls, invocation); | } | } | Which would kind of work as it currently stands (since it doesn't validate the method). The "kind of" is because it is not intended to work, and wouldn't work if you don't use the constructor with the Method in it. If you don't pass the Method object, it has to search for the Method and will instead find the one in Sub.class. Is there a Jira for the new method signature? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170354#4170354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170354

17 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Looking at deployment structure - JBAS-5823

by alesj

I'm done with porting the old deployment structure to new ManagedDeployment API: - https://jira.jboss.org/jira/browse/JBAS-5823 But there are a couple of issues: 1) in order to use this new API, we must run in profileservice configuration 2) deployment needs to go over DeploymentManager, which copies whole deployment, not what we've done before -> deployed directly from testsuite/output/lib 3) this API is asynchronous, so testing deployments requires some hacks (Thread sleep + multiple tries) I still need to fix ProfileService to properly undeploy/delete newly added deployments. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170350#4170350 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170350

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MDR doesn't work on annotated privates

by wolfc

"adrian(a)jboss.org" wrote : Ok, I understand now. It's not an override. | | This isn't even really java since without a setAccessible() it's illegal. :-) | | | | Sub sub = new Sub(); | | Method method = Super.class.getDeclaredMethod("doSomething"); | | // method.setAccessible(true); | | method.invoke(sub); | | | | Exception in thread "main" java.lang.IllegalAccessException: Class Sub can not access a member of class Super with modifiers "private" | | at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) | | at java.lang.reflect.Method.invoke(Method.java:588) | | at Sub.main(Sub.java:36) | | | | I guess it's mitigated by the super class having to add the annotation | that allows it? Ehr... nope, not really. You're still thinking to cleanly. ;-) "adrian(a)jboss.org" wrote : Since you don't need to setAccessible() to retrieve annotations from | the private super method then I don't think we would be introducing a security | hole by supporting it within the MDR (this prints null). | | | | Method method = Super.class.getDeclaredMethod("doSomething"); | | //method.setAccessible(true); | | System.out.println(method.getAnnotation(Inherited.class)); | | | | I'd say you're idea of a new Signature is probably the easiest way to resolve this. | | My concern would be whether AOP needs to also use annotations on the | method during the invocation and so know to use this Signature? Not right now, because the EJB3 container sets up a manual interceptor chain. In future this chain should also come from aop.xml, then it might become a problem. Note that both web container & client container have so far been left out of scope. Is there a Jira for the new method signature? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170338#4170338 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170338

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MDR doesn't work on annotated privates (Repost)

by adrian＠jboss.org

"wolfc" wrote : anonymous wrote : | | So I don't see why you have to look at annotations on overridden methods. | A private method is considered to be non-overriddable. So I need that declaring class somewhere. Ok, I understand now. It's not an override. This isn't even really java since without a setAccessible() it's illegal. :-) | Sub sub = new Sub(); | Method method = Super.class.getDeclaredMethod("doSomething"); | // method.setAccessible(true); | method.invoke(sub); | | Exception in thread "main" java.lang.IllegalAccessException: Class Sub can not access a member of class Super with modifiers "private" | at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) | at java.lang.reflect.Method.invoke(Method.java:588) | at Sub.main(Sub.java:36) | I guess it's mitigated by the super class having to add the annotation that allows it? Since you don't need to setAccessible() to retrieve annotations from the private super method then I don't think we would be introducing a security hole by supporting it within the MDR (this prints null). | Method method = Super.class.getDeclaredMethod("doSomething"); | //method.setAccessible(true); | System.out.println(method.getAnnotation(Inherited.class)); | I'd say you're idea of a new Signature is probably the easiest way to resolve this. My concern would be whether AOP needs to also use annotations on the method during the invocation and so know to use this Signature? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170330#4170330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170330

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MDR doesn't work on annotated privates

by adrian＠jboss.org

"wolfc" wrote : | So I don't see why you have to look at annotations on overridden methods. A private method is considered to be non-overriddable. So I need that declaring class somewhere. Ok, I understand now. It's not an override. This isn't even really java since without a setAccessible() it's illegal. :-) | Sub sub = new Sub(); | Method method = Super.class.getDeclaredMethod("doSomething"); | // method.setAccessible(true); | method.invoke(sub); | | Exception in thread "main" java.lang.IllegalAccessException: Class Sub can not access a member of class Super with modifiers "private" | at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) | at java.lang.reflect.Method.invoke(Method.java:588) | at Sub.main(Sub.java:36) | I guess it's mitigated by the super class having to add the annotation that allows it? Since you don't need to setAccessible() to retrieve annotations from the private super method then I don't think we would be introducing a security hole by supporting it within the MDR (this prints null). | Method method = Super.class.getDeclaredMethod("doSomething"); | //method.setAccessible(true); | System.out.println(method.getAnnotation(Inherited.class)); | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170330#4170330 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170330

17 years, 7 months

1
0
0 / 0

[Design of JBoss/Tomcat Integration] - Re: Building JBossWeb from Source

by remy.maucherat＠jboss.com

As with Tomcat, do "ant download" first. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170325#4170325 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170325

17 years, 7 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: MDR doesn't work on annotated privates

by wolfc

"adrian(a)jboss.org" wrote : So I'm no longer understanding this issue. | | In my example would Sub::postConstruct() be invoked or not? No, but if Super.postConstruct is private it must be invoked. "adrian(a)jboss.org" wrote : The part of the EJB3 spec you refer to says the opposite of your "weird part" | anonymous wrote : | | If a lifecycle callback interceptor method is overridden by another method (regardless of | | whether that method is itself a lifecycle callback interceptor method (of the same or different | | type)), it will NOT be invoked. | | | | My emphasis. | | So I don't see why you have to look at annotations on overridden methods. A private method is considered to be non-overriddable. So I need that declaring class somewhere. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4170321#4170321 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4170321

17 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 2008