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

[Design of JBoss jBPM] - Re: process declared tasks

by camunda

Why not rename it to task-definition? Having two elements with the same name sounds a bit confusing to me View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234062#4234062 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234062

14 years, 11 months

1
0
0 / 0

[Design of JBoss jBPM] - process declared tasks

by tom.baeyens＠jboss.com

hi guys, just realized something. we renamed task-node (jbpm3) to task (jbpm4). so now we must also rename the globally defined tasks with tag 'task' in jbpm3. there are 2 options: 1) put them in a collection tag on the process top level 2) find another tag name for globally defined tasks i tend to think that 1) is the best solution. in that case we don't have to worry. and we can add it when we want without problems. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234061#4234061 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234061

14 years, 11 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - Re: I got failure in queue-message-redistribution

by jmesnil

I've reduced a bit the scope of the failure: it always fails if *server1/data* is deleted before the test is run. Delete server0/data and the example still works Starting server1 before server0 and the example still works (in this case, the deletion of server1/data will still make the example fails) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234059#4234059 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234059

14 years, 11 months

1
0
0 / 0

[Design of OSGi Integration] - Re: felix.framework.URLHandlersStreamHandlerProxy errors wit

by thomas.diesler＠jboss.com

I added support for jboss520 in trunk. AFAICS, this issue does not occur any more with felix-1.8.0 Here is a successful run http://jbmuc.dyndns.org:8280/hudson/job/jbossosgi-jdk16/36/ View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234056#4234056 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234056

14 years, 11 months

1
0
0 / 0

[Design of OSGi Integration] - Re: felix.framework.URLHandlersStreamHandlerProxy errors wit

by thomas.diesler＠jboss.com

Thanks, I look into it ... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234037#4234037 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234037

14 years, 11 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: How to Expose MBean Invocation Stats into admin-console?

by ALRubinger

It's this bit in DeployersImpl.getManagedObjects: for (DeployerWrapper deployer : deployers) | { | outputs.addAll(deployer.getOutputs()); | // If the deployer supports ManagedObjectCreator let is augment/modify the managed objects | if(deployer.getManagedObjectCreator() != null) | mocs.add(deployer); | } | // | mgtObjectCreator.build(unit, outputs, managedObjects); Meaning that only the *outputs* of all deployers are scanned. If you just add an attachment with a name, that won't get passed to DefaultManagedObjectCreator.build. So this helps in my deployer: du.addAttachment(uniqueName, bean, BeanMetaData.class); | this.addOutput(uniqueName); Is this the expected behaviour? Even still, I'm not seeing all the ManagedObjects that I'm expecting come through. More tomorrow. S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234031#4234031 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234031

14 years, 11 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: How to Expose MBean Invocation Stats into admin-console?

by ALRubinger

k, I'll debug in a few hours after dinner. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234015#4234015 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234015

14 years, 11 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: How to Expose MBean Invocation Stats into admin-console?

by scott.stark＠jboss.org

Correct, there can only be one BeanMetaData.class attachment in a unit. To have multiple BeanMetaDatas you need to create a component deployment and add the attachment to it. Its the org.jboss.deployers.spi.deployer.helpers.DefaultManagedObjectCreator that is building the set of managed objects for a deployment, and it is just iterating over all attachment names so I'm not sure why the unique name approach would not work. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234014#4234014 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234014

14 years, 11 months

1
0
0 / 0

[Design of JBossXB] - Re: Marshalling an AbstractKernelDeployment

by alex.loubyansky＠jboss.com

First of all, you should be using marshal method which takes SchemaBinding argument. SchemaBinding for AbstractKernelDeployment is created by parsing JAXB/JBossXB annotations, not by parsing the XSD (this XSD doesn't contain any binding information). You'll need to use one of the build methods of org.jboss.xb.builder.JBossXBBuilder to create SchemaBinding from annotated Java classes. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234012#4234012 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234012

14 years, 11 months

1
0
0 / 0

[Design of Management Features on JBoss] - Re: How to Expose MBean Invocation Stats into admin-console?

by ALRubinger

Cool, so I'm still going the POJO route to pave the way for the future. Plus it's easy to just write a deployer to do this. What I'm seeing however, is that only *one* @ManagedObject is exposed per DeploymentUnit, and it's whatever the last one added by my deployer is. ManagedDeployment: vfszip:/home/alrubinger/business/jboss/wc/jbossas/branches/Branch_5_x/build/output/jboss-5.2.0.Beta/server/default/deploy/stateless-test.jar/ | +++ ManagedComponent(name=org.jboss.ejb3.metrics.deployer.BasicStatelessSessionInstanceMetrics, type=(ComponentType{type=MCBean, subtype=*}), compName=jboss.j2ee:service=EJB3,name=UnsecuredStatelessBean-metrics-instance, attachment: org.jboss.ejb3.metrics.deployer.BasicStatelessSessionInstanceMetrics | ++++++ properties: [removeCount, currentSize, maxSize, createCount, availableCount Is this because of a non-unique name for the attachment? du.addAttachment(BeanMetaData.class, bean); The following does not pick up any attachments: du.addAttachment(uniqueName, bean, BeanMetaData.class) What's the deployer which inspects the DU attachments? Once I get all my attachments in place, I'm done w/ exposing EJB3 Metrics :) S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4234009#4234009 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4234009

14 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2009