Blojsom, The Company?

Update: please welcome Red Cog. It’s about time :).

Note: the following is just a speculation. My predictions for World Cup 2006 were all wrong, so…

David posted a picture of a business card with a large Blojsom logo. This is a follow up to his earlier post on name title with his usual ‘cryptic’ style. Tracing way back, it got to be related to Blojsom as a registered trademark, following yet another cryptic hint.

I’m guessing that he’s setting up Blojsom, the company. And I predict that it is going to provide paid customer support for Blojsom. Which is good for the project/product!

Last year I had a chance to suggest Blojsom for use as an internal blogging service for a large company with a couple of thousand employees. After considering the options (other than Blojsom, obviously they considered something like MovableType), they immediately ruled out Blojsom. Why? Because there’s no paid customer support!

Lesson learnt. Companies love the warm fuzzy feeling provided by customer support.

This whole Blojsom company thing is just my wild guess, I could be way off. Maybe it’s going to be Blojsom the detective agency, or Blojsom the bakery.

Ooo, the tlot phickens!

Tagyu Service Has Been Shutdown, For Now

Adam announced that Tagyu has been shutdown for now (as of 16 Aug 2006), citing the lack of room for growth as perhaps one of the causes.

Hopefully Tagyu service will be back up someday. I guess people will just be using Yahoo! Term Extraction.

Tagyu Widget has been downloaded 773 times since 16 Jun 2006, and Tagyu4J has been available since 31 Dec 2005.

JSP Precompilation For Maven2 Project

You can precompile JSP as part of your Maven2 project build by using Maven2 JSPC Plugin.

Follow the usage guide for copy-paste samples to add insert-fragment in web.xml file and jspc-maven-plugin + maven-war-plugin as part of build plugins in pom.xml file.

Here are some problems that I encountered while adding JSP precompilation to Wish:

Some of the JSPs use SiteMesh taglib and since the application only needed it as part of the war package, I originally set the dependency scope to be runtime. This causes JSPC to complain because it needs the library in the classpath while compiling the JSPs.

Embedded error: file:E:/tazmania/eclipse-workspace/wish/src/main/webapp/404.jsp(1,1)
The absolute uri: http://www.opensymphony.com/sitemesh/decorator cannot be resolved
in either web.xml or the jar files deployed with this application


The solution is to change the scope from runtime to compile so SiteMesh becomes available during JSP precompilation.

The next problem is with JSP API and Jasper Runtime.

E:\tazmania\eclipse-workspace\wish\target\jsp-source\jsp\login_jsp.java:[194,68]
cannot resolve symbol
symbol : class JspTag
location: package tagext

E:\tazmania\eclipse-workspace\wish\target\jsp-source\jsp\_404_jsp.java:[7,61]
package org.apache.jasper.runtime does not exist
The solution is to add the missing libraries as dependencies in pom.xml file.

<dependency>
  <groupId>tomcat</groupId>
  <artifactId>jasper-runtime</artifactId>
  <version>5.5.12</version>
  <scope>compile</scope>
</dependency>
<dependency>
  <groupId>javax.servlet</groupId>
  <artifactId>jsp-api</artifactId>
  <version>2.0</version>
  <scope>compile</scope>
</dependency>

Note that you might want to specify the library versions based on the target environment you’re going to deploy the application to.