This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I tested out using a LightSpeed entity in a web service call last night and found it wasn't completely serializable. It broke on ValidationError which doesn't have a parameterless constructor. Should this occur? |
|
|
Thanks will take a look. Until then you could always go CSLA style and |
|
|
We are getting the same error / problem. Is there a fix for this? We are using the nightly build of the 2008-08-18 |
|
|
Sorry to be a nag but was wondering if this will be resolved at all or in the near future? Need to plan solution.
Thanks in advance, Alfred |
|
|
Hi Alfred, We have added in an internal parameterless constructor to ValidationError which caters for this issue, and it will be available in the nightlies numbered 20080827 and above. We have set up a test ASMX based web service which reproduces the original issue and this works happily with the new build - let us know how you get on with it. A couple of things of note:
Jeremy |
|
|
Thank you very much for this. Since I had to deliver a project I have already coded a Code generator that would create a new bunch of objects that where identical in member fields as the designer model (i used *.lsmodel xml file). With a member method to create one from the other (using partial classes for the conversion LS class to the mirror class). When converting from mirror object to an LS object I used the Id (or as defined in the .lsmodel file) to retrive from the xxxUnitOfWork and if not foudn create a new one and add it to the UOW object. Works a charm but now I'm going to reconsider if shipping LS objects is a better option all round. Depends if I can "deserialize" an LS object and how the LS library handles it (if at all). You know? |
|
|
Generally you are thinking of either remoting your objects or shipping DTO equivilants and then handling the marshalling in your service methods. We are currently looking more closely at how Lightspeed entities can be used in remoted scenarios, so would value your thoughts on this. Current nightly builds of Lightspeed support serializing your entites, so this is an option you could look at. In general we would recommend you look at a DTO based approach as this is going to give you the best end result, however if you do need to remote entities we have a sample that you can test out in the meantime; you can download it from here: http://www.mindscape.co.nz/forums/Post.aspx?ThreadID=1363&PostID=2386
Jeremy |
|