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

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

by kukeltje

Personally, I prefer personal and group. Sounds more 'natural' since for me a task that has just a group 'assigned' to it is already assigned. but just on a group level. Could be because in the real life situations I encountered, tasks could be 'assigned' to different groups during a process because e.g. it should go to a different department. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230563#4230563 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230563

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Sharing task nodes between processes

by kukeltje

This is a question for the userforum... please post there and I'll be happy to respond View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230561#4230561 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230561

16 years, 11 months

1
0
0 / 0

[Design of JBossXB] - Re: SchemaResolverDeployer and JBossXB

by jesper.pedersen

Installing the SchemaResolverConfig bean with all the JCA DTDs and XSDs did the trick (http://fisheye.jboss.com/changelog/JBossAS/projects/jboss-jca/trunk?cs=88744). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230557#4230557 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230557

16 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Sharing task nodes between processes

by Sujatha

how do I link the sub process with the mail process..just by name? the process which i create is always processdefinition.xml - so i have to keep it in some other folder and call it here? i dont understand how to do that? Can anybody help please..i am completely struck here.. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230539#4230539 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230539

16 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Where is the DDL for Messaging?

by clebert.suconic＠jboss.com

I just updated jb5 after Dimitris changes and was double checking the output: | clebert@MYBOX:/projects/JBoss5/build/output/jboss-5.1.0.GA/docs/examples/jms$ ls clebert@powerbox:/work/projects/JBoss5/build/output/jboss-5.1.0.GA/docs/examples/jms$ ls | clustered-hsqldb-persistence-service.xml | mssql-persistence-service.xml | oracle-persistence-service.xml | remoting-sslbisocket-service.xml | db2-persistence-service.xml | mysql-persistence-service.xml | postgresql-persistence-service.xml | sybase-persistence-service.xml | example-destinations-service.xml | ndb-persistence-service.xml | remoting-bisocket-service.xml | hsqldb-persistence-service.xml | null-persistence-service.xml | remoting-http-service.xml | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230526#4230526 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230526

16 years, 11 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Default JGroups Configs

by ALRubinger

https://jira.jboss.org/jira/browse/JBBOOT-72 And the failing case: /** | * Ensures that the partitioning properties are not initialized, | * and return null from {@link System#getProperty(String)} | * | * JBBOOT-72 | */ | @Test | public void testClusteringPropertiesUninitialized() throws Throwable | { | // Log | log.info("testClusteringPropertiesUninitialized"); | | // Initialize | server.initialize(); | | // Define property keys | final String udpGroupPropKey = JBossASServerConfig.PROP_KEY_JBOSSAS_PARTITION_UDP_GROUP; | final String udpPortPropKey = JBossASServerConfig.PROP_KEY_JBOSSAS_PARTITION_UDP_PORT; | | // Get Properties from System | final String udpGroupFromSystem = System.getProperty(udpGroupPropKey); | final String udpPortFromSystem = System.getProperty(udpPortPropKey); | | // Ensure null | final String failMessage = "Expected non-defaulted property value to be null from system property"; | TestCase.assertNull(failMessage, udpGroupFromSystem); | TestCase.assertNull(failMessage, udpPortFromSystem); | } S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230507#4230507 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230507

16 years, 11 months

1
0
0 / 0

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

by jaikiran

"kabir.khan(a)jboss.com" wrote : Although jaikiran says otherwise, AFAICR the filters are turned off for proxies anyway, they only apply to weaving classes. | I think there's a misunderstanding. When i said the EJB3 containers being deployed as MC beans, i meant the org.jboss.ejb3.EJBContainer and other such EJBTHREE project specific MC Beans and not the proxies that are generated for the end user EJB3 application deployments. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230504#4230504 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230504

16 years, 11 months

1
0
0 / 0

[Design of Clustering on JBoss] - Re: Default JGroups Configs

by ALRubinger

I'm brilliant: // Adjust for null | String valueToSet = value; | if (valueToSet == null) | { | valueToSet = ""; | } | | // Set | SecurityActions.setSystemProperty(key, valueToSet); Thanks, guys. :D S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230496#4230496 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230496

16 years, 11 months

1
0
0 / 0

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

by kabir.khan＠jboss.com

"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". Adding something to AOP to avoid the aspect dependency checking in the Describe phase and avoiding the proxy checking in the Instantiate phase is trivial. The question is the easiest/best mechanism to do so. I think the default should be to use AOP as current unless you opt out for a particular bean, since a lot of tests already rely on AOP being turned on. 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. The simplest option would be to add an annotation per bean instance, e.g. @NoAopCheck which would make the AOPDependencyBuilder a no-op, and force the AOPConstructorJoinPoint to avoid the heavy stuff and simply call the default implemetation in its super class BasicConstructorJoinPoint. So, AOP is either on (default) or off for a bean. As you say, this runs the risk of the class not getting the necessary aspects applied to beans where the aop stuff is turned off, but I don't see anything wrong with having this as a choice for an advanced user who knows what they are doing? You have to add the @JMX annotation anyway to register things in JMX, which seems to be the main use-case. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230495#4230495 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230495

16 years, 11 months

1
0
0 / 0

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

by jaikiran

"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's the hack that i tried when i first saw this behaviour :) And that's what showed me an improvement in the deployment timing. "adrian(a)jboss.org" wrote : | Otherwise you could just configure the dependency directly on the bean. | That's what we currently do for EJB3 containers. "adrian(a)jboss.org" wrote : | You'd be better off speaking to Kabir about how to optimise/avoid the AOP checking | for what you want than getting Ales to hack things into the MC that are fundamentally wrong. Sure, i don't mind trying out a different approach - whichever is the correct one :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4230492#4230492 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4230492

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