VijayKiran.com

Passionate about technology

Programs as a hobby

Will talk your ear off on a technical subject if encouraged

Significant and often numerous personal side-projects over the years

Learns new technologies on his/her own

Opinionated about which technologies are better for various usages

Very uncomfortable about the idea of working with a technology he doesn’t believe to be “right”

Clearly smart, can have great conversations on a variety of topics

Started programming long before university/work

Has some hidden “icebergs”, large personal projects under the CV radar

Knowledge of a large variety of unrelated technologies may not be on CV

via How to recognise a good programmer.

mvn clean install brain:run-exploded -Psleepy

If you think you’re a genius, that’s great. But you’re not. Even if you are, realise that you aren’t. Even if you actually are, keep it to yourself. Key words here: “Show, don’t tell.”

Long story short, do what you enjoy. Do it lots and lots. You’ll get better at it. There’s no easy way to success.

→think pink: You’ll never get what you want..

This post is part of a series which will be focusing mainly on Hippo CMS’s extensibility. These posts are more targeted towards the developers who want to customize and enhance the core CMS functionality.

Introduction

Hippo CMS is part of the Hippo’s Open Source Enterprise Content Management System. It provides a browser based user interface for managing the content in the Hippo Repository. Hippo CMS is fully customizable and developer friendly CMS that provides various ways to extend its functionality.

Hippo CMS application is built using Apache Wicket, one the best frameworks available today for building web applications using Java. Wicket is known for its simplicity, and its component-oriented programming, thus providing solid base for the Hippo CMS.

Hippo CMS has pluggable architecture which boasts of first class plug-in mechanism. Depending on your needs, you can create complex document types, extend and enhance the user interface and even create a combined add-on that can change the Core CMS and even replace. All you need to know to build the GUI add-ons is Java and Wicket.

I’ll try to explain each of these extensibility in detailed examples in this series of blog posts. So let us get started.

Yesterday we have announced a new version of Hippo CMS (version 7.1) and Hippo Site Toolkit 2(Version 2.03.09).

Getting and Building Hippo CMS
I’m assuming you are using a Unixy Operating system (Linux/Mac OS X). If you use windows replace the commands appropriately.

Before starting to checkout the source and building please make sure you have the following installed on your computer.

• Subversion
• Apache Maven 2.1.0
• JDK

Open a command line and check out the code for Hippo ECM using following command. Please note that if you are using an graphical client such as Tortose SVN, then you can checkout using the appropriate menu option.

svn co http://svn.onehippo.org/repos/hippo/hippo-ecm/tags/Tag-HREPTWO-v2_06_06 cms-7.1

Now change to the cms-7.1 directory and build the Hippo ECM using maven.

cd cms-7.1
mvn clean install [-DskipTests]

If you are getting out of heap space error, set the MAVEN_OPTS using the following command:

export MAVEN_OPTS="-Xms256m -Xmx700m -XX:MaxPermSize=1024m"

If you are building for the first time, please note that it may take some time since maven needs to download all the dependencies. Once you are done with building Hippo ECM and you can run the provided Quick-start WAR file to get a feel of the user interface and the CMS application.

Change to the quickstart/war directory and run the hippo-cms web application using embedded jetty.

cd quickstart/war
mvn jetty:run-war

After jetty has been started, goto http://localhost:8080/cms to check the version of the CMS that you’ve just built. You can login using default username/password combination of admin/admin.

Hippo CMS Login Screen

Note that you can even deploy the generated war file in Tomcat or an Application Server. Check the documentation for more information.

This concludes the first part of Hippo CMS Customization Part 1- Getting Started . In the next post of this series we will see how to create a simple backend templates (a.k.a Document Types) using Document Type Editor provided within Hippo CMS.

Setup Jetty to run with Debugging enabled on port 8000

export MAVEN_OPTS="-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000"

Run Jetty using Maven Plugin

mvn jetty:run

In NetBeans, Goto Debug→ Attach Debugger menu. Select Java Debugger(JPDA) and specify the port as 8000. Now you can debug the webapplication using NetBeans.

From comment in the code of Xee

// At this point, I’d like to take a moment to speak to you about the Adobe PSD format.
// PSD is not a good format. PSD is not even a bad format. Calling it such would be an
// insult to other bad formats, such as PCX or JPEG. No, PSD is an abysmal format. Having
// worked on this code for several weeks now, my hate for PSD has grown to a raging fire
// that burns with the fierce passion of a million suns.
// If there are two different ways of doing something, PSD will do both, in different
// places. It will then make up three more ways no sane human would think of, and do those
// too. PSD makes inconsistency an art form. Why, for instance, did it suddenly decide
// that *these* particular chunks should be aligned to four bytes, and that this alignement
// should *not* be included in the size? Other chunks in other places are either unaligned,
// or aligned with the alignment included in the size. Here, though, it is not included.
// Either one of these three behaviours would be fine. A sane format would pick one. PSD,
// of course, uses all three, and more.
// Trying to get data out of a PSD file is like trying to find something in the attic of
// your eccentric old uncle who died in a freak freshwater shark attack on his 58th
// birthday. That last detail may not be important for the purposes of the simile, but
// at this point I am spending a lot of time imagining amusing fates for the people
// responsible for this Rube Goldberg of a file format.
// Earlier, I tried to get a hold of the latest specs for the PSD file format. To do this,
// I had to apply to them for permission to apply to them to have them consider sending
// me this sacred tome. This would have involved faxing them a copy of some document or
// other, probably signed in blood. I can only imagine that they make this process so
// difficult because they are intensely ashamed of having created this abomination. I
// was naturally not gullible enough to go through with this procedure, but if I had done
// so, I would have printed out every single page of the spec, and set them all on fire.
// Were it within my power, I would gather every single copy of those specs, and launch
// them on a spaceship directly into the sun.
//
// PSD is not my favourite file format.

→ XeePhotoshopLoader.m

I was working with a Jboss seam application, and found out that I cannot send attachment when the body type is set to ‘plain’. After searching the seam bugs, I found this: https://jira.jboss.org/jira/browse/JBSEAM-3970

I checked out the code to rebuild the fixed seam-mail.jar. If you are also experiencing the issue, then you can just replace your jboss-seam-mail.jar with the attached from here: jboss-seam-mail

Wouldn’t it be great to have a site that cares about your code ? That threats it as a piece of art and at the same time, encourage people to make it better and more beautiful ?

→ RefactorMyCode.com