[Design of JBoss jBPM] - Task integration with external apps
by heiko.braun＠jboss.com
Hi Heiko,
pardon me for contacting you directly and bypassing the jBPM forums... We're currently integrating jBPM4 with a document management system that is based on Tapestry 4.1.5 and Spring, running in Tomcat 6. We're planning to go live with our application very close to the release date of jBPM4, so I suppose you can call us early adopters. I'm in touch with Andries Inze regarding the spring integration, but I suppose you are the right person to ask about what I'm working on right now.
I'm wondering what is the best way to integrate jBPM with our user interface and establish signalling of processes. I've seen your task form examples and the post in the developers forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155048), but
Nils wrote:
I'm wondering what is the best way to integrate jBPM with our user interface and establish signalling of processes. I've seen your task form examples and the post in the developers forum (http://www.jboss.org/index.html?module=bb&op=viewtopic&t=155048), but
1) I'm a bit lost as to whether there is a way to deploy those task forms together with our application in Tomcat
and
2) it seems like some things are still undecided (form reference in jPDL/Task still seems to be discussed etc.) and undocumented (I'm currently developing using the jBPM4 trunk and I didn't really find any task form documentation in the freshly built user guide)
My idea at the moment is to just display a task list in our user interface and use the process variables to generate links that work in our GUI framework. Then, by passing the task ids as parameters to our pages, we'll be able to detect that a user is accessing the page as part of a work flow and add specific buttons to provide signaling etc. I'm just wondering if this is a feasible way to do this or if I'm missing something and I'll windup re-inventing the wheel.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242535#4242535
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242535
16 years, 9 months
[Design of JBossXB] - Referencing the bean-deployer namespace from a custom metada
by david.lloyd＠jboss.com
In the jboss-logging.xml deployer that I'm developing, I want to reuse the MC's "AbstractPropertyMetaData" type in order to represent arbitrary properties that can be set on jboss-logging entities. To that end I have this:
| public abstract class AbstractHandlerMetaData {
| (...)
| private List<PropertyMetaData> propertyMetaDataList;
| (...)
| public List<PropertyMetaData> getPropertyMetaDataList() {
| return propertyMetaDataList;
| }
|
| @XmlElementWrapper(name="properties")
| @XmlElement(name="property", type=AbstractPropertyMetaData.class)
| public void setPropertyMetaDataList(final List<PropertyMetaData> propertyMetaDataList) {
| this.propertyMetaDataList = propertyMetaDataList;
| }
|
But I get a weird error:
| Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: The type of the attribute search must be simple or complex with a value adapter: org.jboss.xb.binding.sunday.unmarshalling.TypeBinding@6acbdf6e[null]
| at org.jboss.beans.metadata.plugins.AbstractDependencyValueMetaData.search
| at org.jboss.beans.metadata.plugins.AbstractClassLoaderMetaData.classLoader
| at org.jboss.beans.metadata.plugins.AbstractBeanMetaData.classLoader
| at org.jboss.beans.metadata.plugins.AbstractPropertyMetaData.value
| at org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList
| at org.jboss.logging.metadata.LoggingMetaData.handlerMetaDataList
| at org.jboss.logging.metadata.LoggingMetaData
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168)
| at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189)
| at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137)
| at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:256)
| at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:188)
| at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348)
| ... 33 more
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: The type of the attribute search must be simple or complex with a value adapter: org.jboss.xb.binding.sunday.unmarshalling.TypeBinding@6acbdf6e[null]
| at org.jboss.beans.metadata.plugins.AbstractDependencyValueMetaData.search
| at org.jboss.beans.metadata.plugins.AbstractClassLoaderMetaData.classLoader
| at org.jboss.beans.metadata.plugins.AbstractBeanMetaData.classLoader
| at org.jboss.beans.metadata.plugins.AbstractPropertyMetaData.value
| at org.jboss.logging.metadata.HandlerMetaData.propertyMetaDataList
| at org.jboss.logging.metadata.LoggingMetaData.handlerMetaDataList
| at org.jboss.logging.metadata.LoggingMetaData
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.rethrowWithLocation(JBossXBNoSchemaBuilder.java:2018)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.createRootElementBinding(JBossXBNoSchemaBuilder.java:346)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.createRootElements(JBossXBNoSchemaBuilder.java:321)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.build(JBossXBNoSchemaBuilder.java:232)
| at org.jboss.xb.builder.JBossXBBuilder.build(JBossXBBuilder.java:291)
| at org.jboss.xb.builder.JBossXBBuilder.build(JBossXBBuilder.java:181)
| at org.jboss.xb.builder.JBossXBBuilder.build(JBossXBBuilder.java:160)
| at org.jboss.xb.binding.resolver.AbstractMutableSchemaResolver.resolve(AbstractMutableSchemaResolver.java:261)
| at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:274)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401)
| at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source)
| at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
| at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
| at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
| at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
| at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
| at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
| at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
| at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199)
| ... 41 more
| Caused by: org.jboss.xb.binding.JBossXBRuntimeException: The type of the attribute search must be simple or complex with a value adapter: org.jboss.xb.binding.sunday.unmarshalling.TypeBinding@6acbdf6e[null]
| at org.jboss.xb.binding.sunday.unmarshalling.AttributeBinding.<init>(AttributeBinding.java:60)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:931)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1684)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1118)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1684)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1118)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1141)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateCollection(JBossXBNoSchemaBuilder.java:710)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:514)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1684)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1118)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1684)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1118)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.bindProperty(JBossXBNoSchemaBuilder.java:1684)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateType(JBossXBNoSchemaBuilder.java:1118)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:779)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateBean(JBossXBNoSchemaBuilder.java:767)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.generateTypeBinding(JBossXBNoSchemaBuilder.java:523)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.resolveTypeBinding(JBossXBNoSchemaBuilder.java:482)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.createElementBinding(JBossXBNoSchemaBuilder.java:361)
| at org.jboss.xb.builder.JBossXBNoSchemaBuilder.createRootElementBinding(JBossXBNoSchemaBuilder.java:341)
| ... 62 more
|
The weird thing is, this is all part of the bean deployer schema classes which were all registered already, so why is this suddenly a problem when my binding references it? Is there some other thing I need to do to make this work, or can I simply not reuse types in this way?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242519#4242519
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242519
16 years, 9 months
[Design of Management Features on JBoss] - Question about issue
by smarlow＠redhat.com
JOPR currently expects to use the Sun jmxremote support with AS 5.x, however, that doesn't seem to work when the following options are added to run.conf:
anonymous wrote :
| JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote"
| JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
| JAVA_OPTS="$JAVA_OPTS -Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl"
|
There seems to be at least two issues at play here:
1. The org.jboss.system.server.jmx.MBeanServerBuilderImpl class is not on the system classpath, so the Sun jdk classes cannot reference it.
2. Even if MBeanServerBuilderImpl became accessible via the system classpath, it seems that we need a different kind of bridge between the Sun JDK mbeanserver and the MC hosted mbean server.
Do we need a new MBeanServerBuilderImpl and LazyMBeanServer implementation that can provide a bridge between the MC and the Sun jdk jmx code?
Ideas?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4242486#4242486
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4242486
16 years, 9 months