Re: Exceptions in servicemix-jms with WebSphereMQ

Ah, good point. Our simplest example is now running. So let's move on to next tests. Thanx for your help. Klaus. gnodet wrote: > > You may want to try with the processorName="standard" attribute on the > JMS endpoint. The default processor uses multiplexing, which is not > available on all

[jira] Commented: (SM-536) The defaultMep is a mandatory attribute on consumer endpoints and should be checked

[ https://issues.apache.org/activemq/browse/SM-536?page=comments#action_36827 ] Guillaume Nodet commented on SM-536: Thx. Please try to ensure that the correct indentation is used (no tabs, 4 spaces) :) > The defaultMep is a mandatory attri

CIMERO plugin : Bull code donation for ServiceMix

Hi, My boss (Christophe Loridan) and me (Camilleri Jérôme) sign agreement (CCLA and CLA) and send them to Apache Fondation the last week. So now, how submit the Cimero code to the serviceMix project ? Regards. Jerome Camilleri Bull R&D

Re: Problem with current build on OS X

FWIW I just tried it and it worked fine for me. Does using the zip make any difference? (Just wondering if you're hitting tar issues with long file names or something)? On 8/23/06, ldangelo <[EMAIL PROTECTED]> wrote: Hi All, I discovered that the current build does not function properly on O

Re: Exceptions in servicemix-jms with WebSphereMQ

Guillaume, the saga continues... After changing to the standard processor WebSphere MQ works, but only for one message. Our next testcase sends a bunch of messages, but never sucessfully. So I recuded the set of messages to only two messages. But receiving the second message from NMR which shall

Re: Exceptions in servicemix-jms with WebSphereMQ

Oops, sorry. This should be fixed now. On 8/23/06, Klaus Alfert <[EMAIL PROTECTED]> wrote: Guillaume, the saga continues... After changing to the standard processor WebSphere MQ works, but only for one message. Our next testcase sends a bunch of messages, but never sucessfully. So I recuded

Re: Exceptions in servicemix-jms with WebSphereMQ

Wow, that was fast. I'll give it a try. Klaus. gnodet wrote: > > Oops, sorry. > This should be fixed now. > > On 8/23/06, Klaus Alfert <[EMAIL PROTECTED]> wrote: >> >> >> Guillaume, >> >> the saga continues... >> >> After changing to the standard processor WebSphere MQ works, but only for >> o

Re: Exceptions in servicemix-jms with WebSphereMQ

Looks good, first test results are very promising. Thanx a lot for your quick help! Klaus. gnodet wrote: > > Oops, sorry. > This should be fixed now. > > On 8/23/06, Klaus Alfert <[EMAIL PROTECTED]> wrote: >> >> >> Guillaume, >> >> the saga continues... >> >> After changing to the standard

[jira] Created: (SM-551) wsdlsoap:address generated by http component for proxied endpoint misses trailing slash

wsdlsoap:address generated by http component for proxied endpoint misses trailing slash --- Key: SM-551 URL: https://issues.apache.org/activemq/browse/SM-551 Project:

[jira] Resolved: (SM-551) wsdlsoap:address generated by http component for proxied endpoint misses trailing slash

[ https://issues.apache.org/activemq/browse/SM-551?page=all ] Guillaume Nodet resolved SM-551. Fix Version/s: 3.0-M3 Resolution: Fixed Assignee: Guillaume Nodet Author: gnodet Date: Wed Aug 23 08:00:06 2006 New Revision: 434058 URL: http

Re: Problem with current build on OS X

Zip made no difference? How can I help debug this issue? -LeoD ldangelo wrote: > > Hi All, > > I discovered that the current build does not function properly on OS X... > Below are the steps to reproduce: > > svn update > mvn -Dmaven.test.skip=true -Dprofile=step1 install > mvn -Dmaven.test