sudo apt-get install ivtv-utils
sudo v4l2-ctl -d /dev/video0 -i 2

Opened VLC  , Media-> opened capture device->capture mode PVR and click play (with norm as pal for me ).

Immediately my output started displaying on the VLC screen . Initially there was some flicker on the video displayed , but once i installed the latest nvidia drivers using following commands the flicker disappeared and a clear video was displayed .

sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
sudo apt-get install nvidia-current nvidia-settings

In case of MSSQL server you need to uninstall  MSXML6  components by using Windows Install Cleanup Utility which can be downloaded from http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe.

After the un installation of the component , you can download the latest MSXML SP from the download site , install it and then proceed with your installation of MSSQL server .The installation goes on smoothly  .

Even tough the post is mostly oriented towards MSXML and MSSQL server , I have tried this scenarios with most of the IBM applications which tend to render a further re-installations of the same application to fail .The cleanup utility helps in removing most of the erroneous components from the system which often fail from the “Add-Remove “program menu

• web.xml
• dispatcher-servlet.xml
• HelloController.java(controller)
• index.jsp,mypage.jsp
• Library files as usual

Lets start with each component step by step :

1.web.xml
This file contains the as usual the servlet stuff and the mapping stuff required for forwarding to any particular servlet .The intercept in the web.xml file for my app  is as follows :

<servlet>
<servlet-name>dispatcher</servlet-name>
<servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>

<servlet-mapping>
<servlet-name>dispatcher</servlet-name>
<url-pattern>*.htm</url-pattern>
</servlet-mapping>

<welcome-file-list>
<welcome-file>
/WEB-INF/pages/index.jsp
</welcome-file>
</welcome-file-list>

Well this file explains itself and states necessity of the .htm extension for forwarding to the servlet .

2.dispatcher-servlet.xml
Spring  by default looks for this file under the WEB-INF directory , so  this lies in parallel to the web.xml file . This file contains the controller names to which any particular request would be mapped based upon the url .This file also lists the view resolvers which are helpful in mapping and forwarding the views from the controller .The main intercept of a basic dispatcher-servlet.xml file is as follows :

<bean id=”viewResolver”>
<property name=”prefix”>
<value>/WEB-INF/pages/</value>
</property>

<property name=”suffix”>
<value>.jsp</value>
</property>
</bean>
<bean name=”/normal.htm”/>

3.HelloController.java(controller)

This is the main part of the application , this is where your java code exist .Controller performs the  business logic (if any or delegates it further) and forward to a view (ideally ViewResolver which further renders view).The intercept for a bare bone controller is as follows :

package com.mvcapp.controller;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import org.springframework.web.servlet.ModelAndView;
import org.springframework.web.servlet.mvc.AbstractController;

public class HelloController extends AbstractController {
private String message;

@Override
protected ModelAndView handleRequestInternal(HttpServletRequest request, HttpServletResponse response) throws                                                     Exception {
Thread.sleep(500);
return new ModelAndView(“mypage”,”mymessage”, message);
}

public void setMessage(String message) {
this.message=message;
}

}

In this file the final return statement hints toward the view that we intend to render . The first parameter “mypage” is the view name and the ViewResolver would resolve it to “/WEB-INF/pages/mypage.jsp” with help of the definition in the in the dispatcher-servlet.xml file .The second parameter “mymessge” is the view parameter and   can be accessed on the view .

4. index.jsp,mypage.jsp

These are the jsp’s that i have used for the demonstation purposes . mypage.jsp is the final jsp that you are rendering through your controller , while index.jsp is the jsp file use for redirecting to your controller url .The intercept for the index.jsp file is as follows :

<a href=”normal.htm”>Click here for normal dispatcher</a><br/>

The pages of course need to be placed under “WEB-INF/pages” directory .

5. Library files
I m not too sure about the exact library files required , but the ones that i required are as follows :

1. spring.jar
2. spring-webmvc.jar
3. spring-web.jar
4. spring-core.jar
5. spring-context.jar
6. spring-context-support.jar
7. spring-beans.jar
8. spring-aop.jar
9. commons-logging-1.1.jar

This is the minimum that you are required to have to get your spring MVC app working (you could have also used annotations , but this did the trick for me ) .

The mysql installation used for this article is mysql no install binary installation .The detailed steps for the replication are as follows :

1.Download the binary distribution for the mysql .
2.Extract the downloaded mysql binary zip files twice to two folders namely the “master” and “slave”.
3.Make a copy of “my-huge.ini” in the two folders and rename it as “my.ini”.
4.Make the configurations to the “my.ini” files in the master and slave folder as follows :

Section required in master my.ini

port=5000
log-error = c:/newmylog/mysql.err
log-bin = c:/newmylog/mysql-bin


Section required in slave my.ini

#log-bin=mysql-bin
server-id = 2
log-error = c:/newmylog/mysql.err


Execute the following code on the master server :

mysql -uroot
mysql>grant replication slave on *.* to slaveuser@'localhost' identified by 'secret';
mysql>\q

Execute the following code on the slave server :

After the last command on the slave for the status we get an output as shown below :

slave status command output

With no error displayed on the slave status you can see that any changes made on the master server databases are reflected on the slave immediately .

In case you want to keep this installation for a bit longer , you can add the mysql installation bin directory to the “PATH” environment variable.

1. ndiswrapper -i path/to/NetRt61G.INF
console output :- installing netrt61g

2. ndiswrapper -l
console output :- Installed ndis drivers:
netrt61g

3.modprobe ndiswrapper
console output :- ndiswrapper version 1.55+CVS loaded

4.ndiswrapper -m

The driver didn’t work and no wifi .So i decided to try with a 64 bit driver and it did the trick for me .
Then i configured the network card using following steps :
1.Browse to “nework settings” from YAST .
2. Enter “Wireless” as device type in the configuration section .
3.Kept the default configuration name as it is .
4.Kept the default hadware config name .
5.Enter “ndiswrapper” in the field Module name.
6.Browse to next step by pressing the button “Wireless settings”.
7.Operating mode is kept as “managed “.
8.Added the network name used by the access point in the field Network Name (ESSID).
9.Kept the encryption settings as WEP-Shared and added a hexadecimal key .
10.Rebooted the system .

And after reboot my wifi was up and running .

The 64 bit driver for Dlink GW510 can be found at DWL-G510_XP64bit_Vista64bit_Driver_v2.1.2.0.zip

1. sudo apt-get install wicd
2.wicd-client

This exception is caused when an object from the database is detached and a collection from the object (which is supposed to be lazily loaded ) is accessed . Due to the closing of the session this exception is thrown .

To overcome this exception either we can use an Open Session in View interceptor or my personal favourite a servlet filter .The configuration required for the filter is a simple one and involves addition of following snippet in web.xml file

That’s it , the exception goes away with such a small addition . However an interesting point to note was the place of application of filter . If i applied the filter after the struts 2 filter ,the filter didn’t seem to work.But if its before the struts 2 filter ,then everything works as breeze