commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oliver Heger <>
Subject [configuration] Serializable configurations
Date Sat, 23 Aug 2014 16:25:17 GMT
Hi all,

we are slowly getting closer to a first alpha release of [configuration]

There is still one thing which should be changed IMHO: Currently, most
configuration implementations are tagged as Serializable - there is
still open with
a long discussion about pros and cons of serializable configurations.

The problem is that it is by far not as simple as just declaring an
*implements Serializable* (which was done in 1.x). Because a
configuration object usually has a bunch of references to other (non
serializable) helper objects it cannot be written out using standard
serialization mechanisms.

I therefore would like to remove such implements clauses. When - and if
- we decide how to handle serialization they can be added again. But
they cannot be removed without breaking binary compatibility; so now is
a good time for dropping them.

Any objections?

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message