Unimplemented

@Tomasz, Thanks for the explanation. Still, I am ...

2009-11-02T23:15:47.213+01:00

@Tomasz,

Thanks for the explanation.
Still, I am not convinced.
I am neither objective nor representative here, as I am a (somewhat highly) technical guy. However I personally would prefer a sentence or two of the explanation what is going on including the stack trace on demand (in a separate collapsible details section or a popup) - I don't believe in security which is based on hiding underlying technology ;) - rather than just a beautiful page with a totally cryptic 20-character-long string. Thus, you deprive your users from guessing what is wrong on their own.
I believe that in some environments it is desirable. I live though is somewhat different area.

WRT logging such identifier - I can understand it, especially if you cannot have line information in production. In most of the circumstances though I'd rather see full stack trace info with line numbers.

Error reporting directly from a web page is something really great. We start here often from implementing this as the first feature of the app (the second being auto-update for desktop apps ;)).

Anyway your presentation was really good and your advice priceless for many folks.

Hi Wojtek. I'd like to clarify what I believe is ...

2009-10-19T16:01:25.620+01:00

Hi Wojtek.

I'd like to clarify what I believe is a small misunderstanding of the point I made during my presentation on exception handling. I assume that I wasn't clear and sharp enough during the presentation, so I'll try again here, hopefully with better result.

What I proposed (and what we at e-point put in our error handling code) is that on every exception handled by global exception handler application should do the following:

1. Generate "unique enough" exception identifier. You don't need proper uniqueness (as in e.g. UUID). Using org.apache.commons.lang.RandomStringUtils.randomAlphanumeric(20) is good enough.

2. Log exception with this identifier and any additional information in application log for future inspection.

3. Generate error page, with identifier prominently displayed. No stack traces, no ORA-XXXX internal codes or any other technical stuff. These should go into log during step 2. Only error message, explanation what to do next, and our freshly generated identifier.

This way users are not overwhelmed with technical details (also, as a bonus you don't leak "security sensitive" information about your internal implementation). However, if a user reports an error to our service desk and provides us with that generated identifier, that basically solves for us the problem of pinpointing in the logs the exception corresponding to this exact ticket.

Not everything is rosy of course. Users often do not report errors, just leave the site. Or hit refresh button a few times and then call a hot line. Or attach a screen shot with error page instead of copying identifier as a text. That's why you should consider putting little JavaScript on your error page, that implements "One-Click-Via-eMail-Error-Report(tm)" feature. Basically just generate proper "mailto:" link that contains generated identifier in e-mail title or body.

Hope that makes my position clear. If you don't agree and/or have other suggestions I'd like to hear about them.

Thanks for your time.

Tomasz Skutnik

On Agile Contracts: Have you read http://agilesoft...

2009-10-18T16:32:35.830+01:00

On Agile Contracts: Have you read http://agilesoftwaredevelopment.com/blog/peterstev/10-agile-contracts ?

Great talk on JDD! I really enjoyed it. Not to men...

2009-10-16T21:44:59.834+01:00

Great talk on JDD! I really enjoyed it. Not to mention great pictures selection :)

I wish I could have good tools support for lightweight code review process, but my company's software process team (bla bla bla) are trying to enforce fagan's way [and I'm not working for NASA or sth].

For people interested in more about Agile2009: Mar...

2009-10-01T22:21:32.499+01:00

For people interested in more about Agile2009: Mark Levison put together a massive post of all the Agile2009 retrospectives (including mine), session summaries and more at http://www.notesfromatooluser.com/2009/09/agile-2009-post-roundup.html.

Thank you Mark!

Yeh... Since 2008 some things change to the better...

2009-09-28T13:26:04.548+01:00

Yeh... Since 2008 some things change to the better state.
APache Commons Compress work pretty fine for now: unicode files, compressed with it - can be decompressed with WinZip or 7zip successfully.

@Giora: thanks for your clarification. Indeed I di...

2009-09-24T11:59:02.943+01:00

@Giora: thanks for your clarification. Indeed I didn't put it probably clear enough. I understood from your presentation that F2F is crucial, but as it's not always possible and cost-effective we have to use various tools to support communication and alleviate the need of regular direct F2Fs.

I wanted to add a quick note. At Agile2009 I pres...

2009-09-24T10:36:51.010+01:00

I wanted to add a quick note. At Agile2009 I presented about way to help overcome the challenges of distributed teams. Ambassadors represents people - have representatives of teams collaborate and share face-2-face. The presentation was about Ambassadors and Carrier Pigeons which are tools - we can also leverage collaboration tools to help bridge the gap. In your summary you state "The speaker is convinced that only by meeting face to face" - in fact the presentation itself was about leveraging tools to help too.

Giora Morein

As far as I know you can change directory layout i...

2009-09-16T14:14:48.980+01:00

As far as I know you can change directory layout in pom setting explicitly source or resources directory.

Thanks for the post. ${project.version} actually w...

2009-09-01T21:17:33.436+01:00

Thanks for the post. ${project.version} actually works for me once I have renamed the file to downloads.apt.vm.

It could be just a mistake. It happens very often ...

2009-07-01T20:34:00.399+01:00

It could be just a mistake. It happens very often on big sites and reporting broken links and missing docs can only help.

Make JLabel draw ellipsis to the left of the text:...

2009-06-15T13:14:12.842+01:00

Make JLabel draw ellipsis to the left of the text: thanks for this evil hack. Why Java has not methods for this?

Or you could get one of those and save yourself th...

2009-04-17T12:55:00.000+01:00

Or you could get one of those and save yourself the hassle:

http://www.apple.com/macpro/

You barely hear any noise coming out of that beast.

Greg definitely convinced me that writing robust, ...

2009-03-27T18:36:00.000+01:00

Greg definitely convinced me that writing robust, scalable software is far from being simple, but you can actually achieve a lot without resorting immediately to distributed computing.

Have they convinced you that Jetty is the best?Esp...

2009-03-27T11:19:00.000+01:00

Have they convinced you that Jetty is the best?
Esp, comparing with Tomcat?

Ah there it is. Thanks so much for this fix, I ne...

2009-03-20T17:27:00.000+01:00

Ah there it is. Thanks so much for this fix, I never would have worked it out.

Tak sobie poczytałem, i jako pracownik innego (tró...

2009-03-10T00:41:00.000+01:00

Tak sobie poczytałem, i jako pracownik innego (trójmiejskiego) sklepu komputerowego - przyznać niestety muszę rację ESC. Jeżeli sprzęt zakupiony w sklepie komputerowym JEST SPRAWNY (na przykładzie komputera "wystawowego") - to nie ma PRAWNEJ możliwości zwrotu/wymiany monitora na inny. Rozmawiałem ze znajomym z ESC w tej sprawie - i jasno wynika: klient, który oskarża sprzedawcę o kłamstwo/oszustwo - nie może oczekiwać, że każdy z pracowników sklepu będzie go całował po nogach i "szedł mu na rękę".

Too many loops and the HotSpot will change the out...

2009-02-22T19:58:00.000+01:00

Too many loops and the HotSpot will change the outcome ;-)
Such microbenchmarks are very fragile anyway.

The problem with HashSet/array was different then the one from the post, I just mentioned it as an argument against implementing arrays over HashMaps.

The HashSet performance problem was one of top performance bottlenecks reported by profiler - 30ms do make difference when invoked in a loop.

Funny ;) Well my conclusion is that it only makes ...

2009-02-22T18:57:00.000+01:00

Funny ;) Well my conclusion is that it only makes sense when the array size is less than 12. With number greater than this HashSet was basically faster (change LOOPS to 100000 to see something) - Java(TM) SE Runtime Environment (build 1.6.0_11-b03)

Was it really such a big problem for you that you had to re-implement Vector? :) Is the gain of 30 ms (during 100K iterations) worth such overengineering?

The smaller value of 20, the more visible the diff...

2009-02-22T15:06:00.000+01:00

The smaller value of 20, the more visible the difference.

import java.util.Random;
import java.util.Arrays;
import java.util.Collections;
import java.util.HashSet;

public class PerfTest {
public static final int LOOPS = 1000;

public static void main(String[] args) {
long[] data = createData(20);
long[] search = createSearch(data);
HashSet<Long> set = new HashSet<Long>(data.length);
for (long l : data) {
set.add(new Long(l));
}

int hitCount = 0;

long t1 = System.currentTimeMillis();
for (int i = 0; i < LOOPS; i++) {
for (long l : search) {
if (Arrays.binarySearch(data, l) >= 0) ++hitCount;
}
}
long t2 = System.currentTimeMillis();
for (int i = 0; i < LOOPS; i++) {
for (long l : search) {
if (set.contains(new Long(l))) ++hitCount;
}
}
long t3 = System.currentTimeMillis();
System.out.println("T1 = " + (t2 - t1) + " T2 = " + (t3 - t2));

}

static long[] createData(int len) {
Random rnd = new Random();
long[] array = new long[len];
for (int i = 0; i < len; i++) {
array[i] = rnd.nextLong();
}
Arrays.sort(array);
return array;
}

static long[] createSearch(long[] data) {
Random rnd = new Random();
long[] array = new long[data.length * 2];
System.arraycopy(data, 0, array, 0, data.length);
for (int i = data.length; i < array.length; i++) {
array[i] = rnd.nextLong();
}
Collections.shuffle(Arrays.asList(array));
return array;
}
}

Could you post the test program you used to justif...

2009-02-22T12:43:00.000+01:00

Could you post the test program you used to justify "I did some experimentation with (Hash)Set of Longs vs sorted long[] array with binary search.
Turned out that for small sizes ( < ~100) binary searched array performed order of magnitude better then {Set<Long>} set.contains(new Long(value))"

I did some experimentation too and I don't agree with you - my results show that HashSet is faster than sorted array.

The default option can be changed by editing logwo...

2009-02-18T13:08:00.000+01:00

The default option can be changed by editing logwork.jsp (run a search from the root level of the installation) and removing the webwork 'if test' for the radio option for the 'set estimated time remaining', so that the it just reads "checked". In JIRA 3.12.3 the changes need to be made around line number 108 (though this may be different across different versions). Hope this helps :)

Problem is I wasn't aware I need to ask this quest...

2009-02-10T11:47:00.000+01:00

Problem is I wasn't aware I need to ask this question ;-)

you could just ask me - I knew that it didn't work...

2009-02-10T11:27:00.000+01:00

you could just ask me - I knew that it didn't work since forever. Stupid macs, shall we replace them with Lenovos? :)

Hi Pawel,this bug just got fixed. It will be avail...

2009-02-09T13:58:00.000+01:00

Hi Pawel,

this bug just got fixed. It will be available in ActiveMQ 5.3. I hope you'll enjoy it :)

Regards
Dejan