Group items matching

in title, tags, annotations or url

Baseline Diagram Comparison Conduct a visual diagram comparison between your current diagram and a previous baseline .

Personal Information Window See how the Personal Information Window in Enterprise Architect can help you organize your daily tasks and workflow.

Working Sets As you perform work on your model, you open various windows, diagrams and views. Working Sets allow you to return to these same views in a later work session.

Business Rules A car rental system is used to illustrate how to generate executable business rules using Enterprise Architect.

Purchase the book at http://leanpub.com/entarch

50 Enterprise Architect Tricks can help you work with elements, diagrams, tagged values, connectors and many other advanced topics.

Java Archive (.jar)

Do not import private members checkbox excludes private members from libraries from being imported into the model

Both Acegi as well as SAF use AspectJ and Spring AOP for Policy Enforcement

JBoss Seam follows a different process when implementing Policy Decision functionality and sets access rules with the help of JBoss Rules [13] the JBoss rules engine

access decision to the domain objects in an application can be based on any number of complex rules

@Restrict annotations

07.2007

elements of the user interface are displayed to the user based on the user's privilege level

assign permissions to individual objects within the application’s business domain

Permissions

Permissions assigned to user for a given resource in the tree are inherited by other resources

Permissions are inherited

persist user, group and role information in database. JPA implementation is his dream

Security Module Drafts

Identity

interface Identity

login()

logout()

getUser()

Events LoggedInEvent LoginFailedEvent AlreadyLoggedInEvent PreLoggedOutEvent PostLoggedOutEvent PreAuthenticateEvent PostAuthenticateEvent

Object level permission

Grant or revoke permissions

Group management

User/Identity management

identity.hasRole

identity.hasPermission

User, Group and Role

hooks for common IDM or Security operations

Audit and logging for permission and IDM related changes

Event API.

Impersonalization

Impersonalization

control which elements of the user interface are displayed to the user based on their assigned permissions

ask for permission

more advanced security resolution mechanisms

Rules based engine

external services - XACML

JSR-303 (“Bean Validation”) ActionScript3 framework for form validation

validation framework is a specific adaptation of the JSR-303 (Bean Validation) specification to Flex: like its Java counterpart, it relies on validation annotations placed on bean properties and provides an engine API that lets you validate your forms without writing by hand a specific validator for each of your input fields

code generation tools provided by GraniteDS so that when you write your Java entity bean with validation annotations, they are automatically replicated in your ActionScript3 beans

problem with LCDS is mainly that it promotes a strict “client / server” architecture, with – roughly speaking – a heavy Flex client application connected to a server almost reduced to a database frontend

big majority of  these organizations use BlazeDS, a free and open-source subset of LCDS

need more advanced mechanisms than just Remoting start looking for open-source libraries to enable deeper integrations with the Java business layer, and GraniteDS is for sure the most popular project

“Flex Data Services” (now renamed to “Live Cycle Data Services”)

Flex Data Services seemed too “client-centric”

for GraniteDS users keeping their Java domain model and ActionScript3 domain model in sync via Gas3, the constraints are kept in sync

a couple of gotchas to be aware of

the constraint implementation is in the same class as the constraint declaration (not a problem in a dynamic language) @Pattern has a sightly different semantic because the regexp engine in Flex is a bit different. instead of the features provided by ConstraintValidatorContext, you can define a properties attribute in your constraints to make it belong to several sub-properties. not as flexible but good enough in many cases.

Known Causes:

First Steps:

dreaded errno 150:

The two key fields type and/or size is not an exact match

One of the key field that you are trying to reference does not have an index and/or is not a primary key

One or both of your tables is a MyISAM table

You have specified a cascade ON DELETE SET NULL, but the relevant key field is set to NOT NULL

Make sure that the Charset and Collate options are the same both at the table level as well as individual field level for the key columns

You have a default value (ie default=0) on your foreign key column

You have a syntax error in your ALTER statement or you have mistyped one of the field names in the relationship

The name of your foreign key exceeds the

max length of 64 chars