Skip to main content

Mamadou Lamine Ba

Mamadou Lamine Ba is a software architect from Senegal. He enjoys reading and writing because he believes that sharing leads to innovation. In this blog, you can read his thoughts as humble contribution to make the Java Community cleverer than it is.

 

lamine_ba's blog

Http Caching with JAX-RS and Groovy

Posted by lamine_ba on October 24, 2012 at 8:25 AM PDT

Do what you think is interesting, do something that you think is fun and worthwhile, otherwise you won’t do it well anyway.
Brian Kernighan

Moving MY IDE in the CLOUD

Posted by lamine_ba on October 1, 2012 at 12:52 PM PDT

STUPIDITY is the next level to INTELLIGENCE
Anonymous

INTRODUCTION

Ladies and Gentlemen, right now the web is really living an exciting time. Even in my craziest dreams, I would have never thought that one day I would have the chance to write this blog post and to share with you the story of how I was able to build for my web application, a virtual editor that can run in the cloud and that can embed with an insolent ease any JavaScript SOURCE CODE or WYSIWYG editors. But no story does come without the rise of a need and the more I'm programming and the more I'm convinced that Eclipse, NetBeans and such are not the right tools for us to build quickly a web application when we are all seeing the mismatch between the two contexts in which both are running. So it is with an immense pride that I'm fully endorsing projects like Eclipse Orion for the great work they are doing in showing us the right way to how to become a more ambitious community.

Consuming a REST service within JSF using JQuery and Handlebars [THE TRUE MVC APPROACH]

Posted by lamine_ba on July 29, 2012 at 3:13 PM PDT

The indispensable first step to getting the things you want out of life is this : decide what you want.
Ben Stein

JAX-RS 2.0 : The Movie

Posted by lamine_ba on July 11, 2012 at 5:36 AM PDT

The shift of focus will have a profound and enduring effect on the way we write programs.
Ward Cunningham and Ralph Johnson

JSR 339 : VIDEO PRESENTATION

Designing and Testing RESTful web services [ UML, REST CLIENT ]

Posted by lamine_ba on June 22, 2012 at 2:23 PM PDT

If you know the enemy and know yourself, you need not fear the result of a hundred battles.
If you know yourself but not the enemy, for every victory gained you will also suffer a defeat.
If you know neither the enemy nor yourself, you will succumb in every battle.
Sun Tzu, Chinese general. The Art of War

INTRODUCTION

Ladies and Gentlemen, Like you, I'm intimately convinced that a professional should not promote a bad practice or a bad technology even though it does serve his own interests or those of his company. And that is one reason why, I wrote this blog post as a replacement of my previous one in which I have shown to many of you, how to build a JAX-RS web service with Groovy. But believe it or not, but I did really ask to myself how I did ever think that giving you the knowledge of a scripting language or whatever to write your RESTful web service, could be the key for you to understand how to design a successful RESTful API.

Building RESTful web services with JAX-RS, JAXB and Groovy

Posted by lamine_ba on May 20, 2012 at 11:14 AM PDT

Any intelligent fool can make things bigger, more complex, and more violent
But it takes a touch of genius and a lot of courage to move in the opposite direction.
Albert Einstein

Introduction

Ladies and Gentlemen, beyond the fact that I'm going today to share with you, most of the things a developer should know when building a JAX-RS web service with Groovy, this blog post is first and foremost a farewell to the Java language. It was a fun ride but now I think it is high time for me to move on. And how odd and ridiculous is it to build the dynamic parts of my application with a static language?

If JAX-RS had an MVC framework?

Posted by lamine_ba on April 10, 2012 at 1:09 PM PDT

We build too many walls and not enough bridges.
Isaac Newton

Introduction

In my previous blog post, I have asked to many of you this question: "What JSF should become?". And since then, I was quite silent. The reason behind it, is that I was working to build a concrete implementation of this vision and today I'm glad to give you a concrete demonstration of it. So Ladies and Gentlemen, why waiting more? Let's first start with the idea you are expecting in JSF 2.2...

What JSF should become?

Posted by lamine_ba on November 27, 2011 at 6:03 AM PST

Perfection is achieved through times.
Anonymous

Introduction

How someone can improve if he has no clear vision of what he could become? I'm asking this tough question to myself while reading to the definition of JSF. As it is written in its specification, JavaServer Faces is a user interface framework designed to significantly ease the burden of writing and maintaining applications that run on a java application server and render their UIs back to a target client. Woow! That is really a lovely definition but is it still relevant in 2011 and beyond? Ladies and Gentlemen, are you sure that we don't need more? 

Our standard web framework is built around the greatest design patterns but it definitely lacks the fundamentals. I have read nowhere that JSF has provided any guidance to developers through the form of "development patterns". And we still have the huge pretension to ask you to use a web framework which has no standard development models coming through the form of conventions. Let me now adopt a more professional attitude in order to clarify my position with some concrete examples thus you will better understand what I'm talking about.

A Multi-templating System : what does it mean for you?

Posted by lamine_ba on November 12, 2011 at 2:25 PM PST

 

For prosperity to be sustained it must be shared.
thegatesnotes

Conventional UI design with Facelets and JSF 2.2

Posted by lamine_ba on October 3, 2011 at 1:54 PM PDT

 

An experience is relevant only if it can prevent you to repeat the same mistake.
Anonymous

Introduction

Make it compliant! Yes, Ladies and Gentlemen, Make it compliant! That is my tip of the day and the statement I woke up with today. Like many of you, I have read the Jsf-spec pdf file and as you may know, JSF 2.2 is coming with two major features : Faces Flows and Multi-templating. Did you see that it will be possible to package a Faces Flow and a template as a jar file, or as an exploded directory? And that it will be possible to offer faces flows and templates as re-usable components in a software repository, such as a maven repository ? In other words, the new vision of JSF is “drop in and go”. There is nothing wrong and suspicious in that strategy but I'm only curious to see how this will gonna happen if we haven't any conventions yet. You would be in a big dream if you think that my view can reuse your template if it does not bring well-known areas. Just take a look at this sample to be convinced :