align the SSD and define an active partition on it
Diskpart List disk Select disk n (where n is the number that was given for your SSD in List disk) Clean Create partition primary align=1024 Format fs=ntfs quick Active (assuming you want to install an OS) Exit
Using @DataSourceDefinition to configure a DataSource
This annotation requires that a data source implementation class (generally from a JDBC driver JAR) be present on the class path (either by including it in your application, or deploying it as a top-level JAR and referring to it via MANIFEST.MF's Class-Path attribute) and be named explicitly.
this annotation bypasses the management layer and as such it is recommended only for development and testing purposes
Defining a Managed DataSource
Installing a JDBC driver as a deployment
Installing the JDBC Driver
deployment or as a core module
managed by the application server (and thus take advantage of the management and connection pooling facilities it provides), you must perform two tasks. First, you must make the JDBC driver available to the application server; then you can configure the data source itself. Once you have performed these tasks you can use the data source via standard JNDI injection.
recommended way to install a JDBC driver into the application server is to simply deploy it as a regular JAR deployment. The reason for this is that when you run your application server in domain mode, deployments are automatically propagated to all servers to which the deployment applies; thus distribution of the driver JAR is one less thing for administrators to worry about.
Note on MySQL driver and JDBC Type 4 compliance: while the MySQL driver (at least up to 5.1.18) is designed to be a Type 4 driver, its jdbcCompliant() method always return false. The reason is that the driver does not pass SQL 92 full compliance tests, says MySQL. Thus, you will need to install the MySQL JDBC driver as a module (see below).
define your module with a module.xml file, and the actual jar file that contains your database driver
content of the module.xml file
Under the root directory of the application server, is a directory called modules
module name, which in this example is com.mysql
where the implementation is, which is the resource-root tag with the path element
define any dependencies you might have. In this case, as the case with all JDBC data sources, we would be dependent on the Java JDBC API's, which in this case in defined in another module called javax.api, which you can find under modules/javax/api/main as you would expect.
Baseline Diagram Compare feature is a quick and easy way to visually compare a current diagram with an earlier version
Access Any of the following:
•Project Browser diagram context menu | Compare to Baseline | <select baseline>: Show Differences•Project Browser package context menu | Package Control | Manage Baselines: Show Differences | Selected diagram context menu | Open Visual Diagram Diff •Diagram context menu | Compare to Baseline: Show Differences, or•Select Package | Project | Baselines: Show Differences | Selected diagram context menu | Open Visual Diagram Diff
Fully polymorphic behavior is available, but there is no annotation support for any mappings.
Hibernate supports fully polymorphic behavior. It provides extra support for any association mappings to an inheritance hierarchy mapped with implicit polymorphism.
if dependency relationships were drawn between every class and the types of it's attributes, the class diagram becomes cluttered very quickly
this dependency is obvious if the type is indicated for each attribute
if a subclass sets an attribute to null, implements a method returning null or throwing a NotImplementedException, it really isn't a subclass, or the superclass needs to be decomposed
7.
Aggregation and Composition Guidelines
object is made up of other objects
aggregation
“is part of” relationships
whole-part relationship between two
objects
Composition
stronger
form of aggregation where the whole and parts have
coincident lifetimes, and it
is very common for the whole to manage the lifecycle of its parts
Apply the Sentence Rule for Aggregation
Depict the Whole to the Left of the Part
Don’t Worry About Getting the Diamonds Right
associations, aggregation, composition, dependencies,
inheritance, and realizations
line on a UML
class diagram
defines a cohesive set of behaviors
Indicate Visibility Only On Design Models
Design Class Diagrams Should Reflect Language Naming Conventions
Using Shiro for Authorization via CDI Interceptors then Easily Test with Arquillian
Did you know Apache Shiro is an easy-to-use security
@Secured @NamedResource("contact")
Interceptors will be ignored by CDI container unless it is listed in beans.xml
Tells the security interceptor to check the permission using "contact" as the resource name, not "contactmanager" inflected from the class name ContactManager