tag:blogger.com,1999:blog-108707522024-10-25T06:25:51.829+02:00... mostly on programming, I think.Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.comBlogger37125tag:blogger.com,1999:blog-10870752.post-13623149254450360612012-12-25T20:23:00.001+01:002012-12-25T22:13:20.820+01:00

The problem Among the shortcomings of CDI (1.0) as a general purpose DI container is the lack of what Spring 3.+ users know as profiles (not to mention Guice, which is much more expressive due to its Java EDSL approach). The CDI feature which looks closest at a first glance is the concept of alternatives, quickly turns out to be utterly useless: You can annotate your beans directly (or

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-68496775677400082892012-04-10T08:30:00.000+02:002012-04-10T09:12:20.638+02:00

Recently, I came to revisit Scala a bit more in depth -- compared to the odd script or hack I did before. Now, things at work change a bit: some green-field stuff to be done, even calling for some kind of DSL -- ok, maybe not really calling, really loudly but close enough to warrant spending some quality playing-time with my favorite "next great programming language". So I threw together some

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-89388687943227893142012-03-27T20:24:00.000+02:002012-03-27T20:34:03.728+02:00

I've long felt contract envy of languages like Eiffel supporting Design by Contract. Only recently, I stumbled over the (not so) recent addition of theories to JUnit. Once the object instances under test are separated from the test-code - now taking on the form of a logical implication, making the latter re-usable is the obvious next step. Ever been tired of writing tests for your value-object's

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-53784148693973693682010-01-17T16:24:00.004+01:002010-01-17T19:32:24.727+01:00

The setupI was used to the assumption that type inheritance in Java is transitive, that is B extends A and C extends B implies that C is a subtype of A as well as of B. As long as A,B and C denote straight classes, this is true to the best of my knowledge. But as I, admittedly only recently, learned, once generic type expressions come into play it gets a bit more interesting:Let's make A a

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-54383335187108278512009-11-14T13:20:00.002+01:002009-11-14T13:28:29.207+01:00

Well over 300,000 Class.forName calls during context-initialisation were the result of setting up a simple "perTarget" advice for a 400-something beans application. With the standard "per class" instantiation model, the overhead went back to "normal", returning the Hibernate SessionFactory to the top of the list of startup resource-consumers. From a quick look at the profiler output, AspectJ's

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-16031632658954787022008-02-23T20:36:00.002+01:002008-02-23T21:12:58.843+01:00

My beloved "old" (3.5 years) powerbook (G4, 15", 1.5 GHz) started to make humming noises, especially when tilted. A couple of weeks later there were sudden hangups, it would only restart after given some cooling time. That it finally survived my amateur-surgery - albeit somewhat battered - let me immediately regret my fancying a new macbook. Some notes: I followed this guide I did need to poke

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-67506346449153869052007-06-04T21:42:00.000+02:002007-06-06T21:27:39.548+02:00

Recently, I became interested in Scala: Multiple inheritance, good support for functional programming, a nice syntax, to mention the greatest highlights.As a first exercise, I tried to write some Tapestry-4 components in Scala to gain some real-world experience, and to see whether Tapestry's pretty extensive use of bytecode-generation would somehow break Scala's Java-compatibility. I was pretty

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com1tag:blogger.com,1999:blog-10870752.post-85367337872681123732007-05-12T12:27:00.000+02:002007-05-14T08:51:50.080+02:00

Currently we'r working on an application that will be used by 4 different departments. And I can already anticipate people dropping in to casually remark someting like "Oh, by the way, we've hired this guy who needs Access to module X of the invoicing system, but of course he mustn't be allowed to press button Y, and he needs to be able to change the comment-field. And don't hurry, he'll not

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-16486621184356932932007-04-25T20:29:00.001+02:002008-03-04T18:44:56.817+01:00

I've switched from subclipse to subversive recently. The former used to annoy me by its inability to handle directory moves/copies. I had to go and delete .svn dirs manuallyThe annoying need to do manual updates after each commitSubversive mostly works in any of these cases. And when it doesn't want to keep track of me moving some directory around, it politely asks me to commit before continuing.

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com4tag:blogger.com,1999:blog-10870752.post-43142879817173282852007-03-08T10:42:00.000+01:002007-05-12T12:14:04.004+02:00

I just spent the better part of the morning trying to make javadoc links work. In short: configuring the proxy did not work - We have to cope with offline package-lists, not a big problem really. Of course, to configure the maven-javadoc-plugin to do this, reading the source was the quickest way to go. So put something like this in your pom.xml:<reporting> <plugins> <plugin>

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com1tag:blogger.com,1999:blog-10870752.post-57785849228660249702007-02-15T13:10:00.000+01:002007-02-16T09:35:35.932+01:00

If you use the jaxb binding (the default with the Maven-plugin) to generate you client proxies, to actually use your service, you have to instantiate a org.codehaus.xfire.jaxb2.JaxbServiceFactory instead of an org.codehaus.xfire.service.binding.ObjectServiceFactory. Otherwise the parameter names (wsdl:part@name) will be replaced with "in0"-elements by XFire - and the server will complain about an

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-90933347830757354212007-02-15T12:54:00.000+01:002007-02-15T13:09:51.839+01:00

Today I realised, how important it became for any open-source project to play nicely with the Maven repository and to get its dependencies right in its pom's . When I had to whip up a web-service client yesterday, I started out trying Axis-2 since I knew the server impl was bases on Axis. Quickly I had to decide to either start debugging their maven-plugins dependencies (obviously wsdl4j was lost

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-46924368880633458492007-02-11T17:56:00.000+01:002007-01-15T06:44:05.262+01:00

Finally, I got around to enhancing the hivedoc-plugin with: Support for sub-modules Removal of empty columns in the module-summary table.The new version 1.0.2 should be on the central repo as soon as MAVENUPLOAD-1377 is resolved.

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-26889639613745414162007-01-08T16:33:00.000+01:002007-01-09T10:38:58.963+01:00

We're using Maven 2 now for all new projects. At the highest level I can summarize our experience as:The concepts behind Maven are sound and amazingly useful.The implementation is just about usable - no show-stoppers anymore, but lots and lots of little, annoying bugs and surprising gotchasThe documentation is sloppy.The really funny thing is, how point 1. still by far outweighs the shortcomings

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com4tag:blogger.com,1999:blog-10870752.post-30100612069762641182007-01-05T08:49:00.000+01:002007-05-12T12:14:04.004+02:00

Since some people seem to use it, I've updated my hivedoc-plugin to version 1.0.1 . Notable changes are:Support for custom resource root directoriesBackport to Java 1.4proper plugin-docsThe new version should show up on the central Maven 2 repo soon. If you need it before that, here's the repo-bundle.

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-67023328210573602642007-01-02T10:42:00.000+01:002007-05-12T12:16:33.355+02:00

If you're using HiveMind and Maven 2, generating docs for your HiveMind descriptors is now really quick and simple.Find the docs under http://marcus-schulte.ch/hivedoc-plugin/.

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-1158349104857777412006-09-15T21:26:00.000+02:002007-05-12T12:15:12.760+02:00

Version 0.3.3 of Honeycomb is released.Honeycomb provides an easy integration for Tapestry and Hibernate. Its distinguishing key feature is session-per-conversation support.The main changes in this release are:re-structuring into 4 libraries replaced the templates for the Core/Webapp projects with maven archetypes. Maven users get started without manual downloads.Fixed rollback on

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com13tag:blogger.com,1999:blog-10870752.post-1156621162566510562006-08-26T21:15:00.000+02:002006-08-26T21:39:23.053+02:00

Maybe it's just my organization's policy of giving its developers relatively free access to db's while, at the same time, putting lots of administrative hurdles and hurdle-like administrators between them and the app-server. But it's really amazing how little there is that you can't get done nicely with a sturdy db and a decent servlet-container (at most).Example: For some time I thought a nice

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-1141022621918048532006-02-27T07:35:00.000+01:002007-05-12T12:15:12.761+02:00

Kickstart has moved from SourceForge to JavaForge, and it's changed its name to Honeycomb (alluding to the central role that HiveMind plays in it). Honeycomb integrates Tapestry with Hibernate for painless full-stack web-dev-support.New features comprise A hibernate DataSqueezer Pluggable Audit-Trail via hibernate interceptor Support for session per request pattern via simple config

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com1tag:blogger.com,1999:blog-10870752.post-1137348545344477152006-01-15T18:58:00.000+01:002007-05-12T12:16:33.356+02:00

I've uploaded a new release of KickStart. Improvements are: Full support for the hibernate-session-per-conversation pattern. See hibernate.org for more. fixed wrong unsaved-value-mapping

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-1136661477462955342006-01-07T19:55:00.000+01:002007-05-12T12:16:33.357+02:00

While Web-Development with Java is supported by a variety of great frameworks it is still not easy (even tedious) to, firstly, choose the right ones for a given problem and, secondly, make them work together. (needless to refer to all the envious appraisals of RoR and, yes, even Visual-Studio by Java-developers). I've set up a Sourceforge project, called KickStart, (first download available right

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com1tag:blogger.com,1999:blog-10870752.post-1130075237263209312005-10-23T15:46:00.000+02:002005-10-23T15:47:17.270+02:00

The new enhancements in Oracle JDBC 10g promises to simplify the insertion and retrieval techniques for the CLOBs using the standard APIs. Handling Clobs in Oracle 10g Just discovered the above link after trying to use Oracle's thin JDBC-Driver with Hibernate to save CLOB-data ... This automatically and silently nullifies the CLOB-field when you try to save more then 4k to it which you are

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com1tag:blogger.com,1999:blog-10870752.post-1129741744966753712005-10-19T19:00:00.000+02:002005-10-19T19:09:04.973+02:00

Had some not so cozy hours debugging a productive app on Tomcat. The thing would spontaneously hang about once a day (The whole of Tomcat, apart from JMX was completely hung). It hung in an infinite wait in the Database-Pool. Funnily the default of the maxWait-Param is "-1", i.e. infinitely. Now, after I fixed this it runs nicely.But it's still not clear to me, where the total deadlock came from.

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-1128524930569450472005-10-05T16:56:00.000+02:002005-10-19T19:26:44.636+02:00

Like a lot of popular anti-patterns the scattered controller stems from the naive implementation of a seemingly obvious abstraction. The reasoning goes like this: Web-Apps show some html-page, each user event (http-request) triggers an action which, in turn, results in an event determining the next state which is either an action or a an html-page transferred back to the user's browser. So, use

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0tag:blogger.com,1999:blog-10870752.post-1127839309570190472005-09-27T18:27:00.000+02:002007-05-12T12:16:33.357+02:00

Handling Hibernate-Sessions is a recurrent topic on the Tapestry users mailing list. Still, long sessions seem to be surprisingly unknown, once one considers the fact that Gavin King advocates its use in "Hibernate in Action".So, I've posted some code implementing the Long-Session-Pattern in Hivemind on the Hivemind-Wiki.I'd be curious to hear whether it worked for anyone (or why it didn't) ...

Anonymoushttp://www.blogger.com/profile/13079542031575873570noreply@blogger.com0