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

[Design of JBoss ESB] - Re: Proposed JBESB Configuration File Schema (JBESB-119)

by mark.little＠jboss.com

Dave, could you post a "before" and "after" example here, so we can discuss? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978512#3978512 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978512

19 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Proposed JBESB Configuration File Schema (JBESB-119)

by tfennelly

Hey Dave, I had a look at that there. Looking at the LoanBrokerConfig, I personally would find that format a bit difficult to follow. While it's XML, it's a very flat structure. I'd find it more difficult to read and navigate than I'd expect. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978509#3978509 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978509

19 years, 5 months

1
0
0 / 0

[Design the new POJO MicroContainer] - Re: Parameter matching issue?

by alesj

Add | <parameter class="java.lang.String">.jar</parameter> | so that you are more specific which ctor you want to use. There is a TODO (JIRA task) on better ctor/setter matching. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978500#3978500 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978500

19 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: extending form / task functionality

by kukeltje

I agree with Tom that initally there is no support for wizard style task handling. Since Seam already has pageflow and jBPM can be used to create those, I do see synergy in this. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978493#3978493 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978493

19 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: MessageService and JMS

by mteira

Hello again. I was not able to make it work with the configuration you pasted here. But I found the code where the configuration is parsed and I think that the only way to inject fields into a factory is to declare explicitly to be a BeanInfo. Looking at the code in JbpmContextInfo constructor, while iterating over the serviceElements: if (serviceElement.hasAttribute("factory")) { | String factoryClassName = serviceElement.getAttribute("factory"); | BeanInfo beanInfo = new BeanInfo(); | beanInfo.setClassName(factoryClassName); | serviceFactoryObjectInfo = beanInfo; | } else { | Element factoryElement = XmlUtil.element(serviceElement, "factory"); | if (factoryElement==null) { | throw new ConfigurationException("element 'service' requires either a factory attribute or a factory element"); | } | Element factoryBeanElement = XmlUtil.element(factoryElement); | if (factoryBeanElement==null) { | throw new ConfigurationException("element 'factory' requires either a bean or ref element"); | } | serviceFactoryObjectInfo = objectFactoryParser.parse(factoryBeanElement); | } I understand that when the 'factory' attribute is present, a BeanInfo is created using the no-args constructor, and then, only the className is set. The only way to create a BeanInfo with fields to inject is to create it using the | public BeanInfo(Element beanElement, ObjectFactoryParser objectFactoryParser) constructor. So, I've used this configuration to create the service factory: <service name="message"> | <factory><bean class="org.jbpm.msg.jms.JmsMessageServiceFactoryImpl"> | <field name="connectionFactoryJndiName"><string value="java:/XAConnectionFactory"/></field> | <field name="destinationJndiName"><string value="queue/JbpmCommandQueue"/></field> | </bean></factory> | </service> As you can see, I've used the same JbpmCommandQueue as the destination for the JMS Message Service, but I was not really sure about that. I was hypothesizing that everything that the message service can generate were Command instances, so new Commands would be generated after processing the Process Instance nodes, and those Commands would be also consumed by the CmdListener MDB. When I tried to send a Composite Command with (NewProcessInstanceCommand, SignalCommand) I finally got an Exception caused by: | org.jbpm.JbpmException: command listener bean only can handle object messages with Command's as the object. So, I think I'm missing part of the picture, and perhaps there's another queue involved. Could you please explain me the whole workflow of the JMS Message Service System? Best regards. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978492#3978492 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978492

19 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: extending form / task functionality

by tom.baeyens＠jboss.com

a wizard always relates to 1 task. the form in that case is just spread out over multiple pages. we currently don't forsee support for that in our default webapp console forms mechanism. getting the next task of the process if it is assigned to the logged on user is fairly easy to add to the current webapp. After a user ends a task in the task form, the webapp could check if there is a new task assigned to this user. If so, navigation could be redirected to this task form instead of the task list home page. does that answer the question ? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978489#3978489 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978489

19 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Status of web console enhancements

by tom.baeyens＠jboss.com

It turned out that pentaho was interested in developing a new process language on top of jbpm for specifying transformations in an ETL type of environment. Not sure what their status is on that. We are indeed going to develop a dedicated BAM functionality ourselves. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978488#3978488 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978488

19 years, 5 months

1
0
0 / 0

[Design of JBossCache] - Re: Hibernate Caching with JBossCache

by manik.surtani＠jboss.com

See http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossCacheHibernate Please note this forum is for discussing design issues in JBoss Cache. Please use the user forum for such questions in future. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978486#3978486 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978486

19 years, 5 months

1
0
0 / 0

[Design of JBossXB] - Re: Still got problems with groups

by alex.loubyansky＠jboss.com

Yes, there is a problem with global components (elements, attributes, groups). There should be a notion of local metadata/handlers/interceptors that are applied at their "use" in the schema. It's also similar to handling wildcard content. Especially when it's from a different schema. Also, for starting/ending buckets, there are callbacks for start/end repeatable term events. But they are not exposed at the moment as a public API. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978473#3978473 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978473

19 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: How to start jbossesb?

by tfennelly

Hi Jinmy. There are a number of guides (PDFs) in the distribution, one of which is a Getting Started Guide. Might try checking that out. As for the actual error you posted, it looks as though the "inputDirURI" config in the ".../TestJBossESB/paramsDir/FileMoverConfigExample.xml" is wrong. In the version of the ESB you downloaded, this parameter must be a valid URI. Also, the back-slashes are probably causing you trouble too. Current Setting: C:\de\jbossesb\product\docs\samples\TestJBossESB\inputDir Try: file:/C:/de/jbossesb/product/docs/samples/TestJBossESB/inputDir View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3978471#3978471 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3978471

19 years, 5 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 October 2006