Group items matching

in title, tags, annotations or url

explained the origin of GraniteDS and the differences with LiveCycle Data Services

ActionScript3 reflection API

GraniteDS 2.2

Overview of Interceptors

allow developers to invoke interceptor methods in conjunction with method invocations or lifecycle events on an associated target class

logging, auditing, or profiling

invariants

customer's last name must not be null

must be between 3 and 80 characters long

Client-Side Validation API (JSR 303)

GraniteDS introduces an ActionsScript3 implementation of the Bean Validation specification and provides code generation tools integration so that your Java constraint annotations are reproduced in your AS3 beans

Data Management

Tide maintains a client-side cache of entity instances and ensures that every instance is unique in the Flex client context

Tide provides an integration between the Flex/LCDS concept of managed entities and the server persistence context (JPA or Hibernate).

AS3 Code Generator

GraniteDS comes with an ActionScript3 code generator that writes AS3 beans for all Java beans

ActionScript 3 generator is able to write AS3 typed client proxies for exposed remote services

Data Management

Tide provides an integration between the Flex/LCDS concept of managed entities and the server persistence context (JPA or Hibernate)

Tide maintains a client-side cache of entity instances and ensures that every instance is unique in the Flex client context

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

Why is the constructor invoked twice when a normal scoped bean is created?

What you see is the instantiation of two objects: one is the actual bean instance, the other one is the proxy. Both likely invoke the default constructor.

That's why it's generally considered a bad idea to do initialization in class construction code. Instead, when using managed beans (objects managed by the EE container) to perform initialisation in a @PostConstruct or @Inject annotated method.

Shiro SHIRO-337 adding support for CDI

Transactional Interceptors

add an annotation

standardized values

CDI Extensions Project

best mature features of

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

queries are also known as native queries

SQL Queries

reasons why a developer using JP QL might want to integrate SQL queries into their application

How it works

write a basic test case and annotate it with declarative behavior that says, "@RunWith Arquillian."

tells Arquillian to take over execution of the test when it's launched