[
https://issues.apache.org/jira/browse/AIRAVATA-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285111#comment-13285111
]
Suresh Marru commented on AIRAVATA-430:
---------------------------------------
I understand the pain in re-creating the workflow, but I think allowing to load
it will lead to other side effects. This is a critical bug, that XBaya should
not allow incorrect workflows should be constructed and saved in the first
place. We probably should take this as a one off situation and raise the JIRA
level and fix it so the type compatibility is strictly checked at construction
time.
> Not able to load workflow created by Airavata Xbaya
> ---------------------------------------------------
>
> Key: AIRAVATA-430
> URL: https://issues.apache.org/jira/browse/AIRAVATA-430
> Project: Airavata
> Issue Type: Bug
> Components: XBaya
> Affects Versions: 0.4-INCUBATING
> Reporter: Raminderjeet Singh
> Attachments: ODI_Prototype_Workflow.xwf
>
>
> while loading workflow i am getting following error
> org.apache.airavata.workflow.model.graph.GraphException: The type
> ({http://schemas.airavata.apache.org/gfac/type}URIParameterType) must be
> same as the type
> ({http://schemas.airavata.apache.org/gfac/type}StringParameterType) of
> Exposure_Split_invoke_in_0.
--
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
