Contribution is important in the open source community, and one project that I had meant to contribute to for a while was the Apache Camel project. I remember it was last year. It was a camel-fop component.
This is an example using the file system as the transport medium with VFS transport listener and sender. This transport is currently used by lot of customers for implementing various file transfer and processing scenarios.
From March 5th 2013 Twitter are removing there current API and it will be fully replaced with the new API V1.1. This means that any application that is currently using the old API will stop working on March 5th. The main feature of the API is that requests need to be authenticated before they will work correctly.
If you're using the Camel-Mail component to handle some business logic that involves receiving email that contains attachments, then you might be interested in how these email attachments can be split into separate messages so they can be processed individually.
During my years on the Mule Community forum I’ve noticed that there are some problem areas that are more common than others. One recurring question, that I thought I should address here, is how to preserve message order in JMS.
We are making this release of Studio available to the Mule community to get valuable feedback on our latest and greatest features. This blog post contains text and video introductions to the freshly-baked features included in this release.
I found a very good review of ZeroMQ from Pieter Hintjens, a veteran in distributed software. He not only had a strength and weakness review of ZeroMQ, but he also had an interesting and critical take on a popular message queue, RabbitMQ.
One common feature I use in the Axway/Vordel API Server is a simple Get/Set: the ability to set an attribute (i.e. a variable) in a policy then to get the value of that variable. I use the "Copy/Modify Attributes" filter to do the "Set".
Ruby on Rails did a lot to bring REST to developers, but its conception leaves the REST devotee feeling a bit empty. "Where's the hypermedia?" she says. "REST isn't RPC," he may cry. In this talk, Steve will explain how to design your APIs so that they truly embrace the web and HTTP. Pros and cons are discussed.
Are you a token distributor? If you provide an API, you probably are. One thing I like about tokens is that when they are compromised, your credentials are unaffected. Unfortunately, it doesn’t work so well the other way around.
In a previous article I discovered fake images please which allowed you to put image placeholders on your webpage by using an image placeholder API. I had a number of comments about this post from other people sending links to other image placeholder APIs. Here is a list of 10 other APIs.
A really cool feature of GlassFish Metro (and maybe other webservice stacks) is the ability to change the webservice endpoint URL at runtime. Check out this example of how to do it.
At the core of many of LinkedIn's analytics applications is a real-time data pipeline built on top of Apache Kafka. This system handles over 10 billion messages writes per day for thousands of production processes.
At first it might seem baffling as to why you are unable to make a remote JMX connection to a Linux server but the resolution is really quite simple.
To understand how replication is implemented in Kafka, we need to first introduce some basic concepts. In Kafka, a message stream is defined by a topic, divided into one or more partitions. Replication happens at the partition level and each partition has one or more replicas.
A web service is proxied with Mule ESB and password protection is added to it by applying Spring Security. The code is quite straightforward. I'm going to use SoapUI to test this setup...
I've spent a good amount of time setting up message-based infrastructures, so I decided to make a tool that would allow me to set up localhost friendly, network available message queues much quicker so I could try out all the things I wanted.
The Axway Vordel API Server allows you to read in REST API parameters from an incoming request, and then use these parameters for a variety of purposes, for example to pass them into a SOAP message, or use them to call a method of a Java class via the Scripting Filter.
To use Twitter API we need to handle http requests. I’ve written several post about http request with PHP (example1, example2), but today we will use one amazing library to build clients: Guzzle. Guzzle is amazing. We can easily build a Twitter client with it.
When creating webservices a lot of people have objections against using JAXB for binding XML to objects. This may be because of performance reasons, allergy to generated code or simply a philosophical belief that you should not mix document centric services with an object oriented model.
This post is a follow on from my previous post OAuth with NancyFX and WorldDomination.Web.Authentication except this demonstrates how you can use WorldDomination.Web.Authentication with ASP.NET MVC, writing only minimal code in the process.
When I think about API Analytics, I like to think about the "Goldilocks Question". This question is "Who's been using my APIs?". One of the tests of an API Analytics solution is how easy it makes it to answer this question.
When using an external API for WebHooks or Callbacks as discussed in Chapters 3 and 5 of Getting Started with Mule Cloud Connect . . .
As I've shown it in my previous post JBoss Drools are a very useful rules engine. The only problem is that creating the rules in the Rule language might be pretty complicated for a non-technical person. That's why one can provide an easy way for creating business rules - decision tables created in a spreadsheet!
I just want to emphasize that the goal of this new camel-servletlistener component is to allow people to easily bootstrap their Camel applications in any web container, without the need to be tied to any particular 3rd party framework such as Spring.