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

[JBoss AS Development Deployment Framework] - Re: ManagementView API question/comment

by emuckenhuber

"ozizka(a)redhat.com" wrote : | 1) Shouldn't the name be ...Names? | We actually use this as a regular expression and do Patter.compile(regex) - so the naming should be fine. "ozizka(a)redhat.com" wrote : | 2) What's the point of throwing an exception in case of zero names found? Why not just reply with an empty set? Now when I just want to check remotely whether or not something is deployed, I have to: | | | | public boolean isDeployed( String name ){ | | try { | | Set<String> names = currentProfileView.getMatchingDeploymentName( name ); | | if( matchingNames.size() > 0 ) | | return true; | | } catch( Exception ex ){ | | if( ex.getCause() != null && ex.getCause().getCause() != null && | | ex.getCause().getCause() instanceof NoSuchDeploymentException ){ | | return false; | | } else { | | throw ex; | | } | | } | | | | instead of | | | | return currentProfileView.getMatchingDeploymentName( name ).size() > 0; | | | Yes, i agree - in this case throwing an exception does not make much sense, returning an empty list would be better to use. "ozizka(a)redhat.com" wrote : | 3) The same applies to getDeployment( String name ) - why not just return null? | | Perhaps there are some tech reasons to do it this ugly way, but I would like it to have the API more user-friendly. | Hmm, getDeployment(String name) should throw an Exception though. It's not intended to be used without previous actions like getDeploymentNames() - otherwise you'll never know which deployments are deployed. Usually when getDeployment(...) throws an except it would mean that the client and the management view are out of sync. We definitely are going to review the interfaces to make them more user-friendly and try to include some feedback we got so far. Thanks, Emanuel View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262609#4262609 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262609

16 years, 1 month

1
0
0 / 0

[JBoss OSGi Development] - Re: Extender Patter vs. LifecycleInterceptors

by thomas.diesler＠jboss.com

Could you pls elaborate on the use case for the adaptors? (i.e. what benefit would these adaptors bring) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262608#4262608 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262608

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool

by alesj

"flavia.rainone(a)jboss.com" wrote : | I have committed a temporary ugly hack, but I need to figure out how can I retrieve the classLoader in this scenario. | I've now at least removed the super horrible hack, but this code definitely needs a proper cleanup, as I've still found a bunch of weird things; catching NPE to do some logic, ... I've currently used reflection to get to the underlying classloader. This might not be so hackish, but we could still make some effort to see if there is a better way of doing this. | static | { | getClassLoader = AccessController.doPrivileged(new PrivilegedAction<Method>() | { | public Method run() | { | try | { | Method method = BaseClassLoaderSource.class.getDeclaredMethod("getClassLoader"); | method.setAccessible(true); | return method; | } | catch (NoSuchMethodException e) | { | throw new RuntimeException("Cannot get classloader from " + BaseClassLoaderSource.class.getName(), e); | } | } | }); | } | | static ClassLoader getClassLoader(BaseClassLoaderSource clSource) | { | try | { | return (ClassLoader)getClassLoader.invoke(clSource); | } | catch (Exception e) | { | throw new RuntimeException(e); | } | } | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262606#4262606 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262606

16 years, 1 month

1
0
0 / 0

[JBoss OSGi Development] - Re: Extender Patter vs. LifecycleInterceptors

by alesj

"thomas.diesler(a)jboss.com" wrote : Any MC bean can be a LifecycleInterceptor. It simply needs to implement that interface. | Sure. But do you already provide both adapters? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262600#4262600 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262600

16 years, 1 month

1
0
0 / 0

[JBoss OSGi Development] - Re: Extender Patter vs. LifecycleInterceptors

by thomas.diesler＠jboss.com

Any MC bean can be a LifecycleInterceptor. It simply needs to implement that interface. The LifecycleInterceptorService plugin picks those up at bean install time. | <bean name="LifecycleInterceptorService" class="org.jboss.osgi.framework.service.internal.LifecycleInterceptorServiceImpl"> | <constructor><parameter><inject bean="OSGiBundleManager" /></parameter></constructor> | | In any case (MCBean or registered programatically), the attachment handling is delegated to the DeploymentUnit. | <incallback method="addInterceptor" /> | <uncallback method="removeInterceptor" /> | </bean> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262591#4262591 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262591

16 years, 1 month

1
0
0 / 0

[jBPM Development] - Multiple instances with synchronization

by fabiomsouto

Hello, I'm currently developing a solution usign jBPM. After a few searches I found that jBPM does not support the pattern of multiple instances with synchronization, but I found a paper where they manually programmed it for jBPM 3. Here is the link http://www.computer.org/portal/web/csdl/doi/10.1109/PACIIA.2008.377 I was wondering if anyone more experienced in jBPM would help me implement this in jBPM 4. Thank you very much for your time. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262584#4262584 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262584

16 years, 1 month

1
0
0 / 0

[Tomcat Integration Development] - Re: jbossweb-tomcat.sar upgrade to Tomcat 5.5.28

by jfrederic.clere＠jboss.com

For our customers we don't replace the bundled 5.5.23 (or 20) by a 5.5.28 but we use the code in the repository. The repository contains all security patches to be as safe as a 5.5.28 Tomcat (and have be tested). If you really want to use 5.5.28 just build it and replace the jar files in your AS installation. Note that is not what JBoss supports so you may ended in troubles.... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262578#4262578 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262578

16 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: feature suggestion: add a description for transitions

by sebastian.s

You might be right, Bernd. But what about using a configuration setting which switches whether names or descriptions are shown? So the description could be completely optional. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262568#4262568 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262568

16 years, 1 month

1
0
0 / 0

[JBoss Microcontainer Development] - Re: Testing Deployers with new Reflect + ClassPool

by flavia.rainone＠jboss.com

The cause of the failure is that ClassPoolDomain was not copying the structure of a domain when the domain's parent is a ClassLoaderToLoader adapter. I have committed a temporary ugly hack, but I need to figure out how can I retrieve the classLoader in this scenario: if (domain.getParent() instanceof ClassLoaderToLoaderAdapter) | { | // how to get the domain.getParent()'s classloader??? | ClassLoader loader = ...; | ClassPool parentPool = ClassPoolRepository.getInstance().registerClassLoader(loader); | poolDomain = new JBossClClassPoolDomain(domain.getName(), parentPool, domain.getParentPolicy(), registry); | } View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262546#4262546 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262546

16 years, 1 month

1
0
0 / 0

[jBPM Development] - Re: Feature proposal: Availability and Reliability Overlay

by koen.aers＠jboss.com

Hi Aliaksei, I am reading through all the info on your site. This is some impressive piece of work! I cannot access the presentation on http://sites.google.com/site/jbpmhq/introduction-2/hqpredecessor though. There seems to be something wrong with the access rights. More feedback later ;-) Cheers, Koen View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4262528#4262528 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4262528

16 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums October 2009