Talkwards
links for 2008-11-29
-
What are the basic emotions? As ever, theorists disagree. Ortony and Turner (1990) collated a wide range of research on identification of basic emotions.
-
There is a tool that allows to locally mount remote DAV repositories under Linux, so it appears in the local directory tree.
links for 2008-11-28
-
Alfresco is the Open Source Alternative for Enterprise Content Management (ECM) led by John Newton, founder of Documentum, and John Powell, former COO of Business Objects, and is backed by Accel Partners, Mayfield Fund and SAP Ventures.
-
Alfresco tutorials: Advanced workflow with JBPM, Intro to the Web Script Framework, Implementing Custom Behaviors, Working with Custom Content Types, Developing Custom Actions
-
Comparing Open Source and Proprietary Enterprise Content Management Systems: Alfresco Compared to IBM Lotus Domino Document Manager Integrated with IBM Lotus WorkFlow.
-
Enterprise Content Management (ECM) is the technologies used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists.
-
The purpose of the Content Management Interoperability Services (CMIS) TC will define a domain model including a data model and abstract capabilities for Content Management (CM) and a set of bindings that can be used by applications to work with one or more Content Management Repositories/systems and that can be implemented by content repositories and enable interoperability across repositories.
CHARVA: A Java Windowing Toolkit for Text Terminals
Looking around for an easy way to create applications with text GUIs for running over SSH terminals I came across CHARVA. CHARVA’s API copies Swings, it unfortunately is not built on top of Swing but is a copy of Swing. This forces implementers to import classes in the charva.awt and charvax.swing packages instead of traditional awt and swing classes. However, the result is rather nice, at least if you’re looking to run applications off a server on a simple Point-of-Sale or Point-of-Service (POS) terminal that may not even support graphics.
In my case I’m looking into making a simple app that I can use to keep track of passwords, both when I’m at home (regular swing) and when I’m away (at work or similar) and only able to access the application via SSH (CHARVA).
For more info, check out CHARVA here: http://www.pitman.co.za/projects/charva/index.html
links for 2008-11-27
-
Inversion of Control is a principle used by framework as a way to allow developers to extend the framework or create applications using it.
-
Now it seems that IoC is receiving attention from the design pattern intelligentia:Martin Fowler renames it Dependency Injection, and, in my opinion, misses the point: IoC is about enforcing isolation, not about injecting dependencies.
links for 2008-11-26
-
The Java Servlet specification version 2.3 introduces a new component type, called a filter. A filter dynamically intercepts requests and responses to transform or use the information contained in the requests or responses. Filters typically do not themselves create responses, but instead provide universal functions that can be "attached" to any type of servlet or JSP page.
-
The Apache Commons Logging (JCL) provides a Log interface that is intended to be both light-weight and an independent abstraction of other logging toolkits. It provides the middleware/tooling developer with a simple logging abstraction, that allows the user (application developer) to plug in a specific logging implementation.
-
Generate Classes from the RDL Schema using the xsd Tool
-
XML Class Generator for C# using XSD for deserialization: Let’s say we have an XML file and we want to deserialize that file to our implemented class. This is an easy task if the XML file is simple. However if it has more complex types, it can take a long time to implement the class without error. Using xsd, part of the .Net framework SDK, this can be done in moments.
links for 2008-11-25
links for 2008-11-23
-
Originally named “Joe’s Quotes”, this plugin shows your favorite random quotes along with a picture of the person saying the quote. Easily expandable to contain quotes from any person/character. Version 3 includes an options page and uses CSS for formatting.
links for 2008-11-22
-
Everything2 is a collection of user-submitted writings about, well, pretty much everything.
Compiling to different versions of Java in Eclipse
I’ve just had the rather unsettling experience of trying to deploy a new jar file (one I recompiled after some changes). This file were to be deployed on a rather old set up of Java 1.4.2. On first try everything broke with the classic “Unsupported major.minor version 50.0″.
So I went back to the drawing board. I installed java 1.4, and made sure my development Tomcat was running it. Then I did some research and found out how to make Eclipse compile 1.4 compliant code. I started and I got the same error still.
Once I figured out what was wrong I realized I was an idiot (Doh!). The error I’ve gotten wasn’t for any file part of the jar I was trying to deploy but for “index_jsp”. The thing is my Tomcat compiled my JSP:s into class files and never looked at them again until they were changed. I am sure there’s several ways to solve the problem, I just went and deleted the files in the “work”-directory (those pertaining to my Context).
The preferences window for setting source and target versions for Java compilation
Now over to how to make Eclipse code projects to a certain Java version.
There are two values you will want to keep track of. The source version and the target version. The source version tells what version your source code is written in. Whereas the target version tells what version of Java you want your class files in.
If for instance you have a project written in Java 1.4 source style, but you have to run it on a Java 5 you’d set the source version to 1.4 and the target to 1.5. You are now compiling Java 1.4 source into Java 5 class files. Unfortunately you’re not able to do the opposite, compile Java 5 source code into Java 1.4 class files. This is probably due to API incompatibilities, Java 5 has a larger API than Java 1.4.
Now, in Eclipse you have two settings in three places that controls the source and target versions of your compilations. Under Window->Preferences->Java->Compiler (Eclipse 3.4) you’re able to set the versions for the whole IDE.
When you create a new project you’re able to determine what version of Java (source and target you want) and right clicking on a project and choosing Properties->Java Compiler, you have the same dialog as before.
You set the target level in the select box “Compiler compliance level”, and optionally by unchecking the “Use default compliance settings” you’re able to change the target (“Generated .class files compatibility”) and source respectively.
If you experience other problems you may want to “clean” your project(s). Cleaning a project means all compiled files are removed and all source files are recompiled (something the IDE will do by itself when you change compilation versions, but if you want to be sure, you can do it manually). This is done by choosing Project->Clean. In the dialog you can chose to clean all projects or just those you select.
links for 2008-11-18
KirkWar isn't a good life, but it's life.