airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lahiru Gunathilake (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRAVATA-57) Consolidate XBaya Web Service Invoker Clients and Re-factor them to use Axis2
Date Wed, 10 Oct 2012 15:21:03 GMT

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

Lahiru Gunathilake resolved AIRAVATA-57.
----------------------------------------

    Resolution: Won't Fix
    
> Consolidate XBaya Web Service Invoker Clients and Re-factor them to use Axis2
> -----------------------------------------------------------------------------
>
>                 Key: AIRAVATA-57
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-57
>             Project: Airavata
>          Issue Type: Improvement
>          Components: XBaya
>         Environment: All OS
>            Reporter: Suresh Marru
>            Priority: Minor
>             Fix For: 0.5
>
>
> XBaya provides a high-level workflow description and various workflow engine specific
execution scripts are generated at deployment or execution time. Due to this abstraction,
XBaya supports multiple enactments each using different web service invocation clients. Most
of them currently use XSUL based WSIF invokers. These clients should be consolidated for easy
maintenance and ported to use AXIS2 based invokers. The clients should work with any standard
SOAP based services generated by popular frameworks like Axis2, CXF, XSUL, SOAP-Lite. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message