Exposing my models as webservices
Nathan Kontny <Nathan.Kontny-UgwZ4owrJFB8UrSeD/[email protected]> Tue, 6 Jul 2004 16:08:52 -0700
| Newsgroups | gmane.comp.java.keel.devel,gmane.comp.java.keel.user |
|---|---|
| Message-ID | <[email protected]> |
Well, I was really attracted to Keel because I knew this type of situation was going to come up for my application: I need to expose the entire application as a set of webservices (this is because the client now longer wants a jsp/struts front end, but one in Flash. And I think the Flash GUI calling webservices might be the niftiest solution.). So hopefully my expectations worked out...but I have a couple questions. How may I ask have people done this? From just a quick glance at clnt-axis, it looks like Keel basically just exposes a generic webservice and it expects a model name plus whatever params the model is going to need. So you had to hand-roll your WSDL file to describe what those parameters are (can't use Java2WSDL of course). But isn't that a pretty messy service description for that one webservice if you want to expose a bunch of models. There would be lots of optional elements in there that only get used depending on which model was specified. Maybe I could break it out in the wsdl file by naming each model as a different service, but then the client still has to make sure they call the service with the model name. An alternative I am thinking about is creating a Java class as a proxy to each model that I want to expose as a service (or group them in the proxy), and then deploy the proxies with traditional Axis tools like Java2WSDL. Thank you so much in advance. -Nate http://keelframework.org/documentation Keelgroup mailing list [email protected] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com