[wsf-c-dev] Embedding mysql to axis2/C

[Samisa Abeysinghe]

If it is about querying a database through a Web service, all that the
user would need to configure would be the tables to be queried and may
be the schema defining the table format. SELECT, INSERT etc are standard
operations? Why do we need to configure them?

I am still not very clear about what exactly you are going to do. Expose
the DB as a service? Can you please explain.

Samisa...

Diluka Moratuwage wrote:
> Hi,
>    Yes, i think its not very appropriate for the database
> owner to write that sort of a configuration file with lengthy
> opearation information.
>
>    Instead we can, generate some predefined set of functions,
> that implement sql queries such as SELECT, INSERT, ..... opon
> the database owner's need. He can specify, which of the queries,
> he needs to support in his database, when he specify the
> configuration file.
>
>    As an example, if the database owner needs to provide the SELECT,
> query, then he should specify that in the configuration file, and
> our module should generate the code that implement the query.
>
>    Then, we can have a wsdl file which fully describes the format
> of input and output, for each of the sql queries.
>
>    Suggestions are welcome..
>
> Thanks,
> Diluka.
>
>
>   
>> Diluka Moratuwage wrote:
>>     
>>> Hi all,
>>>         Relevent to embedding mysql into axis,
>>>       
>> Or Axis2/C into MySQL?
>>     
>>> we can make a seperate
>>> software module, which helps a database owner to expose his database's
>>> information, using a mysql database(or any other), as a webservice.
>>>
>>>         In order to use the module,  which we are going to implement,
>>> the
>>> database owner, needs to write a configuration xml file, which
>>> describes all the services which are exposed, and also the format,
>>> of how the input and output would be.
>>>
>>>         The following example shows, an example of a  simple
>>> configuration
>>> file, which might not contain all the information needed.
>>>
>>> <config>
>>>         <database>
>>>                 <host>
>>>                 </host>
>>>                 <usrname>
>>>                 </usrname>
>>>                 <password>
>>>                 </password>
>>>         </database>
>>>         <operations>
>>>                 <opname name="op1">
>>>                         <input>
>>>                                 <!-- This element describes the input
>>> message format>
>>>                         </input>
>>>                         <output>
>>>                                 <!-- This element describes the output
>>> message format>
>>>                         </output>
>>>                         </opname>
>>>                 <opname name="op2">
>>>                         <input>
>>>                         </input>
>>>                         <output>
>>>                         </output>
>>>                 </opname>
>>>         </operations>
>>> </config>
>>>
>>>
>>>       
>> This is almost like writing a WSDL manually :(.
>>
>> What are we going to support with this module? Querying the database
>> with SOAP requests or invoke stored procedures/ functions through SOAP
>> messages?
>>
>> Samisa...
>>
>>     
>
>
>   


-- 
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web 
Services Developers' Portal)