Monday, August 27, 2007
I use Quod Libet for Audio, it has similar interface as iTunes, with more features (ability to play most audio formats). I chose Quod Libet instead of the standard Rhythmbox because of its practical mp3 tags handling. This also means that unlike iTunes, when I reimport my full library with another player, or on another computer, I have it all organized the right way, because the right meta data is in the audio files and not in a xml file that sometimes gets corrupted.
I can use Open Office (not yet available in non alpha version for Mac Os X).
I can use Picasa or other more standard alternatives instead of iPhoto.
I can use free guitar tuners, plenty of esoteric software.
Remote control, fancy bluetooth apple keyboard, cd burning, dvd player, printer work flawlessly. And it's all free software (except Picasa which is only gratis).
I am happy with my Ubuntu system :).
Thursday, August 23, 2007
I used to work with Web Services the simple way: create a java class (or EJB), expose it as Web Service through Axis or RAD, generating the WSDL in the process. And then a client would just be the reverse, take the WSDL, use a tool (Axis or RAD) that creates client Java classes from it automatically. Simple, easy.
But this process starts to fail if you have
- several very similar WSDL: you want reuse instead of copy.
- other means of communicating XML represented by the XML schema embedded in the WSDL, for example via direct MQ use.
I found 2 techs that can help:
- SDOs (Service Data Objects): from my short experience, I find it a bit too verbose, and not yet fully mature, as you depend on libraries external to SDO ones for it to work in the case of web services. It can work, and if you use IBM products, it could be a good way to write Web Services Providers/Clients.
- Spring Web Services: I have not tried it yet, but it seems to solve exactly the kind of problems I described earlier. And you can plug-in any marshalling/unmarshalling framework you want :).
Thursday, August 02, 2007
I had not seen that before, and was wondering why one would do such a thing. It seems to be unintuitive. I found my answer through... GWT widgets. In this page, the author explain motivations behind doing such a thing:
While not 100% in tune with the MVC pattern, it is often convenient to access the servlet
container, the HTTP session or the current HTTP request from the business layer. The GWT-SL
provides several strategies to achieve this which pose a compromise in the amount of configuration
required to set up and the class dependencies introduced to the business code.
The easiest way to obtain the current HTTP request is by using the
which provides convenience methods for accessing the
HttpServletResponseinstances. Please note that it makes use of thread local variables
and will obviously not return correct values if used in any other than the invoking thread.