Upgrade has been smooth. Took almost 24 hrs on my Photon+ wireless connection.  All applications and hardware is working good.

Things I miss in 11.04 are:

1. Show Desktop

2. Computer( to see all my disk and attached drives)

Issues Faced

1. TeamViewer in fullscreen mode does not seem to work properly. To click on any menu we have to do it from few pixels below(Strange).

2. Eclipse running on another workspace will not get highlighted for editing if we click directly on eclipse Icon. We have to go back and use workspace switcher to continue normally in eclipse.

Thats all. If there is any more issues I will report it soon here. Overall 11.04 is much more polished than previous versions of Ubuntu.

sudo gedit /etc/modprobe.d/alsa_base.conf

add following entry

options snd-hda-intel model = dell-m4-1

save the file.

Goto Audio applet select sound preferences..

Select Input Tab

select connector microphone/microphone.

Finally set input volume to 50%.

Run following command from terminal  sudo apt-get install usb-modeswitch

Then goto  Sytem-> Preferences -> Network Connections

Select Mobile Broadband tab

Click Add select country India and  Provider as Reliance.

Complete the steps and for  username/password  enter you MDN number.

From Network Manager applet select Reliance connection  you should be online.

For Tata Photon + Modem follow the same step instead of Reliance select TataPhoton+ as provider.

Tata Photon+ does not need username/password for connection.

For example handling UnchekedException at JSP/View layer is very simple like just adding an ErrorPage attribute in JSP or global exception tag in Struts. To do the same in JSF-Facelets we may need to write customActionListener/delegation servlet but these are not standards.

• Since JSP servlet development is request/response based to the JSF Event/Component based architecture it is bit difficult to adopt. JSF is similar to Swing so a Swing developer may find it very easy.
• Using Facelets as View in JSF application may contribute to further complications to the regular JSP-Struts Developer.
• Use RichFaces or MyFaces, as these frameworks provide rich UI components along with AJAX support out of the box developing professional looking application is a breeze.
• Uses of Facelets: It provides templating feature simlar to tiles. It is faster than JSP.
• We can avoid using JSTL and scriptlets completely in Facelets.
• Instead of using c:if,  use rendered attribute to optionally display a block of html/Facelet code.
• To iterate over a list or collection use h:dataTable or h:colum instead of using c:forEach
• Unified EL is evaluated at runtime where as JSTL and EL tags are evaluated at compile time.

Writing directly to response stream in JSF

Writing to a response stream directly in JSF is not recommended but there are instances where we need this feature like report generation. If we need to export PDF or any binary files in a JSF application the code would be as below.

public void writeToResponse(String headerType, ByteArrayOutputStream bos) {

FacesContext faces = FacesContext.getCurrentInstance();

HttpServletResponse resp = (HttpServletResponse) faces.getExternalContext().getResponse();

try {

resp.setContentType(headerType);

resp.setHeader("Content-Disposition", "inline;filename=" + reportName + "." + reportType );

bos.writeTo(sos);

sos.flush();

faces.responseComplete();// without this response write error will come

} catch (IOException e) {

e.printStackTrace();

}

Handling Exceptions in JSF is quite easy as long as they are checked exceptions. If we have to handle unchecked exceptions we need to use one of the solutions below.

1. Implementing custom ActionListener
2. Spring AOP
3. Delegation FacesServlet

Implementing custom ActionListener

Custom ActionListener works only with JSF actions.

First we need to create ExceptionActionListener Class.

public class ExceptionActionListener extends ActionListenerImpl implements ActionListener{

public ExceptionActionListener () {

super ();

}

public void processAction (ActionEvent event) {

try{

super.processAction(event);

}catch (Exception ex) {

FacesContext facesContext = FacesContext.getCurrentInstance();

Application application = facesContext.getApplication();

NavigationHandler navigationHandler = application.getNavigationHandler();

navigationHandler.handleNavigation(facesContext,null,"exceptionNavigation");

FacesMessage facesMsg = new FacesMessage(FacesMessage.SEVERITY_ERROR,ex.getMessage(), ex.getMessage());

facesContext.addMessage(null, facesMsg);

facesContext.renderResponse();

}

}

}

Then we need to add this actionListener in faces-config.xml

com.rajiv.demojsf.helpers.ExceptionActionListener

That's it now any actions used in ManagedBeans which throws any unchecked exception message will be propogated to the View.

class TestBean{

public String divideAction()

{

int a = 10/0;

log.debug("a=" + a);

return null;

}

}

Above example will throw ArithmeticException which will be handled by ExceptionActionListener.

Implementing AspectJ Error Handler

To enable annotation support for Aspects we need to add below tag in application-context.xml

@Aspect

public class JSFExceptionHandlingAspect {

@Around("execution(* com.rajiv.demojsf.backing.*Bean.*Action(..))")

public Object handleAllExceptions(ProceedingJoinPoint pjp) throws Throwable {

Object retVal = null;

try {

retVal = pjp.proceed();

} catch (Exception e) {

FacesContext.getCurrentInstance().addMessage(

null,

new FacesMessage("General error (from advice) "

+ e.getMessage()));

}

return retVal;

}

}

@Around(“execution annotation means

In the above class exception is handled for any class name ending with Bean and method name with ending with Action.