You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Jamie McCrindle (JIRA)" <ji...@apache.org> on 2006/10/04 15:24:09 UTC

[jira] Created: (SM-670) Including JMSFlow in default servicemix.conf

Including JMSFlow in default servicemix.conf
--------------------------------------------

                 Key: SM-670
                 URL: https://issues.apache.org/activemq/browse/SM-670
             Project: ServiceMix
          Issue Type: Improvement
          Components: servicemix-assembly
    Affects Versions: 3.0
         Environment: All
            Reporter: Jamie McCrindle


It would be useful to have JMSFlow in addition to the SedaFlow and JCAFlow servicemix flows as part of the default install (SERVICEMIX_HOME/conf/servicemix.xml). That way third party components or applications that need to use synchronous remote exchanges can work out of the box.

          <sm:jmsFlow jmsURL="tcp://localhost:61616" />


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (SM-670) Including JMSFlow in default servicemix.conf

Posted by "Jamie McCrindle (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-670?page=all ]

Jamie McCrindle updated SM-670:
-------------------------------

    Attachment: servicemix.xml.jmsflow.patch

patch for 3.0.1

> Including JMSFlow in default servicemix.conf
> --------------------------------------------
>
>                 Key: SM-670
>                 URL: https://issues.apache.org/activemq/browse/SM-670
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-assembly
>    Affects Versions: 3.0
>         Environment: All
>            Reporter: Jamie McCrindle
>         Assigned To: Guillaume Nodet
>             Fix For: 3.1
>
>         Attachments: servicemix.xml.jmsflow.patch
>
>
> It would be useful to have JMSFlow in addition to the SedaFlow and JCAFlow servicemix flows as part of the default install (SERVICEMIX_HOME/conf/servicemix.xml). That way third party components or applications that need to use synchronous remote exchanges can work out of the box.
>           <sm:jmsFlow jmsURL="tcp://localhost:61616" />

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (SM-670) Including JMSFlow in default servicemix.conf

Posted by "Jamie McCrindle (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/SM-670?page=comments#action_37157 ] 
            
Jamie McCrindle commented on SM-670:
------------------------------------

Could you add this to 3.0.1 branch?

thanks,
j.

> Including JMSFlow in default servicemix.conf
> --------------------------------------------
>
>                 Key: SM-670
>                 URL: https://issues.apache.org/activemq/browse/SM-670
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-assembly
>    Affects Versions: 3.0
>         Environment: All
>            Reporter: Jamie McCrindle
>         Assigned To: Guillaume Nodet
>             Fix For: 3.1
>
>
> It would be useful to have JMSFlow in addition to the SedaFlow and JCAFlow servicemix flows as part of the default install (SERVICEMIX_HOME/conf/servicemix.xml). That way third party components or applications that need to use synchronous remote exchanges can work out of the box.
>           <sm:jmsFlow jmsURL="tcp://localhost:61616" />

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (SM-670) Including JMSFlow in default servicemix.conf

Posted by "Guillaume Nodet (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/SM-670?page=all ]

Guillaume Nodet resolved SM-670.
--------------------------------

    Fix Version/s: 3.1
       Resolution: Fixed
         Assignee: Guillaume Nodet

Author: gnodet
Date: Wed Oct  4 06:50:36 2006
New Revision: 452889

URL: http://svn.apache.org/viewvc?view=rev&rev=452889
Log:
SM-670: including JMSFlow in default servicemix config

Modified:
   incubator/servicemix/trunk/apache-servicemix/src/main/release/conf/servicemix.xml



> Including JMSFlow in default servicemix.conf
> --------------------------------------------
>
>                 Key: SM-670
>                 URL: https://issues.apache.org/activemq/browse/SM-670
>             Project: ServiceMix
>          Issue Type: Improvement
>          Components: servicemix-assembly
>    Affects Versions: 3.0
>         Environment: All
>            Reporter: Jamie McCrindle
>         Assigned To: Guillaume Nodet
>             Fix For: 3.1
>
>
> It would be useful to have JMSFlow in addition to the SedaFlow and JCAFlow servicemix flows as part of the default install (SERVICEMIX_HOME/conf/servicemix.xml). That way third party components or applications that need to use synchronous remote exchanges can work out of the box.
>           <sm:jmsFlow jmsURL="tcp://localhost:61616" />

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira