mvn deploy:deploy-file with WebDAV
Deploying third party artifacts to an internal Maven repo
Though most of the Java libraries are already in the official Maven repository you will from time to time encounter artifacts that are not available there. Reasons for this include licensing issues (e.g. Oracle JDBC drivers and some Sun Java APIs) and a lack of maintainers.
Most users of Maven run an internal repository for those artifacts and to distribute their own work products.
Recent versions of Maven support uploading artificats along with their sources directly into your internal repo through WebDAV:
mvn deploy:deploy-file \
-DrepositoryId="internal" \
-Durl="dav:https://server/repo" \
-Dfile="oracle-jdbc.jar" \
-DgroupId="com.oracle" \
-DartifactId="oracle-jdbc" \
-Dversion="1.2.3" \
-Dpackaging=jar \
-DgeneratePom=true
Estonia
A cool country with a warm heart
Estonia is a small country in the north east of Europe in the Baltic region. As a former Soviet republic it became independant in 1991 and is a member of NATO and the European Union since 2004.
Estonia has a strong information technology sector and plays a leading role in terms of eGovernment. It has declared internet access a basic human right and there are free wlan hotspots throughout the country. Over 90% of the population own a mobile device while in 1991, when Estonia regained its independence, only half of the country's 1.4 million people even had a telephone line. Being a very small country without much natural resources, Estonia has realized that it has to move fast and that innovative ideas are the way to future.
In terms of political and civil freedom Estonia quite ahead in Europe. Reporters sans frontières has ranked Estiona 3rd out of 169 countries in its press freedom index while Germany is only on rank 20.
Liberal economic policies, low taxes and a well-educated population build a solid ground for entrepreneurs.
Next week I'll have a look on my own.
Update 2008-10-08
I've uploaded some pictures.
Book: Openfire Administration
A step-by-step guide to managing Openfire
Packt has released a new book on Openfire a Java based Instant Messaging server.
Openfire Administration by Mayank Sharma is a step-by-step guide for everybody who wants to setup an internal IM server for private or corporate use. It walks you through the whole installation and configuration process including integration with external authentication sources like OpenLDAP and Active Directory and covers a bunch of useful plugins.
In contrast to other similar products Openfire is based on open standards as it uses the same XMPP protocol that is also used by Google Talk and Apple's iChat. Openfire is available under the GNU General Public License so there are no license fees and it's maintained by a vibrant community. There are a lot of free and commercial clients that you can use to connect to Openfire like Spark and the Flash based SparkWeb, Psi, iChat and many more.
Additional free plugins are available that cover a wide range of requirements like connection to other IM networks like MSN, ICQ/AIM and Yahoo!, server side archiving for compliance and integration with the Asterisk PBX.
If you are new to running IM infrastructure and interested in setting up a proven enterprise ready solution Mayank's book is for you and will provide you with the information required to install and run a professional IM solution.
References
- Openfire product page at igniterealtime.org
- Openfire Administration at Packt
- "Openfire: Effectively Managing Users", extracted from the book
Kuschelworkshop
Eindrücke vom MinD Camp 2008
Wenn ich von meiner Teilnahme am diesjährigen MinD Camp berichte, taucht eine Frage immer wieder auf: Was hat man sich eigentlich unter dem Programmpunkt "Kuschelworkshop" vorzustellen?
Using Namespaces in XSLT and XPath
Don't miss factory.setNamespaceAware(true)
You can use namespaces in XSLT and XPath like
<xsl:value-of select="//a:account/b:accountType" xmlns:a="http://example.com/accounts" xmlns:b="http://example.com/types"/>
For this to work in Java the document builder must be namespace aware otherwise namespaces are stripped when parsing the document and your transformation will fail for obvious reasons.
DocumentBuilderFactory f = DocumentBuilderFactory.newInstance(); f.setNamespaceAware(true);
At least in JDK 6 the default seems to be false.