If you look at the W3C document listing HTTP status codes, you may notice that only a small portion of all possible codes represents the happy path – i.e. 2xx codes. Most other codes are there to let client know that something went wrong with the request and the expected response cannot be returned.
Now that we have understood the basics of ActiveMQ network connector in part 1 and part 2 of this blog series, in this part 3, we will examine how ActiveMQ load balances consumers which connect to a network of brokers.
Mule Studio makes it easy for developers to build hybrid integration applications. In our latest webinar, I’ll walk you through a demo on how to build a complete integration scenario and deploy it on a local machine on-premises, as well as to CloudHub.
Make sure you didn't miss anything with this list of the Best of the Week in the Enterprise Integration Zone (Mar. 14 to Mar. 20). This week's topics include Spring Integration with Spring Boot, Java 8's Optional class, WebSockets with Spring 4, 350 API providers, and creating dynamic Mule proxies.
In this post I will show a proof-of-concept for a dynamic HTTP proxy implemented using Mule. The proxy forwards HTTP request using the context and relative path parts of the request URL to determine the server and port to which the request is to be forwarded.
The Axway API Gateway is often used as a gateway in front of APIs / Web Services. The connection to the API behind the API Gateway often is over SSL. If this connection uses a self-signed certificate (i.e. not VeriSign or another global CA), then how do you configure the trust for this connection?
I am throwing the entire kitchen sink into a small web application that I am developing as part of this post - Spring Boot, Spring Integration, RabbitMQ and finally the topic of the post, the Websocket support in Spring MVC with Spring 4.
We'd like to offer everybody in the DZone community the opportunity to be part of DZone's 2014 Continuous Delivery Research Report. By taking our survey, you will help decision-makers understand trends and preferences around deployment automation and configuration management solutions.
Previously we wrote about how to run this component in the Cloud. Now we want to provide you with not only a standalone local installation, but also a small introductory lab-based workshop to keep you busy. It is time to get hands-on with this component!
In the previous part 1 we created a network connector from broker-1 and broker-2. We were able to see how messages for queue "foo.bar" on broker-1 were forwarded queue "foo.bar" on broker-2 when there was a consumer on broker-2 for queue "foo.bar".
This post describes how to use this new Mule message class can be extended to allow for session and/or invocation scoped message properties to be set on the message before it is being sent to a Mule flow. I created this new Mule message class to unit test Mule transformers.
I’m excited to announce our early access release of Mule 3.5. We’ve done a ground-up rethink of our database and web services connectivity, resulting in new connectors which help you integrate in fewer clicks than ever that are fully integrated with DataSense.
Cisco plans to apply software-defined networking (SDN) and policy management across three major areas — the WAN, the data center, and the access network — in an ambitious plan that, in a sense, turns the entire network into one product.
A good practice in Mule ESB is to supply properties using a property file. You will end up adding passwords to the properties file. You might want to encrypt the passwords so it is not visible for every one who has access to the property file. Mulesoft described how to do this in combination with the Mule ESB.