February 2009 - jboss-dev-forums - Jboss List Archives

[Design the new POJO MicroContainer] - Re: Redeploy is done wrong

by scott.stark＠jboss.org

Yes, your right, the MainDeployerImpl does not know about the vfs. So can the existing DeploymentContext cleanup be leveraged for this, or would this drop the metadata repository info too soon? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210533#4210533 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210533

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBREFLECT-50, determining need for setAccessible bug

by david.lloyd＠jboss.com

Since the class is implementing a public interface, can't you get the Method from the interface instead of the class? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210532#4210532 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210532

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: JBREFLECT-50, determining need for setAccessible bug

by scott.stark＠jboss.org

Note that to integrate with the current security manager check done in setMethod, the fix should be something like this rather than what I show on the jira issue: | public void setMethod(Method method) | { | boolean callSetAccessible = false; | if (method != null) | { | int classModifiers = method.getDeclaringClass().getModifiers(); | boolean isPublic = isPublic() && Modifier.isPublic(classModifiers); | accessCheck(isPublic); | callSetAccessible = !isPublic; | } | | this.method = method; | | if (callSetAccessible) | setAccessible(); | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210529#4210529 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210529

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-1495 - Replicate Expiry and DLQ

by clebert.suconic＠jboss.com

"timfox" wrote : Management is always available. | Ok... I thought it was optional on the embedded case. anonymous wrote : Obviously if the server is not clustered you don't need to replicate The DLQ/expire/move call will be sent to Management, and Management will deal with that. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210528#4210528 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210528

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - JBREFLECT-50, determining need for setAccessible bug

by scott.stark＠jboss.org

I ran into a curious behavior I either never knew, or forgot regarding access permissions via reflection. In order for a method to be accessible via reflection without calling setAccessible on the method, both the method and the class have to be public. A public method in a non-public class cannot be accessed by the resulting java.lang.reflect.Method object. It fails with an java.lang.IllegalAccessException like that shown on JBREFLECT-50. I also show the required change to allow the ReflectMethodInfoImpl to determine when a call to setAccessible is needed. I'm going to need a new jboss-reflect release for the current work I'm doing on JBAS-6285. Its the jdk platform mbeans that are instances of non-public classes implementing a public interface that I cannot create valid ManagedObjects for because of this issue. Can I do a 2.0.3.GA release to pickup this fix for inclusion into jbossas 5.1.x? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210527#4210527 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210527

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-1495 - Replicate Expiry and DLQ

by timfox

Obviously if the server is not clustered you don't need to replicate View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210522#4210522 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210522

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-1495 - Replicate Expiry and DLQ

by timfox

Management is always available. You just need to replicate the messages as we have discussed (several times now)! View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210520#4210520 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210520

17 years, 1 month

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Redeploy is done wrong

by alesj

How would you pull this? IMO it needs to be on DeploymentContex, as that's what knows about vfs and old root. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210515#4210515 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210515

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: JBMESSAGING-1495 - Replicate Expiry and DLQ

by clebert.suconic＠jboss.com

I mean... I agree that Management should replicate calls properly when an user is using management to manually expire/move messages. However I don't think that QueueImpl should rely on Management to expiry queues, as Management may not be available, right? Or am I missing anything here? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210513#4210513 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210513

17 years, 1 month

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - JBMESSAGING-1495 - Replicate Expiry and DLQ

by clebert.suconic＠jboss.com

As part of the Expiry Queue and DLQ task, we have talked about using Management to send Move messages to the backup node. But that would add a dependency on Management for both DLQ and ExpiryQueue management. Do we really want to do that? IMO it would be better to have some sort Communication Channel between MessagingServerImpl on live and MessagingServerImpl on backup. This way if we embed start a server without Management, DLQ and Expiry would still work. Any thoughts? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210512#4210512 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210512

17 years, 1 month

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 February 2009