Each element corresponds to a WSDL for which we need to generate artifacts. Check out my XML snippet below...
Guillaume Balas, our CMO, talked about API Business Models, about how to define your API business strategy based on your core business assets, and about how to enable new business models for your company by exposing and API. Here are some of the highlights of his talk...
Developers building a Service Oriented Architecture commonly run into pitfalls such as using too many web services or using the wrong ESB. These are just some of the tips from this short video.
Creating integrations is hard, but testing them is even harder. Here are the hard-won best practices that we’ve developed which you can apply to your integrations.
There are a few drawbacks with this design. If you find yourself having to add new types (via new methods) to the Abstract Factory class, you will have to add this same method to all concrete Factory classes as well.
This talk will review the state of this work and the implications for software and system engineering practice of bringing real meaning to UML.
Here is another helpful resource when using Retrofit, JSON to POJO. The library is really simple to use especially if you create your POJO class with the JSONGen.
See why you should write ugly code and how you can build your own Google TV with Raspberry Pi. Plus the new plan to curb frivolous software patent lawsuits.
Setting up load-balancing on the Vordel/Axway API Server is as simple as creating a "Remote Host" entry, then whenever you route to that host in a configuration, the load-balancing will apply.
There is an upcoming released at Red Hat of the new JBoss BPM product, something expected to hit the market later this year, but we have something kinda fun for you setup to preview some of the components to be offered.
It's been around 2 weeks now since we released WildFly 8.0.0.Alpha1 version. The download is available on the WildFly downloads page. I'm sure many of you might be wondering what WildFly is and some of you who are aware of what it is, might not be aware that there has been a release.
As a follow up to the previous Spring HATEOAS post, this post will cover how to use the @ExposesResourceFor annotation as an alternative to using the resource's Controller to obtain links.
In legacy Spring applications I have to develop new features in, I regularly stumble upon a big hindrance that slows down my integration-testing effort. This hindrance, and I’ll go as far as naming it an anti-pattern, is to put every bean in the same configuration file (either in XML or in Java).
Picture an architecture where production data gets painstakingly replicated to a very expensive secondary database, where, eventually, yesterday’s information gets analyzed. What’s the name for this “pattern”?
On the whole I'm in favor of using copyright in this way - as one who writes a lot of prose describing software development, the mechanism seems to fit well. But that fit breaks down when it comes to interfaces of software components.
I still remember the heated arguments I’d have with my high school professors about dynamic languages. What do you mean python isn’t a real language? What’s wrong with you!? Dynamic languages are the coolest thing ever!
Until recently the only way to interact with Cassandra databases from Mule was to reuse one of the existing Java clients, like Hector or Astyanax, in a component. Mule’s Cassandra DB Module now provides message processors to insert, update, query and delete data in Cassandra.
Many of today’s APIs rely on 3rd party systems, software and services, and on-premise API infrastructure that comes in various flavors. This panel discussion covers these different API infrastructure flavors, and how to choose between them.
I recently had the pleasure of reviewing Instant Apache ActiveMQ Messaging: Application Development How-To and wanted to share some thoughts. If you’re new to messaging, new to ActiveMQ, or just want a quick, no-nonsense introduction to get up and running with ActiveMQ, then you gotta check out this book.
A big difference compared with having Mule running inside the company network is the security. One of the steps to make the communication more secure is to use HTTPS instead of HTTP.
API skeptics always step up and say they are different, that they have core web products, existing business models, etc. Sure, there are differences, but Salesforce, eBay and Amazon have all managed to achieve success with continued investment in their API ecosystem.
In many cases (but not all) these quick solutions are built without regard for business logic reuse. This is not as important for one off apps but if they are part of a group of related apps this can be more of an overriding factor.
Most of the roles that we associate with software development teams are relatively well understood ... developers, testers, ScrumMasters, Product Owners, business analysts, project managers, etc. The software architecture role? Not so much.
In Part 2, we took a look at how to easily turn this into a SOAP XML service without any coding by utilizing the SOAP component for top-down web service generation and the Data Mapper for transformations.
Over the course of the past few weeks my team has been hard at work on creating a bunch of Starter Kits in response to the questions we had been getting from Windows Store developers. In particular these Kits focus on calling open web API’s for numerous services and wrap them into workable sample apps.