title: JAXB unmarshalling Custom entities without annotation
body: <p>We have an xml file which we need to unmarshall(convert into a Java Object). Now the Java object is of third party and I cannot annotate it for unmarshalling. Any idea as to how I can Unmarshal without annotation. Please find my code snippet below</p>
  
  <pre><code>JAXBContext context;
          try {
              context = JAXBContext.newInstance(Abc.class);
              Unmarshaller unMarshaller = context.createUnmarshaller();
              Abc abc= (Abc) unMarshaller.unmarshal(new FileInputStream("C:\\Documents and Settings\\sandeep.nair\\Desktop\\abc.xml"));
          } catch (JAXBException e) {
              // TODO Auto-generated catch block
              e.printStackTrace();
          }catch (Exception e){
  
          }
  </code></pre>
  
  <p>I am getting the following exception. One for No argument Constructor(I know I can solve this by adding annotation for Adapter but I want to know or see a sample snippet for handling it without annotation)</p>
  
  <p>Similarly I am getting another message as to Interfaces cannot be handle by JAXB.</p>
  
  <p>com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 5 counts of IllegalAnnotationExceptions
  java.sql.Timestamp does not have a no-arg default constructor.
      this problem is related to the following location:
          at java.sql.Timestamp
          at public java.sql.Timestamp com.test.Abc.getSomeTimestamp()
          at com.riteaid.entities.customer.Customer
  com.test.Def does not have a no-arg default constructor.
      this problem is related to the following location:
          at com.test.Def...</p>
  
  <p>java.sql.Date does not have a no-arg default constructor.
      this problem is related to the following location:
          at java.sql.Date
          ...
  com.test.Ghi is an interface, and JAXB can't handle interfaces.
      this problem is related to the following location:
          ...
  com.test.Ghi does not have a no-arg default constructor.
      this problem is related to the following location:
          ..</p>