[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ecf-dev] Problem serializing Exceptions with OSGIObjectOutputStream
|
I've fixed the issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=540082
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.
Thanks,
Scott
On 10/12/2018 11:17 AM, Scott Lewis wrote:
On 10/12/2018 5:48 AM, Peter Hermsdorf wrote:
Hi,
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
https://bugs.eclipse.org/bugs/show_bug.cgi?id=540082
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.
Scott
[1]
https://osgi.org/specification/osgi.cmpn/7.0.0/service.remoteservices.html#service.remoteservices-osgi.basic
Thanks, Bye Peter
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev