In general, OSCP5 works fantastically! It is great to have such a simple clear clean library to handle this.

But there is one major flaw. When OSCP5 is handling an incoming OSC message, and encounters an error, it just throws a generic error message with no helpful information:

### [2011/4/17 14:37:30] ERROR @ OscP5 ERROR. an error occured while forwarding 

an OscMessage

 to a method in your program. please check your code for any 

possible errors that might occur in the method where incoming

 OscMessages are parsed e.g. check for casting errors, possible

 nullpointers, array overflows ... .

method in charge : oscEvent  java.lang.reflect.InvocationTargetException

In an extremely simple program, this might be sufficient. But for a program with any complexity, this is basically useless. At minimum, it's important to know which line number of which file is causing the error. Eclipse's other debug tools (stacktrace, variable-monitors, breakpoints, etc) would be useful as well. Instead, we're just being told "an error some kind occurred, now go figure it out."

Have others experienced this problem? Have any of you found a way around it? Does anyone have a favorite Java/OSC library other than OSCP5?

As I said above -- massive respect to the folks who've built OSCP5, it is an awesome library that has worked perfectly for me other than this one major problem.

Update, 5pm PT: After some more testing, I can clarify what's wrong. Breakpoints and variable-monitors actually work fine. I think the only problem is that OSCP5's handling of the InvocationTargetException doesn't show a useful stack-trace, or trigger Eclipse's pause/break in debug mode.