This will cause issues for people who want to have multiple copies of the widget in
the page.  There is to much risk of ID collision.

There is always a way of navigating down the tree to find children (Especially if you
are writing a JQueryUI widget).

Classes are ok – and use them to find children – but DO NOT add an ID.

(This blog post written as a public service, after having seen way to many JQueryUI widgets that don’t get this right).

Step 1) get and install macfuse http://code.google.com/p/macfuse, along with the ssh filesystem http://code.google.com/p/macfuse/wiki/MACFUSE_FS_SSHFS

Step 2) create a folder to mount to. mkdir -p /mnt/remote

Step 3) setup the ssh tunnel: ssh -C -L 2022:server_with_data_to_get:22 ssh.tunnel.server (going into server_with_data_to_get via ssh.tunnel.server, making this available at localhost:2022).

Step 4) Use sshfs to mount the drive: sshfs -C -p 2022 username@localhost:/path/to/folder_to_mount /mnt/remote (connect to the localhost -ssh tunnel end point- mount remote folder /path/to/folder_to_mount to the local folder /mnt/remote).

Having said that this is non-trivial, it is reassuring to know that the process to do this is very straight forward.

1. Create a subclass of play.Invoker.Invocation.
2. Override the public void execute() method.
3. Call the run() method of the invocation.

With this simple snippet of code, it is possible to have non-Play! code easily and cleanly call your Play! application code.

1. Rapid development via a local development server that automatically compiles your java code for you. It’s amazing how good it is to develop like this, and what a difference the rapid feedback loop makes.
2. A good clean MVC famework.
3. Nice testing support baked in.
4. A useful routing table to make clean urls easy to work with.
5. A focus around REST, but no slavish observence of it.
6. built-in simple JSON support.
7. A good module framework with useful modules including a “CRUD” module, and a Scala module currently under development
8. An interesting mix of Java class enhancement that makes it easy to work with code, and then have the enhancer provide some of the hard work for ensuring that multiple threads are handled well.
9. Deployment to a range of platforms, including JEE Servlets (Play! 1.0.2 has been tested on containers such as tomcat, jetty, JBoss and IBM WebSphere Portal 6.1), and the GAE.
10. Enhancements to the JPA which make it really easy to work with.
11. An active and supportive community. There is the right balance between having strong opinions about the “Play!” way of doing things, and helping people to get things done.

Play! makes Java web development fun and productive. The feedback loop is really quick, and much of the boilerplate code is removed. It’s well worth considering for any application you want to write in Java.

Take a look at the video, and work through the tutorial to get a feel for what development with Play! is like.

1) Don’t install from a directory with spaces.

If you download the pilot to your desktop and try and install from here, things will crash and burn

2) Don’t expect the VM to be easily moved around networks

I started my second installation on my laptop at home, then brought it to work. This crashed and burned.

3) Use fully qualified hostnames

While the installer said that you could specify a short hostname or a fully qualified hostname, the short hostname did not work for me.

4) Connections 2.5 is RAM hungry

1.5 GBytes is not enough 2.5 GBytes is. Not sure of the exact threshold for it to work, but I can confirm that 2.5 GBytes is enough RAM.

You have received a WebSphere Portal VM that is setup to use security settings that don’t match your environment, and you need to go back to a simple config.

Running the recommended

does not work, because you have not got a working Portal environment in the first place, so it won’t start.

Overview of solution

Disable the security, then perform wp-restore-default-repository-configuration.

Files and Tools used

• security.xml
• ConfigEngine 
• wkplc.properties

Whenever you see some code with bold and italics that is something for you to change to match your environment 

Details:

1) disable security.

This involves directly editing the security.xml file for your node. Note that your portal instance will NOT work when security is disabled, so performing this step will disable your portal instance. You should not think about doing this in a production environment (you probably shouldn’t be passing around Portal VM’s for production environments anyway). (The security.xml will live in the config for your node. I’ll assume you know where this is, if not use the find command on your operating system).

To disable security, edit the security.xml, and change the enabled attribute on the root security element to be false ie change enabled=”true” to enabled=”true”

2) start up your portal instance using whatever commands are appropriate.

On linux you might find

useful.

3) Setup restore properties in your wkplc.properties file.

Profile/ConfigEngine/properties/wkplc.properties

# The realm name to be used. A realm with this name will be created.
restore.file.realm=New Unique Realm restore.file.delimiter=/

# Portal and WAS admin UID (short name) and password
restore.file.primaryAdminId=New Unique Admin ID 

restore.file.primaryAdminPassword=Password

# CN of portal admin group (short name)
restore.file.primaryPortalAdminGroup=adminGroupCN

4) run ConfigEngine.sh

Profile/ConfigEngine/ConfigEngine.sh wp-restore-default-repository-configuration

5) Turn on security (reversing step 1)

6) shutdown (or kill) portal

7) startup portal.

You should now see your portal server running without using LDAP.

One of the big overriding factors is how much external influences impact people. The location and cultural context in which someone is born, the year in which they were born, and even the birth month has a huge impact. Before reading the book I would have had no idea, after I can agree with him, but don’t worry, I’m not about to become an astrologer, and I don’t think it is directly related to the Chinese birth years (although there might be some links). Of additional interest is the idea of 10000 hours of practice being required to become an expert.

The quick list of impacts of particular interest for me were:

1. 10,000 hours of practice is required before becoming an expert
2. the birth month can have a huge impact (6-9 months of age difference can make a huge difference in early childhood – so early streaming favours the older children, with cascading effects)
3. the birth year can have a huge impact (careers available, and many hugely successful people are early adopters, so there is only a small window of age/experience that makes it available)
4. our cultural heritage makes a huge difference (what path and options make sense is often dependant on how we are guided by our parents, which cascades backwards)

The lessons are taught well through the book, and it is a compelling read. You may not agree with all the findings, but I’m sure you will get a good read, learn the stories of some successful people, and be challenged in some of your thinking about success.

If you are interested in having a look at the site he put together, or if you are interested in buying a house in the coastal suburb of Wynnum, in Brisbane, Australia, take a look at Bayside House For Sale.

I always find the latest incarnations of phishing spam entertaining.  I almost clicked on one of the fake facebook links a while ago, but really wasn't at all tempted to click on the links in the one that came in today..

Yes, I am looking at that message in Mail.app, and viewing the source did show that the link didn't go to where it said it would go.