[
https://issues.apache.org/jira/browse/AIRAVATA-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408723#comment-13408723
]
Bhathiya Jayasekara commented on AIRAVATA-338:
----------------------------------------------
I'm facing a problem with getWorkflow(...) method implementation. The signature
of the method is as follows.
public Node getWorkflow(QName templateID, String userName)
This method returns a JCR Node object. Since current implementation uses JCR
API, it knows what JCR node is. But in the new API, jackrabbit is accessed
through Sling. So, the new API does not know anything about JCR Nodes. So
returning JCR Nodes is not possible. That's the problem I'm facing.
More details about this is mentioned in following post.
http://summerwithairavata.blogspot.com/2012/07/problem-in-implementing-getworkflow.html
> [GSoC] Integrate Apache Sling to Apache Airavata Registry
> ----------------------------------------------------------
>
> Key: AIRAVATA-338
> URL: https://issues.apache.org/jira/browse/AIRAVATA-338
> Project: Airavata
> Issue Type: New Feature
> Components: Registry API
> Affects Versions: 0.4-INCUBATING
> Reporter: Suresh Marru
> Assignee: Lahiru Gunathilake
> Priority: Minor
> Labels: gsoc2012, mentor
> Attachments: sling_api.patch
>
>
> Implement the Sling support for Apache Airavata, currently Airavata has an
> API to store/retrieve data from Jackrabbit, but its not scalable when to
> handle large amount of data because of keeping the session in the client
> side. Sling supports accessing Jackrabbit in REST full way. So we need to
> come up with another API which looks like the current API but uses jackrabbit
> through Sling Interface. The integration will require testing to ensure
> Airavata tutorials will work as is out of the box. The current data
> structures have limitations, so its strongly advisable to come up with
> hierarchical tree structure to store different data categories. Airavata
> community is very knowledgable on the requirements and will provide good
> inputs.
> User community & Impact of the software: Airavata is primarily targeted to
> build science gateways using computational resources from various
> disciplines. The initial targeted set of gateways include projects supporting
> research and education in chemistry, life sciences, biophysics, environmental
> sciences, geosciences astronomy and nuclear physics. The goal of airavata is
> to enhance productivity of these gateways to utilize cyberinfrastructure of
> resources (e.g., local lab resources, the Extreme Science and Engineering
> Discovery Environment (XSEDE), the Open Science Grid (OSG), University
> Clusters, Academic and Commercial Computational Clouds like FutureGrid &
> Amazon EC2). By using open community based software components and services
> like Airavata, gateways will be able to focus on providing additional
> scientific capabilities and to expanding the number of supported users. The
> capabilities of these gateways will offer clear benefits to society.
--
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
