Group items tagged

other CDI Extensions projects.

container agnostic

different containers get activated via

CDI container integration via

Building Apache DeltaSpike

DeltaSpike-0.3

Release Notes

[DELTASPIKE-62] - Discuss security module

[DELTASPIKE-74] - unit and integration tests for @Secured

 [DELTASPIKE-75] - documentation for @Secured

[DELTASPIKE-78] - review and discuss Authentication API

 [DELTASPIKE-77] - review and discuss Identity API

[DELTASPIKE-79] - review and discuss Authorization API

[DELTASPIKE-81] - review and discuss Identity Management

[DELTASPIKE-82] - review and discuss external authentication

[DELTASPIKE-176] - unit and integration tests for @Transactional

[DELTASPIKE-177] - documentation for @Transactional

 [DELTASPIKE-179] - unit and integration tests for @TransactionScoped

[DELTASPIKE-175] - @Transactional for EntityTransaction

 [DELTASPIKE-178] - @TransactionScoped

 [DELTASPIKE-190] - Create ConfigurableDataSource

[DELTASPIKE-219] - @Transactional for JTA UserTransaction

[DELTASPIKE-230] - Fallback stragtegy for resource bundles and locales

  [DELTASPIKE-223] - Add convention for @MessageResource annotated types.

by the container in order to realize common use cases

An interface becomes a vehicle for encapsulation or abstraction,

“Interfaces are used to encode similarities which the classes of various types share, but do not necessarily constitute a class relationship. For instance, a human and a parrot can both whistle; however, it would not make sense to represent Humans and Parrots as subclasses of a Whistler class. Rather they would most likely be subclasses of an Animal class (likely with intermediate classes), but both would implement the Whistler interface.” [http://en.wikipedia.org/wiki/Java_interface]

Extensive use of interfaces derives from a

Premature Extensibility Is the Root of Some Evil

The number of artifacts will double and you will have to introduce a configuration facility

 logout() 

An implementation of this interface must be thread safe

If authorization fails, either because the user is not logged in or because it doesn't have required rights, it must throw an appropriate org.granite.messaging.service.security.SecurityServiceException.

Writing a Security Service

nothing to do with a true Flex destination

only one instance of this service is used in the entire web-app and will be called by concurrent threads

This method is called upon each and every service method call invocations (RemoteObject) or subscribe/publish actions (Consumer/Producer). When used with RemoteObjects, the authorize method is responsible for checking security, calling the service method, and returning the corresponding result.

default implementation of this method in AbstractSecurityService is to do nothing

security services are not exposed to outside calls

names

addresses

checking similar products!

Tutorials All Tutorials UML Tutorials UML 2.1 Tutorial UML Tutorial - Part 1 Intro UML Tutorial - Part 2 Intro The Business Process Model The Component Model The Dynamic Model The Logical Model The Physical Model The Use Case Model UML Database Modeling Enterprise Architect Tutorials Creating Strategic Models Diagram Filters BPEL: Step by Step Guide Resource Management Testing Management Traceability RTF Documentation Use Case Metrics Structured Use Case Scenarios

Video Demonstrations All Videos Getting Started Requirements Management Modeling & Productivity Tools Code Engineering and the Debug Workbench Version Control Integration (Eclipse, Visual Studio, TFS)

UML Tutorial - Structure UML Tutorial - Behavior The Business Process Model Deployment of EA MDA Overview Rich-Text (RTF) Reporting Version Control Integration Requirements Management

White Papers & E-Books

Roles Business Analyst Database Administrator Deployment & Rollout Developer Project Manager Software Architects Software Engineer Technology Developer Testers

Solutions

MDG Technologies MDG Technologies EJB Technology.xml Testing Technology.xml

UML Profiles & Patterns UML Patterns UML Patterns Create UML Patterns Import UML Patterns Use UML Patterns UML Profiles UML Profiles: Introduction UML Profile for SPEM XML Schema (XSD) Generation Web Modeling Profile Eriksson-Penker Business Extensions Open Distributed Processing (UML4ODP)

@RunWith(Arquillian.class)

JDBC Templates hardly give any abstraction on top of the database and you’re on your own for Object Relational Mapping. We strongly advise to use JPA wherever possible; it gives portability by abstracting most of the database specific SQL that you would need, and it does all the hard and painful work of object mapping

small part of your application

 @UsingDataSet("datasets/users.yml")

   @ShouldMatchDataSet("datasets/expected-users.yml")

@Inject

CDI managed beans. The @EJB annotation is removed and @Inject is used instead

Annotating the boundary (Cart) with the @Named annotation makes the Cart immediately visible for expression language (EL) expressions in JSP and JSF

@Named annotation takes the simple name of the annotated class, puts the first character in lowercase, and exposes it directly to the JSF pages (or JSP). The Cart bean can be accessed directly, without any backed or managed beans, by the JSF pages: <h:commandButton value="Check out!" action="#{cart.checkout}" />

If there is a need for abstraction, the class can be turned into an interface (or abstract class)

local implementation (with CDI events

@Inject Event<String> event;

event.fire("Order proceeded!");

remote implementation:

javax.enterprise.event.Event belongs to the CDI-implementation

class Event can be considered to be a lightweight alternative to the java.beans.PropertyChangeSupport class

@Inject Event<String> event;

event.fire("Order proceeded!");

event can be received by any managed bean and also by EJB beans

provide a method with a single @Observes annotated parameter

@Observes String event

there is no real event, just the payload:

The during attribute in the @Observes annotation allows you to select in which transactional phase the event gets delivered. The default setting is IN_PROGRESS, which causes an immediate event delivery regardless of the transaction outcome. The AFTER_SUCCESS configuration causes the delivery to occur only after successful transaction completion

Although CDI events work only inside a single process (in the default case, CDI is extensible), they are perfectly suitable for decoupling packages from modules

The method checkout() starts a transaction that gets "reused" by the OrderSystem and CustomerNotification session beans

ordering.placeOrder(); notifier.sendNotification();

EJB beans cannot be directly exposed to JSF or JSP without a little help from CDI

Think of JSR-299 as the core of Seam 3 - it's the basic programming model for your application components, and for the built-in components that make up the Seam framework

Seam 3 is implemented as a set of portable extensions, or modules

run in any environment which supports JSR-299 (including any Java EE 6 environment).

BPM integration, Seam Security, Drools integration, RESTeasy integration, PDF and email templates, Excel generation, etc

2.0.0.Final End of 2012 Full specification compliance

Weld 2

We have no intention of releasing Seam 4

eventual aim is to migrate all of Seam 3 and MyFaces CODI to DeltaSpike