Group items matching

in title, tags, annotations or url

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

deploy the example by right clicking on the jboss-as-login project, and choosing Run As -> Run On Server

src/main/webapp directory

beans.xml and face-config.xml tell JBoss AS to enable CDI and JSF for the application

don't need a web.xml

src/main/resources

persistence.xml, which sets up JPA, and import.sql which Hibernate, the JPA provider in JBoss AS, will use to load the initial users into the application when the application starts

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

with a DVI monitor attaced

All managed entity instances are unique in a Tide context

Tide keeps the classic three layers web architecture, when LCDS removes the service layer, and is some kind of remote JPA provider for Flex applications

Tide approach is to minimize the amount of code needed to make things work between the client and the server

principles are very similar to the ones of JBoss Seam, which is the main reason why the first integration of Tide has been done with this framework. Integrations with Spring, EJB 3 and CDI are also available

need to compile your MXML/AS sources with the granite-essentials.swc and granite.swc libraries

3 separate projects: a Java project, a Flex project and a Webapp project.

GraniteDS archetypes

archetypeGroupId: org.graniteds.archetypes archetypeVersion: 1.1.0.GA archetypeArtifactId:

Maven 3.x required

mvn archetype:generate    -DarchetypeGroupId=org.graniteds.archetypes    -DarchetypeArtifactId=graniteds-tide-spring-jpa-hibernate    -DarchetypeVersion=1.1.0.GA    -DgroupId=org.example    -DartifactId=springgds    -Dversion=1.0-SNAPSHOT

cd springgdsmvn clean package

build the project

CDI archetype requires a Java EE 6 server and uses an embedded GlassFish

cd webappmvn embedded-glassfish:run

With the Eclipse Maven integration (the M2E plugin), you can simply choose one of the archetypes when doing New Maven Project.

mvn war:war

two very easy ways to quickly create a new GraniteDS project

Due to the limited capabilities of the ActionScript 3 reflection API than cannot access private fields, it is necessary to create an externalizable AS3 class (implementing flash.utils.IExternalizable and its corresponding externalizable Java class

In both classes you have to implement two methods

the Gas3 generator can automatically generate the writeExternal and readExternal methods.

With GraniteDS automated externalization and without any modification made to our bean, we may serialize all properties of the Person class, private or not

In order to externalize the Person.java entity bean, we must tell GraniteDS which classes we want to externalize with a

externalize all classes named com.myapp.entity.Person by using the org.granite.hibernate.hibernateExternalizer

you could use this declaration, but note that type in the example above is replaced by

            <include annotated-with="javax.persistence.Entity"/>             <include annotated-with="javax.persistence.MappedSuperclass"/>             <include annotated-with="javax.persistence.Embeddable"/>

: type

annotated-with

Instead of configuring externalizers with the above method, you may use the

feature:

precedence rules for these three configuration options: