Bug Fixes

If you experienced problems with rule parameterization in Rewrite 2.0.7.Final, then sorry about that, and this release of [[Rewrite]] is for you: https://github.com/ocpsoft/rewrite/issues/133

Erroneous failures such as the following exception should be fixed by this release:

org.ocpsoft.rewrite.exception.ParameterizationException: The value of required parameter [s] was null.
	at org.ocpsoft.rewrite.param.RegexParameterizedPatternBuilder.extractBoundValues(RegexParameterizedPatternBuilder.java:262)
	at org.ocpsoft.rewrite.param.RegexParameterizedPatternBuilder.build(RegexParameterizedPatternBuilder.java:136)
	at org.ocpsoft.rewrite.servlet.config.Forward.performHttp(Forward.java:85)
	at org.ocpsoft.rewrite.servlet.config.HttpOperation.perform(HttpOperation.java:42)
	at org.ocpsoft.rewrite.servlet.config.rule.Join.perform(Join.java:264)

New Features

• Rewrite will now display version information at application boot time: https://github.com/ocpsoft/rewrite/issues/129

  02:37:34,570 INFO  [org.ocpsoft.rewrite.servlet.RewriteFilter] (ServerService Thread Pool -- 68) Rewrite 2.0.8.Final initialized.

• Compilation mode may now be set on JRuby based Transform modules: https://github.com/ocpsoft/rewrite/issues/131

We are glad to announce the latest version of [[Rewrite]], servlet toolkit and URL-rewriting extensions. This release includes serveral bug fixes and enhancements:

Simplified Configuration

We heard you! It is now much easier to register ConfigurationProvider objects. You can forget about creating a service file, and simply use the convenient @RewriteConfiguration annotation:

import org.ocpsoft.logging.Logger.Level;
import org.ocpsoft.rewrite.annotation.RewriteConfiguration;
import org.ocpsoft.rewrite.config.Configuration;
import org.ocpsoft.rewrite.config.ConfigurationBuilder;
import org.ocpsoft.rewrite.config.Log;
import org.ocpsoft.rewrite.servlet.config.HttpConfigurationProvider;

@RewriteConfiguration
public class ApplicationConfigurationProvider extends HttpConfigurationProvider
{
   @Override
   public Configuration getConfiguration(ServletContext context)
   {
      return ConfigurationBuilder.begin()
         .addRule()
         .perform(Log.message(Log.message(Level.INFO, "Rewrite is active.")))
      ;
   }

   @Override
   public int priority()
   {
      return 0;
   }
}

Issues resolved

• https://github.com/ocpsoft/rewrite/issues/123 – Rewrite should have a @RewriteConfiguration annotation for simpler configuration provider registration
• https://github.com/ocpsoft/rewrite/issues/128 – NullPointerException in ResponseContentInterceptor when no output written to ServletResponse
• https://github.com/ocpsoft/rewrite/pull/124 – Extended AddressBuilder to support custom Schemes.
• https://github.com/ocpsoft/rewrite/issues/122 – Bookstore app only works on AS7
• https://github.com/ocpsoft/rewrite/pull/120 – Added check if binding supports retrieval in the method ‘performRetrieval’

Upgrade to 2.0.7.Final

Read the installation guide, or configuration manual.

<dependency>
   <groupId>org.ocpsoft.rewrite</groupId>
   <artifactId>rewrite-servlet</artifactId>
   <version>2.0.7.Final</version>
</dependency>

So i’ve recently started working on making http://redoculous.io function better in a cluster, to support scaling out for large-scale use, and I’ve been working with http://openshift.com/ as my PaaS hosting provider. I started to run into some problems where I wasn’t sure if the cluster was responding how I wanted to.

Being a good developer, my application has logging, so I know that if I can just watch the logs as they occur (or sift through them after the fact), I can probably figure out what is wrong, and fix it.

Unfortunately, running rhc tail will tail the gear running HA-proxy, but not the gears running the actual application, or any of the duplicate gears if HA-proxy is sharing a gear with an app! You’ll just get HA-proxy logs or maybe one of your application gears if you are lucky. What to do? I ran crying for help to the #openshift channel on IRC, where the openshift gurus quickly set me straight. This is all you need to do (for the ‘jbosseap’ cartridge, at least):

rhc ssh <app> --gears 'tail -f jbosseap/logs/*';

The rhc ssh command will execute a command on each of your gears simultaneously, and stream the output to your termainal, which is just an absolute perfect match for tail -f. Note, though, that you’ll need to pass in your application name, and the path to your logs on each gear (which should be fairly easy to find out if you ssh in and take a look around. The log location is even documented for your cartridge on the openshift site: ) I retrieved it using the same rhc ssh command:

sharktop:gems lb3$ rhc ssh redoculous --gears 'echo $OPENSHIFT_JBOSSEAP_LOG_DIR';
[gear1name jbosseap-6+haproxy-1.4] /var/lib/openshift/gear1name/jbosseap/logs/
[gear2name jbosseap-6+haproxy-1.4] /var/lib/openshift/gear2name/jbosseap/logs/
[gear3name jbosseap-6+haproxy-1.4] /var/lib/openshift/gear3name/jbosseap/logs/

So in this case, the log-dir relative to the home directory is just, jbosseap/logs. Good to go!

Now, I do think that this would be much better suited as rhc tail-all (DOES NOT CURRENTLY WORK), but I’ll just have to file an issue request, or maybe take a stab at the code here if nobody beats me to it:

https://github.com/openshift/rhc/blob/master/lib/rhc/commands/tail.rb#L18
https://github.com/openshift/rhc/blob/master/lib/rhc/commands/ssh.rb#L37

I hope this helps. Good luck, openshifters!

If you are looking for examples on how to use some of the new or improved features of Java EE 7, I highly recommend checking out this git repository from Arun Gupta. https://github.com/arun-gupta/javaee7-samples

He has created over 160 samples that should work on every EE application server. If you find a bug, it’s likely a bug in the particular container you are using, but Arun is also welcoming feedback on these examples. So if there’s something you’d like to see that isn’t there, let him know. Additionally, if there’s something there that isn’t done right, speak up and he’ll fix it!

This is a great resource for the Java Enterprise Ecosystem 🙂

~Lincoln