Group items tagged

Setting the SESSION variable affects only the current client. Any client can change its own session sql_mode value at any time

STRICT_TRANS_TABLES

Strict mode does not affect whether foreign key constraints are checked

can be handled on the

by defining a

possible to define common handlers for particular fault codes on the client-side, and exception converters on the server-side, to convert server exceptions to common fault codes

define an

class

Converter

ExceptionConverter

t.getMessage(), detail, t

ENTITY_NOT_FOUND

This class will

all EntityNotFound exceptions on the server-side, and convert it to a proper ENTITY_NOT_FOUND fault event.

exception converter has to be

scan="true" in granite-config.xml

in the jar containing the exception converter class

granite-config.xml

<exception-converters> <exception-converter type="com.package.SomeExceptionConverter"/> </exception-converters>

Handler

register it as an exception handler for the

in a static initializer block to be sure it is

ExceptionConverter

5. Exception Handling

5. Exception Handling

file listed under the filename parameter can be deployed to the server using the deploy goal

deploy

redeploy

undeploy

<phase>install</phase>

<goal>deploy</goal>

Deploying other artifacts

possible to deploy other artifacts that are not related to your deployment, e.g. database drivers:

<phase>install</phase>

<goal>deploy-artifact</goal>

<configuration> <groupId>postgresql</groupId> <artifactId>postgresql</artifactId> <name>postgresql.jar</name> </configuration>

artifact must be already listed as a dependency in the projects pom.xml.

Deploying your application in domain mode.

add the domain tag as well as specify at least one server group.

<domain> <server-groups> <server-group>main-server-group</server-group> </server-groups> </domain>

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).

Installing a JDBC driver as a module

<module xmlns="urn:jboss:module:1.0" name="com.mysql">  <resources>    <resource-root path="mysql-connector-java-5.1.15.jar"/>  </resources>  <dependencies>    <module name="javax.api"/>  </dependencies></module>

jboss-7.0.0.<release>/modules/com/mysql/main

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.

Defining the DataSource itself

   <datasource jndi-name="java:jboss/datasources/MySqlDS" pool-name="MySqlDS">      <connection-url>jdbc:mysql://localhost:3306/EJB3</connection-url>         <driver>com.mysql</driver>

    <drivers>      <driver name="com.mysql" module="com.mysql">        <xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>      </driver>    </drivers>

jboss-7.0.0.<release>/domain/configuration/domain.xml or jboss-7.0.0.<release>/standalone/configuration/standalone.xml

application stops working when you move it to another server

project in Flex Builder

check “use remote object access service”

This adds a compiler argument pointing to the location of your

When you then

your application, the required

of services-config.xml are

read at

not at runtime

{server.name}

{server.port}

{context.root}

{server.name} and {server.port} are replaced at

{context.root} is still substituted at

Flex SDK provides an API that allows you to configure your channels at runtime

number of ways you can pass values to a SWF at runtime

read a configuration file using HTTPService at application startup

Subversion Tagging Plugin — This plugin automatically performs subversion tagging (technically speaking svn copy) on successful build.

ViewVC Plugin — This plugin integrates ViewVC browser interface for CVS and Subversion with Hudson.

Source code management

Build Pipeline Plugin — This plugin creates a pipeline of Hudson\Jenkins jobs and gives a view so that you can visualise it.

Build tools

JBoss Management Plugin — This plugin allows to manage a JBoss Application Server during build procedure

Maven 2 Project Plugin — Jenkin's Maven 2 project type

Phing Plugin — This plugin allows you to use Phing to build PHP projects.

Post build task — This plugin allows the user to execute a shell/batch task depending on the build log output. Java regular expression are allowed.

Promoted Builds Plugin — This plugin allows you to distinguish good builds from bad builds by introducing the notion of 'promotion'.

Publish Over SSH Plugin — Publish files and/or execute commands over SSH (SCP using SFTP)

Selenium AES Plugin — This plugin is for continuous regression test by Selenium Auto Exec Server (AES).

Vagrant Plugin — This plugin allows booting of Vagrant virtual machines, provisioning them and also executing scripts inside of them

Unicorn Validation Plugin — This plugin uses W3C's Unified Validator, which helps improve the quality of Web pages by performing a variety of checks.

Build wrappers

Android Emulator Plugin — Lets you automatically generate, launch and interact with an Android emulator during a build, with the emulator logs being captured as artifacts.

Artifactory Plugin — This plugin allows deploying Maven 2, Maven 3, Ivy and Gradle artifacts and build info to the Artifactory artifacts manager.

AWS Cloudformation Plugin — A plugin that allows for the creation of cloud formation stacks before running the build and the deletion of them after the build is completed.

Build Keeper Plugin — Select a policy for automatically marking builds as "keep forever" to enable long term analysis trending when discarding old builds - or use to protect logs and artifacts from certain builds

Build Name Setter Plugin — This plugin sets the display name of a build to something other than #1, #2, #3, ...

SSH plugin — You can use the SSH Plugin to run shell commands on a remote machine via ssh.

SeleniumRC Plugin — This plugin allows you to create Selenium server instance for each project build.

Vagrant Plugin — This plugin allows booting of Vagrant virtual machines, provisioning them and also executing scripts inside of them

Timestamper — Adds timestamps to the Console Output.

VirtualBox Plugin — This plugin integrates Jenkins with VirtualBox (version 3, 4.0 and 4.1) virtual machine.

Version Number Plugin — This plugin creates a new version number and stores it in the environment variable whose name you specify in the configuration.

VMware plugin — This plugin allows you to start a VMware Virtual Machine before a build and stop it again after the build completes.

AWS Cloudformation Plugin — A plugin that allows for the creation of cloud formation stacks before running the build and the deletion of them after the build is completed.

Desktop Notifier for Jenkins — This is useful for those who are looking for a Desktop Notifier for Jenkins builds to automatically notify you about failed builds directly from their desktops.

Email-ext plugin — This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says.

Google Calendar Plugin — This plugin publishes build records over to Google Calendar

HTML5 Notifier Plugin — Provides W3C Web Notifications support for builds.

Jabber Plugin — Integrates Jenkins with the Jabber/XMPP instant messaging protocol. Note that you also need to install the instant-messaging plugin.

Build reports

Checkstyle Plugin — This plugin generates the trend report for Checkstyle, an open source static code analysis program. 

Clover PHP Plugin — This plugin allows you to capture code coverage reports from PHPUnit. For more information on how to set up PHP projects with Jenkins have a look at the Template for Jenkins Jobs for PHP Projects.

Crap4J Plugin — This plugin reads the "crappy methods" report from Crap4J. Hudson will generate the trend report of crap percentage and provide detailed information about changes.

Dependency Analyzer Plugin — This plugin parses dependency:analyze goal from maven build logs and generates a dependency report

Dependency Graph View Plugin — Shows a dependency graph of the projects using graphviz. Requires a graphviz installation on the server.

FindBugs Plugin — This plugin generates the trend report for FindBugs, an open source program which uses static analysis to look for bugs in Java code. 

Grinder Plugin — This plugin reads output result files from Grinder performance tests, and will generate reports showing test results for every build and trend reports showing performance results across builds.

JSUnit plugin — This plugin allows you publish JSUnit test results

Performance Plugin — This plugin allows you to capture reports from JMeter and JUnit . Hudson will generate graphic charts with the trend report of performance and robustness.

PerfPublisher Plugin — This plugin generates global and trend reports for tests results analysis. Based on an open XML tests results format, the plugin parses the generated files and publish statistics, reports and analysis on the current health of the project.

PMD Plugin — This plugin generates the trend report for PMD, an open source static code analysis program. 

Sonar plugin — Quickly benefit from Sonar, an open-source dashboard based on many analysis tools like Checkstyle, PMD and Cobertura.

testng-plugin — This plugin allows you to publish TestNG results.

Violations — This plug-in generates reports static code violation detectors such as checkstyle, pmd, cpd, findbugs, codenarc, fxcop, stylecop and simian.

xUnit Plugin — This plugin makes it possible to publish the test results of an execution of a testing tool in Jenkins.

Artifact uploaders

ArtifactDeployer Plugin — This plugin makes it possible to copy artifacts to remote locations.

Artifactory Plugin — This plugin allows deploying Maven 2, Maven 3, Ivy and Gradle artifacts and build info to the Artifactory artifacts manager.

Confluence Publisher Plugin — This plugin allows you to publish build artifacts as attachments to an Atlassian Confluence wiki page.

Deploy Plugin — This plugin takes a war/ear file and deploys that to a running remote application server at the end of a build

FTP-Publisher Plugin — This plugin can be used to upload project artifacts and whole directories to an ftp server.

HTML Publisher Plugin

Publish Over FTP Plugin — Publish files over FTP

Publish Over SSH Plugin — Publish files and/or execute commands over SSH (SCP using SFTP)

S3 Plugin — Upload build artifacts to Amazon S3

SCP plugin — This plugin uploads build artifacts to repository sites using SCP (SSH) protocol.

Hudson Helper for Android — Monitor your CI builds right from your Android device.

Hudson Mobi, the iPhone, iPod and Android client for Hudson CI — The iPhone, iPod and iPad client for Hudson CI monitoring on the road.

Hudson Monitor for Android — Monitor and display the status of your builds on your Android™ phone.

External site/tool integrations

ChuckNorris Plugin — Displays a picture of Chuck Norris (instead of Jenkins the butler) and a random Chuck Norris 'The Programmer' fact on each build page.

UI plugins

Active Directory plugin — With this plugin, you can configure Jenkins to authenticate the username and the password through Active Directory.

Audit Trail Plugin — Keep a log of who performed particular Jenkins operations, such as configuring jobs.

JClouds Plugin — This plugin uses JClouds to provide slave launching on most of the currently usable Cloud infrastructures.

Checkstyle Plugin — This plugin generates the trend report for Checkstyle, an open source static code analysis program. 

FindBugs Plugin — This plugin generates the trend report for FindBugs, an open source program which uses static analysis to look for bugs in Java code. 

JIRA Plugin — This plugin integrates Atlassian JIRA to Jenkins.

M2 Release Plugin — This plugin allows you to perform a release build using the maven-release-plugin from within Jenkins.

PMD Plugin — This plugin generates the trend report for PMD, an open source static code analysis program. 

Meme Generator Plugin — Generate Meme images when a build fails (and returns to stable), and post them on the project page.

JBoss AS Tools

able to deploy my application directly from the workspace

bad news is that JBoss AS 7 does not currently support other persistence providers like Eclipselink, OpenJPA or DataNucleus

GlassFish and Resin, you can simply drop the JARs of your preferred provider and its dependencies in a designated folder of your server installation and edit your persistence.xml to override the default provider of the server

JBoss AS 7 appears to require an adapter per persistence provider, which to me looks like an unfortunate and unnecessary design decision

documentation continues to be sketchy and far below the standard of JBoss AS 5

top-level performance

classloader leaks

productivity issues of the Eclipse integration

lack of support for JPA providers other than Hibernate

Each of these is currently a blocker for using JBoss AS 7 in production

Redeployment

after a couple of redeployments, there was an OutOfMemoryError

new classloader leak

JBoss AS 7: Catching up with Java EE 6

Performance measurements

JBoss AS 7.0.2

GlassFish 3.1.1

Empty server startup time 1.9 s

3.2 s

Empty server heap memory 10.5 MB

26.5 MB

Empty server PermGen memory 36.3 MB

28.4 MB

MyApp deployment time 5.8 s

JBoss AS 7 is now at a competitive level with Resin and Glassfish and actually outperforms Glassfish in almost all of these tests

character encoding

could either be automatically detected from the server configuration, or could be configured by the user through the useUnicode and characterEncoding properties

character encoding between client and server is automatically detected upon connection

character_set_server for server versions 4.1.0 and newer

To override the automatically detected encoding on the client side, use the characterEncoding property in the URL used to connect to the server.

Asynchronous Servlets Performance

With a non NIO or non Continuation based server, this would require around 11,000 threads to handle 10,000 simultaneous users. Jetty handles this number of connections with only 250 threads.

Classical synchronous model: 10,000 concurrent users -> 11,000 server threads. 1.1 ratio.

Comet asynchronous model: 10,000 concurrent users -> 250 server threads. 0.025 ratio.

classical (synchronous) servlet model

request -> immediate processing -> response

Comet implementations rely on a different model:

request -> wait for available data -> response

With synchronous servlet processing, each request is handled by one dedicated server thread

All entities marked as [Managed] are considered as corresponding to Hibernate/JPA managed entities on the server

It is highly recommended to use JPA optimistic locking in a multi-tier environment (@Version annotation

In conclusion, the recommended approach to avoid any kind of subtle problems is to have a real uid property which will be persisted in the database

Here all loaded collections of the Person object will be uninitialized so uperson contains only the minimum of data to correctly merge your changes in the server persistence context

Tide uses the client data tracking (the same used for dirty checking, see below) to determine which parts of the graph need to be sent.

Dirty Checking and Conflict Handling

Data Validation

Tide integrates with Hibernate Validator 3.x and the Bean Validation API (JSR 303) implementations, and propagate the server validation errors to the client UI components

Data Paging

Changes for Hibernate 3.5 applications

if your application uses Hibernate 3 classes that are not available in Hibernate 4, for example, some of the validator or search classes, you may see ClassNotFoundExceptions when you deploy your application. If you encounter this problem, you can try one of two approaches: You may be able to resolve the issue by copying the specific Hibernate 3 JARs containing those classes into the application "/lib" directory or by adding them to the classpath using some other method. In some cases this may result in ClassCastExceptions or other class loading issues due to the mixed use of the Hibernate versions, so you will need to use the second approach. You need to tell the server to use only the Hibernate 3 libraries and you will need to add exclusions for the Hibernate 4 libraries. Details on how to do this are described here: JPA Reference Guide.

In previous versions of the application server, the JCA data source configuration was defined in a file with a suffix of *-ds.xml. This file was then deployed in the server's deploy directory. The JDBC driver was copied to the server lib/ directory or packaged in the application's WEB-INF/lib/ directory. In AS7, this has all changed. You will no longer package the JDBC driver with the application or in the server/lib directory. The *-ds.xml file is now obsolete and the datasource configuration information is now defined in the standalone/configuration/standalone.xml or in the domain/configuration/domain.xml file. A JDBC 4-compliant driver can be installed as a deployment or as a core module. A driver that is JDBC 4-compliant contains a META-INF/services/java.sql.Driver file that specifies the driver class name. A driver that is not JDBC 4-compliant requires additional steps, as noted below.

DataSource Configuration

domain mode, the configuration file is the domain/configuration/domain.xml

standalone mode, you will configure the datasource in the standalone/configuration/standalone.xml

MySQL datasource element:

        <connection-url>jdbc:mysql://localhost:3306/YourApplicationURL</connection-url>        <driver-class> com.mysql.jdbc.Driver </driver-class>        <driver> mysql-connector-java-5.1.15.jar </driver>

       <security>            <user-name> USERID </user-name>            <password> PASSWORD</password>        </security>

example of the driver element for driver that is not JDBC 4-compliant. The driver-class must be specified since it there is no META-INF/services/java.sql.Driver file that specifies the driver class name.

 <driver-class>com.mysql.jdbc.Driver</driver-class>

JDBC driver can be installed into the container in one of two ways: either as a deployment or as a core module

Install the JDBC driver

Install the JDBC driver as a deployment

In AS7 standalone mode, you simply copy the JDBC 4-compliant JAR into the AS7_HOME/standalone/deployments directory

example of a MySQL JDBC driver installed as a deployment:     AS7_HOME/standalone/deployments/mysql-connector-java-5.1.15.jar

GraniteDS does not support the standard Consumer and Producer Flex messaging API

its own client implementations of these classes org.granite.gravity.Consumer and org.granite.gravity.Producer that provide very similar functionality

most advanced features and greatly simplifies asynchronous handling and client data management

preferred for new projects

Server Options

two options

RemoteObject API,

GraniteDS support for externalization of lazily loaded JPA entities/collections, and support for scalable messaging though Gravity

Tide API

full feature set of Tide data management and further integration with data push through Gravity

complete support for Spring and Seam security or integration with CDI events

Tide/CDI/JPA2/Java EE 6 on JBoss 6/7 or GlassFish 3

If you are on a Java EE 6 compliant application server, it is definitely the best option