Skip to main content

路 2 min read

This year I was lucky enough to have a presentation at the second edition of the "Universit茅 du SI", organized by Octo Technologies. I have to say that this conference is one of the best that I have attended, for sure it is the best in France. Unfortunately I was only able to attend the first day of the conference, but even in one day, I was very happy with the content of the presentations, keynotes, and networking opportunities.

I won't go in details in all the presentations that I have seen, Google for the Enterprise, Application Server Future, Usability concerns, and keynotes. If you want to have a good feedback about this conference I invite you to read, in French, the reports from Le Touilleur Express.

Let me just share the presentation that I gave with Vincent Massol from XWiki, about CMS vs Wiki.

Wiki vs CMS duel

First of all, the room was packed, so it looks like it is an interesting subject for many of you, so do not hesitate to post comments or question on this entry. Vincent and I will be pleased to update our presentation for a new event.

The main message of the talk was:

  • For collaboration on content the wiki is king
  • For publication of content the CMS is king

Wiki vs CMS

路 One min read

eXo Platform, and I, will be present in conferences in the upcoming weeks:

  • Linux Solutions, March 31st - April 2nd : In addition to the demonstration pod where you can meet eXo people, I am inviting you to joing us during the OW2 Annual Conference presentations:
    • Next generation Portals: how OpenSocial standard adds social to the mix (April 2, 01:30 - 02:00)
    • Which Portlet Bridge is made for you? (April 2, 02:00 - 02:30)

You can find the full program here.

  • Salon Intranet, May 12th,13th : Once again, eXo will be present with a demonstration pod, but also come to meet eXo CEO, Benjamin Mestrallet and myself during the "eXo Platform, the Open Source solution for your Intranet" on May 12th from 3pm-4pm.

路 2 min read

When deploying your Web Service client you often need to change the endpoint of the service that 聽has been set during the code generation. This short post explains how you can set change it at runtime in the client code.

You have two approaches to do that:

  • set the endpoint in the Port using the BindingProvider
  • get the endpoint URL from the WSDL itself at runtime

Use the Binding Provider to set the endpoint URL#

The first approach is to change the BindingProvider.ENDPOINT_ADDRESS_PROPERTY property value of the BindingProvider (Port) using the following code:

try {  EmployeeServiceService service = new EmployeeServiceService();  EmployeeService port = service.getEmployeeServicePort();
  BindingProvider bp = (BindingProvider)port;  bp.getRequestContext().put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "");
  Employee emp = port.getEmployee(123);
  System.out.println("Result = "+ emp);} catch (Exception ex) {...}

Use the WSDL to get the endpoint URL#

Another part is to set the WSDL when you are creating the Service. The service will be using the value that is located in the WSDL port -SOAP Endpoint-. This is simply done using the following code:

try {  EmployeeServiceService service =  new org.demo.service.EmployeeServiceService  (new URL(""),  new QName("","EmployeeServiceService"));
  EmployeeService port = service.getEmployeeServicePort();  Employee emp = port.getEmployee(123);
  System.out.println("Result = "+ emp);} catch (Exception ex) { ... }

Note that, in Glassfish, like lot of Web Service environments the WSDL can generate dynamically the Endpoint URL based on the URL used 聽to get the WSDL. With this approach you can also dynamically change the Soap endpoint. (If compatible with the network configuration of the production environment.)

路 10 min read

I am writing this post as an answer to Christian Faure's blog post, (in French), about interest of enterprise portals. Let me take each point, one by one and comment them. I won't go in the all the details of many other points that why new enterprise portals are interesting for many of us, I just want to focus on Christian's remarks.

路 One min read

When working on software design, UI Mockups are quite important and Patrice, colleague of mine at eXo has pointed me to a very cool tool to use when you have to quickly do a mockup, and work with the dev team in an iterative fashion: This tool is "Balsamiq Mockup". Here an example of mockup realized with Balsamiq:

Also if you read more about the tool, you can see that it has native integration with others tools such as JIRA, so cool to be able to integrate a mockup easily when defining a new item...

Take a look to this screencast explaining the basic features and use of the product:

Another interesting tool is the online white board "DabbleBoard" that allows user to quickly create and share graphs, ideas, ... A very cool feature of this tool is the automatic recognition of shapes. The best way to understand, is simply to see it in action:

<object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" id="viddler" height="342" width="437">    <param name="movie" value="" />    <param name="allowScriptAccess" value="always"><param name="allowFullScreen" value="true"/>    <embed src="" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" name="viddler" height="342" width="437">    </embed></object>