September 2007 - jboss-dev-forums

[Design of POJO Server] - Re: Unifying metadata

by alex.loubyansky＠jboss.com

Unless Adrian wants to look into that, I can. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087309#4087309 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087309

18 years, 6 months

1
0
0 / 0

[Design of Clustering on JBoss (Clusters/JBoss)] - Re: Transaction Sticky LB policy for 4.2/trunk

by bstansberry＠jboss.com

Yes, please add for standard LBs. :) There are some tests of EJB 2 and 3 load balancing but they don't really cover all the LB impls and probably don't cover as many cases as you could. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087308#4087308 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087308

18 years, 6 months

1
0
0 / 0

[Design of JBoss Remoting, Unified Invokers] - Re: Transport Use Cases

by jason.greene＠jboss.com

"ron.sigal(a)jboss.com" wrote : The use of Remoting by JBossWS is a counterexample, since they use a Remoting client without a Remoting server, but I can't say much more than that, not being very familiar with their code. | JBossWS uses Remoting solely for basic client side http transport functionality. SOAP marshalling is implemented in JBossWS using a custom remoting marshaller. The server side component of JBossWS is currently just a servlet, which is needed for container integration, however, it was also desired for remoting to provide a lightweight standalone http server API. Tom did a prototype awhile back using an embedded slimed down version of tomcat, but it would also be a good idea to reuse any VM provided http server, the sun vm includes one, for example. This is obviously less important than the main and more prevalent use cases of remoting, but I thought I would mention it nonetheless. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087303#4087303 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087303

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme

by alesj

"adrian(a)jboss.org" wrote : You can getCallerClassLoader() using code similar to the HACK class in the classloader project, although it is suble because you need to skip reflection classes. Probably there is no reflection invocation in classloading code? | protected Class<?> getRequestingClass(Class[] stack) | { | for (Class clazz : stack) | { | if (Hack.class.isAssignableFrom(clazz) == false && | JDKChecker.class.isAssignableFrom(clazz) == false && | BaseClassLoaderDomain.class.isAssignableFrom(clazz) == false && | BaseClassLoaderPolicy.class.isAssignableFrom(clazz) == false && | ClassLoader.class.isAssignableFrom(clazz) == false && | Class.class.isAssignableFrom(clazz) == false) | { | return clazz; | } | } | throw new RuntimeException("Should not be here!"); | } | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087301#4087301 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087301

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme

by adrian＠jboss.org

You can getCallerClassLoader() using code similar to the HACK class in the classloader project, although it is suble because you need to skip reflection classes. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087295#4087295 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087295

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme

by scott.stark＠jboss.org

"alesj" wrote : | Eh silly me, didn't even think for a second :-(, there are ManagedProperties for that kind of stuff. :-) | | How do you currently invoke those? | Since I think they should be invoked the same way as ManagedOperations - over the KernelBus. | That's why we introduced AttributeDispatchContext. The properties are updated during the ManagementView.process call based on what updateComponent calls have been made. These currently just map back to the deployemnt attachment. For those properties with a ViewUse.RUNTIME setting: | public enum ViewUse | { | /** A read-write property used for creating/updating a config */ | CONFIGURATION, | /** A read-only type of property */ (this comment is wrong, its an extension of CONFIGURATION that has a runtime component the property change should be dispatched to) | RUNTIME, | /** A read-only type of property that provides runtime stats */ | STATISTIC | } | we also need to send the change to the runtime component. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087293#4087293 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087293

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ManagedObject support in next messaging release

by scott.stark＠jboss.org

Here is another approach that also moves toward having the annotations in the xml config. We do have some annotation support in the service mbean descriptors, for example: | <mbean name="jboss.test:type=BasicMBeanName" code="BasicMBeanCode"> | <annotation>@org.jboss.test.system.metadata.annotation.CompType(type="DS",subtype="LocalTX")</annotation> | </mbean> | so I can add a ManagedCode annotation that allows you to specify the class to scan for the management annotations. You can then add empty subclasses of the jms destination mbeans in the server/messaging project and then specify the management annotations on those, and point to those classes using the annotation element. Perhaps this can reuse the legacy mbeans Clebert updated. I have reopened JBAS-4658 for this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087289#4087289 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087289

18 years, 6 months

1
0
0 / 0

[Design of POJO Server] - Re: ManagedOperation aspects for the ProfileService.Manageme

by adrian＠jboss.org

"alesj" wrote : | Is this enough: | The question is will the callers have that privilege. e.g. Where this occurs is when somebody is deploying a bean from xml That will run under the privileges of whoever registered the MC context. We should be testing whether they can get access to the classloader of the other context to create the objects, otherwise it is a security hole. We don't want somebody using the MC to create objects they wouldn't otherwise have access to. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087287#4087287 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087287

18 years, 6 months

1
0
0 / 0

[Design of JBoss Web Services] - Re: JBossWS productization

by thomas.diesler＠jboss.com

Development continues in trunk until we reach code freeze. Then we branch and do the remaining QA related work in that branch. Finally we tag from the QA branch. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087283#4087283 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087283

18 years, 6 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: ManagedObject support in next messaging release

by timfox

Can't we just annotate via xml as Ales mentioned? That would make life a whole lot easier View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4087278#4087278 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4087278

18 years, 6 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 September 2007