-
Sorry, I mean uploading the code, not the presentation :)
05:35AM UTC on Jul 09 2009 in undx
-
Hello Marc,
I read your presentation and it looks promising. Do you plan to upload it to SF anytime soon?
Thanks,
Peter.
05:32AM UTC on Jul 09 2009 in undx
-
This would be very nice to have, and it's likely trivial to implement.
I'm lefthanded and I use those keystrokes intensively, but get nasty surprises in SoapUI when Ctrl+Ins doesn't work, but Shift+Ins does, pasting some old clipboard content.
03:52PM UTC on Jan 22 2009 in soapUI
-
Sorry, I slipped in a bug: at line 501, it should be:
sb.append( buffer, 0, bufferIndex );.
10:08AM UTC on Jul 24 2008 in Json-lib
-
I've done some profiling over JSON marshalling and unmarshalling and it seems they are quite slow.
I set out to improving the performance and I can present a small victory: the improvement of JSONUtils.quote().
Changes:
- reorganized the switch/case
- eliminated charAt() calls
- buffered chars for bulk appends (this brings the biggest improvement)
- replaced StringBuffer with...
10:28AM UTC on Jul 17 2008 in Json-lib
-
Yes, that would also be an elegant solution.
However, in my case I found it more convenient to have them both in the same interface, for that would achieve a higher cohesion of the PropertyNameProcessor implementation.
Either way, I'm looking forward to the next release!
07:08AM UTC on Jun 19 2008 in Json-lib
-
To generalize, better support for deserialization customization is required, to mirror existing serialization functionality. E.g.: value processor, bean processor, etc.
08:18AM UTC on Jun 18 2008 in Json-lib
-
As I understand it, a PropertyNameProcessor allows a JSON key to be matched to a bean property name when deserializing JSON content to a bean.
However, it would be helpful to "close the circle", i.e. to have a way to also map bean properties to JSON keys when generating JSON content from a bean. Otherwise, round-trip (un)marshalling would be a problem.
Instead of defining a new interface...
02:08PM UTC on Jun 17 2008 in Json-lib
-
Scenario:
I have several bean classes, which contain properties of simple types, as well as collections and other bean types.
The properties of collection type are lazy, i.e. no setter is provided, only a getter that lazily instantiates the collection (actually, the code is generated this way via XJC).
I assumed that if I provide a custom PropertySetStrategy, I can control the way the...
01:51PM UTC on May 27 2008 in Json-lib
-
How about allowing units to escort other units?
This could be useful to defend weak units, such as wagon trains.
For instance, you could tell a dragoon to escort a wagon train, or a privateer to escort a merchantman.
Both units would then move with the speed of the slowest, in order to always have them stacked on the same tile. This would make it impractical e.g. to order an artillery...
11:00AM UTC on Aug 02 2007 in FreeCol
