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

[Design of JBoss jBPM] - Re: swimlane candidate roles - task list allocations

by kukeltje

Again, please use the userforum for this. Has nothing to do with the development ON jBPM, merely development WITH jBPM. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230682#4230682 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230682

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: swimlane candidate roles - task list allocations

by heiko.braun＠jboss.com

anonymous wrote : | Tasks therefore firstly get assigned to an organisation and then to an individual within it. | Be careful with the terminology here. A "candiate-group" statement doesn't "assign" the task. It merely states what groups (or group members actually) are elected for an assignment. Even when the task finally get's assigned to a user, the "candidate-group" remains an orthogonal entity. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230681#4230681 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230681

16 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: DESCRIBE phase - Dependency builders for MC Beans

by alesj

"kabir.khan(a)jboss.com" wrote : "adrian(a)jboss.org" wrote : | | If you really want to exclude the AOPDependencyBuilder processing from a bean then | | you should really use one of AOP's existing mechanisms like exclude "org.jboss.ejb3.*" | | from having aspects applied to it (that can be configured on the AspectManager). | | | | That way AOP should be able to "short circuit" the aspect dependency checking | | for those pojos using the same "filters". | The current filters are classname based, which is not a good choice for this. Although jaikiran says otherwise, AFAICR the filters are turned off for proxies anyway, they only apply to weaving classes. | What exactly do you mean by "current filters are classname based"? You cannot do globing (org.acme.foobar.*) like Adrian suggests? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230680#4230680 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230680

16 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - FailBackupServerTest in a loop of 1000?

by clebert.suconic＠jboss.com

Is that on purpose? It takes forever.. and sometimes it times out on Hudson. Tim: I'll revert it back to 5 and it looks it was an accident. Feel free to commit it back to 1000 if you really meant to do it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230653#4230653 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230653

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - swimlane candidate roles - task list allocations

by citylights

How are task lists impacted when we are using swimlane candidate-groups which both a user and a group of users [organisation] can belong? The intention is to support workflow task allocations across organisational boundaries. Tasks therefore firstly get assigned to an organisation and then to an individual within it. In the jPDL xsd I can not see how to assign human tasks [wait states] to a swim lane with a candidate-group. The eclipse GPD v4 does not seem to allow for this. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230643#4230643 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230643

16 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: All sorts of failures with JDK 1.6

by clebert.suconic＠jboss.com

I did a run with JDK 1.6 ** by accident ** today, and it wasn't as bad as it was before. I had a few issues with out of files... but it wasn't as bad as it was. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230637#4230637 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230637

16 years, 11 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: ManagedObjects for MBeans

by scott.stark＠jboss.org

I have expanded the ProxyManagedDeploymentFactory to support multiple mbeans under a single MBeanDeployment so that a single ManagedDeployment results. Now all three of the war related mbean types are found under a single ManagedDeployment, for example, the jmx-console has the following ProfileServiceDebugServlet view: | ManagedDeployment: //localhost/jmx-console | +++ ManagedComponent(name=jboss.web:host=localhost,path=/jmx-console,type=Manager, type=(ComponentType{type=MBean, subtype=WebApplicationManager}), compName=jboss.web:host=localhost,path=/jmx-console,type=Manager, attachment: null | ++++++ properties: [sessionIdLength, maxInactiveInterval, expiredSessions, entropy, sessionCounter, maxActiveSessions, className, processingTime, algorithm, processExpiresFrequency, rejectedSessions, sessionAverageAliveTime, randomFile, modelerType, duplicates, pathname, sessionMaxAliveTime, activeSessions, name, maxActive, distributable] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,j2eeType=WebModule,name=//localhost/jmx-console, type=(ComponentType{type=MBean, subtype=WebApplication}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,j2eeType=WebModule,name=//localhost/jmx-console, attachment: null | ++++++ properties: [privileged, compilerClasspath, crossContext, swallowOutput, antiResourceLocking, caseSensitive, cookies, workDir, loader, unloadDelay, path, managedResource, objectName, servlets, tldScanTime, realm, namingContextListener, configFile, modelerType, saveConfig, stateManageable, state, eventProvider, cacheTTL, cachingAllowed, cacheObjectMaxSize, startupTime, statisticsProvider, javaVMs, manager, staticResources, override, docBase, defaultContextXml, server, startTime, defaultWebXml, deploymentDescriptor, mappingObject, parentClassLoader, processingTime, useNaming, delegate, antiJARLocking, valveObjectNames, cacheMaxSize, logger, engineName, allowLinking, children, reloadable, welcomeFiles] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=DisplayOpResult, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=DisplayOpResult, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=jsp, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=jsp, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=ProfileServiceDebugServlet, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=ProfileServiceDebugServlet, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=default, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=default, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=DisplayMBeans, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=DisplayMBeans, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=InspectMBean, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=InspectMBean, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=ClusterView, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=ClusterView, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=ClusteredConsoleServlet, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=ClusteredConsoleServlet, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | +++ ManagedComponent(name=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=HtmlAdaptor, type=(ComponentType{type=MBean, subtype=Servlet}), compName=jboss.web:J2EEApplication=none,J2EEServer=none,WebModule=//localhost/jmx-console,j2eeType=Servlet,name=HtmlAdaptor, attachment: null | ++++++ properties: [objectName, minTime, statisticsProvider, loadTime, classLoadTime, processingTime, requestCount, modelerType, errorCount, stateManageable, eventProvider, engineName, maxTime] | This is based on a single ProxyManagedDeploymentFactory in the profileservice-jboss-beans.xml that combines the three types of mbeans: | <bean name="WarManagedDeploymentFactory" | class="org.jboss.profileservice.management.ProxyManagedDeploymentFactory"> | <property name="factoryName">War</property> | | <property name="defaultViewUse">STATISTIC</property> | <property name="rootMOPatterns"> | <set elementClass="org.jboss.profileservice.management.ProxyDeploymentInfo"> |  | <bean class="org.jboss.profileservice.management.ProxyDeploymentInfo"> | <property name="compType">MBean</property> | <property name="compSubtype">WebApplicationManager</property> | <property name="pattern">jboss.web:host=localhost,type=Manager,*</property> | <property name="nameBuilder"> | <inject bean="WarManagerMBeanDeploymentNameBuilder"/> | </property> | </bean> |  | <bean class="org.jboss.profileservice.management.ProxyDeploymentInfo"> | <property name="compType">MBean</property> | <property name="compSubtype">WebApplication</property> | <property name="pattern">jboss.web:J2EEApplication=none,J2EEServer=none,j2eeType=WebModule,*</property> | <property name="nameBuilder"> | <inject bean="SimpleMBeanDeploymentNameBuilder"/> | </property> | <property name="componentInfo"> | <map keyClass="java.lang.String" valueClass="java.lang.String"> |  | <entry> | <key>servlets</key> | <value>MBean:Servlet</value> | </entry> | </map> | </property> | </bean> | </set> | </property> | </bean> | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230636#4230636 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230636

16 years, 11 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: DESCRIBE phase - Dependency builders for MC Beans

by jason.greene＠jboss.com

"alesj" wrote : "jaikiran" wrote : But in the long term, shouldn't we be moving away from this default? | | | No, that's why it's called *transparent* AOP integration. ;-) | | You can only argue that the AOP mechanism is not performant enough, | but that's as far as I agree with you. | Although this comes with a cost, it does bring lots of nice features. | They are mostly true in a sense of AOP; aspects, concerns separation, ... | @JMX, @JNDI, @Password, @(add-your-own-metadata-here) are good examples of this. | And if I was a user, that's what I would want too, out-of-the-box. | It can be the greatest feature in the world, but if the performance sucks as bad as this does, no one will use it. In general we should avoid expanding our usage of this until we know that the design is even fixable. I do agree that supporting various service annotations is useful, and there is even some value in having pluggable behavior. However, building this behavior using arbitrary pointcut expressions in arbitrary locations is beyond overkill. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230635#4230635 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230635

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: names for personal task list and takable task list

by brittm

We often use the terminology "user" queue and "group" queue to distinguish. This seems to be terminology that our users understand. "Personal" would work just as well as "user". View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230621#4230621 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230621

16 years, 11 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: JBAS-6875 discussion thread

by bstansberry＠jboss.com

Both trunk and Branch_5_x are updated. Thanks again, Scott. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230586#4230586 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230586

16 years, 11 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 May 2009