There is a .NET implementation of Spring but not sure if that would help
you in your situation.
On Wed, Dec 14, 2011 at 12:27 PM, JRR wrote:
> Hello Martin,
>
> Thank you for the suggestion to use Spring, but we're a C++ based client,
> not Java. Hence usage of a Spring client isn't available to
We have to run some .NET code on CentOS. We use mono but I'm not sure why
you would choose that route unless you have some functional code that you
don't want to port.
On Thu, Sep 29, 2011 at 4:09 PM, Timothy Bish wrote:
> On Thu, 2011-09-29 at 13:02 -0700, newbieSCS wrote:
> > >From what I've
When I processing a message something might fail that I want it to try again
and after it tries a specified number times, I want to push that message to
another queue for alternate processing. I have looked at JMS retries but
doesn't seem like the way I want to go.
With a valid Message, what is t
I actually don't have a good answer for your question but I thought I would
add something based on my recent experience...
activemq-all seems to already have an slf4j (5.x) contained as a dependency.
This caused me issues because I was trying to use SLF4j 6.x. I switched to
activemq-core and all
runtime
"org.springframework.integration:spring-integration-jms:$springIntegrationVersion"
// this one surely
runtime 'org.apache.activemq:activemq-all:5.x.0'
On Wed, Aug 17, 2011 at 11:12 AM, Todd Crone wrote:
> I would avoid the Grails plugin. It openly admits to not be
I would avoid the Grails plugin. It openly admits to not be good for
production usage and I have seen these types plugins in Grails that give you
nothing but heartache. In my Grails app, I simply configured activemq in
resources.groovy.
Sample config in resources.groovy:
jmsFactory(org.
For #3, I'm using a Spring JmsTemplate:
This is Groovy sample code for a selector...
String documentIdFieldName = DocumentConversionMessage.DOCUMENT_ID
String selector = "$documentIdFieldName='$documentId'"
Message jmsMessage = jmsTemplate.receiveSelected(destination,
selec
I'm an ActiveMQ newbie but I've been readying ActiveMQ in Action and I've so
far seen two ways to potentially address #1.
If the message is temporary, set the JMSExpiration header for the message.
For a temporary queue (typically for request/response) pg. 162
public void start() throws JMSExcept
