SoftwareEngineering

Subscribing to Email Notifications of Updates to Confluence Content

setNamingStrategy(ImprovedNamingStrategy.INSTANCE)

3.6. Implementing a NamingStrategy

trackers see/get nothing, not even your IP address

but allows widgets on a per-company or per-website basis to keep a non-broken web experience

March 29th, 2013

command-line syntax and programming APIs remain entirely upward compatible with ImageMagick 5.5.2

maintains a stable source repository with complete version history so that changes are controlled

maintains a detailed ChangeLog

maintains a stable release branch

more time has been spent optimizing and debugging its code

dramatically fewer dependencies on external libraries

much smaller than ImageMagick

installation footprint is 3-5X smaller than ImageMagick

usually faster than ImageMagick

more efficient at dealing with large images

GraphicsMagick has been significantly updated to use multiple CPU cores to speed up the image processing

non-parallelizable code paths often dominating the time

multi-threaded

context

unique context that exists during the whole lifetime of the Flex application. It can be compared to to the server-side session

two main kinds of contexts:

stateful objects that can be of any ActionScript 3 class with a default constructor

temporary contexts that can be created and destroyed at any time during the lifetime of the application

conversation context always has an identifier

usually tied to a particular use case in the application

three available scopes:

@MappedSuperclass

Important things on ID/UID

entity lives in three layers:

Flex client

JPA persistence context

database

id is defined and is maintained in the three layers during the different serialization/persistence operations

most common solution is to

which is created by the client and persisted along with the entity

recommended approach to avoid any kind of subtle problems is to have a real uid property which will be persisted in the database but is not a primary key for efficiency concerns

You can now ask Tide to

Flex with the following API :

EntityGraphUnintializer

Person object will be uninitialized

uperson contains

to correctly merge your changes in the server persistence context

Tide uses the

to determine which parts of the graph need to be sent

Calling the EntityGraphUninitializer manually is a bit tedious and ugly, so there is a cleaner possibility when you are using generated typesafe service proxies

in the Flex application, register the UninitializeArgumentPreprocessor component in Tide as follows :

[UninitializeArgumentPreprocessor]

all calls to PersonService.save() will

of the person argument.

15.4. Dirty Checking and Conflict Handling

simplify the handling of data between Flex and Java EE

Chapter 15. Data Management

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

 uid().hashCode();

Tide currently only supports Integer or Long version fields, not timestamps and that the field must be nullable

in a multi-tier environment (@Version annotation)

highly recommended to use

highly recommended to add a

in general this identifier will be

@Column(name="ENTITY_UID", unique=true, nullable=false, updatable=false, length=36)     private String uid;

uid().equals(((AbstractEntity)o).uid())

consistent identifier through all application layers

@PrePersist

15.3. Reverse Lazy Loading

15.4. Dirty Checking and Conflict Handling

15.4. Dirty Checking and Conflict Handling

15.4. Dirty Checking and Conflict Handling

Dirty Checking and Conflict Handling

entity instance can be in two states :

Stable

Dirty

property meta_dirty is

could be used

to enable/disable a Save button

correct way of knowing if any object has been changed in the context, is to use the property meta_dirty of the Tide context

tideContext.meta_dirty

reliable when using optimistic locking

check that its @Version field has been incremented