1. Disconnect your external monitor from your macbook
2. Shut the lid on your macbook putting it to sleep
3. Reconnect your external monitor (macbook will still be sleeping)
4. Force the mac to wake by connecting something in to the USB port
5. Open the lid and you should find the monitor is the only and primary output source.

Try It!

Try It!

Hudson is an open source continuous integration tool offering optional commercial support provided by Sun Microsystems.  It has a growing number of extensions thanks to the loyal community and in my humble opinion is the best free build tool on the market.

In no particular order here are some of my favourite plugins.

1. Batch Task Plugin

2. Sidebar Link PLugin

3. Backup Plugin

4. CVS Tagging Plug-in

5.  M2 Release Plugin

6. FindBugs Plugin

A full list of the available plugins can be found here.

Try It!

Assumptions

• You know all the columns which make up the table even the intial hidden ones

Quick Google

In my usual fashion, I did a quick search to find some best practice and get a heads up from other developers who had solved this before.  Results were pretty scare and pointed me down the route of rebuilding the entire table via a structure change event.

AbstractTableModel  has numerous events and the structure event is typically one you don’t want to fire often, especially if you have a huge table of 20,000 rows.  Yes 20,00 rows was the requirement!

Selected Solution

The method I choose after speaking to my friend Lorenzo, was to make the hidden column widths zero in length.  Then when they needed displaying adjust that value, fire a data changed event and importantly remember to repaint the table.  Once the repaint is called you can apply the width adjustment to the TableColumn model.

Finally in the DefaultTableCellRenderer I would advise setting the hidden or zero length table columns to not be resizeable because it is possible to adjust them even though they cannot be seen!

Setting the Width to Zero

Be careful to set the TableColumn min width to zero, otherwise you will see the column.

private void hideColumn(TableColumn tableColumn) {
  tableColumn.setPreferredWidth(0);
  tableColumn.setMinWidth(0); // Don't forget this
  tableColumn.setResizable(false);
}

Why is this Better?

• You never need to worry about firing a structure change event to update the table
  
• Your implemented AbstractTableModel functions like getColumnCount() are simple because there is no need for a function to determine which columns are displayed and which are not as they are all technically displayed.
  

Try It!

In order to fix this I recommend the following wiki page.

Do It!

The current list of contributions hoping to make it to print can be found here.

Uncle Bob has posted a few of my favourites; small, the three laws of test driven development and the professional programmer.

This could become another must own text like Essential Java, Clean Code and Java Concurrency in Practice.

Hidden Gem

Tomcat has a hidden gem in a little known script named setenv.sh/bat.  You won’t find this file when you unpack your newly downloaded distribution or in the documentation.  The only reference to it is in the catalina.sh/bat file.  (Catalina was the original name for the product).

Script: setenv.sh/bat

This file is called during the start up process by catalina.sh/bat and should be used to set environment variables like JAVA_HOME.  The end goal of this script is to ensure that you do not edit catalina.sh/bat because in doing so will effect your upgrade path.

Extract from catalina.sh

if [ -r "$CATALINA_BASE"/bin/setenv.sh ]; then
  . "$CATALINA_BASE"/bin/setenv.sh
elif [ -r "$CATALINA_HOME"/bin/setenv.sh ]; then
  . "$CATALINA_HOME"/bin/setenv.sh
fi

Example: setenv.sh

JAVA_HOME=/usr/java/jdk1.6.0_04
ARCHIVA_BASE=/home/admin/apache-archiva-data
ARCHIVA_HOME=/home/admin/apache-archiva-1.2.1

Script: server.xml and catalina.properties

Server.xml is an important file.  It contains configuration relating to ports, max threads, connection timeout and much much more.  The problem is most of the time this file is edited by an administrator with hard coded values.  Don’t do this!

Tomcat has property placeholder support already configured.  All you need to do is to place your key=value in catalina.properties.

tomcat.http.port=80

Use the following notation in order to import the property.

port=${tomcat.http.port}

Example

<Connector
  port="${tomcat.connector.http.port}"
  protocol="HTTP/1.1"
  connectionTimeout="${tomcat.connector.http.connectionTimeout}"
  redirectPort="${tomcat.connector.http.redirectPort}"
/>

Try it!

Bit.ly Stats

Just for fun: http://bit.ly/info/Z2q58

The following tip however is still a very useful one know. Thanks must go to Ben Halton aka The Gizard Wizard for this.

When you are casting an object, the quickest way to end up with the right result is within the brackets type CTRL + T. This should open a small menu with a compatible class for you to choose from.

If you had a deep hierarchy your really see the benefit of this one.

Try it!

Configuring Web.xml

In order for Spring to understand how to deal with the RESTFUL URL you firstly need to setup a new Servlet Mapping. Restlets has Spring support included out of the box. The servlet-name will ofcourse become your mapping into the Restlet framework instead of a SpringMVC.

web.xml

<servlet>
   <servlet-name>webapi</servlet-name>
   <servlet-class>
    com.noelios.restlet.ext.spring.RestletFrameworkServlet
   </servlet-class>
 </servlet>

 <servlet-mapping>
   <servlet-name>webapi</servlet-name>
   <url-pattern>/webapi/*</url-pattern>
 </servlet-mapping>

Configuring the Spring Context

Here is how you configure and build up your Restful URL’s which should be in a file named webapi-servlet.xml based on the above configuration. Simply create a SpringRouter bean and add an entry per URL.

Spring Context

<bean id="root" class="org.restlet.ext.spring.SpringRouter">
  <property name="attachments">
    <map>
      <entry key="/{variable}/your/restful/call/{variable2}">
        <bean>
          <lookup-method name="createResource" bean="yourBean" />
        </bean>
      </entry>
   </map>
</bean>

Resource Example

@Component("someResource")
@Scope("prototype")
public class SomeResource extends Resource {

 @Override
 public void init(Context context, Request request, Response response) {
   super.init(context, request, response);    
   getVariants().add(new Variant(MediaType.TEXT_PLAIN));
 }

 /**
 * HTTP-GET request representation handler. 
 */
 @Override
 public Representation represent(Variant variant) {        
   .
   .
   .
 }
}

1. In the main project set up an environment variable to your shared project in Xcode Preferences Source Tree.



2. Close Preferences. In Groups and Files click on the root icon which represents your project and click OPTION+CMD+A. This will open the Add Project window. Find your the xcodeproj file you would like to share and Add it.
3. In the next prompt make sure you have, Copy files into your destination group’s folder (if needed), unchecked.
4. Select the targets you want and click OK. You should now see the project included on the Files and Groups window.



5. Expand the Target(s) you want to build for.
6. Notice a folder named Link Binary With Libraries, expand this also.
7. Now drag the .a file from the newly added project to the Link Binary With Libraries folder.
8. Click on the Target and Open the Info menu CMD+i
9. In the General Tab there is a Direct Dependices selection. Click the + and add the shared project.



10. In the Build Tab search for User Header Search Paths, and double click in the value selection.
11. In the new window, click the + to create a new blank entry.
12. In the Path, add the reference you created to the shared library in step 1 with the following format $(SHARED_PROJECT_NAME) make sure you check the Recursive box.



13. Assuming the shared project is build you should now simply build and use the project normally.
14. Additional: If you have more than one shared library which share the same library, the you will need to set the references as weak.