You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@airavata.apache.org by "Lahiru Gunathilake (JIRA)" <ji...@apache.org> on 2011/07/15 00:35:59 UTC

[jira] [Updated] (AIRAVATA-27) MessageBroker Integration with embedded derby database

     [ https://issues.apache.org/jira/browse/AIRAVATA-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lahiru Gunathilake updated AIRAVATA-27:
---------------------------------------

    Attachment: diff.out

This patch is for derby support and some other issues, created in airavata Jira. I will put comments on each issue by pointing to AIRAVATA-27. I was able to get it working with derby with this patch but I do not consider this as a final version of the derby implementation. I thought of providing a patches one by one and improve the embedded derby implementation. 

If patch looks good please apply this patch in ws-messenger location and add the newly added file in to svn too.

Regards
Lahiru

> MessageBroker Integration with embedded derby database
> ------------------------------------------------------
>
>                 Key: AIRAVATA-27
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-27
>             Project: Airavata
>          Issue Type: Sub-task
>          Components: WS-Messenger
>            Reporter: Suresh Marru
>         Attachments: diff.out
>
>
> Message Broker receives subscription requests and publishes messages and stores it in two tables for a mysql database. These default databases should be changed to Derby and all test cases should be verified to work.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira