You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by an...@apache.org on 2014/06/25 14:47:41 UTC
svn commit: r1605373 - in /tomee/site/trunk/content:
arquillian-available-adapters.mdtext tomee-1.7.0.mdtext
Author: andygumbrecht
Date: Wed Jun 25 12:47:40 2014
New Revision: 1605373
URL: http://svn.apache.org/r1605373
Log:
Release doc
Modified:
tomee/site/trunk/content/arquillian-available-adapters.mdtext
tomee/site/trunk/content/tomee-1.7.0.mdtext
Modified: tomee/site/trunk/content/arquillian-available-adapters.mdtext
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/arquillian-available-adapters.mdtext?rev=1605373&r1=1605372&r2=1605373&view=diff
==============================================================================
--- tomee/site/trunk/content/arquillian-available-adapters.mdtext (original)
+++ tomee/site/trunk/content/arquillian-available-adapters.mdtext Wed Jun 25 12:47:40 2014
@@ -30,21 +30,25 @@ The above can also be set as system prop
When a port is set to -1, a random port will be chosen. This is key to avoiding port conflicts on CI systems or for just plain clean testing.
-The TomEE Arquillian adapters will export the actual port chosen back as a system propert using the same name. The test case can use the property to retrieve the port and contact the server.
+The TomEE Arquillian adapters will export the actual port chosen back as a system property using the same name. The test case can use the property to retrieve the port and contact the server.
URL url = new URL("http://localhost:" + System.getProperty("tomee.httpPort");
// use the URL to connect to the server
+
+If that property returns null
When you are actually using a test on the client side, you can use instead
- @Arquillian private URL url;
+ import org.jboss.arquillian.test.api.ArquillianResource;
+ ...
+ @ArquillianResource private URL url;
The url will get injected by Arquillian. Be careful, that injection only works if your are on the client side (it does not make sense in the server side). So, if for a specific need to need it, just use the system property.
# TomEE Embedded Adapter
-The TomEE Embedded Adapter will boot TomEE right inside the testcase itself resulting in one JVM running both the application and the test case.
-This is generally much faster than the TomEE Remote Adapter and great for development. That said, it is strongly recommended to also run all tests in a Continous Integration
+The TomEE Embedded Adapter will boot TomEE right inside the test case itself resulting in one JVM running both the application and the test case.
+This is generally much faster than the TomEE Remote Adapter and great for development. That said, it is strongly recommended to also run all tests in a Continuous Integration
system using the TomEE Remote Adapter.
To use the TomEE Embedded Arquillian Adapter, simply add this Maven dependency to your Arquillian setup:
@@ -76,6 +80,10 @@ Or more specifically as a System propert
The TomEE Remote Adapter will unzip and setup a TomEE or TomEE Plus distribution. Once setup, the server will execute in a separate process. This will be slower, but
with the added benefit it is 100% match with the production system.
+Clients can get the remote server port using the following System property:
+
+ final String port = System.getProperty("server.http.port");
+
The following shows a typical configuration for testing against TomEE (webprofile version). The same can be done against TomEE+ by changing `<tomee.classifier>webprofile</tomee.classifier>` to `<tomee.classifier>plus</tomee.classifier>`
<properties>
Modified: tomee/site/trunk/content/tomee-1.7.0.mdtext
URL: http://svn.apache.org/viewvc/tomee/site/trunk/content/tomee-1.7.0.mdtext?rev=1605373&r1=1605372&r2=1605373&view=diff
==============================================================================
--- tomee/site/trunk/content/tomee-1.7.0.mdtext (original)
+++ tomee/site/trunk/content/tomee-1.7.0.mdtext Wed Jun 25 12:47:40 2014
@@ -2,12 +2,22 @@
After many months of hard work and dedicated community commitment Apache TomEE is happy to finally announce the feature release of [Apache TomEE 1.7.0](http://tomee.apache.org/downloads.html) which is based on [Apache Tomcat 7.0.54](http://tomcat.apache.org/tomcat-7.0-doc/index.html). Please do not forget that nearly all of the work that goes into this purely open source project is community driven. Very special thanks go out to all that have dedicated their time to make this release possible. Anyone active on the [mailing lists and/or IRC](http://tomee.apache.org/support.html) will know that an extra special thanks for [Romain Manni-Bucau](http://rmannibucau.wordpress.com) is well deserved.
-The 1.7.0 feature release is the final Java 1.6 compatible Oracle Java EE 6 Web Profile Certified branch. From this point on the TomEE community will be focusing all of it's efforts on TomEE 2.0.0, which will be the Java EE 7 driven.
+The 1.7.0 feature release is the final Java 1.6 compatible Oracle Java EE 6 Web Profile Certified branch.
-So what's new? Well the most important feature has to be the new PLUME profile, which is basically TomEE PLUS with [Mojarra](https://javaserverfaces.java.net/) and [eclipselink](http://www.eclipse.org/eclipselink/) added support.
+So what's new?
+
+###PLUME
+
+One the most important features has to be the new PLUME profile, which is basically TomEE PLUS with [Mojarra](https://javaserverfaces.java.net/) and [EclipseLink](http://www.eclipse.org/eclipselink/) added support.
This makes the transition to TomEE from a Glassfish environment a lot less painful. So no more excuses, come and join us - We're all yours!
-In addition to PLUME there have been a train, plane and truck load of tweaks, improvements and bug fixes to make this release one of the most stable and feature rich versions we have ever released. Just have a quick look at these lists to get an idea of how much has been achieved. Amazing!
+###Java 8 Runtime Support
+
+A lot of work has been completed to ensure that Apache TomEE 1.7.x will run within a Java 8 environment, yet remain backwards compatible with Java 6. Several libraries used have been shaded and patched to achieve this goal.
+
+###Bug Fixes and Improvements
+
+In addition to PLUME and Java 8 support there have been a train, plane and truck load of tweaks, improvements and bug fixes to make this release one of the most stable and feature rich versions we have ever released. Just have a quick look at these lists to get an idea of how much has been achieved. Amazing!
[145 TomEE](https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+TOMEE+AND+fixVersion+%3D+1.7.0) issues addressed
[237 OpenEJB](https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+OPENEJB+AND+fixVersion+%3D+4.7.0) issues addressed (OK, to be fair, some of these were legacy JIRA's stuck in the cobweb)
@@ -30,3 +40,6 @@ A complete [Changelog](tomee-1.7.0-relea
[tomee-1.7.0-release-notes.html](tomee-1.7.0-release-notes.html)
So please feel free to jump in feet first and [get started with TomEE](http://tomee.apache.org/documentation.html). You will nearly always find someone to help you on one of our [support channels](http://tomee.apache.org/support.html).
+
+###Java EE7 and Beyond
+From this point on the TomEE community will be focusing all of it's efforts on TomEE 2.0.0, which will be the Java EE 7 driven.