January 2003 - Posts
Why seal a class!!!! I mean, if I want to use it let me at least give it a shot; even if you know as a writer of a class that extending it may be impossible, at least let me try!!!
Ugghh... I'm just pissed. I would like to use the SoapClientMessage object from the System.Web.Services.Protocals namespace, but I can't because the class is sealed, and the .ctor is private... Can't do it... nope... Do not pass go... Do not collect $200.00.
Anyway, if anyone out there knows of a class in .NET that would allow me to take a SOAP encoded response message, serialize it into a class, then get the return value out let me know.
I should have known better than to attempt something like this @ 6:00 on a Friday =)
[Currently Playing: 311 - Music]
Micky and Kevin were working last night debugging a web service that was misbehaving. When I left them at 7:15, they were still frustrated and not any closer to figuring out what was going on. It turns out, they were bit by a "feature" of .NET that bit our team a several months ago.
Back in December of 2001, we pushed our first set of web services to QA. We set up all the client side web references to be dynamic; which we though was a slick feature. We modified the URL's in the app.config file and pushed then client over to QA. The testers did thier thing for a few days, inserting data, running queries, blah blah blah. Then, then went to reconcile some database stuff and noticed that none of thier data was in the QA database... hmmm... what happened?
Well, it turns out that the autogenerated proxy for web references has a somewhat disturbing behavior. If it cannot locate the key for the dynamic web reference in the client app.config, it will revert back to whatever URL was used when the Web Reference was orgionally created; in our case this was our dev instance, meaning all data was inserted into the dev database. So all the work the QA group did had to be redone! ugghh...
MS here is some input for the next patch release of VS.NET. Make the runtime throw an exception when the referenced key for dynamic web referance cannot be located! This will save us all much time and grief!!!
[Currently Playing: Primus - Frizzle Fry]
If you read a lot of blogs, you really need to try out Synderella. This is a great open source, C# based news aggragator. I stumbled upon it last week sometime, and have several people at work hooked on it... Not only does is let you hook up to rss feeds, you can also have it grab information from web pages. It's a nice app that puts others (feedreader, radio) to shame.
Ok... Here we go again... This is my 2nd attempt at being an active member of the blogging community, and hopefully this one will stick. I dropped my first blog for a number of reasons, primarily my frustration with the Radio software. Thanks Scott for providing space for my 2nd blogging effort.
History: I've been writing .NET code for a few years now. I was part of the .NET EAP effort early on and I still remember how stoked I was when I got my copy of the PDC release in August of 2000. Though I'm interested in J2EE, especially from the architectural side, I firmly believe .NET is the most productive and enjoyable development environment available.
I'm currently sitting watching the MS Webcast of the Architecture comparison of J2EE and .NET. The speaker is basically explaining why .NET whipped up on J2EE in the pet shop test. I must say I was a bit skeptical about the usefulness of webcasts like this at first, but this one has been very informative.
Anyway, more to come in future posts, including information about my upcoming book .NET Remoting, and many rants and raves about .NET, Java, UML, software design, portals, and anything else that is currently consuming my time...