|
From: Christophe B. <dz...@ho...> - 2002-05-06 09:02:18
|
Hi Riaan, I agree it could be confusing. Let me try to re-phrase the concept. The JPass server is the application which runs the SOAP methods and accepts the SOAP messages from the network. The server can be 1. Running on a trusted server on the internet. (Actually I would like to have a sample server on the internet where we can demonstrate the functionality, .....once ready of course:-). 2. On your home PC. This option seems very attractive, as you can manage the service, yourselve and don't need to trust on anyone else . The disadvantages I see however are that you need to install both the JPass server, Tomcat and a database like MySQL. BTW Michael is currently investigating a leigthweight database which could store native XML or potentially convert to SQL. The JPass client application can be: 1. a desktop client (like the current J2SE client, but could also be a win32 client). 2. a MIDP client application on a mobile 3. a Server side script, like JSP (Java Server Pages). 4. An embedded client which runs on the web server you wich to access. I am working on the client SOAP api. and an XSD traversal API. (To learn XML schemas and create XML). The SOAP api will be able to generate SOAP messages according to the JPass spec. (I hope to have some pre-alpha ready with a couple of weeks). When coding the server (1), you could start by writing the methods which receive the SOAP messages. The methods are equal to the SOAP messages. example: The getWSPlist SOAP message would look like: <?xml version='1.0'?> <env:Envelope xmlns:env="http://www.w3.org/2001/12/soap-envelope"> <env:Body> <wsp:getWSPlist xmlns:wsp="http://jpass.sourceforge.net" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://jpass.sourceforge.net/getWSPlist.xsd"> <wsp:Master_User></wsp:Master_User> <wsp:Master_Password></wsp:Master_Password> <wsp:wsData> <wsp:URL></wsp:URL> <wsp:ServiceCharge></wsp:ServiceCharge> </wsp:wsData> </wsp:getWSPlist> </env:Body> </env:Envelope> The method, handling this soap message is also called: public void getWSPlist() { // 1. code reading the SOAP message // 2. query the DOM with WSP examples. // 3. return a list of WSP's. } It's important to get the Deployment descriptors right, which point to the proper methods. (I hope you can put these in cvs), and Second you need to load a DOM, with example XML from the webservice-profile-jpass.xsd XML schema. After that you can try to create a class which looks up the SOAP request in the DOM. You can propably reuse the wpDOMengine file, like the Search method to get the right node back from the DOM. I will create an XML sample from the ws-jpass.xsd file, as I need it for the client aswell. ( i use the tool XML writer to create .XSD and XML but my trial license ran out....@$@%#... need an opensource XML editor. ) Any ideas from your side are of course most welcome. Cheers / Christophe >From: "Riaan Minne" <ar...@in...> >To: "Pietje puk" <dz...@ho...> >Subject: SOAP Specification >Date: Mon, 6 May 2002 00:07:54 +0200 > >Hi, hows it going? > >I went through our website, and somethings are a bit confusing. Looking at >the page explaining the server side development, it seems to suggest that >the service is running on the clients machine itself (looking at the first >diagram on the page). I also nee dinfo on the storage of these Profiles. >What DB are we using. Could you also send the necessary details on what >methods are needed, and the strucure on the data that is used as parameters >and returned by these methods. > >Just to set things clear. My knowledge of SOAP is more system orientated, >like networking and transport and how to use it in Java, not in the usage >xsd and xmi and so on (but i'm working on that). > >I got Tomcat and Apache SOAP working and has been coding simple server and >client using the samples as a base. > >I'm eager to hear from you again... > >Riaan Minne. > > _________________________________________________________________ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx |