On Thu, Jul 10, 2008 at 10:10 AM, Christopher Painter < [EMAIL PROTECTED]> wrote:
> I know this won't directly answer your question, but any chance you could > just switch to .NET? You could create a ComVisible(true) class that deals > with your XML/SOAP issues and exposes it to your unmanaged code. > > The reason I mention this is MSFT retired the SOAP SDK several years ago > and a lot of the merge modules that Microsoft has put out over the years > aren't all that great. > > Christopher Painter, Author of Deployment Engineering Blog > If that's what it takes we'll just do it in Java. We already have a large chunk of Java code in the project, and similar SOAP calls are already happening on the Java side. One bit of native code needed to do this SOAP call though, and it just didn't make sense to start up the JVM for this. Normally the calls are going in the other direction Java ->native, but this code can run independent of the Java front-end so it gets complicated. Thanks. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
