|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 7
Messages: 7
Messages: 7
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Mule IDE 2.0 Released
MuleSoft announces that Mule IDE 2.0 for Mule ESB has been released.
Mule IDE 2.0 is a development and testing environment based on Eclipse. It supports the following features:
* Creating a new Mule project in Eclipse
* Creating a working Mule project in Eclipse based on Mule examples
* Creating a new Mule configuration file with selected namespace declarations
* Editing Mule configuration files
* Integrated Mule schema auto-complete and documentation (using Eclipse-compatible XML editor with context-sensitive content assistant)
* Switching between Mule distributions in a project
* Running the Mule Server in Eclipse to test your Mule project
* Debugging your Mule project in Eclipse
Mule IDE 2.0 is compatible with any Mule 2.1 or later community or enterprise Mule distribution.
To try it out, go to the Mule IDE installation guide for instructions on installing it.
For the future of Mule IDE, we would like to get more feedback from the community. What works for you? What doesn’t? Your comments will help us make the Mule IDE a better tool for you.
|
|
|
Message #328575
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
does anyone care anymore?
Guys, honestly this is sad. Everything you do is a mirror clone of what SpringSource did. Are you capable of anything creative anymore?
The ESB space is now a commodity like app. servers. You had a great innovative product at one time, and Ross was doing amazing things early on. Now? It's all just a clone of what others are doing, and even those are way behind others in the same space.
Can you try and come up with something, anything new and innovative, and not be pimped by your marketing and sales staff?
|
|
|
Message #328579
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: does anyone care anymore?
Guys, honestly this is sad. Everything you do is a mirror clone of what SpringSource did. Are you capable of anything creative anymore?
The ESB space is now a commodity like app. servers. You had a great innovative product at one time, and Ross was doing amazing things early on. Now? It's all just a clone of what others are doing, and even those are way behind others in the same space.
Can you try and come up with something, anything new and innovative, and not be pimped by your marketing and sales staff?
I am not affiliated with Mule, but what is your problem? They have business proposal, if you like it, buy it, if you don't, then do not purchase. You spring fanboys are really amazing. When was the last time SS has innovated please? Is wrapper-around-wrapper-around-wrapper innovation? Give me a single piece of code spring has that would make any mature developer say "gees, this is really creative, i have to read some reasearch papers before I am capable to comprehend what they actually did here".
In before, "innovation-with-OSGi-jar-file-with-lifecycle" response.
PS
Nothing against SS either, if people want to buy what they are selling, im fine with that, just this guy pissed me off.
|
|
|
Message #328586
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Mule is wrapper of spring
Mule is built on spring.... I'm working on it for a year, and i just say : leave it, go for spring-integration insteed. It took me 2 month to understand Mule, and 2 hours for Spring-Int...
For people who know Spring source code quality : dont look at Mule source code, you'll have an heart attack. Do they know Checkstyle or PMD ? And it's an anti-pattern nest... I'm sorry but go and see by yourself.
If you want to understand integration patterns, start with Spring-Integration.
|
|
|
Message #328590
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Mule is wrapper of spring
Mule is built on spring.... I'm working on it for a year, and i just say : leave it, go for spring-integration insteed. It took me 2 month to understand Mule, and 2 hours for Spring-Int...
For people who know Spring source code quality : dont look at Mule source code, you'll have an heart attack. Do they know Checkstyle or PMD ? And it's an anti-pattern nest... I'm sorry but go and see by yourself.
If you want to understand integration patterns, start with Spring-Integration.
These two are obvious trolls. Only threads they participated in is this one.
If someone wants to understand integration, read book enterprise integration patterns.
|
|
|
Message #328623
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: does anyone care anymore?
Well, Imitation is a valid business strategy! They can offer similar "competitive" product.
They will save a lot on RnD and still offer value to their customers. They are also saving a lot on marketing, since customers should be already be familiar with the product nature. And finally this is actually healthy to the market, adding more players, enlarging the market size, offering choice etc ...
Maybe they won't make the headlines, and probably shouldn't. But if they are knowingly following an imitation strategy, it actually good business
|
|
|
Message #328625
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Mule is wrapper of spring
Hi
I'm not defending anyone. But you're right - read "Enterprise Integration Patterns" (AW, 2004, ISBN 0321200683). Both Mule and Spring-Int declare that they "implement this book".
But do really have a look at their source code - Sprint-Int does have Channels (pipes) and filters. In Mule, everything is built around the concept of components (models) wrapped with interceptors, decorated with transformers and separated with routers. Try implementing some dynamic routing or endpoints (another Mule concept).
I don't say Mule is bad. I've just used it since 1.2 version and now I have active project depending on each major version (1.2, 1.3, 1.4, 2.x) and don't feel brave enough to upgrade - I'm sure some people know what I'm talinkg about. I also know Mule's source code - been there too many times to check why some method is not called or why the payload suddenly has changed.
In Spring-Int everything's in it's right place. You have messages, channels and filters (transformers, routers, selectors, ...). You want more separation? Use Spring-Int gateways (and for comparison try Mule's nested routers...)
When deciding between Spring-Int and Mule, one has to check available providers/transports. Mule has more of them, but it's much easier to implement your own in Spring-Int (I have written several in Mule myself, so I know what I'm talking about).
regards
Grzegorz Grzybek
|
|
|
Message #328663
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Mule is wrapper of spring
Actually, my experience integrating Spring and Mule was somewhat horrific. I'm sure it's better now, but a year or so ago, the integration wasn't nearly as seamless as they made it sound on the website. If you had an existing app context you wanted to drop Mule into, it was nearly impossible to get working. I think things have improved in Mule 2.0, though, although I'm not sure. I think their preference is to run the Mule server as it's own server process, rather than embedded as a drop-in integration server. My preference is to drop the integration server in as necessary, or at least it was in the project I worked on at the time.
Also, if you're choosing between Spring Integration and Mule, you might want to take a look at Camel. I agree with the poster who said it took 2 months to get his head around Mule. I had the same experience, whereas with Camel I had things up and running VERY quickly. It also integrated with Spring the way that I wanted it to (isn't that the point of Spring, so that you get things working the way you want them to rather than the way some spec or vendor tells you?), as a drop-in integration server.
And from what I've seen, Camel is hands-down the best implementation of the "Enterprise Integration Patterns" book. Their entire design is driven by that book, and the terminology is all the same. You can drill down into each one of the EIP patterns and see exactly how they're implemented in Camel, with names that match up in the configuration and everything. Spring integration isn't bad in this regard but at the time I was evaluating, it just wasn't as mature as Camel.
Lastly, I believe that Camel has a support option as well through FUSE, if you need that kind of support. Just like SpringSource and Mule.
FWIW I don't have any financial interest in Camel but it was really one of the best projects I have used in the integration space. After working with numerous products like Vitria, WebMethods, and other such tools over the years, it was great to find an open source alternative that was cleanly designed and adaptable to multiple use cases. I didn't find that with Mule and frankly, their licensing structure is absolutely horrible in terms of cost, IMHO.
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
In this session Nati Shalom demonstrates how to take a standard Java EE web application and scale it out or down dynamically without changes to the application code. Seeing as most web applications are over-provisioned to meet infrequent peak loads, this is a dramatic change because it enables growing your application as needed, when needed, without paying for unutilized resources.
(May 19, Tech Talk)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
