in
Forums
Blogs
Files
Devexpress.Com
ClientCenter
DevExpress Channel

XPO

eXpress Persistent Objects

July 2006 - Posts

  • XPO through XML Web Services - a new detail

    I have previously blogged about our knowledge base article AK3911, which describes an approach to tunneling XPO’s IDataStore layer communications through XML Web Services. There’s news in this regard – no special client is needed for this any longer. The feature has actually been around since version 6.1.4, but somebody forgot to tell us about it :-)

    How does it work? Very simple: the client-side functionality from the demo project of AK3911 has been integrated into XPO itself. That demo project implements a class called WebDataStore on the client side and uses that class to communicate with the Web Service on the server side. The Main method contains this code to build up the XPO data connection:

      XpoDefault.DataLayer = new SimpleDataLayer(new WebDataStore("http://localhost:2224/XpoGate/Xpo.asmx"));
    

    With the new feature, this is no longer needed, so the WebDataStore class can be removed from the demo project. Instead of the line above, the Main method should have this line:

      XpoDefault.DataLayer = XpoDefault.GetDataLayer("http://localhost:2224/XpoGate/Xpo.asmx", AutoCreateOption.SchemaAlreadyExists);
    

    XPO will find the extension .asmx on the end of the connection string URL and automatically connect to the given Web Service. On the server side, you can either go the lazy way that the knowledge base article suggests and only implement the two methods SelectData(…) and ModifyData(…) (in that case, make sure to use AutoCreateOption.SchemaAlreadyExists, as shown above), or you can implement all methods from the IDataStore interface for complete functionality.

  • NRW 06, Duesseldorf, Germany - The Community Conference

    Deutsche Leser, bitte den ersten Absatz überspringen!

    On July 27th I’m going to be in Düsseldorf, Germany, for NRW 06. This is a community conference, sponsored by Developer Express. I’m going to do a vendor session there, and I’ll be available all day to demonstrate all our technologies for .NET – come ask me about XPO, XAF, our controls for Windows Forms and ASP.NET, CodeRush, Refactor!… whatever you want. I’m looking forward to seeing you there. Right, did I mention it is only 5€? It’s only 5€!

    Am 27. Juli werde ich in Düsseldorf sein zur NRW 06. Das ist eine Community-Konferenz, die von Developer Express gesponsort wird. Ich werde dort eine Vendor-Session halten und ich bin den ganzen Tag verfügbar, um all unsere Produkte für .NET zu demonstrieren – kommen Sie vorbei und fragen Sie mich nach XPO, XAF, unseren Controls für Windows Forms und ASP.NET, CodeRush, Refactor!… was Sie wollen. Ich freue mich darauf, Sie da zu sehen. Habe ich erwähnt, dass die Veranstaltung nur 5€ kostet? Es kostet nur 5€!

  • XPO documentation - what do you need?

    Some recent e-mail conversations prompted me to want to find out even more about what’s currently lacking in our XPO documentation. Let me first say that we are already working on this, as much as time allows – no need to tell me that many are not perfect, I’m aware of that. Documentation for XPO brings with it a lot of challenges that we don’t face with other products, because as a framework library it’s meant to be extended, to be used as a basis for your own inventions. Of course our other products have an extensibility angle – but it’s not their raison d'être.

    Here’s how I want to classify the problems:

    1. Incomplete reference documentation – that’s easy – we’re constantly working on this, and if you find specific problems, please report them as bugs in support center. The online version of the product help is sometimes more current than what was delivered with the latest distribution.
    2. Documentation exists, but is hard to find. As far as I can see, this is a pretty big part. Documentation is currently in the online help, the knowledge base, support center issues, technical articles on the website, this blog, this blog and this blogour newsgroups and of course non-linkable resources like loads of other blogs or the sample code that comes with the distribution.
      Of course we are working on this problem as well, mainly by trying to consolidate information as much as possible in our product help.
    3. Documentation we don’t know is missing. Obviously, when writing product documentation, we write stuff about our product (duh). But the whole topic of object/relational mapping is complicated in itself. Even more importantly, working with (or creating) domain object models is something that many people have never done. For many applications you don’t need to be an expert in one or the other, but I’m sure there are many programmers out there who really have questions belonging into one of these blocks, so to make XPO more easily accessible for these people, we should probably extend our documentation to include this kind of information, even if it’s not XPO specific.

    I would like your help with (3) (or maybe (4)?). Please let me know what your problems are (or were) and what you think how they could be solved from our side. Feel free to comment on this post, to send me e-mail or to provide feedback any other way. I’m looking forward to hearing from you!

Copyright © 1998-2008 Developer Express Inc.
ALL RIGHTS RESERVED