It's interesting to see the discussions around error handling in JBoss ESB, particularly the need for better notification generation within the ActionProcessor. Effective error management is crucial for maintaining robust applications, especially in complex systems. The suggestion to attach notifications directly to messages seems like a reasonable approach, as it could streamline the process and enhance clarity for developers. For those in Germany looking to enhance their gaming experience or explore additional options, you might want to check out some bonuses available online. I recently came across a helpful resource that offers various promotions and bonuses that could be beneficial. You can find more information here: https://vegas-hero.de/bonus. It's always great to have some extra incentives while enjoying your favorite games!

[ http://jira.jboss.com/jira/browse/JBESB-193?page=comments#action_12345026 ] Tom Fennelly commented on JBESB-193: ------------------------------------ Just wanted to add another note to this issue, otherwise I'll forget. One possible workaround for people that encounter an issue with the current notification model may be (depending on the issue of course :-) ) to use one of the Message containers (e.g. Body, Attachment) to attach the notification data to the message such that it can be retrieved again from within the "getOk/ErrorNotification" methods. Example: public class MyMessageActionProcessor implements ActionProcessor { public Message process(Message message) throws ActionProcessingException { // ... Do some processing on the message... // ... encouter an error... Object specialMandatoryAttachment = message.getAttachment().get("specialMandatoryAttachment"); if(specialMandatoryAttachment == null) { // ... Exit with exception, setting an error notification to be picked up by the getErrorNotification call) ... setNotification(message, "... Special Attachment Object required by MyMessageActionProcessor not set on Message XYZ ... "); message.getFault().setCode(URI.create("fault://MyMessageActionProcessor?messageid=XYZ")); message.getFault().setReason("A44197"); throw new ActionProcessingException("Special Attachment Object required by MyMessageActionProcessor not set on Message XYZ"); } // ... Do some more processing on the message ... // ... Exit without throwing an exception (can optionally set a notification to be picked up by the getOkNotification call) ... setNotification(message, "... Message XYZ processed successfully ... "); return message; } public Serializable getOkNotification(Message message) { return getNotification(message); } public Serializable getErrorNotification(Message message) { return getNotification(message); } private void setNotification(Message message, Serializable notification) { message.getAttachment().put(NOTIFICATION_KEY, notification); } private Serializable getNotification(Message message) { return (Serializable) message.getAttachment().get(NOTIFICATION_KEY); } private static String NOTIFICATION_KEY = "PROCESSING_NOTIFICATION"; } Note that a solution like this will not work with any of the Abstract*Processor implementions that have blocked access to the Message (e.g AbstractFileAction). Also note, this is just 1 possible solution. I'm sure there are others!! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBESB-193?page=all ] Mark Little updated JBESB-193: ------------------------------ Component/s: ESB Core -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira