[#QRTZNET-84] Quartz's exceptions are not properly serializable when using remoting

Quartz.NET

Quartz's exceptions are not properly serializable when using remoting

Created: 07/Jan/08 08:51 AM Updated: 20/Jan/08 11:22 AM

Component/s:

Core

Affects Version/s:

0.9

Fix Version/s:

0.9.1

File Attachments:	1. deserializeErrors.patch (12 kB)
Environment:	.Net Framework 2.0

Flags:

Patch

Description

« Hide

When connecting to a remote Scheduler, exceptions are not able to be serialized to be sent to client.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Nik added a comment - 07/Jan/08 08:55 AM

Here is a patch to address the problem. I have simply added the proper constructors to all Exceptions that extend SchedulerException.

SchedulerException's new constructor simply calls the base (System.Exception) passing in the message parameter.

I have added the documentation generated by GhostDoc.

Please let me know if you decide to add this to the project - it will be my first open source contribution! (How's that for 2008 resolutions?)

Thanks,
Nik

[ Permlink | « Hide ]

Marko Lahma added a comment - 07/Jan/08 04:40 PM

More descriptive summary

[ Permlink | « Hide ]

Marko Lahma added a comment - 07/Jan/08 04:42 PM

Patch applied to trunk, added to AdoJobStore exceptions also