Group items tagged

Model Driven Generation (MDG) Technologies

MDG Technologies allow users to extend Enterprise Architect's modeling capabilities to specific domains and notations. MDG Technologies seamlessly plug into Enterprise Architect to provide additional toolboxes, UML profiles, patterns, templates and other modeling resources.

Free MDG Technology downloads for Enterprise Architect:

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

CDI + JSF + EJB + JTA + Bean Validation + JAX-RS + Arquillian: Kitchensink quickstart

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

Subversion administrators commonly ask if it is possible to configure, on the server side, a set of property definitions which all connecting clients will automatically consider when operating on working copies checked out from that server. Unfortunately, Subversion doesn't offer this feature. Administrators can use hook scripts to validate that the properties added to and modified on files and directories match the administrator's preferred policies, rejecting commits which are non-compliant in this fashion. (See the section called “Implementing Repository Hooks” for more about hook scripts.) But there's no way to automatically dictate those preferences to Subversion clients beforehand.

CDI, JPA2 and JSF2

Apache Shiro

JpaRealm

Java EJB 3.0 UML Profile

[UML Profile for Java and EJB. Version 1.0]

Java 1.3, EJB 1.1 and most likely UML 1.4, so it could be only of some interest

Seam 3·>/Cron Module·

Scheduling and asynchronous invocation support for managed beans

Documentation: Reference Guide

this externalizer may be used with any POJO bean.

Java EE 7 Roadmap

support for use in cloud environments

Web Sockets

think in structs. Try to as frictionless as possible export/generate the JPA-entities from the existing database

Implement a very thin facade / transaction boundary

@Stateless Bean (EJB 3)

Domain object instance security: In many applications it's desirable to define Access Control Lists (ACLs) for individual domain object instances. We provide a comprehensive ACL package with features including integer bit masking, permission inheritance (including blocking), an optimized JDBC-backed ACL repository, caching and a pluggable, interface-driven design.

OpenID Support: the web's emerging single sign-on standard (supported by Google, IBM, Sun, Yahoo and others) is also supported in Spring Security

Easy integration with existing databases: Our implementations have been designed to make it easy to use your existing authentication schema and data (without modification). Of course, you can also provide your own Data Access Object if you wish. Password encoding: Of course, passwords in your authentication repository need not be in plain text. We support both SHA and MD5 encoding, and also pluggable "salt" providers to maximise password security.

Spring Security Dependencies

This appendix provides a reference of the modules in Spring Security and the additional dependencies that they require in order to function in a running application

C.1 spring-security-coreThe core module must be included in any project using Spring Security.

In order to initialize GDS/Tide for CDI and Hibernate, you must add granite.jar, granite-hibernate.jar and granite-cdi.jar to your WEB-INF/lib

The easiest way to add GraniteDS support to a CDI project in a Servlet 3 compliant container (currently only GlassFish v3) is by adding a configuration class in your project. This class will be scanned by the servlet 3 container and GraniteDS will use the annotation parameters to determine the application configuration

GraniteConfig.java import org.granite.config.servlet3.FlexFilter; import org.granite.gravity.config.AbstractMessagingDestination; import org.granite.gravity.config.servlet3.MessagingDestination; import org.granite.tide.cdi.CDIServiceFactory; import org.granite.tide.cdi.Identity; @FlexFilter( tide=true, type="cdi", factoryClass=CDIServiceFactory.class, tideInterfaces={Identity.class} ) public class GraniteConfig { }

The configuration of a GraniteDS project will generally involve the following steps : Add the GraniteDS jars to the WEB-INF/lib folder of the WAR file or the lib folder of the EAR file Add the GraniteDS listener, servlets and filters in the standard WEB-INF/web.xml configuration file Define the internal configuration of GraniteDS in the WEB-INF/granite/granite-config.xml file Define the application configuration of GraniteDS (remoting destinations, messaging topics...) in the WEB-INF/flex/services-config.xml

You will always need granite.jar

jar for your JPA provider (granite-hibernate.jar for Hibernate)

@Secured @NamedResource("contact")

Interceptors will be ignored by CDI container unless it is listed in beans.xml

In fact people still love those books without realizing that the world has changed dramatically ever since

The reality check here is to wonder whether the rhetorics set forth by Rod Johnson in his 2003/2004 books are still actual today

So if you still care about those books, the best way to show your appreciation is probably to use them as your monitor stand

Getting Started Developing Applications Guide

Installing and starting JBoss AS on Windows

Starting JBoss AS from Eclipse with JBoss Tools