This blog is supposed to keep track of all the small fixes, good tutorials and cheat-sheets I encounter in my binary life so I won't have to seek them on the web again.
Tuesday, January 12, 2010
Backup & restore MySQL DB basics
http://www.devshed.com/c/a/MySQL/Backing-up-and-restoring-your-MySQL-Database/
Saturday, January 9, 2010
Glassfish v2 install tip
If port 8080 is taken (on Ubuntu - of course) by the tcp6 service run the following:
netstat -anp | grep 8080
sudo kill [Process_ID]
this way when you run ant -f setup.xml on your glassfish installation folder, you won't run into trouble
netstat -anp | grep 8080
sudo kill [Process_ID]
this way when you run ant -f setup.xml on your glassfish installation folder, you won't run into trouble
Friday, January 8, 2010
Extra repositories for Karmic Koala
http://journalxtra.com/2009/11/extra-repositories-for-karmic-koala/
Saturday, January 2, 2010
A session bean alternative: Spring
Clearly, EJB 3 session beans are not your only option in developing your applica-
tion’s business tier. POJOs managed by lightweight containers such as Spring could
also be used to build the business logic tier. Before jumping on either the EJB 3
session bean or Spring bandwagon, think about what your needs are.
If your application needs robust support for accessing remote components or the
ability to seamlessly expose your business logic as web services, EJB 3 is the clear
choice. Spring also lacks good equivalents of instance pooling, automated session
state maintenance, and passivation/activation. Because of heavy use of annotations,
you can pretty much avoid “XML Hell” using EJB 3; the same cannot be said of Spring.
Moreover, because it is an integral part of the Java EE standard, the EJB container
is natively integrated with components such as JSF, JSP, servlets, the JTA transaction
manager, JMS providers, and Java Authentication and Authorization Service (JAAS)
security providers of your application server. With Spring, you have to worry whether
your application server fully supports the framework with these native components
and other high-performance features like clustering, load balancing, and failover.
If you aren’t worried about such things, then Spring is not a bad choice at all and
even offers a few strengths of its own. The framework provides numerous simple,
elegant utilities for performing many common tasks such as the JdbcTemplate
and JmsTemplate. If you plan to use dependency injection with regular Java
classes, Spring is great since DI only works for container components in EJB 3.
Also, Spring AOP or AspectJ is a much more feature-rich (albeit slightly more com-
plex) choice than EJB 3 interceptors.
Nevertheless, if portability, standardization, and vendor support are important to
you, EJB 3 may be the way to go. EJB 3 is a mature product that is the organic
(though imperfect) result of the incremental effort, pooled resources, shared own-
ership, and measured consensus of numerous groups of people. This includes the
grassroots Java Community Process (JCP); some of the world’s most revered com-
mercial technology powerhouses like IBM, Sun, Oracle, and BEA; and spirited open-
source organizations like Apache and JBoss.
Source: Enterprise Java Beans 3 in Action,chapter 3, Manning publications, 2007

tion’s business tier. POJOs managed by lightweight containers such as Spring could
also be used to build the business logic tier. Before jumping on either the EJB 3
session bean or Spring bandwagon, think about what your needs are.
If your application needs robust support for accessing remote components or the
ability to seamlessly expose your business logic as web services, EJB 3 is the clear
choice. Spring also lacks good equivalents of instance pooling, automated session
state maintenance, and passivation/activation. Because of heavy use of annotations,
you can pretty much avoid “XML Hell” using EJB 3; the same cannot be said of Spring.
Moreover, because it is an integral part of the Java EE standard, the EJB container
is natively integrated with components such as JSF, JSP, servlets, the JTA transaction
manager, JMS providers, and Java Authentication and Authorization Service (JAAS)
security providers of your application server. With Spring, you have to worry whether
your application server fully supports the framework with these native components
and other high-performance features like clustering, load balancing, and failover.
If you aren’t worried about such things, then Spring is not a bad choice at all and
even offers a few strengths of its own. The framework provides numerous simple,
elegant utilities for performing many common tasks such as the JdbcTemplate
and JmsTemplate. If you plan to use dependency injection with regular Java
classes, Spring is great since DI only works for container components in EJB 3.
Also, Spring AOP or AspectJ is a much more feature-rich (albeit slightly more com-
plex) choice than EJB 3 interceptors.
Nevertheless, if portability, standardization, and vendor support are important to
you, EJB 3 may be the way to go. EJB 3 is a mature product that is the organic
(though imperfect) result of the incremental effort, pooled resources, shared own-
ership, and measured consensus of numerous groups of people. This includes the
grassroots Java Community Process (JCP); some of the world’s most revered com-
mercial technology powerhouses like IBM, Sun, Oracle, and BEA; and spirited open-
source organizations like Apache and JBoss.
Source: Enterprise Java Beans 3 in Action,chapter 3, Manning publications, 2007

Monday, December 28, 2009
How to change port number in JBoss App Server
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
6. Change the port number here.
7. Restart the server.
Source: http://minddiary.com/2008/02/15/how-to-change-post-number-in-jboss-app-server/
Saturday, November 21, 2009
koala chrome
Chrome for Ubuntu linux (works on karmic koala) : http://www.ubuntugeek.com/install-chromium-google-chrome-web-browser-in-ubuntu.html
Sunday, November 15, 2009
How to install adobe flash player 64-bit after upgrading to Ubuntu 9.10 Karmic Koala
You'll need this because of certain glitches occuring when using ff to watch flash-based sites (such as Youtube). Just check out the link: http://news.softpedia.com/news/How-to-Install-Adobe-Flash-Player-64-bit-on-Ubuntu-8-10-98076.shtml


Subscribe to:
Posts (Atom)