like I said this stuff is all new to me.... Clients will be accessing known Web Services and will be provided information about the service (like message layout). Will probably implement WSDL/UDDI down the road. Does the client really care how the service is being processed? Just need a service that can process specific SOAP messages.
Paul Faulkner -----Original Message----- From: Pae Choi [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 19, 2002 4:07 PM To: [EMAIL PROTECTED] Subject: Re: general question about AXIS How would your external client access your Web service(s)? Shouldn't you consider things other than "only requirements" such as: + RPC-style or Document-style? + If RPC-style is the choice, will your clients all agree to write program, perhaps AXIS compatible client, to communciate your Web service(s)? + Will your client be arbitrary prospectives in public? If so, will you be able to predict how they will discover your Web service(s)? + ... But since you have mentioned that "only requirements" are Java and AIX. Axis will do among many others. Pae ----- Original Message ----- From: "Paul Faulkner" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, November 19, 2002 11:20 AM Subject: general question about AXIS > I have very general question. We have several systems that we wish to SOAP > enable, our plan is to create a web service that communicates with these > systems and allow external SOAP clients to access them. > > I am very new to this technology, is AXIS a good place to start? The only > requirements we have is for the Web service to run on AIX and would prefer > to use JAVA as our language. > > Appreciate and feedback, comments, etc... > > thanks, > > Paul Faulkner >
