Thanks for the link -- The problem with Ja.Net, SOAP, and CORBA is that they're all "active" (request-response) protocols. I'm looking at least common denominator passive data exchange mechanisms that would let you serialize an object on one platform, and then deserialize a *conceptually* identical object on a different platform without respect to any particular transport or RPC model.
I'm sure the going in approach most folks would recommend in a case like this is to develop an independent XML Schema for a specific data interchange XML document and simply have the Java or .Net apps use their respective XML writers and readers to output or extract the data for their corresponding objects. The problem with this is that it's then up to the developers on each side of the "Great Divide" to navigate and query these XML documents and populate their own objects. Conceptually, this approach isn't very different from two apps sharing data through a relational database by each app having to execute their own SQL against a raw schema to build their own notion of the underlying object. You probably wouldn't take this approach today with databases because it's both error prone and lets schema and database API dependencies proliferate throughout the code. What you'd be more likely to do is construct database views, stored procedures, and reusable business objects that localize dependencies and enforce business rules. If you can map the different standard serialization schemas via XSLT, I would think you could begin to develop business objects on either platform that closely or exactly mimic each other functionally, and that can share data via their respective platform's built-in serialization capabilities without having to manually develop a lot of specific custom XML schemas for data exchange. Bill Watkins Applications Architect Boeing Space and Communications - Houston "Any opinions are my own and do not represent those of Boeing." -----Original Message----- From: Duncan Godwin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 07, 2002 7:58 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Java / .Net interfaces via XML serialization? This product provides bridge between the .NET and Java world using Remoting. http://www.intrinsyc.com/products/bridging/janet.asp Duncan ----- Original Message ----- From: "Watkins, Bill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, May 07, 2002 12:27 AM Subject: [ADVANCED-DOTNET] Java / .Net interfaces via XML serialization? > Is anyone aware of any efforts going on to bridge Java and .Net objects via > their respective XML serialization interfaces, i.e., JAXB (still in > development) on the Java side, and XMLSerializer on the .Net side? It seems > like it should be possible to come up with some standard XSLT to facilitate > going back and forth between the two formats. > > Bill Watkins > Applications Architect > Boeing Space and Communications - Houston > > "Any opinions are my own and do not represent those of Boeing." > > You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
