links for 2011-02-17

18 02 2011
  • Overview: What is pages.xml?

    The pages.xml file and any .page.xml file is Seam's way of describing:

    1. RESTful (non-Faces) pages – That is, what to do with the URL parameters for a GET request.
    2. View restrictions – Restrict users from viewing pages based on an EL expression.
    3. Page actions – Invoke EL expressions whenever a page is accessed (RESTful or not).
    4. Page flow – The Seam <navigation> elements can replace the ordinary JSF navigation rules.

  • 1. Open the JBoss Folder
    2. Goto its Deploy folder.
    3. Goto the jbossweb-tomcat55.sar
    4. Find out the server.xml inside that folder. Actually this is the server configure file of the BuildIn Tomcat.
    5. Find the folowing Tag
    <Connector port=”8080″ address=”${jboss.bind.address}”…….
    6. Change the port number here.
    7. Restart the server.
  • # Integer.valueOf(String) converts a String to a number by assuming the String is a numeric representation. In other words. Integer.valueOf("12345") yields the number 12345.
    # Integer.getInteger(String) converts a String to a number by assuming the String is the name of a system property numeric representation. In other words. Integer.getInteger("12345") is likely to yield null.
  • Compared to Ruby on Rails,the ability to type check Java code is a nice feature and lets you find a certain kind of mistake very quickly,in an IDE such as Eclipse even as you type.This support rapidly degrades when moving outside the statically typed world of Java.As soon as the programmer has to jump to using strings,as is the case when using e.g. regular expression,SQL and HQL,the safe,checked world of Java comes to an end.The only kind of checks that are performed in languages like Java are type checks.This also means that the only mistakes are found that are related to types and can be expressed in types.This gets you only up to a certain point in finding programming errors. In order to use regular expressions in Java, programmers have to encode them in strings;SQL queries are encoded in strings compilers do not check strings. Strings are parsed and interpreted only at runtime,meaning problems only appear at runtime typically buried in an enormous stacktrace.And that’s a big shame.

Acciones

Information

Responder

Introduce tus datos o haz clic en un icono para iniciar sesión:

Logo de WordPress.com

Estás comentando usando tu cuenta de WordPress.com. Cerrar sesión / Cambiar )

Imagen de Twitter

Estás comentando usando tu cuenta de Twitter. Cerrar sesión / Cambiar )

Foto de Facebook

Estás comentando usando tu cuenta de Facebook. Cerrar sesión / Cambiar )

Google+ photo

Estás comentando usando tu cuenta de Google+. Cerrar sesión / Cambiar )

Conectando a %s




A %d blogueros les gusta esto: