JPA 2 Enhancements Every Java Developer Should Know
Group items matching
in title, tags, annotations or url
7More
The JPA 2 Enhancements Every Java Developer Should Know - Developer.com - 0 views
-
-
JPA 2 also introduced a second layer of cache, which is shared across various persistence contexts and can be accessed using the EntityManagerFactory
-
Cache cache = emf.getCache();
- ...4 more annotations...
-
Enhancements in EntityManagerFactory Interface
-
Enhancements in EntityManager Interface
-
detach
-
getEntityManagerFactory
2More
Auditing Entities With JPA Events | Andy Gibson - 0 views
-
Auditing Entities With JPA Events
-
An alternative is if you are using a generic DAO class to handle entity persistence is to put the enhanced populateTimestamp method on there and call it prior to inserting or updating the entity in the DAO
6More
Migrating from Spring to Java EE 6 - Part 4 | How to JBoss - 0 views
-
discuss the rationale for migrating your applications from Spring to Java EE 6 and show you real examples of upgrading the web UI, replacing the data access layer, migrating AOP to CDI interceptors, migrating JMX, how to deal with JDBC templates, and as an added bonus will demonstrate how to perform integration tests of you Java EE 6 application using Arquillian
-
EntityManagerClinicTest
-
There is also an interesting Arquillian Persistence extension that integrates DBUnit in Arquillian where you can define your test data externally
- ...3 more annotations...
-
@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
11More
Drivers and Downloads | Dell [United States] - 0 views
-
Win7 64 Graphics driver update 15.17.16.2302 for Cantiga M09 (except AMG) and E3 KrugMV 14/15
-
Windows 7 64-bit
-
Latitude E6500
- ...8 more annotations...
-
Win7 64-bit driver 15.17.16 2302
-
E6500
-
- Improved DisplayPort monitor behavior (including non-Dell monitors)
-
- Fixed issue where system LCD defaults to Max brightness on Standby/resume, Hibernate/resume or reboot
-
- Improved DisplayPort monitor behavior (including non-Dell monitors)
-
- Improved mode persistence after
-
hot undock/redock
-
with a DVI monitor attaced
1More
DomainPermission (Apache Shiro 1.2.1 API) - 0 views
-
used as a base class for JPA/Hibernate persisted permissions that wish to store the parts of the permission string in separate columns (e.g. 'domain', 'actions' and 'targets' columns)
34More
UML Class Diagrams - structure diagrams which show architecture of the designed system ... - 0 views
-
«Boundary»
-
Boundary is a stereotyped class or object that represents some system boundary
-
«Control»
- ...31 more annotations...
-
Control is a stereotyped class or object that is used to model flow of control or some coordination in behavior
-
usually describe some "business logic"
-
«Entity»
-
Entity is a stereotyped class or object that represents some information or data, usually but not necessarily persistent.
-
Features of a class are
-
attributes
-
operations
-
Static features are underlined
-
«Boundary»
-
«Boundary»
-
«Control»
-
«Entity»
-
«Control»
-
Interface
-
An interface is a classifier that declares of a set of coherent public features and obligations
-
specifies a contract.
-
Data Type
-
A data type is a classifier - similar to a class - whose instances are
-
identified only by their value
-
typical use of data types would be to represent value types
-
«dataType»
-
Enumeration
-
An enumeration is a data type whose values are enumerated in the model as user-defined enumeration literals.
-
«enumeration».
-
Multiplicity
-
Multiplicity allows to specify cardinality (allowed number of instances) of described element
-
Visibility
-
UML has the following types of visibility: public package protected private
-
Package visibility is represented by '~' literal.
-
Protected visibility is represented by '#' literal.
-
Private visibility is represented by '-' literal.
Pro JPA 2: Mastering the Java™ Persistence API: InformIT: Safari Books Online - 0 views
2More
Lean service architectures with Java EE 6 - JavaWorld - 0 views
-
key ingredients of a service-oriented component: Facade: Provides simplified, centralized access to the component and decouples the client from the concrete services. It is the network and transaction boundary. Service: The actual implementation of business logic. Domain structure: This is a structure rather than an object. It implements the component's persistence and exposes all of its state to the services, without encapsulation.
-
This convention not only standardizes the structure and improves maintainability, but also allows automatic dependency validation with frameworks like JDepend, Checkstyle, Dependometer, SonarJ, or XRadar. You can even perform the validation at build time. If you do, the continuous build would break on violation of defined dependencies. The rules are clearly defined with strict layering: a facade may access a service, and the service a domain object, but not vice versa
9More
Java Persistence/Auditing and Security - Wikibooks, open books for an open world - 0 views
-
Use a common database user id, and manage auditing and security in the application
-
managed in the application by having an application user, and a single shared database user
-
adding a AUDIT_USER and AUDIT_TIMESTAMP column to all of the audited tables and auditUser and auditTimestamp field to all of the audited objects
- ...5 more annotations...
-
When the application inserts or updates an object, it will set these fields and they will be stored in the database. JPA events could also be used to record the audit information, or to write to a separate audit table.
-
Example AuditedObject class
-
@MappedSuperclass public Class AuditedObject {
-
@Column("AUDIT_USER"); protected String auditUser; @Column("AUDIT_TIMESTAMP"); protected Calendar auditTimestamp;
-
@PrePersist @PreUpdate public void updateAuditInfo() { setAuditUser((String)AuditedObject.currentUser.get()); setAuditTimestamp(Calendar.getInstance()); }
-
Use a common database user id, and manage auditing and security in the application
6More
Java Persistence/Runtime - Wikibooks, open books for an open world - 0 views
-
In JEE the EntityManager or EntityManagerFactory can
-
injected into a SessionBean
-
A managed EntityManager should never be closed, and integrates with JTA transactions
- ...3 more annotations...
-
Example of injecting an EntityManager and EntityManagerFactory in a SessionBean
-
@Stateless
-
@PersistenceContext(unitName="acme") private EntityManager entityManager;
7More
How To Deal With Interfaces In Java EE 6 (or no more Impl) : Adam Bien's Weblog - 0 views
-
How To Deal With Interfaces In Java EE 6 (or no more Impl)
-
In Java EE 6 interfaces became absolutely optional. Neither in EJB 3.1, nor CDI / JSR-330 you need interfaces. You can inject classes directly. They will be still proxied, so all aspects like persistence, transactions, interceptors, decorators are still available. So you are no more forced to implement interfaces by the container
-
used for: Strategy Pattern: there are already several implementations of an algorithm or concept Layering: there is a clear need to hide e.g. an ugly implementation of a legacy framework API (not very common): you have to expose a API, which gets implemented by SPI (e.g. JDBC)
- ...4 more annotations...
-
If you introduce interfaces intentionally - and not as a general rule, you will considerably reduce the number of files. Your code becomes easier to understand and so maintain
-
Even for decoupling purposes, interfaces are no more needed
-
"Contract First", "Coding To Interfaces" or "Decoupling"
-
is not a reason to introduce an interface for everything
41More
Security Module Drafts - Apache DeltaSpike - Apache Software Foundation - 0 views
-
Authorization
-
Impersonalization
-
-
authenticates “as a user” or access application imitating his identity - without knowing his password
- ...36 more annotations...
-
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
-
Permissions model
-
Identity Management (IDM)
-
User, Group and Role
-
Events
-
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
-
without need to obtain object from DB
-
String resourceId
-
structure of resources
-
more advanced security resolution mechanisms
-
Rules based engine
-
external services - XACML
8More
Comparison - 0 views
-
TomEE is a superset of OpenEJB
-
Tomcat
-
TomEE
- ...5 more annotations...
-
TomEE+
-
OpenEJB
-
Java API for XML Web Services (JAX-WS) Java API for RESTful Web Services (JAX-RS) Java EE Connector Architecture Java Messaging Service (JMS)
-
Java Servlets Java ServerPages (JSP) Java ServerFaces (JSF) Java Transaction API (JTA)
-
Java Persistence API (JPA) Java Contexts and Dependency Injection (CDI) Java Authentication and Authorization Service (JAAS) Java Authorization Contract for Containers (JACC) JavaMail API Bean Validation Enterprise JavaBeans
37More
Selling Weld and EE6 | Weld | JBoss Community - 0 views
-
regarding the issue of selling Weld and EE6 to developers/shops....
-
How bout a JdbcTemplate Spring equivalent in the case of projects using legacy db schemas
-
portable extension to Weld
- ...32 more annotations...
-
William Drai
-
Honestly I don't see any value in switching to CDI if it is
-
to reproduce the same awful patterns
-
please not this Dao/Template mess
-
Gavin King
-
Their template pattern is a solution in search of a problem
-
-
to reproduce the same awful patterns
-
please not this Dao/Template mess
-
Because, of course, there are no other well-known patterns for dealing with boiler-plate cleanup code and connection leaks.
-
This is exactly the kind of
-
brain-damage that Spring does to people!
-
-
It gives people a
-
half-assed solution
-
and somehow shuts down their brains so they
-
stop asking themselves how this solution could be improved upon
-
It's a very impressive magic trick, and I wish I knew how to do it myself. But then, I'm just not like that. I'm always trying to poke holes in things - whether they were Invented Here or Not.
-
but that might be too high-level for your taste. Their are other, less-abstract options.
-
exception handling, this is one area where Spring does a good job: "The Spring Framework's handling of SQLException is one of its most useful features in terms of enabling easier JDBC development and maintenance. The Spring Framework provides JDBC support that abstracts SQLException and provides a DAO-friendly, unchecked exception hierarchy."
-
Utter nonsense and dishonest false advertising
-
Automatic connection closing (and other boiler-plate code) is obviously a hard requirement to be handled by the fwk.
-
Pffffff. It's a trivial requirement which I can solve in my framework with two lines of code in a @Disposes method. Did you see any connection handling in the code above?
-
I mean, seriously guys. The Spring stuff is trivial and not even very elegant. I guess it's easier for me to see that, since I spent half my career thinking about data access and designing data access APIs. But even so...
-
I don't understand. You hate the ability to write typesafw SQL that much?
-
Gavin King
-
Methods with long argument lists are a code smell.
-
It's something Spring copied from Hibernate 1.x, back in the days before varargs
-
It's something we removed in Hibernate2 and JPA.
-
there are a bunch of people
-
who don't want to use JPA.
-
They don't understand, or see the value of, using managed objects to represent their persistent data.
-
Um. Why? Why would that be a bad thing? I imagine that any app with 1000 queries has tens of thousands of classes already. What's the problem? Why is defining a class worse than writing a method?
-
Are you working from some totally bizarre metric where you measure code quality by number of classes?