Contact databases are easily made unmanageable. They tend to grow in an unordered manner and carry those defects inherent to non categorized huge databases. Users might be able to see the whole database or may end up creating contact duplicates. As long as contacts database is attached to web users database, privacy isn't satisfied. Anyone seeing contacts sees users, maybe even permissions, roles and the like. But how to avoid it? Giving yourself each customer, provider, collaborator and so on, its permissions? Certainly not.

Here is where Social Groups comes in help. Build upon BlueBee Contacts, Social Groups define the way a contact has to be categorized, to those has to be related and which permissions is allowed. Social Groups make a clear vision of Contacts database.

I have been disconnected from this site quite long. It seems that time isn't working the right way with me. You know, the more I'm supposed to understand the more complicated to write about it. Well, this time I made a break and gathered myself in order to put my two cents saying something about Zkoss.

First, I would like you to notice that this goes about web application frameworks. Java Server Faces, Flex, Google Web Toolkit, Wicket and those of that kind. I have stressed most of them in my way of being productive writing web applications. Difficult, let me tell you.

Aquests darrers dies han circulat una pila de noticies referents a Facebook i els problemes que tenia amb la confidencialitat de les dades. Resumint, alguns usuaris es queixaven que les seves dades no s'esborraven completament al donar-se de baixa. Altres deien que un usuari un pel avispat podia accedir a fotografies, encara que no se li permetés per la via de convertir-se en amic.

I love Java, from the very beginning. It happened as much like with C++, one gave me computer control, the other offered the world. That's what Java was all about, being able to be everywhere. Today things had come bigger and Java isn't anymore the applet programing language, but a whole set of APIs to create almost anything.

You could call that the good and the bad of Java. Will depend on who you believe in and where Sun goes to.

A week a go I found the incredible Google Web Toolkit and decided to develop XMLPortal administration with it. Since I'm using NetBeans, the first thing was looking for NB support on GWT. This directed me to the always interesting Roumen's blog. Unfortunately NB module doesn't support server-side code and I had to configure by hand the new GWT library. This is how I did it:

Can't tell you how happy I am. And I can't even realize why. The fact is that I wanted to make this step from long time ago and there were always things stopping me from doing that. Blai Capdevila, who is impulsing XMLPortal development from the very beginning, has been also compelled by the move. Now is a reality, everyone interested in XMLPortal developement can follow this address xmlportal.dev.java.net and checkout source code from repository.

Lately I have been thinking about how to neatly allow new users into web sites. The think goes about a requirement for the Elephant library project: Visitors may register and eventually be enabled to perform some actions.

I made myself more assured about developing free applications. Afterall, what difference it makes for business with few customers, all depending on our services. We tell them which software to install, how it works and what could be achieved --understand me, I mean the real truth, not those achievements found on brochures, talking about how good could be done with software and making costumers feel like dummies, when they eventually are unable to reach such wonders.

This is a personal site. I was looking for a place where I could write my thoughts, those unordinary days that I have thoughts, but I found that nobody was interested in them. Odd, let me tell you, since rare things are usually highly valuated.

Earlier 2005 I had the need to install web statistics for Tomcat web servers. The reason might be obvious: XMLPortal runs on JSP/Servlet containers. Usually, Java hosting plans use Apache server to generate access logs and then redirect requests to Tomcat. This runs pretty well, but once a hosting provider offers to improve your account by sending requests directly to Tomcat, you can't say no. And I said yes. Soon I start missing things, like web statistics. This is how, step by step, I dealt with it. Today I have splendid AWStats on my web site!