OpenESB community blog center

Welcome to OpenESB community blog center where OpenESB people and users exchange views about the project, the best practices, the new requirements and its future. Your comment and feedback helps us to stay in touch together

Today, the community is working on OpenESB migration to new container (GF V3-V4 or Jboss V5-6). If OpenESB framework and JBI component are relatively easy to migrate, some peripheral applications or features (ex: the console, Netbeans plugins) aNew OpenESB pluging for Netbeansre strongly tied with GF V2 and make the migration tricky. We cannot blame SUN designers who certainly made it to promote their application server but this migration forces us to transform these applications into agnostic tools accurate to any containers. Ex: Until now, deploying a Service Assembly on many OpenESB instance was made through Glassfish V2 cluster architecture. Since we want to be platform agnostic, we have to design and implement agnostic multi instance deployment features. In the community, some developers are working OpenESB Netbeans plugin (see the screenshot on the right) and our team was given new console development management. In order to start the project, I wrote a draft document with the first basis for the new console architecture. There are many points where I pose design questions without having any solution (for the moment I hope). In the community there are many really good architects and developer. Guys we rely on you to refine the document and propose technical solution certainly more accurate than mine. I don’t expect any congratulation but shape criticisms and technical propositions. Any serious technical proposition will be taken into account, thinks are completely open for the moment, please feel free to participate to the key project in OpenESB community.

The document can be downloaded here:  New administrator console for OpenESB

I propose you to discuss about this document and the console on our OpenESB community forum

Thanks for your help. 


Tags: Untagged
Hits: 7081
Paul Perez is Chief Software Architect of Pymma. He is an author, software architect, consultant and speaker. He brings more than 17 years experience helping corporations for mission-critical information systems. Prior to co-found Pymma, Paul was an independent software consultant, working for large financial services companies in France, UK, Benelux, Israel and Germany Paul's extensive experiences in high-performance architecture design helps the company's clients solve real-world business problems through technology. As chief software architect, Paul assists current and future client engagements and develops best practices based on his domain expertise. Paul holds a post master degree from Paris University and is a Sun Certified Enterprise Architect, Togaf certified and holds several other certifications. You can contact paul at: paul.perez (at)


Please login first in order for you to submit comments