July 2007 - jboss-dev-forums - Jboss List Archives

[Design of JBoss jBPM] - Re: Failure handling

by bill.burke＠jboss.com

"estaub" wrote : | If my description isn't clear, let me know and I'll elaborate. | Hey Ed, can you elaborate? You're doing async actions? Not async nodes? Async actions seem pretty scary to me, mainly because of failures and your PI could be in an inconsistent state of some actions succeeding and some failing. I've never really written a jBPM application, so maybe my fears are just superstition. You tell me... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069361#4069361 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069361

17 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Failure handling

by bill.burke＠jboss.com

I think I have a different solution to yours: dead letter queue processing. You can take the code as-is, add a MDB that listens on the dead letter queue. The node could have a "failure" transition. Dead Leter MDB could see if the node had that transition and just transition to it. Thoughts? I'm thinking that JBPM should have a failure-transition that could be describe in the process definition. The failure-transition is different from exception handling in that exception handling allows you to recover, failure handling changes the state of the PI to a failure state that you can do BPM on. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069354#4069354 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069354

17 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Re: Failure handling

by estaub

Yeah, I've written a couple of posts about this too. No one responded with a solution. I intend to run actionhandlers that may setRollback() in another transaction. I'm running in a J2EE CMT environment, so I've got a local bean with a command-pattern interface for performing the action, set to REQUIRES_NEW. In practice, it looks like ActionHandlers using this pattern will mostly consist of a static inner command class. If my description isn't clear, let me know and I'll elaborate. I don't have any experience with this approach yet, so it may fall apart for some reason I haven't thought of. If you think of something better, please sing out! -Ed Staub View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069345#4069345 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069345

17 years, 5 months

1
0
0 / 0

[Design of JBoss jBPM] - Failure handling

by bill.burke＠jboss.com

I'm thinking of a scenario of asynchronous continuations that travel over JMS. I don't see a way of handling a transaction rollback and transitioning to a new state based on that event. Yes, jBPM has exception handlers, but these seem to run within the JTA transaction started by the command service MDB. Since this transaction would be rolling back you wouldn't be able to transition out of that state, right? Or am i missing something fundamentral? So, what I'm saying is, shouldn't there be the ability to rollback the transaction, catch that, then transition to a failure state? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069320#4069320 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069320

17 years, 5 months

1
0
0 / 0

[Design of JBoss Portal] - Can not deploy helloworld portlet

by saigon_man

Hello, I am trying to deploy the helloworld.war portlet as said in the reference document. Once I deploy the war file, there is no helloworld portlet showed up in the main page. What am I missing here? I am using JBoss portal 2.6.1 bundled with Jboss server. Your help is appreciated Thanks, sg View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069314#4069314 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069314

17 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Composers (like PackageFileContents in FileGatewayListen

by mark.little＠jboss.com

Just to put Tom's comments into context, remember that we inherited a lot of the core code through a partner donation. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069224#4069224 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069224

17 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Providers vs. Listeners and Configuration

by tfennelly

"bsheward" wrote : Can anyone summarize what is the difference between a provider and a listener? Am I right thinking that providers are global with the ESB, whereas listeners are "local" to a service, and tie the provider with the service? Yep, that's the basic idea. Listeners listen for messages provided by a bus. There's more on this in the configuration section of the programmers guide. "bsheward" wrote : Why would a particular configuration exist in one, but not the other? For example, In SQL, the provider seems to define the sql-message-filter, and the listener defines the number of threads. Why not the other way around? You're dead right there. Some of the listener configurations are a bit messed up. I've actually logged JIRA issues for this and I think the SQL based configs were in that. "bsheward" wrote : Finally, why are some configuration properties defined using and others are attributes of the <xxx-listener> element? For example, I define my poll-frequency-seconds in <fs-listener>, but need to define my composer-class and composer-process in a . Not sure about the poll-frequency-seconds and composer-class properties not being attributes (revert to your previous comment), but I can guess that the "composer-process" one was left as a property simply because it was considered to be a bad idea for the same reasons you outlined at the top i.e. that composition should be done based on an interface and therefore no need to define process methods. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069205#4069205 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069205

17 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Re: Composers (like PackageFileContents in FileGatewayListen

by tfennelly

This is just one of a number of issues with this listener type. We're currently debating the best approach to take on these, so stay tuned. One way or another, those composers will be changed to implement the MessageComposer interface, it's just a case of when. We're not sure of the logic as to why it wasn't done this way to start. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069199#4069199 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069199

17 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Composers (like PackageFileContents in FileGatewayListener)

by bsheward

The PackageFileContents composer in the FileGatewayListener is invoked using reflection. Is there a reason why it doesn't implement an interface, so it can be invoked as a type of Composer? Also, it seems likely that a user might want to configure a composer, for example, if I wanted to put the contents of a file into a named attachment rather than the body of the Message, I might want to configure the name of the attachment to use. The PackageFileContents is an inner class with access to the configuration of the FileGatewayListener, but external classes wouldn't have this benefit. Is there any way to support configurable composers? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069187#4069187 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069187

17 years, 5 months

1
0
0 / 0

[Design of JBoss ESB] - Providers vs. Listeners and Configuration

by bsheward

Can anyone summarize what is the difference between a provider and a listener? Am I right thinking that providers are global with the ESB, whereas listeners are "local" to a service, and tie the provider with the service? Why would a particular configuration exist in one, but not the other? For example, In SQL, the provider seems to define the sql-message-filter, and the listener defines the number of threads. Why not the other way around? Finally, why are some configuration properties defined using and others are attributes of the <xxx-listener> element? For example, I define my poll-frequency-seconds in <fs-listener>, but need to define my composer-class and composer-process in a . View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4069182#4069182 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4069182

17 years, 5 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 July 2007