Web services concept uses WSDL file to describe the service and SOAP as a transport protocol. That WSDL file is essentially your 'simple declarative file'. You then register your service with a public or private UDDI registry via the WSDL file and your services/methods/functions/calls are available to the world. My sense is ejb is the middle-tier machine and this web services technology will provide b2b or xml portal or (how many buzz words can we throw in here?). Yes, parsing overhead and wrapper et al is not trivial so you don't use SOAP as a generic internal interface, but I believe it will become a key platform neutral external interface. (BTW, I've seen references of 40-400 rough-rough-rough calls per second w/ SOAP). Do we need to beat on this in jBoss now? No. As others have noted it's just another external API into our box. ALSO ALSO ALSO (wow), SOAP is keyed to XML Data Schema and that's much more powerful than DTD, so.... the parsers are having trouble. Check out comparisons of SOAP parsers. For trivial stuff they play nice together. But for arbitrarily complex input/output forget it. I'm running my mouth/fingers, but this is an interesting area for me. Heitzso -----Original Message----- From: James Cook [mailto:[EMAIL PROTECTED]] At that point, I would think it would be a simple matter to expose any ejb method by using a simple declarative file. jim _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
