Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Problem serializing Exceptions with OSGIObjectOutputStream

It seems that the 2018-12 M2+0 is on Friday Nov 2 [1].

For inclusion in the platform +0 release it would probably be best for us to do the build/release during the previous week...i.e. week of Oct 22nd.

I've scheduled our 3.14.4 release for Oct 26 [2].



On 10/15/2018 6:23 AM, Peter Hermsdorf wrote:

Thanks for the fix.

Before end of October would be good. We are still testing for more issues.

Bye Peter

Am 14.10.2018 um 00:39 schrieb Scott Lewis:
I've fixed the issue:

and added test code to verify.

I've also prepared the feature changes for a 3.14.4 release, which will go to M2, given that M1 came out last Friday.

I would like to hear about people's view of timing for 3.14.4.   I would like to wait a week or two (certainly before the end of October), so more testing can occur, but am willing to build/release 3.14.4 sooner if desired...and if Mat will agree to publish the new bundle to maven central.



On 10/12/2018 11:17 AM, Scott Lewis wrote:
On 10/12/2018 5:48 AM, Peter Hermsdorf wrote:

after upgrading to the latest ECF release i faced another problem with the "new" serialization.

Serializing Exceptions lead to StackOverflow errors.

I created a bug report with test case

Bonus question: What was the intention/use case/requirement for implementing "another serialization" (OSGIObjectOutputStream)?

To support OSGi R7 intents.   'osgi.basic' intent requires being able to serialize Version, DTOs and a few other OSGi classes [1] when they appear as arguments or return values.



Thanks, Bye Peter

ecf-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top