My design style is to split the business layer into 2 parts, the
Application layer (which contains all the publicly creatable classes)
and the Domain layer, which contains the actual objects that run
across applications (think of them as the pure business objects). The
Application layer handles th
Just in thinking about it something akin to the Whidbey ObjectDataSource
might be an answer to hand-coding all these conversions between your
business objects and web services??
Also, remoting will not work in my particular scenario as the clients can
be anything such as Axis/Java. My understandin
of advanced .NET topics.
[mailto:[EMAIL PROTECTED] Behalf Of Shawn A. Van
Ness
Sent: 18 November 2004 17:45
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] XML public property and constructor
serialization issues.
I advise people to give up bending their business o
nced .NET topics.
[mailto:ADVANCED-
> [EMAIL PROTECTED] On Behalf Of Shawn A. Van Ness
> Sent: Friday, 19 November 2004 4:45 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [ADVANCED-DOTNET] XML public property and constructor
> serialization issues.
>
> I advise people to give up bending their
I advise people to give up bending their business object models to
work with XmlSerializer. The constraints are pretty heavy...
http://www.windojitsu.com/blog/zenandtheartofxmlserializer.html
In addition to the need for public default ctors and public visibility
on all serializable fields, there
> 3. I assume that pushing the existing object's data into an xml
> serialization/web service specific object before is a bad idea.
I'd examine that assumption *grin*. It's certainly a pain, but remember
that what's travelling over the wire is a message, not an object. A
message exposes data; an
Bassler
Sent: Thursday, November 18, 2004 8:44 AM
To: [EMAIL PROTECTED]
Subject: [ADVANCED-DOTNET] XML public property and constructor serialization
issues.
1. Can I do anything (like an xml attribute to mark the class with?) about
the requirement for the serialized classes to expose a defau
Towlson
White Carbon
-Original Message-
From: Unmoderated discussion of advanced .NET topics.
[mailto:[EMAIL PROTECTED] Behalf Of Eric Means
Sent: 18 November 2004 15:11
To: [EMAIL PROTECTED]
Subject: Re: [ADVANCED-DOTNET] XML public property and constructor
serialization issues.
I believe th
I believe that you can implement ISerializable and add a protected
constructor with a specific signature to get around your problems.
For instance, here's an EventArgs class:
///
/// The event handler for a general error event.
///
public delegate void ErrorEvent
I'm attempting to return from a web service an xml serialized version of an
existing business object. However, the design of this object is posing a
few challenges for the xml serializer.
1.It forces me to expose a public constructor in all serialized classes.
Specifically, I have several classes
10 matches
Mail list logo
