Archive for the ‘Uncategorized’ Category

10 malentendidos sobre spring

septiembre 12, 2006

Interesante articulo sobre spring en oreally hoy :

1. Spring no es lightweight.

2. spring es overkill par aplicaciones simples

3. Spring no escala bien con aplicaciones realmente grandes

4. Spring  te fuerza a usar  Programación orientada a objetos (AOP) Aspect-Oriented Programming (AOP) la cua es experimental.

5. Spring sustituye a Java Enterprise Edition (JEE).

6. Spring yEJB son mutuamente excluyentes

7. Spring no puede Spring tomar aprovechar las ventajas de las anotaciones en Java 5 annotations como lo hace EJB3

8. Para aplicaciones grandes, el mantenimiento de los archivos XML de Spring es una pesadilla

9. Spring lo hace todo con reflexion, por lo tanto es lento.
10. Spring MVC es complejo y no es tan sencillo como el resto de Spring.

Hace 15 años :

agosto 7, 2006


In article <6…> I promised to post a short summary  of the
WorldWideWeb project.  Mail me with any queries.

WorldWideWeb – Executive Summary

The WWW project merges the techniques of information retrieval and hypertext to
make an easy but powerful global information system.

The project started with the philosophy that much academic information should
be freely available to anyone. It aims to allow information sharing within
internationally dispersed teams, and the dissemination of information by
support groups.

Reader view

The WWW world consists of documents, and links.  Indexes are special documents
which, rather than being read, may be searched. The result of such a search is
another (“virtual”) document containing links to the documents found.  A simple
protocol (“HTTP”) is used to allow a browser program to request a keyword
search by a remote information server.

The web contains documents in many formats. Those documents which are
hypertext,  (real or virtual) contain links to other documents, or places
within documents. All documents, whether real, virtual or indexes, look similar
to the reader and are contained within the same addressing scheme.

To follow a link,  a reader clicks with a mouse (or types in a number if he or
she has no mouse). To search and index, a reader gives keywords (or other
search criteria). These are the only operations  necessary to access the entire
world of data.

Information provider view

The WWW browsers can access many existing data systems via existing protocols
(FTP, NNTP) or via HTTP and a gateway. In this way, the critical mass of data
is quickly exceeded, and the increasing use of the system by readers and
information suppliers encourage each other.

Making a web is as simple as writing a few SGML files which point to your
existing data. Making it public involves running the FTP or HTTP daemon, and
making at least one link into your web from another. In fact,  any file
available by anonymous FTP can be immediately linked into a web. The very small
start-up effort is designed to allow small contributions.  At the other end of
the scale, large information providers may provide an HTTP server with full
text or keyword indexing.

The WWW model gets over the frustrating incompatibilities of data format
between suppliers and reader by allowing negotiation of format between a smart
browser and a smart server. This should provide a basis for extension into
multimedia, and allow those who share application standards to make full use of
them across the web.

This summary does not describe the many exciting possibilities opened up by the
WWW project, such as efficient document caching. the reduction of redundant
out-of-date copies, and the use of knowledge daemons.  There is more
information in the online project documentation, including some background on
hypertext and many technical notes.

Try it

A prototype (very alpha test) simple line mode browser is currently available
in source form from node [currently] as


Also available is a hypertext editor for the NeXT using the NeXTStep graphical
user interface, and a skeleton server daemon.

Documentation is readable using www (Plain text of the instalation instructions
is included in the tar file!). Document

is as good a place to start as any. Note these coordinates may change with
later releases.


Tim Berners-Lee                 Tel:    +41(22)767 3755
WorldWideWeb project            Fax:    +41(22)767 7155
C.E.R.N.                        email:  t…
1211 Geneva 23

Hidrogeno y estupidez.

julio 23, 2006

The two most common elements in the universe are Hydrogen and stupidity.

Dorothy Nevill

10 nuevas caracteristicas de Eclipse 3.2

julio 5, 2006

Poco a poco voy descubriendo las nuevas caracteristicas que trae el nuevo Eclipse 3.2. Esta vez gracias a un post publicado por ZDNet

1. Refactoring scripts and API-awareness

2. Clean Up Wizard

3. Pervasive filtering support

4. Improved patching support

5. CVS Quick Diff annotations

6. Null reference analysis

7. File system API

8. JFace field assistance

9. Custom draw trees and tables

10. Faster and smaller

Install Tomcat 5.5 en ubuntu

julio 1, 2006


  • SDK: 1.5
  • Tomcat: 5.5

Step 1 – Instalar JRE y SDK

# sudo apt-get install java# java -version javac -help

Paso 2 – Obtener tomcat

Descarga Tomcat 5.5 desde

Descomprime el archivo :

tar xvfz jakarta-tomcat-5.5.x.tar.gz

N.T: Para hacer las cosas sencillas renombrar el archivo a tomcat Si prefiere no hacer esto sustituye la palabra ‘tomcat’ por ‘tomcat-5-5.x’…

Step 3 – Add tomcat

ruta para descomprimir tomcat :

Step 4 – Settear JAVA_HOME y el CLASSPATH

Es necesario que JAVA_home apunte a el directorio donde esta instalado java. Para esto editaremos el fichero .bashrc. Guarda primero el archivo antiguo :

cp ~/.bashrc ~/.bashrc.oldgedit ~/.bashrc

Añadir las siguientes lineas:

export JAVA_HOME=/usr/lib/j2sdk1.5-sun/

export CLASSPATH=$CLASSPATH:/usr/local/tomcat/common/lib/jsp-api.jar

export CLASSPATH=$:/usr/local/tomcat/common/lib/servlet-api.jar

N.B. remember to change the word tomcat to the name of the package you placed in /usr/local.

Save and close. Es necesario reiniciar la sesion para que los cambio tengan efecto

Los proximos pasos son opcionales. Sirvenpara configurar tomcat como entorno de desarrollo.

Desactivar consolar virtuales

junio 7, 2006

En ubuntu tenemos 6 consolas virtuales aprates del modo grafico podemos acceder a ellas pulsando Ctrl+Alt+F1…F6 y salir de llas con Ctrl+Alt+F7, cada consolo suele ocupar entorno a 1 o 2 megas de memoria RAM. Podemos desactivarlas comentando las lineas en el archivo /etc/inittab 

  • 1:2345:respawn:/sbin/getty 38400 tty1
  • 2:23:respawn:/sbin/getty 38400 tty2
  • # 3:23:respawn:/sbin/getty 38400 tty3
  • # 4:23:respawn:/sbin/getty 38400 tty4
  • # 5:23:respawn:/sbin/getty 38400 tty5
  • # 6:23:respawn:/sbin/getty 38400 tty6

Eligiendo las herramientas

mayo 1, 2006

Antes de ponerme a trabajar evalue cual, en principio, iban a ser las tareas que iba a tener que realizar :

  • Edición de texto : Latex
  • Lenguaje de programación y entorno de desarrollo de software :
    • Lenguaje de programación : Java
    • Entorno de programación : Eclipse
  • Editor de Latex : Texlipse, plugin de latex para eclipse
  • Otras herramientas utiles :
    • Bookmarks :
    • Organizador : Basecamp

Pronto ire haciendo algunos post de cada una de estas herramientas y de las que vayan apareciendo por el camino.