3D Java Web Based API is Required

Project details: 1. System purpose: Enable the user to drop and drag and kind of object to particular panel, enable the administrator to pre-define places of objects in the panel, in addition to creating a list of the object that allowed being drop and dragged. 2. System Specs: 2.1. Technology used: 2.1.1. JSP, JSF or Servlet, the developer should develop the API up on one of these JAVA base. 2.1.2. Ajax and JQuery should be use. Follow point 3.3 Reloading. 2.1.3. VMC methodology should be the base system development way. 2.1.4. Database connection should be instance JNDI, using pool connection. 2.2. System delivered points: 2.2.1. Drop and drag API. 2.2.2. Methods to fill the list of object. 2.2.3. Methods to Pre-defined configuration for each object 2.2.4. Save the new panel with new Object. 2.2.5. 3 Dimensions view for all objects. 2.2.5.1. Before drop and drag. 2.2.5.2. After drop and drag without save. 2.2.5.3. After save. 2.2.6. Pre- defined places should be lighted when the drag object selected. 2.2.7. The panels should be divided to 3 sub panel: 2.2.7.1. Main Panel that will carry on all objects. 2.2.7.2. List panel for all objects. 2.2.7.3. 3D panel which will show the 2 more view for the object displayed in the main panel 2.3. Drop and Drag API: When the user navigate to the Drop and Drag panel the fallowing points should be taken: 1. The main panel will be loaded, and it could be image, which mean the user will be able to drop and drag any object from the list to this image. 2. The photo or panel will be viewed as 3 dimensions. 3. The user will be able to rotate the panel with 3D way. 4. The API should allow the user to drop an object from the list in specific area, this mean: When the user select any object from the list, there will be changing color in specific places on the panel, and the user can use only these places. 5. Any Object can’t be removed or moved to another place after save. 6. 3D view can be happened in each step the user do, in addition to the Panel will be modified from more than one user at the same time, but next access or refresh for the API user should see new panel that ALL USERS modify. 3. System flow: Here we will explain how the user will work with the API: When the user log to the system (no need for login procedure here, userid is enough to access), the API will have a trigger run connector which will do the following points: 1. Fill object list. 2. Load the XML file for each object positions (more than one position could be available). 3. Object photo path. 4. Panel ID. When the API has all the data above, it will start loading last modified panel for the user; Panel ID will be provided by the connector, but the modification happened on the panel will be loaded by the API itself, By other words: When the connector parse the panel ID for the drop and drag API, this API will read all modification from XML file, and build the new panel view up on these info. Meanwhile, any user makes any change the API should have a facility to update a database, by any query or ask another connector to do this task. The system will be like a middle ware between other APIs and connectors, so it should be fixable for this task.