Fixed RESTful Services

To be Noticed:
1. Put jaxb.properties into the same package with model classes, since
this app is running in an ear then I just put the file stay with
Platform/Core/net.madz.core.entities/AbstractBaseEntity.java, if
someone wants to test within a JavaSE mode, keep to remember to place
another copy with your own model classes.

2. DO NOT define JAXB or Eclipselink extension Annotations on both
Field and Properties, because it will create Duplicate properties name
JAXBException, even if @XmlAccessType has been specified with Field or
Properties, and especially, this problem will occur in a Class
Hierarchy, where you may incorrectly  put @XmlAccessType(FIELD) on base
class and @XmlAccessType(PROPERTY), it will cause chaos.

3. @XmlID ONLY can be set on String field/property

4. @XmlIDREF ONLY can be set on a field/property whose type(class) has
@XmlID defined.

5, Once packaging with an EAR file with WAR file inside, DO put RESTful
Application class and Resoures EJB classes inside the same WAR file,
and DO NOT try to put part of it inside an EJB Module separately, since
those ejb classes will run inside EJB Lite container, and during
runtime, web container will use java:module namespace to locate those
resources EJBs. If you want to encapsulate business logics inside EJB
Module, you can inject  EJB from EJB Module into Web Module, then those
resources EJBs act as RESTful Facade EJBs