You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@airavata.apache.org by "Suresh Marru (JIRA)" <ji...@apache.org> on 2011/08/02 15:21:28 UTC
[jira] [Created] (AIRAVATA-57) Consolidate XBaya Web Service
Invoker Clients and Re-factor them to use Axis2
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
Environment: All OS
Reporter: Suresh Marru
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AIRAVATA-57) Consolidate XBaya Web Service
Invoker Clients and Re-factor them to use Axis2
Posted by "Chathura Herath (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chathura Herath updated AIRAVATA-57:
------------------------------------
Component/s: XBaya
Priority: Minor (was: Major)
> 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.3-INCUBATING
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AIRAVATA-57) Consolidate XBaya Web Service
Invoker Clients and Re-factor them to use Axis2
Posted by "Suresh Marru (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Suresh Marru updated AIRAVATA-57:
---------------------------------
Fix Version/s: 0.3-INCUBATING
> 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
> Environment: All OS
> Reporter: Suresh Marru
> Fix For: 0.3-INCUBATING
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AIRAVATA-57) Consolidate XBaya Web Service
Invoker Clients and Re-factor them to use Axis2
Posted by "Chathura Herath (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171173#comment-13171173 ]
Chathura Herath commented on AIRAVATA-57:
-----------------------------------------
This task is too broad. We currently have the SimpleInvoker with axis2 . I suggest we set specific goals for this task like;
1) Unsecure asynchronous invoker - Done
2) Secure GFac Invoker
3) Secure Asynchronous invoker
As it seem remaining tasks have security goal dependency. So this will be differed till security discussion.
> 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
> Environment: All OS
> Reporter: Suresh Marru
> Fix For: 0.3-INCUBATING
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AIRAVATA-57) Consolidate XBaya Web Service
Invoker Clients and Re-factor them to use Axis2
Posted by "Lahiru Gunathilake (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AIRAVATA-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lahiru Gunathilake updated AIRAVATA-57:
---------------------------------------
Fix Version/s: (was: 0.3-INCUBATING)
0.5-INCUBATING
> 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-INCUBATING
>
>
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira