RADK Project

DataBase Schema limitations

• Composite primary keys are not supported by Radk at the moment.

• We don't recommend using autoincrement primary keys. Although Radk will work for autoincrement primary keys, the end user

will run into confusion while doing CRUD operations with the autoincrement primary keys.

• The column names of a table should not have any alien characters like white spaces, $ or any other special charaters.

For example, if student name is a column in the student table, the valid names for Radk will be,
StudentName,
studentname,
student_name,
Student_Name.

Some of the invalid representions are shown below,

student name,
student$name,
student*name.

EJB deployment Issues

GlassFish does not allow the session bean, which has the same name as the one already existing in the EJB container to be deployed again. It will throw an error if you try to do this. Assume a session bean with name "StudentFacade" of the EJB project1 was deployed in the GlassFish EJB container. Now, if you try to deploy a session bean with the name "StudentFacade" of the EJB project 2, then GlassFish will throw deployment error since a session bean with the name StudentFacade has already been deployed previosuly. We are not sure why this happens or if it is a GlassFishV2 bug. The only way to overcome this problem is to undeploy the previous project(project1) and deploy the new project(project2)

Entities generator limitations

------

• Many to Many annotations, which are involved with the join tables(tables that do not have primary key) are not supported.

• No entities/ session beans will be generated for the join tables. This behaviour is same as the entities generation wizard of NetBeans IDE

Web Services and Web pages only support one primary key per table for GET, DELETE and PUT methods

RADK Project