Group items tagged

Entity–attribute–value model

Entity–attribute–value model (EAV) is a data model to describe entities where the number of attributes (properties, parameters) that can be used to describe them is potentially vast, but the number that will actually apply to a given entity is relatively modest

also known as object–attribute–value model, vertical database model and open schema

powerful way of formalizing the recurring bean roles that often arise as a result of application architectural patterns

Project permissions can be granted to:

Individual usersGroupsProject rolesIssue roles such as 'Reporter', 'Project Lead' and 'Current Assignee''Anyone' (e.g. to allow anonymous access)A (multi-)user picker custom field.A (multi-)group picker custom field. This can either be an actual group picker custom field, or a (multi-)select-list whose values are group names.

one of the most important value propositions for frameworks like Spring has been the ability to easily extend the framework or integrate third-party solutions

SPI allows you to register your own beans, custom scopes, stereotypes, interceptors and decorators with CDI even if is it not included in the automatic scanning process (such as perhaps registering Spring beans as CDI beans), programmatically looking up CDI beans and injecting them into your own objects (such as injecting CDI beans into Spring beans) and adding/overriding annotation-metadata from other sources (such as from a database or property file)

SPI can be segmented into three parts. Interfaces like Bean, Interceptor and Decorator model container meta-data (there are a few other meta-data interfaces such as ObserverMethod, Producer, InjectionTarget, InjectionPoint, AnnotatedType, AnnotatedMethod, etc). Each meta-data object encapsulates everything that the CDI container needs to know about the meta-data type

differences between CDI beans and EJBs is that EJBs are : Transactional Remote or local Able to passivate stateful beans freeing up resources Able to make use of timers Can be asynchronous

Stateless EJBs can be thought of as thread safe single-use beans that don’t maintain any state between two web requests

Stateful EJBs do hold state and can be created and sit around for as long as they are needed until they are disposed of

key ingredients of a service-oriented component: Facade: Provides simplified, centralized access to the component and decouples the client from the concrete services. It is the network and transaction boundary. Service: The actual implementation of business logic. Domain structure: This is a structure rather than an object. It implements the component's persistence and exposes all of its state to the services, without encapsulation.

This convention not only standardizes the structure and improves maintainability, but also allows automatic dependency validation with frameworks like JDepend, Checkstyle,  Dependometer, SonarJ, or XRadar. You can even perform the validation at build time. If you do, the continuous build would break on violation of defined dependencies. The rules are clearly defined with strict layering: a facade may access a service, and the service a domain object, but not vice versa

Test Java EE applications effectively

Needle is a lightweight framework for testing Java EE components

SQE attempts to provide first-class NetBeans IDE integration for different software quality tools.

Currently supported tools: FindBugs PMD CheckStyle Dependency Finder

Tide client framework

framework features notably

Dependency Injection

Lazy Loading with Flex, BlazeDS and Hibernate

By using dpHibernate and lazy loading, none of this extra work is required

proxies are sent initially for collections and complex objects, and fetched on-demand when requested by the client