Hi Scott, You build it, I'll buy it!
As usual, you put more thought into your response then I did my question. The wrapper would be the icing on the cake! What prompted my question is the added abilities of Flash Professional 2004. They have added a ton of Webservices to the product. One of which is to read a WSDL and bind to the form fields. (I'll stop here before my lack of knowledge shows through and I embarrass myself!) Anyway, I see flash forms with server side Witango as a very powerful combination with lots of possibilities now that Macromedia has streamlined the development process. And of course they are pushing Coldfussion as the preferred server. Scott, if you can have it ready by Monday we can show it off at Comdex! Chuck Lockwood ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ LockData Technologies, Inc. 309 Main Avenue, Hawley, Pa 18428 570-226-7340 ~ Fax: 570-226-7341 [EMAIL PROTECTED] ~ www.lockdata.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > -----Original Message----- > From: Scott Cadillac [mailto:[EMAIL PROTECTED] > Sent: Wednesday, November 12, 2003 2:24 AM > To: [EMAIL PROTECTED] > Subject: Re: Witango-Talk: TCF --> WSDL > > > Hi Chuck, > > I've got bits and pieces of something along these lines, but I > just haven't found time to > finish it. This is not a small project, so I'd like to know as > well if anybody else is > working on something similar? > > You've asked the right question Chuck. But the part that is > missing is the step between WSDL > and TCF which is the HTTP/SOAP callable wrapper. > > My thinking is to create a "Wizard" style application that reads > in a selected TCF (with all > the defined functionality you create in Witango code), and the > Wizard spits out a generated > TAF file as the wrapper to expose the TCF's Methods (and their > input/output Parameters) for > the Web. > > The TAF wrapper would of course translate the HTTP/SOAP request > and response to and from the > TCF. This is what constitutes exposing a TCF (or COM or Bean for > that matter) as a Remote > Object or Web Service. > > The Wizard would also generate the WSDL. A WSDL file is the > "definition" of a TCF's Methods > in SOAP readable format (i.e., XML). > > Having something like this that supports the SOAP standard > dynamically for Witango Classes > would be better than writing one-off custom SOAP implementations > everytime - wouldn't you > say Chuck? > > With enough work, the Wizard could "publish" a TCF as a Service > in a few mouse clicks. In an > ideal world it would be great to have this as part of the Dev > Studio. But starting as a 3rd > Party product is good too :-) > > Any comments? > > Scott Cadillac, > Witango.org - http://witango.org > 403-281-6090 - [EMAIL PROTECTED] > -- > Information for the Witango Developer Community > --------------------- > > XML-Extranet - http://xmlx.ca > 403-281-6090 - [EMAIL PROTECTED] > -- > Well-formed Development (for hire) > --------------------- > > > -----Original Message----- > From: "Chuck Lockwood" <[EMAIL PROTECTED]> > To: "WiTango-Talk" <[EMAIL PROTECTED]> > Date: Tue, 11 Nov 2003 11:58:09 -0500 > Subject: Witango-Talk: TCF --> WSDL > > > Has anyone created a utility to create a WSDL for a TCF? Is it > > possible, as > > does the Soap Toolkit on a COM object? > > > > Thanks, > > > > Chuck Lockwood > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > LockData Technologies, Inc. > > 309 Main Avenue, Hawley, Pa 18428 > > 570-226-7340 ~ Fax: 570-226-7341 > > [EMAIL PROTECTED] ~ www.lockdata.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > _______________________________________________________________________ > > _ > > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
