Home >> All >> org >> jeteam >> bean

•	org.jeteam.bean.common.* (6)	•	org.jeteam.bean.config.* (27)	•	org.jeteam.bean.project.* (9)
•	org.jeteam.bean.security.* (18)	•	org.jeteam.bean.task.* (18)	•	org.jeteam.bean.user.* (10)

Package Samples:

• org.jeteam.bean.common
• org.jeteam.bean.config
• org.jeteam.bean.project
• org.jeteam.bean.security
• org.jeteam.bean.task
• org.jeteam.bean.user
• org.jeteam.bean.common.web
• org.jeteam.bean.config.web
• org.jeteam.bean.project.web
• org.jeteam.bean.security.web
• org.jeteam.bean.task.web
• org.jeteam.bean.user.web

Classes:

• PrivilegeBean: A privilege represents an authorization for a certain action in the system. It is represented by the permission attribute that indicates what specific action is authorized. There are two types of privileges: 1. First there are fine-grained privileges, these operate on the level of a specific method call, for example the permission User.createUser represents the authorization to create a new user in the system. 2. Secondly there are coarse-grained privileges, these are the ones that give authorization for a whole entity, for example the permission User represents the authorization to have full control ...
• DTOFactory: The DTOFactory is a utility class that centralizes the code that converts a data transfer objects (DTOs) into value objects. Value objects are representations of the domain, similar but very much simpler than the actual entity beans they are associated with. DTOs on the other hand are the client's view of the beans. For each bean we need an object that can transfer the bean attributes from the service to the entity, in the case of Container Manager Relations we do not include associated bean information in the DTO. Since a service may need to work with several entity beans it is therefore necessary ...
• DataFactory: The DataFactory is a utility class that centralizes the code that converts a client's data transfer objects (DTOs) into value objects from the domain. DTOs are the client-side view of the actual entity beans, please note they only hold the persisted state of the corresponding entity bean, not the relationships with other beans. Since a service may need to work with several entity beans it is therefore necessary to centralize the code to create these Value Objects, otherwise we risk having duplicate code spread over the services. This class is designed to do exactly that. As an extra there are method ...
• ProjectBean: A project is one of the central entities in the system, in fact everything is built around it. Users can be assigned to work on a project, this gives them the right to work on related tasks. However, it is only possible to assign users that have a valid role. Users that do not have that role are unable to work on the project. Users create tasks for a project and can update the current status of the project, depending on the individual statusses of the different tasks it is possible to derive a general completion percentage on the current project status. The created and deleted attributes indicate ...
• UserBean: A user represents an actor in the system, he logs on using a username and a password, the password itself is not stored, but the system uses a SHA-1 hash instead. This is to discourage potential hackers and make it more difficult to retrieve one's credentials. Furthermore the SHA-1 is represented as a hexadecimal String, not unlike the result calling BigInteger.toString(16) . The created and deleted attributes indicate the date of creation and (logical) removal respectively. By verifying whether the optional deleted attribute is null one can know if the user is still actively participating or not, ...
• TaskServiceBean: This bean is a service to Task CRUD operations. A task has only meaning in the context of a project. Please note that the task will always be associated to this project. There is no means of associating another project to this task after the task has been created. If the argument project does not exist or is invalid (deleted flag) an exception will be thrown. A task typically is assigned by a user to a user, a user is allowed to assign a task to himself. A task can have many notes attached to it giving some more extra information along the way. A task also has a status and priority field associated ...
• ProjectCRUDDispatchAction: This class extends the AbstractCRUDDispatchAction class to provide a means to gather similar functionality for CRUD operations on a project. All methods prefixed with "go" are used to pre-populate the form bean with data required by the accompanying CRUD method, for example goCreate(...) sets those values in the form bean that will be required for a user to effectively call create(...) , one should always dispatch to the methods prefixed with "go" prior to dispatching to the actual method.
• RoleBean: A role is a way of bundling priviliges into a logical unit. The name of the role should make it easy to understand what kind of priviliges are assigned to it. A developer for example may have the privilige to create a new task for a project he has been assigned to. A role without priviliges does not have any access to the system, it could be interesting however to setup some roles and assign priviliges to them at a later point in time.
• PriorityBean: The priority of a task denotes the urgency, this is a way of making it easier for users to choose which task to work on first. The level is an integer value formally indicating the level of priority, the higher the value, the higher the priority. Normally this value is hidden from the user and should only be seen by users that create or update the priority. All other users will only see the names but sorted in order of their priority level.
• ProjectServiceBean: This bean is a service to Project CRUD operations. Some other services are also provided, be extremely careful when removing roles from a project since this may impact the set of associated users too (read method documentation for more info). A project is the center point of the jeteam system as user will be assigned to work on it, and all the tasks will be under the context of a project.
• RoleServiceBean: This bean is a service to Role CRUD operations. A role identifies a profile in the system, this can be a developer, a manager, a reviewer, etc... Each role has a set of privileges associated with it which will allow an entity associated to that role to have access to the system. While privileges are a fine-grain view on the system authorization a role is coarse-grained.
• NoteServiceBean: This bean is a service to Note CRUD operations A note is a piece of information a user would like to associate with a task, the information can describe anything the user wants and is useful in the context of the task. The subject is like the subject of an email, it is a brief desciption of the content. The message is the information.
• StatusServiceBean: This bean is a service to Status CRUD operations. A status is an indicator telling you the status of a certain task or other item, this is not really like the progress, rather it will tell you if a project is suspended, closed, deleted, etc...
• PriorityException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• SettingException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• StatusException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• ProjectException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• PrivilegeException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• RoleException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• NoteException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• TaskException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• UserException: This exception represents a business exception, the arguments passed to the constructor should be the i18n context message key, its associated parameters, and a Throwable instance that cause this exception (if any).
• PrivilegeServiceBean: This bean is a service to Privilege CRUD operations. A privilege is a fine-grain method of authorizing access to a particular part of the system such as a call to a method.
• SettingServiceBean: This bean is a service to Setting CRUD operations. A setting is a personal setting/preference a user like to have. At this point it is not yet well defined.
• PriorityServiceBean: This bean is a service to Priority CRUD operations. A priority could be attached to almost any action in the system as it indicates the importance.

Home | Contact Us | Privacy Policy | Terms of Service