From servicemix-users-return-11666dustinhughes@example.org Thu Nov 01 00:19:13 2007 Return-Path: <servicemix-users-return-11666dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 39548 invoked from network); 1 Nov 2007 00:19:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Nov 2007 00:19:12 -0000 Received: (qmail 66180 invoked by uid 500); 1 Nov 2007 00:19:00 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 66162 invoked by uid 500); 1 Nov 2007 00:18:59 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 66153 invoked by uid 99); 1 Nov 2007 00:18:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2007 17:18:59 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO vhost.badgers-in-foil.co.uk) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 00:19:18 +0000 Received: from dave by vhost.badgers-in-foil.co.uk with local (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1InNlh-0000wY-Di for dustinhughes@example.org; Thu, 01 Nov 2007 00:18:42 +0000 Date: Thu, 1 Nov 2007 00:18:41 +0000 From: David Holroyd <dustinhughes@example.org> To: dustinhughes@example.org Subject: Re: Handling unreliable binding components Message-ID: <dustinhughes@example.org> Mail-Followup-To: dustinhughes@example.org References: <dustinhughes@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <dustinhughes@example.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-SA-Exim-Connect-IP: <locally generated> X-SA-Exim-Mail-From: dustinhughes@example.org X-SA-Exim-Scanned: No (on vhost.badgers-in-foil.co.uk); SAEximRunCond expanded to false X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Oct 30, 2007 at 12:32:06AM +0000, David Holroyd wrote: > I've done the above, but so far, I've not got any of the reliability I > want. Hunting around in the list archives, it looks like the way to do > this would be to have the BC rollback any current transaction on > failure, but I'm not sure how to make the JMS stuff be transacted. I see this example referenced from the servicemix-jms docs, http://svn.apache.org/viewvc/incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-jms/src/test/resources/org/apache/servicemix/jms/spring-jca.xml?revision=HEAD but this seems to be a configuration for an embedded servicemix, rather than something I can plonk into my SU xbean.xml (?) I tried a bit of cut'n'paste in the dark, but the result is no messages arriving at the Binding Component any more, and no errors logged anywhere. Is it reasonable / possible to enable transacted JCA processing in a service unit's xbean.xml, or will this only be possible by 'static configuration' (if I understand the term correctly)? ta! dave -- http://david.holroyd.me.uk/ From servicemix-users-return-11667dustinhughes@example.org Thu Nov 01 10:44:33 2007 Return-Path: <servicemix-users-return-11667dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 71764 invoked from network); 1 Nov 2007 10:44:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Nov 2007 10:44:33 -0000 Received: (qmail 17367 invoked by uid 500); 1 Nov 2007 10:44:20 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 17352 invoked by uid 500); 1 Nov 2007 10:44:19 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 17343 invoked by uid 99); 1 Nov 2007 10:44:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 03:44:19 -0700 X-ASF-Spam-Status: No, hits=4.1 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WEIRD_PORT,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dustinhughes@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 10:44:39 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1InXWr-0007Ku-17 for dustinhughes@example.org; Thu, 01 Nov 2007 03:44:01 -0700 Message-ID: <dustinhughes@example.org> Date: Thu, 1 Nov 2007 03:44:01 -0700 (PDT) From: Barath <dustinhughes@example.org> To: dustinhughes@example.org Subject: to add normalized message to MessageExchange----- MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dustinhughes@example.org X-Virus-Checked: Checked by ClamAV on apache.org Hi, i build one BC which listen to http://localhost:9090/ (using jetty server) and if any client requested, it ll send a hello world to browser. i am using servlet for this. its working fine. now i am tring to retrive a parameter from the request and normalize it and put it in message exchange and send to Myendpoint.java 's process method. but i dono how to do that. can u give any code explanation for the same.? My class structure is 1 . MyBootstrap.java -- which listen to http:\\localhost:9090\ and calls Servlet.java. 2 . Servlet.java -- doGet method calls join.java 's start method. 3 . join.java -- start method should call process method of Myendpoint.java with MessageExchange as parameter. I tried this code but dono how to initialize MessageExchangeFactory. ----------------------------8<----------------------------------- MyEndpoint endpoint= new MyEndpoint(); InOut exchange; NormalizedMessage nm; MessageExchangeFactory exchangeFactory= try { exchange = exchangeFactory.createInOutExchange(); nm = exchange.createMessage(); nm.setContent(new StringSource(inp)); exchange.setInMessage(nm); endpoint.process(exchange); } catch( Exception ex) { System.out.println(ex); ex.printStackTrace(); } ---------------------------------------8<---------------------------------------- Advanced Thanks, Barath -- View this message in context: http://www.nabble.com/to-add-normalized-message-to-MessageExchange------tf4730489s12049.html#a13526388 Sent from the ServiceMix - User mailing list dustinhughes@example.org. From servicemix-users-return-11668dustinhughes@example.org Thu Nov 01 20:53:30 2007 Return-Path: <servicemix-users-return-11668dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 72304 invoked from network); 1 Nov 2007 20:53:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Nov 2007 20:53:30 -0000 Received: (qmail 9908 invoked by uid 500); 1 Nov 2007 20:53:18 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 9584 invoked by uid 500); 1 Nov 2007 20:53:17 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 9575 invoked by uid 99); 1 Nov 2007 20:53:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 13:53:17 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dustinhughes@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 20:53:20 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1Inh2C-0001zj-Cn for dustinhughes@example.org; Thu, 01 Nov 2007 13:53:00 -0700 Message-ID: <dustinhughes@example.org> Date: Thu, 1 Nov 2007 13:53:00 -0700 (PDT) From: Learn Learn <dustinhughes@example.org> To: dustinhughes@example.org Subject: ServiceMix Bean endpoint calling other endpoints... MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dustinhughes@example.org X-Virus-Checked: Checked by ClamAV on apache.org Hi, Can a Servicemix-bean endpoint call other endpoints? I realise that if we implement the MessageExchangeListener, we wouldn't be able to do so...nothing present in the MessageExchange object to set my target Destination too..is there any other way of doing it? I need to do some routing in my Bean component (messages not XML based) based on some business logic and decide my next in chain based on what my routing logic evaluates to...similarly, if there is an exception somewhere, I need to route to a ExceptionListener that we have that massages our exception trace into a more amiable message.. Let me know if this can be done...if somebody has already done this and has a little code to share, wonderful... Thanks a lot for your help.. Victor -- View this message in context: http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537231 Sent from the ServiceMix - User mailing list dustinhughes@example.org. From servicemix-users-return-11669dustinhughes@example.org Thu Nov 01 20:57:37 2007 Return-Path: <servicemix-users-return-11669dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 73298 invoked from network); 1 Nov 2007 20:57:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Nov 2007 20:57:37 -0000 Received: (qmail 12712 invoked by uid 500); 1 Nov 2007 20:57:24 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 12690 invoked by uid 500); 1 Nov 2007 20:57:24 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 12681 invoked by uid 99); 1 Nov 2007 20:57:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 13:57:24 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO mpg-web-1.madplanet.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 20:57:42 +0000 Received: from localhost (localhost [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id EF8FC575993 for <dustinhughes@example.org>; Thu, 1 Nov 2007 13:58:37 -0700 (PDT) Received: from mpg-web-1.madplanet.com ([83.161.120.155]) by localhost (mpg-web-1.madplanet.com [83.161.120.155]) (amavisd-maia, port 10024) with ESMTP id 16707-08; Thu, 1 Nov 2007 13:58:36 -0700 (PDT) Received: from [83.161.120.155] (unknown [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id D245557598A; Thu, 1 Nov 2007 13:58:36 -0700 (PDT) Cc: Andreas Schaefer <dustinhughes@example.org> Message-Id: <dustinhughes@example.org> From: Andreas Schaefer <dustinhughes@example.org> To: dustinhughes@example.org In-Reply-To: <dustinhughes@example.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Subject: Re: ServiceMix Bean endpoint calling other endpoints... Date: Thu, 1 Nov 2007 13:57:01 -0700 References: <dustinhughes@example.org> X-Mailer: Apple Mail (2.912) X-Virus-Scanned: Maia Mailguard 1.0.2 X-Virus-Checked: Checked by ClamAV on apache.org Declare a Delivery Channel with the @Resource annotation and then use the DC to create a ME, set the data and message and then send it. Have fun Andreas Schaefer CEO of Madplanet.com Inc. dustinhughes@example.org On Nov 1, 2007, at 1:53 PM, Learn Learn wrote: > > Hi, > > Can a Servicemix-bean endpoint call other endpoints? I realise that > if we > implement the MessageExchangeListener, we wouldn't be able to do > so...nothing present in the MessageExchange object to set my target > Destination too..is there any other way of doing it? > > I need to do some routing in my Bean component (messages not XML > based) > based on some business logic and decide my next in chain based on > what my > routing logic evaluates to...similarly, if there is an exception > somewhere, > I need to route to a ExceptionListener that we have that massages our > exception trace into a more amiable message.. > > Let me know if this can be done...if somebody has already done this > and has > a little code to share, wonderful... > > Thanks a lot for your help.. > > Victor > -- > View this message in context: http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537231 > Sent from the ServiceMix - User mailing list dustinhughes@example.org. > From servicemix-users-return-11670dustinhughes@example.org Thu Nov 01 21:14:30 2007 Return-Path: <servicemix-users-return-11670dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 81602 invoked from network); 1 Nov 2007 21:14:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Nov 2007 21:14:27 -0000 Received: (qmail 29344 invoked by uid 500); 1 Nov 2007 21:14:14 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 29327 invoked by uid 500); 1 Nov 2007 21:14:14 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 29318 invoked by uid 99); 1 Nov 2007 21:14:14 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 14:14:14 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dustinhughes@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 21:14:15 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1InhMQ-0002oa-Lq for dustinhughes@example.org; Thu, 01 Nov 2007 14:13:54 -0700 Message-ID: <dustinhughes@example.org> Date: Thu, 1 Nov 2007 14:13:54 -0700 (PDT) From: Learn Learn <dustinhughes@example.org> To: dustinhughes@example.org Subject: Re: ServiceMix Bean endpoint calling other endpoints... In-Reply-To: <dustinhughes@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dustinhughes@example.org References: <dustinhughes@example.org> <dustinhughes@example.org> X-Virus-Checked: Checked by ClamAV on apache.org Well, that wont help me...that would only send back a response to my caller...what I want is to send this message across to some other endpoint (determined thru business logic and configuration) Mad Andy wrote: > > Declare a Delivery Channel with the @Resource annotation and then use > the DC to create a ME, set the data and message and then send it. > > Have fun > > Andreas Schaefer > CEO of Madplanet.com Inc. > dustinhughes@example.org > > > On Nov 1, 2007, at 1:53 PM, Learn Learn wrote: > >> >> Hi, >> >> Can a Servicemix-bean endpoint call other endpoints? I realise that >> if we >> implement the MessageExchangeListener, we wouldn't be able to do >> so...nothing present in the MessageExchange object to set my target >> Destination too..is there any other way of doing it? >> >> I need to do some routing in my Bean component (messages not XML >> based) >> based on some business logic and decide my next in chain based on >> what my >> routing logic evaluates to...similarly, if there is an exception >> somewhere, >> I need to route to a ExceptionListener that we have that massages our >> exception trace into a more amiable message.. >> >> Let me know if this can be done...if somebody has already done this >> and has >> a little code to share, wonderful... >> >> Thanks a lot for your help.. >> >> Victor >> -- >> View this message in context: >> http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537231 >> Sent from the ServiceMix - User mailing list dustinhughes@example.org. >> > > > -- View this message in context: http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537622 Sent from the ServiceMix - User mailing list dustinhughes@example.org. From servicemix-users-return-11671dustinhughes@example.org Thu Nov 01 22:15:32 2007 Return-Path: <servicemix-users-return-11671dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 6430 invoked from network); 1 Nov 2007 22:15:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Nov 2007 22:15:31 -0000 Received: (qmail 85336 invoked by uid 500); 1 Nov 2007 22:15:18 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 85318 invoked by uid 500); 1 Nov 2007 22:15:18 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 85309 invoked by uid 99); 1 Nov 2007 22:15:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 15:15:18 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO vhost.badgers-in-foil.co.uk) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 22:15:20 +0000 Received: from dave by vhost.badgers-in-foil.co.uk with local (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1IniJV-00052D-D0 for dustinhughes@example.org; Thu, 01 Nov 2007 22:14:58 +0000 Date: Thu, 1 Nov 2007 22:14:57 +0000 From: David Holroyd <dustinhughes@example.org> To: dustinhughes@example.org Subject: Re: Handling unreliable binding components Message-ID: <dustinhughes@example.org> Mail-Followup-To: dustinhughes@example.org References: <dustinhughes@example.org> <dustinhughes@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <dustinhughes@example.org> User-Agent: Mutt/1.5.13 (2006-08-11) X-SA-Exim-Connect-IP: <locally generated> X-SA-Exim-Mail-From: dustinhughes@example.org X-SA-Exim-Scanned: No (on vhost.badgers-in-foil.co.uk); SAEximRunCond expanded to false X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Nov 01, 2007 at 12:18:41AM +0000, David Holroyd wrote: > On Tue, Oct 30, 2007 at 12:32:06AM +0000, David Holroyd wrote: > > > I've done the above, but so far, I've not got any of the reliability I > > want. Hunting around in the list archives, it looks like the way to do > > this would be to have the BC rollback any current transaction on > > failure, but I'm not sure how to make the JMS stuff be transacted. > > I see this example referenced from the servicemix-jms docs, > > http://svn.apache.org/viewvc/incubator/servicemix/trunk/deployables/bindingcomponents/servicemix-jms/src/test/resources/org/apache/servicemix/jms/spring-jca.xml?revision=HEAD > > but this seems to be a configuration for an embedded servicemix, rather > than something I can plonk into my SU xbean.xml (?) > > I tried a bit of cut'n'paste in the dark, but the result is no messages > arriving at the Binding Component any more, and no errors logged > anywhere. So I enabled DEBUG loggin for "org.apache.activemq", and see, INFO - ServerSessionImpl:2 - Endpoint failed to process message. Reason: java.lang.RuntimeException: Endpoint after delivery notification failure running in the debugger, I see that the underlying cause is, java.lang.IllegalStateException: Cannot log transactions unles XAResources are named! org.apache.activemq.ra.LocalAndXATransaction@1b10e9e this happens over here, org.apache.geronimo.transaction.manager.TransactionImpl$TransactionBranch.getResourceName(TransactionImpl.java:716) org.apache.geronimo.transaction.log.HOWLLog.prepare(HOWLLog.java:254) org.apache.geronimo.transaction.manager.TransactionImpl.internalPrepare(TransactionImpl.java:443) org.apache.geronimo.transaction.manager.TransactionImpl.commit(TransactionImpl.java:315) org.apache.geronimo.transaction.manager.TransactionManagerImpl.commit(TransactionManagerImpl.java:264) org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:105) Any simple way to make it happy? Here is my xbean.xml, <beans xmlns:custsupplier="urn:cust:supplier" xmlns:jms="http://servicemix.apache.org/jms/1.0" xmlns:jencks="http://jencks.org/2.0" xmlns:amqra="http://activemq.org/ra/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <jms:endpoint service="custsupplier:jms" endpoint="endpoint" targetService="custsupplier:service" defaultMep="http://www.w3.org/2004/08/wsdl/in-only" role="consumer" destinationStyle="queue" processorName="jca" bootstrapContext="#bootstrapContext" connectionFactory="#connectionFactory" resourceAdapter="#resourceAdapter" synchronous="false"> <jms:activationSpec> <amqra:activationSpec destination="supplier/subscribe" destinationType="javax.jms.Queue" /> </jms:activationSpec> </jms:endpoint> <amqra:managedConnectionFactory id="activemqMCF" resourceAdapter="#resourceAdapter"/> <amqra:resourceAdapter id="resourceAdapter" serverUrl="tcp://83.161.120.155:61616?jms.asyncDispatch=true&amp;jms.useAsyncSend=true"/> <jencks:connectionFactory id="connectionFactory" managedConnectionFactory="#activemqMCF" connectionManager="#connectionManager" /> <!-- Transaction manager --> <jencks:transactionManager id="transactionManager"/> <!-- Work manager --> <jencks:workManager id="workManager" transactionManager="#transactionManager"/> <!-- Bootstrap context for JCA --> <jencks:bootstrapContext id="bootstrapContext" workManager="#workManager" transactionManager="#transactionManager"/> <!-- Connection manager for JCA --> <jencks:connectionTracker id="connectionTracker" geronimoTransactionManager="#transactionManager"/> <jencks:poolingSupport id="poolingSupport" allConnectionsEqual="false"/> <jencks:connectionManager id="connectionManager" containerManagedSecurity="false" transaction="xa" transactionManager="#transactionManager" poolingSupport="#poolingSupport" connectionTracker="#connectionTracker"/> </beans> ta much! dave -- http://david.holroyd.me.uk/ From servicemix-users-return-11672dustinhughes@example.org Thu Nov 01 23:22:12 2007 Return-Path: <servicemix-users-return-11672dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 21249 invoked from network); 1 Nov 2007 23:22:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Nov 2007 23:22:12 -0000 Received: (qmail 44664 invoked by uid 500); 1 Nov 2007 23:21:59 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 44641 invoked by uid 500); 1 Nov 2007 23:21:59 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 44632 invoked by uid 99); 1 Nov 2007 23:21:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 16:21:59 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO mpg-web-1.madplanet.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 23:22:17 +0000 Received: from localhost (localhost [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id 98ACE575993 for <dustinhughes@example.org>; Thu, 1 Nov 2007 16:23:12 -0700 (PDT) Received: from mpg-web-1.madplanet.com ([83.161.120.155]) by localhost (mpg-web-1.madplanet.com [83.161.120.155]) (amavisd-maia, port 10024) with ESMTP id 18641-09; Thu, 1 Nov 2007 16:23:10 -0700 (PDT) Received: from [83.161.120.155] (unknown [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id F142957598A; Thu, 1 Nov 2007 16:23:09 -0700 (PDT) Cc: Andreas Schaefer <dustinhughes@example.org> Message-Id: <dustinhughes@example.org> From: Andreas Schaefer <dustinhughes@example.org> To: dustinhughes@example.org In-Reply-To: <dustinhughes@example.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Subject: Re: ServiceMix Bean endpoint calling other endpoints... Date: Thu, 1 Nov 2007 16:21:34 -0700 References: <dustinhughes@example.org> <dustinhughes@example.org> <dustinhughes@example.org> X-Mailer: Apple Mail (2.912) X-Virus-Scanned: Maia Mailguard 1.0.2 X-Virus-Checked: Checked by ClamAV on apache.org Well, I am not here to give you free code or do your homework. The DC is enough to create a new ME through an exchange factory and then you can set the service name, endpoint or interface and its operation etc. Have a look at the JavaDoc and if everything else fails then you should try out something. The only thing I will say is that we use it this way ! Have fun Andreas Schaefer CEO of Madplanet.com Inc. dustinhughes@example.org On Nov 1, 2007, at 2:13 PM, Learn Learn wrote: > > Well, that wont help me...that would only send back a response to my > caller...what I want is to send this message across to some other > endpoint > (determined thru business logic and configuration) > > > Mad Andy wrote: >> >> Declare a Delivery Channel with the @Resource annotation and then use >> the DC to create a ME, set the data and message and then send it. >> >> Have fun >> >> Andreas Schaefer >> CEO of Madplanet.com Inc. >> dustinhughes@example.org >> >> >> On Nov 1, 2007, at 1:53 PM, Learn Learn wrote: >> >>> >>> Hi, >>> >>> Can a Servicemix-bean endpoint call other endpoints? I realise that >>> if we >>> implement the MessageExchangeListener, we wouldn't be able to do >>> so...nothing present in the MessageExchange object to set my target >>> Destination too..is there any other way of doing it? >>> >>> I need to do some routing in my Bean component (messages not XML >>> based) >>> based on some business logic and decide my next in chain based on >>> what my >>> routing logic evaluates to...similarly, if there is an exception >>> somewhere, >>> I need to route to a ExceptionListener that we have that massages >>> our >>> exception trace into a more amiable message.. >>> >>> Let me know if this can be done...if somebody has already done this >>> and has >>> a little code to share, wonderful... >>> >>> Thanks a lot for your help.. >>> >>> Victor >>> -- >>> View this message in context: >>> http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537231 >>> Sent from the ServiceMix - User mailing list dustinhughes@example.org. >>> >> >> >> > > -- > View this message in context: http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537622 > Sent from the ServiceMix - User mailing list dustinhughes@example.org. > From servicemix-users-return-11673dustinhughes@example.org Fri Nov 02 01:02:15 2007 Return-Path: <servicemix-users-return-11673dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 53205 invoked from network); 2 Nov 2007 01:02:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Nov 2007 01:02:15 -0000 Received: (qmail 15982 invoked by uid 500); 2 Nov 2007 01:02:02 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 15961 invoked by uid 500); 2 Nov 2007 01:02:02 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 15952 invoked by uid 99); 2 Nov 2007 01:02:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 18:02:02 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dustinhughes@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 01:02:19 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1Inkuq-0000GF-Ap for dustinhughes@example.org; Thu, 01 Nov 2007 18:01:40 -0700 Message-ID: <dustinhughes@example.org> Date: Thu, 1 Nov 2007 18:01:40 -0700 (PDT) From: Learn Learn <dustinhughes@example.org> To: dustinhughes@example.org Subject: Re: ServiceMix Bean endpoint calling other endpoints... In-Reply-To: <dustinhughes@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dustinhughes@example.org References: <dustinhughes@example.org> <dustinhughes@example.org> <dustinhughes@example.org> <dustinhughes@example.org> X-Virus-Checked: Checked by ClamAV on apache.org That's an interesting way of doing it. How do you tie back your responses from the Exchanges? Do you use some kind of an interim store? Or do your clients get two responses and consider the first one to be an acknowledgement? Basically, if I get in a sync/async request thru a Binding Component into the bus and I forward it to the bean component thru the NMR and later on create a new Exchange from the Bean Component...doesn't my client get two responses..first response after the bean endpoint creates and puts a new MessageExchange on the DC.. (since the first MessageExchange life is over and a blank response is sent back)..and the second response is the final response (the real one) through the new MessageExchange that should go back to the client ... hope that this is not a dumb question...Thanks for taking the time to answer this. Mad Andy wrote: > > Well, I am not here to give you free code or do your homework. The DC > is enough to create a new ME through an exchange factory and then you > can set the service name, endpoint or interface and its operation etc. > Have a look at the JavaDoc and if everything else fails then you > should try out something. The only thing I will say is that we use it > this way ! > > Have fun > > Andreas Schaefer > CEO of Madplanet.com Inc. > dustinhughes@example.org > > > On Nov 1, 2007, at 2:13 PM, Learn Learn wrote: > >> >> Well, that wont help me...that would only send back a response to my >> caller...what I want is to send this message across to some other >> endpoint >> (determined thru business logic and configuration) >> >> >> Mad Andy wrote: >>> >>> Declare a Delivery Channel with the @Resource annotation and then use >>> the DC to create a ME, set the data and message and then send it. >>> >>> Have fun >>> >>> Andreas Schaefer >>> CEO of Madplanet.com Inc. >>> dustinhughes@example.org >>> >>> >>> On Nov 1, 2007, at 1:53 PM, Learn Learn wrote: >>> >>>> >>>> Hi, >>>> >>>> Can a Servicemix-bean endpoint call other endpoints? I realise that >>>> if we >>>> implement the MessageExchangeListener, we wouldn't be able to do >>>> so...nothing present in the MessageExchange object to set my target >>>> Destination too..is there any other way of doing it? >>>> >>>> I need to do some routing in my Bean component (messages not XML >>>> based) >>>> based on some business logic and decide my next in chain based on >>>> what my >>>> routing logic evaluates to...similarly, if there is an exception >>>> somewhere, >>>> I need to route to a ExceptionListener that we have that massages >>>> our >>>> exception trace into a more amiable message.. >>>> >>>> Let me know if this can be done...if somebody has already done this >>>> and has >>>> a little code to share, wonderful... >>>> >>>> Thanks a lot for your help.. >>>> >>>> Victor >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537231 >>>> Sent from the ServiceMix - User mailing list dustinhughes@example.org. >>>> >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537622 >> Sent from the ServiceMix - User mailing list dustinhughes@example.org. >> > > > -- View this message in context: http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13540522 Sent from the ServiceMix - User mailing list dustinhughes@example.org. From servicemix-users-return-11674dustinhughes@example.org Fri Nov 02 02:14:06 2007 Return-Path: <servicemix-users-return-11674dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 5115 invoked from network); 2 Nov 2007 02:14:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Nov 2007 02:14:06 -0000 Received: (qmail 83502 invoked by uid 500); 2 Nov 2007 02:13:53 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 83482 invoked by uid 500); 2 Nov 2007 02:13:53 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 83473 invoked by uid 99); 2 Nov 2007 02:13:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 19:13:53 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of dustinhughes@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 02:14:11 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1Inm2N-00026S-Id for dustinhughes@example.org; Thu, 01 Nov 2007 19:13:31 -0700 Message-ID: <dustinhughes@example.org> Date: Thu, 1 Nov 2007 19:13:31 -0700 (PDT) From: MrRothstein <dustinhughes@example.org> To: dustinhughes@example.org Subject: Re: ServiceMix Bean endpoint calling other endpoints... In-Reply-To: <dustinhughes@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dustinhughes@example.org References: <dustinhughes@example.org> <dustinhughes@example.org> <dustinhughes@example.org> <dustinhughes@example.org> <dustinhughes@example.org> X-Virus-Checked: Checked by ClamAV on apache.org Take a look at the source code for some of the eip modules. Also, look at the ExchangeTarget class and how it's used. What Andy is suggesting is that you do "manually" what the ExchangeTarget would do for you. You end up with two message exchanges. One where you are the provider, the other where you are the consumer. For the exchange where you are the provider (assuming in-out), the bean has to set the out message on the original, client sent, exchange. The client will get that exchange back. For the exchange you create, you are the consumer (again assuming in-out), the response will be in the form of an out (or fault) message in the message exchange you create. Learn Learn wrote: > > That's an interesting way of doing it. How do you tie back your responses > from the Exchanges? Do you use some kind of an interim store? Or do your > clients get two responses and consider the first one to be an > acknowledgement? > > Basically, if I get in a sync/async request thru a Binding Component into > the bus and I forward it to the bean component thru the NMR and later on > create a new Exchange from the Bean Component...doesn't my client get two > responses..first response after the bean endpoint creates and puts a new > MessageExchange on the DC.. (since the first MessageExchange life is over > and a blank response is sent back)..and the second response is the final > response (the real one) through the new MessageExchange that should go > back to the client ... hope that this is not a dumb question...Thanks for > taking the time to answer this. > > > > Mad Andy wrote: >> >> Well, I am not here to give you free code or do your homework. The DC >> is enough to create a new ME through an exchange factory and then you >> can set the service name, endpoint or interface and its operation etc. >> Have a look at the JavaDoc and if everything else fails then you >> should try out something. The only thing I will say is that we use it >> this way ! >> >> Have fun >> >> Andreas Schaefer >> CEO of Madplanet.com Inc. >> dustinhughes@example.org >> >> >> On Nov 1, 2007, at 2:13 PM, Learn Learn wrote: >> >>> >>> Well, that wont help me...that would only send back a response to my >>> caller...what I want is to send this message across to some other >>> endpoint >>> (determined thru business logic and configuration) >>> >>> >>> Mad Andy wrote: >>>> >>>> Declare a Delivery Channel with the @Resource annotation and then use >>>> the DC to create a ME, set the data and message and then send it. >>>> >>>> Have fun >>>> >>>> Andreas Schaefer >>>> CEO of Madplanet.com Inc. >>>> dustinhughes@example.org >>>> >>>> >>>> On Nov 1, 2007, at 1:53 PM, Learn Learn wrote: >>>> >>>>> >>>>> Hi, >>>>> >>>>> Can a Servicemix-bean endpoint call other endpoints? I realise that >>>>> if we >>>>> implement the MessageExchangeListener, we wouldn't be able to do >>>>> so...nothing present in the MessageExchange object to set my target >>>>> Destination too..is there any other way of doing it? >>>>> >>>>> I need to do some routing in my Bean component (messages not XML >>>>> based) >>>>> based on some business logic and decide my next in chain based on >>>>> what my >>>>> routing logic evaluates to...similarly, if there is an exception >>>>> somewhere, >>>>> I need to route to a ExceptionListener that we have that massages >>>>> our >>>>> exception trace into a more amiable message.. >>>>> >>>>> Let me know if this can be done...if somebody has already done this >>>>> and has >>>>> a little code to share, wonderful... >>>>> >>>>> Thanks a lot for your help.. >>>>> >>>>> Victor >>>>> -- >>>>> View this message in context: >>>>> http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537231 >>>>> Sent from the ServiceMix - User mailing list dustinhughes@example.org. >>>>> >>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537622 >>> Sent from the ServiceMix - User mailing list dustinhughes@example.org. >>> >> >> >> > > -- View this message in context: http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13541160 Sent from the ServiceMix - User mailing list dustinhughes@example.org. From servicemix-users-return-11675dustinhughes@example.org Fri Nov 02 02:24:49 2007 Return-Path: <servicemix-users-return-11675dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 8357 invoked from network); 2 Nov 2007 02:24:49 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Nov 2007 02:24:49 -0000 Received: (qmail 95749 invoked by uid 500); 2 Nov 2007 02:24:37 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 95424 invoked by uid 500); 2 Nov 2007 02:24:36 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 95415 invoked by uid 99); 2 Nov 2007 02:24:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 19:24:36 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO mpg-web-1.madplanet.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 02:24:37 +0000 Received: from localhost (localhost [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id 23AE5575993 for <dustinhughes@example.org>; Thu, 1 Nov 2007 19:25:52 -0700 (PDT) Received: from mpg-web-1.madplanet.com ([83.161.120.155]) by localhost (mpg-web-1.madplanet.com [83.161.120.155]) (amavisd-maia, port 10024) with ESMTP id 20816-05; Thu, 1 Nov 2007 19:25:50 -0700 (PDT) Received: from [83.161.120.155] (unknown [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id 0576457598A; Thu, 1 Nov 2007 19:25:50 -0700 (PDT) Cc: Andreas Schaefer <dustinhughes@example.org> Message-Id: <dustinhughes@example.org> From: Andreas Schaefer <dustinhughes@example.org> To: dustinhughes@example.org In-Reply-To: <dustinhughes@example.org> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Subject: Re: ServiceMix Bean endpoint calling other endpoints... Date: Thu, 1 Nov 2007 19:24:14 -0700 References: <dustinhughes@example.org> X-Mailer: Apple Mail (2.912) X-Virus-Scanned: Maia Mailguard 1.0.2 X-Virus-Checked: Checked by ClamAV on apache.org It is fairly easy. In the synchronous case meaning if you send with DC.sendSync() the thread waits until the response comes back and the ME will contain the response. In case of the asynchronous case with DC.send() your thread will go on and you onMessageExchange() will end. When the response comes back your Bean is invoked again with the response on onMessageExchange() and you will have to deal how to return the response to your caller. Have fun Andreas Schaefer CEO of Madplanet.com Inc. dustinhughes@example.org On Nov 1, 2007, at 1:53 PM, Learn Learn wrote: > > Hi, > > Can a Servicemix-bean endpoint call other endpoints? I realise that > if we > implement the MessageExchangeListener, we wouldn't be able to do > so...nothing present in the MessageExchange object to set my target > Destination too..is there any other way of doing it? > > I need to do some routing in my Bean component (messages not XML > based) > based on some business logic and decide my next in chain based on > what my > routing logic evaluates to...similarly, if there is an exception > somewhere, > I need to route to a ExceptionListener that we have that massages our > exception trace into a more amiable message.. > > Let me know if this can be done...if somebody has already done this > and has > a little code to share, wonderful... > > Thanks a lot for your help.. > > Victor > -- > View this message in context: http://www.nabble.com/ServiceMix-Bean-endpoint-calling-other-endpoints...-tf4733999s12049.html#a13537231 > Sent from the ServiceMix - User mailing list dustinhughes@example.org. > From servicemix-users-return-11676dustinhughes@example.org Fri Nov 02 04:02:53 2007 Return-Path: <servicemix-users-return-11676dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 28016 invoked from network); 2 Nov 2007 04:02:53 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Nov 2007 04:02:53 -0000 Received: (qmail 43585 invoked by uid 500); 2 Nov 2007 04:02:40 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 43567 invoked by uid 500); 2 Nov 2007 04:02:40 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 43558 invoked by uid 99); 2 Nov 2007 04:02:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 21:02:40 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO mpg-web-1.madplanet.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 04:02:58 +0000 Received: from localhost (localhost [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id E70DD575993 for <dustinhughes@example.org>; Thu, 1 Nov 2007 21:03:53 -0700 (PDT) Received: from mpg-web-1.madplanet.com ([83.161.120.155]) by localhost (mpg-web-1.madplanet.com [83.161.120.155]) (amavisd-maia, port 10024) with ESMTP id 22118-04 for <dustinhughes@example.org>; Thu, 1 Nov 2007 21:03:41 -0700 (PDT) Received: from [83.161.120.155] (unknown [83.161.120.155]) by mpg-web-1.madplanet.com (Postfix) with ESMTP id 9247457598A for <dustinhughes@example.org>; Thu, 1 Nov 2007 21:03:41 -0700 (PDT) Message-Id: <dustinhughes@example.org> From: Andreas Schaefer <dustinhughes@example.org> To: dustinhughes@example.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v912) Subject: JBI Message Exchange Pattern Redux Date: Thu, 1 Nov 2007 21:02:05 -0700 X-Mailer: Apple Mail (2.912) X-Virus-Scanned: Maia Mailguard 1.0.2 X-Virus-Checked: Checked by ClamAV on apache.org Hi I want to try to come up with a short docu about the JBI Message Exchange Patterns. Please check it out and let me know what you think: Preamble: Any active (if status is not in DONE or ERROR) Message Exchanges (ME) can be set to status ERROR and returned to the other party (send()). Any received inactive ME cannot be sent again meaning that the exchange ends there. Consumer is the party that sends the ME for the first time meaning it is the party from where the ME originates. Provider is the other party in the ME. Possible Exchanges: 1) Consumer sends an IN message to the Provider Applicable: ALL 2) Provider sends DONE ME back to the consumer Applicable: ALL except IN-OUT 3) Provider sends FAULT ME back to the consumer which HAS to sent back the ME with status DONE (or ERROR for that matter) Applicable: ALL except IN-ONLY 4) Provider sends OUT message back to the consumer which HAS to sent back the ME with status DONE Applicable: IN-OUT 5) Provider sends OUT message back to the consumer which either can: a) Consumer sends back a ME with status DONE or b) Consumer sends back a FAULT to the Provider which has to sent back the ME with status DONE A summary of the usages of the MEPs: IN-ONLY: The Consumer wants to send the ME but is not interested in any type of response except the acknowledgement of that it is done. ROBUST-IN-ONLY: The Consumer wants to send the ME but is interested to hear from the Provider in case of a FAULT (for example request not understood). This gives the Consumer a chance to react to such a fault and try alternatives. IN-OUT: The Consumer wants to send the ME and is interested to receive a response from the Provider which can be an OUT message or a FAULT. In case of a FAULT the Consumer can try alternatives. Note: This MEP looks like the ROBUST-IN-ONLY except that the DONE message from the Provider is replaced by the OUT message. IN-OPTIONAL-OUT: The Consumer wants to send the ME but let the Provider decide if there is a response (OUT or FAULT) or not (DONE). In case of an OUT message the Consumer can send a FAULT back to the Provider to tell him about problems with his response (like Response not understood). Note: This is the only MEP that allows the Consumer to respond to the response of a Provider even though I am not quite sure what it is good for because the Provider cannot react and send back a different response. It is still up to the Consumer to look for alternatives. Thank you Andreas Schaefer CEO of Madplanet.com Inc. dustinhughes@example.org From servicemix-users-return-11677dustinhughes@example.org Fri Nov 02 05:32:45 2007 Return-Path: <servicemix-users-return-11677dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 40022 invoked from network); 2 Nov 2007 05:32:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Nov 2007 05:32:45 -0000 Received: (qmail 78370 invoked by uid 500); 2 Nov 2007 05:32:32 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 78349 invoked by uid 500); 2 Nov 2007 05:32:32 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 78340 invoked by uid 99); 2 Nov 2007 05:32:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2007 22:32:32 -0700 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dustinhughes@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO kuber.nabble.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 05:32:34 +0000 Received: from isper.nabble.com ([83.161.120.155]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from <dustinhughes@example.org>) id 1Inp8g-0006Dq-5q for dustinhughes@example.org; Thu, 01 Nov 2007 22:32:14 -0700 Message-ID: <dustinhughes@example.org> Date: Thu, 1 Nov 2007 22:32:14 -0700 (PDT) From: tpounds <dustinhughes@example.org> To: dustinhughes@example.org Subject: Re: Synchronization between two clustered SM instances In-Reply-To: <dustinhughes@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: dustinhughes@example.org References: <dustinhughes@example.org> X-Virus-Checked: Checked by ClamAV on apache.org You could try to use JMS topics to send the message to all interested parties. The basic setup being each servicemix in the cluster has a special JMS bc that listens on a named topic and passes those messages to other service units inside your assembly. I hope this helps :) -Trevor prossma wrote: > > Hi, > > In a project, we're extending the SecuredBroker's authorization > mechanism by including XACML functionality. We're operating on SM 3.1.1. > > Basically, this is rather straightforward to implement. The broker > maintains all XACML policies (in memory). Whenever a MessageExchange > passes along, we extract certain attributes and run authorization on it. > > However, there'll be a (JSR181) service who allows changing the set of > available policies. Now we'd need a mechanism that informs the broker > that a change has occurred, such that it updates its policies. > > When we only have a single instance of the SM container running, from > the service, we can get access to the container via the component > context, obtain its broker, and give it an update (see JIRA issue > SM-858). > > However, our project will deploy SM in a clustered environment - and the > outlined approach will only allow us to update the broker of the > container in one of the clustered instances. > > I understand that sending an "update" message won't work, as it will be > consumed by the "fastest" container and won't reach all clustered > brokers. > > Now my question is: > What would be the best way to achieve synchronization between the > brokers of different clustered containers? > E.g., is there a way to make sure that a message is being sent to all > clustered containers? > > We'd like to avoid mechanisms based on writing information to permanent > memory, as this would seriously affect performance. We were thinking > about something related to stateful session beans (we're deploying into > JBoss), but then our solution would be bound to the availability of an > EJB container. > > Any ideas? > > Thanks in advance, > Ciao, > Philipp > > This e-mail and any attachments may contain confidential or > privileged information. Any unauthorised copying, use or distribution of > this information is strictly prohibited. > > -- View this message in context: http://www.nabble.com/Synchronization-between-two-clustered-SM-instances-tf4727151s12049.html#a13542562 Sent from the ServiceMix - User mailing list dustinhughes@example.org. From servicemix-users-return-11678dustinhughes@example.org Fri Nov 02 11:44:27 2007 Return-Path: <servicemix-users-return-11678dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 44121 invoked from network); 2 Nov 2007 11:44:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Nov 2007 11:44:27 -0000 Received: (qmail 92662 invoked by uid 500); 2 Nov 2007 11:44:14 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 92639 invoked by uid 500); 2 Nov 2007 11:44:14 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 92630 invoked by uid 99); 2 Nov 2007 11:44:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 04:44:14 -0700 X-ASF-Spam-Status: No, hits=1.7 required=10.0 tests=SPF_PASS,WEIRD_PORT,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO alnrmhc11.comcast.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 11:44:35 +0000 Received: from [83.161.120.155] (213.sub-70-208-101.myvzw.com[83.161.120.155]) by comcast.net (alnrmhc11) with SMTP id <20071102114348b1100255ise>; Fri, 2 Nov 2007 11:43:51 +0000 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <dustinhughes@example.org> References: <dustinhughes@example.org> Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes; format=flowed Message-Id: <dustinhughes@example.org> Content-Transfer-Encoding: quoted-printable From: Daryl Richter <dustinhughes@example.org> Subject: Re: to add normalized message to MessageExchange----- Date: Fri, 2 Nov 2007 07:43:36 -0400 To: dustinhughes@example.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org On Nov 1, 2007, at 6:44 AM, Barath wrote: > > Hi, > > i build one BC which listen to http://localhost:9090/ (using jetty =20 > server) > and if any client requested, it ll send a hello world to browser. i =20= > am using > servlet for this. its working fine. > > now i am tring to retrive a parameter from the request and =20 > normalize it and > put it in message exchange and send to Myendpoint.java 's process =20 > method. > > but i dono how to do that. > can u give any code explanation for the same.? > > My class structure is > > 1 . MyBootstrap.java -- which listen to http:\\localhost:9090\ and =20= > calls > Servlet.java. > 2 . Servlet.java -- doGet method calls join.java 's start method. > 3 . join.java -- start method should call process method of =20 > Myendpoint.java > with MessageExchange as parameter. > > I tried this code but dono how to initialize MessageExchangeFactory. > > ----------------------------8<----------------------------------- > MyEndpoint endpoint=3D new MyEndpoint(); > InOut exchange; > NormalizedMessage nm; > MessageExchangeFactory exchangeFactory=3D > =09 > try > { > exchange =3D exchangeFactory.createInOutExchange(); > nm =3D exchange.createMessage(); Here you also need to tell it where to go via exchange.setService() =20 and, optionally, .setEndpoint(). > nm.setContent(new StringSource(inp)); > exchange.setInMessage(nm); > endpoint.process(exchange); Don't call endpoint.process. You want to do this following instead: channel.send( exchange ) or channel.sendSync( exchange ) That will get the message to your endpoint. Make sure you have declared: @Resource private DeliveryChannel channel; In your bean class to have access to the channel. HTH. > } =09 > catch( Exception ex) > { > System.out.println(ex); > ex.printStackTrace(); > } > ---------------------------------------8<-----------------------------=20= > ----------- > Advanced Thanks, > Barath > --=20 > View this message in context: http://www.nabble.com/to-add-=20 > normalized-message-to-MessageExchange------=20 > tf4730489s12049.html#a13526388 > Sent from the ServiceMix - User mailing list dustinhughes@example.org. > -- Daryl Email *my =3D [ daryl at: @"eddl" dot: @"us" ]; Weblog *blog =3D @=94http://itsallsemantics.com=94; From servicemix-users-return-11679dustinhughes@example.org Fri Nov 02 11:46:33 2007 Return-Path: <servicemix-users-return-11679dustinhughes@example.org> Delivered-To: dustinhughes@example.org Received: (qmail 45285 invoked from network); 2 Nov 2007 11:46:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Nov 2007 11:46:33 -0000 Received: (qmail 93539 invoked by uid 500); 2 Nov 2007 11:46:21 -0000 Delivered-To: dustinhughes@example.org Received: (qmail 93517 invoked by uid 500); 2 Nov 2007 11:46:20 -0000 Mailing-List: contact dustinhughes@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:dustinhughes@example.org> List-Unsubscribe: <mailto:dustinhughes@example.org> List-Post: <mailto:dustinhughes@example.org> List-Id: <servicemix-users.geronimo.apache.org> Reply-To: dustinhughes@example.org Delivered-To: mailing list dustinhughes@example.org Received: (qmail 93508 invoked by uid 99); 2 Nov 2007 11:46:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 04:46:20 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO QMTA02.westchester.pa.mail.comcast.net) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Nov 2007 11:46:40 +0000 Received: from OMTA08.westchester.pa.mail.comcast.net ([83.161.120.155]) by QMTA02.westchester.pa.mail.comcast.net with smtp id 7nfT1Y0010Fqzac0000R00; Fri, 02 Nov 2007 11:45:59 +0000 Received: from [83.161.120.155] ([83.161.120.155]) by OMTA08.westchester.pa.mail.comcast.net with comcast id 7nlo1Y0014cF5QN0000000; Fri, 02 Nov 2007 11:46:00 +0000 X-Authority-Analysis: v=1.0 c=1 a=UILgdPHdAAAA:8 a=qQiUt6xVuIn7aXAD5XEA:9 a=l8gZg4_cXp9MnCQfFB8A:7 a=E77DYkcAZbP3Oh7lG2lJomc2h4cA:4 a=AxOnZC-zs-EA:10 a=IjgBF4XsRXUA:10 a=kJVaTwQnZmMA:10 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <dustinhughes@example.org> References: <dustinhughes@example.org> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <dustinhughes@example.org> Content-Transfer-Encoding: 7bit From: Daryl Richter <dustinhughes@example.org> Subject: Re: JBI Message Exchange Pattern Redux Date: Fri, 2 Nov 2007 07:45:44 -0400 To: dustinhughes@example.org X-Mailer: Apple Mail (2.752.3) X-Virus-Checked: Checked by ClamAV on apache.org Andreas- Nice writeup. Thanks. I have found that really understanding MEs is a major key to being able to understand how ServiceMix works. Hopefully this will help many people. On Nov 2, 2007, at 12:02 AM, Andreas Schaefer wrote: > Hi > > I want to try to come up with a short docu about the JBI Message > Exchange Patterns. Please check it out and let me know what you think: > > Preamble: > > Any active (if status is not in DONE or ERROR) Message Exchanges > (ME) can be set to status ERROR and returned to the other party > (send()). Any received inactive ME cannot be sent again meaning > that the exchange ends there. > > Consumer is the party that sends the ME for the first time meaning > it is the party from where the ME originates. Provider is the other > party in the ME. > > Possible Exchanges: > > 1) Consumer sends an IN message to the Provider > > Applicable: ALL > > 2) Provider sends DONE ME back to the consumer > > Applicable: ALL except IN-OUT > > 3) Provider sends FAULT ME back to the consumer which HAS to sent > back the ME with status DONE (or ERROR for that matter) > > Applicable: ALL except IN-ONLY > > 4) Provider sends OUT message back to the consumer which HAS to > sent back the ME with status DONE > > Applicable: IN-OUT > > 5) Provider sends OUT message back to the consumer which either can: > a) Consumer sends back a ME with status DONE > or > b) Consumer sends back a FAULT to the Provider which has to sent > back the ME with status DONE > > A summary of the usages of the MEPs: > > IN-ONLY: > The Consumer wants to send the ME but is not interested in any type > of response except the acknowledgement of that it is done. > > ROBUST-IN-ONLY: > The Consumer wants to send the ME but is interested to hear from > the Provider in case of a FAULT (for example request not > understood). This gives the Consumer a chance to react to such a > fault and try alternatives. > > IN-OUT: > The Consumer wants to send the ME and is interested to receive a > response from the Provider which can be an OUT message or a FAULT. > In case of a FAULT the Consumer can try alternatives. > > Note: This MEP looks like the ROBUST-IN-ONLY except that the DONE > message from the Provider is replaced by the OUT message. > > > IN-OPTIONAL-OUT: > The Consumer wants to send the ME but let the Provider decide if > there is a response (OUT or FAULT) or not (DONE). In case
{'source': 'Apache Software Foundation Public Mail Archives'}