Video tutorial de JasperReport y Struts 1

Ver este link

Múltiples struts-config.xml e internacionalización de Jasper Report

Struts optionsCollection

Código fuente para implementar optionsCollection lo encontraras en este link

XHTML Estructura global del documento

ver este link

Tejedores del Web XHTML

Caracteres especiales JavaScript

Ver este link

JSTL Funciones

Introduction to JSP Standard Tag Library (JSTL Basics)

Tomcat Monitoreo de Procesos

Monitoreando aplicaciones JAVA con jAMON y VisualVM HAT

Hibernate Mapping

Ejemplos de Mapping:

Hibernate Mapping One-to-One

Añadir una fila a una tabla con jQuery

ver este link

jQuery add table row function

How to tell if an element is visible with jQuery (Ocultar Elementos)

Como agregar filas o rows a una tabla dinamicamente mediante jQuery

Formatear numeros con JQuery

ver este link: jQuery Format Currency Plugin

Algunos ejemplos

Formatear numeros mientras los tipeas

Formatting numbers in jquery

Implementar Login con Seguridad en Spring

Ver documentación de Spring Security Plugin


Login en Struts 1


Un recorrido por Spring Security 3.0

Utilización de grupos en Spring Security

Implementación de Spring Security con Oracle

Simple web application with Spring Security: Part 1

Ejemplo con Spring Security 2.0

Spring Security 2.0.x Reference Documentation

Proyecto que integra Struts 1 + tiles + Spring Security 2.0.x (DelegatingActionProxy)

Spring plugin para Struts 1.3.X (DelegatingActionProxy)


Custom AuthenticationProcessingFilter for spring security to perform actions on login

How to handle expired session using spring-security and jQuery?

Spring security session timeout and JQuery

Documentación en Ingles

En la pagina www.docme.ru que esta en Ruso encontraran libros actuales TOP de la especialidad

Checking database parameters in Oracle

A very easy way to check parameter values for Oracle database is to issue following command from SQL*Plus prompt. It is followed by abbreviated output.

SQL>show parameter

NAME TYPE VALUE
————————— ———– ——————————
background_core_dump string partial
background_dump_dest string D:\ORACLE\PRODUCT\10.2.0\ADMIN
\ORCL\BDUMP
backup_tape_io_slaves boolean FALSE
bitmap_merge_area_size integer 1048576
blank_trimming boolean FALSE

To view specific values of parameters related to SGA command should be

SQL>show parameter area

NAME TYPE VALUE
————————— ———– ——————————
bitmap_merge_area_size integer 1048576
create_bitmap_area_size integer 8388608
hash_area_size integer 131072
sort_area_retained_size integer 0
sort_area_size integer 65536
workarea_size_policy string AUTO

Alternatively Oracle provides two dynamic performance views to look at all the parameter values specified for the database.

V$Parameter – provides information about all parameters. It also indicates whether parameters are modifiable at session level or system level. Following is the query to look for parameters related to SGA.

SQL> SELECT name,value,isses_modifiable,issys_modifiable
FROM v$parameter
WHERE name like ‘%sga%’;

NAME VALUE ISSES ISSYS_MOD
————— ————— —– ———
sga_max_size 612368384 FALSE FALSE
pre_page_sga FALSE FALSE FALSE
lock_sga FALSE FALSE FALSE
sga_target 612368384 FALSE IMMEDIATE

V$NLS_Parameters – provides information about all parameters related to NLS settings.

SQL> select * from v$nls_parameters;

PARAMETER VALUE
—————————— ——————————
NLS_LANGUAGE AMERICAN
NLS_TERRITORY AMERICA
NLS_CURRENCY $
NLS_ISO_CURRENCY AMERICA
NLS_NUMERIC_CHARACTERS .,
NLS_CALENDAR GREGORIAN
NLS_DATE_FORMAT DD-MON-RR
NLS_DATE_LANGUAGE AMERICAN
NLS_CHARACTERSET WE8MSWIN1252
NLS_SORT BINARY
NLS_TIME_FORMAT HH.MI.SSXFF AM

Certain parameters can be changed dynamically using ALTER SYSTEM command. Other parameter values need to be changed in init.ora or spfile or both.

ver fuente

Oracle LIKE clause searches with text indexes

One serious SQL performance problem occurs when you use the SQL “LIKE clause” operator to find a string within a large Oracle table column (e.g. VARCHAR(2000), CLOB, BLOB):

Select stuff from bigtab where text_column like ‘%ipod%’;
Select stuff from bigtab where full_name like ‘%JONES’;

Because standard Oracle cannot index into a large column, there “like” queries cause full-table scans, and Oracle must examine every row in the table, even when the result set is very small. These unnecessary full-table scans are a problem:

1. Large-table full-table scans increase the load on the disk I/O sub-system

2. Small table full table scans (in the data buffer) cause high consistent gets and drive-up CPU consumption


Ver Articulo completo

A CONTEXT Query Application

Oracle SQL "contains" clause tips

Filtrar por cadenas parecidas en una lista en oracle

Oracle case insensitive searches(Implementación)

Búsquedas fuzzy, índices context y gestión documental con Oracle 9i