You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org> on 2011/08/02 16:03:27 UTC
[jira] [Created] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
ASM90005 error when a deployable composite is used as the implementation of another deployable composite
--------------------------------------------------------------------------------------------------------
Key: TUSCANY-3907
URL: https://issues.apache.org/jira/browse/TUSCANY-3907
Project: Tuscany
Issue Type: Bug
Reporter: Greg Dritschler
I have attached a test case with 2 contributions.
Contribution export1 contains a deployable composite with a java component.
Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
This test fails with message
SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
Here is what is happening:
1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
So the code is confusing a runtime update to the model for an external error.
This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
If subsequent contributions are going to reprocess import1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild C1.
In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13080256#comment-13080256 ]
Greg Dritschler commented on TUSCANY-3907:
------------------------------------------
I am no longer seeing the ASM90005 error and the test appears to be working.
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Assignee: Simon Laws
> Priority: Minor
> Fix For: Java-SCA-2.0
>
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079375#comment-13079375 ]
Greg Dritschler commented on TUSCANY-3907:
------------------------------------------
Composites are being cloned so this alleviates some of my concerns about the builder reprocessing the previously deployed composite. However it appears to me that ServiceImpl doesn't clone the binding elements. Maybe the solution is to clone the bindings and clear the @uri attribution. (I'm not sure it's safe to just change ServiceImpl.clone() to do this. I don't know if anyone could be cloning services and assuming the bindings remain intact.)
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Assignee: Simon Laws
> Priority: Minor
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Dritschler updated TUSCANY-3907:
-------------------------------------
Priority: Minor (was: Major)
Affects Version/s: Java-SCA-2.0
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Priority: Minor
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess import1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild C1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (TUSCANY-3907) ASM90005 error when a
deployable composite is used as the implementation of another deployable
composite
Posted by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079375#comment-13079375 ]
Greg Dritschler edited comment on TUSCANY-3907 at 8/4/11 1:37 PM:
------------------------------------------------------------------
Composites are being cloned so this alleviates some of my concerns about the builder reprocessing the previously deployed composite. However it appears to me that ServiceImpl doesn't clone the binding elements. Maybe the solution is to clone the bindings and clear the @uri attribute. (I'm not sure it's safe to just change ServiceImpl.clone() to do this. I don't know if anyone could be cloning services and assuming the bindings remain intact.)
was (Author: gregdritschler):
Composites are being cloned so this alleviates some of my concerns about the builder reprocessing the previously deployed composite. However it appears to me that ServiceImpl doesn't clone the binding elements. Maybe the solution is to clone the bindings and clear the @uri attribution. (I'm not sure it's safe to just change ServiceImpl.clone() to do this. I don't know if anyone could be cloning services and assuming the bindings remain intact.)
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Assignee: Simon Laws
> Priority: Minor
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Dritschler updated TUSCANY-3907:
-------------------------------------
Attachment: TUSCANY-3907-testbinaries.zip
TUSCANY-3907-testcase.patch
Test added to domain-node.
Patch file contains an update to the junit test.
Zip file contains new binaries needed for the test.
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Priority: Minor
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess import1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild C1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws closed TUSCANY-3907.
-------------------------------
Thanks for checking Greg
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Assignee: Simon Laws
> Priority: Minor
> Fix For: Java-SCA-2.0
>
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Greg Dritschler (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Dritschler updated TUSCANY-3907:
-------------------------------------
Description:
I have attached a test case with 2 contributions.
Contribution export1 contains a deployable composite with a java component.
Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
This test fails with message
SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
Here is what is happening:
1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
So the code is confusing a runtime update to the model for an external error.
This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
In other words, this validation error may be the least of the problem.
was:
I have attached a test case with 2 contributions.
Contribution export1 contains a deployable composite with a java component.
Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
This test fails with message
SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
Here is what is happening:
1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
So the code is confusing a runtime update to the model for an external error.
This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
If subsequent contributions are going to reprocess import1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild C1.
In other words, this validation error may be the least of the problem.
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Priority: Minor
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws reassigned TUSCANY-3907:
-----------------------------------
Assignee: Simon Laws
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Assignee: Simon Laws
> Priority: Minor
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (TUSCANY-3907) ASM90005 error when a deployable
composite is used as the implementation of another deployable composite
Posted by "Simon Laws (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Laws resolved TUSCANY-3907.
---------------------------------
Resolution: Fixed
Fix Version/s: Java-SCA-2.0
I've cloned the composite at the top level and added a change to clone bindings in references and services. I can't think of a reason why we should do that. There's a test now which I believe matches the scenario described in itest/implementation-composite/CompositeMultiStartTestCase. I've marked this as resolved Greg so can you give it a spin and close/re-open as appropriate.
> ASM90005 error when a deployable composite is used as the implementation of another deployable composite
> --------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-3907
> URL: https://issues.apache.org/jira/browse/TUSCANY-3907
> Project: Tuscany
> Issue Type: Bug
> Affects Versions: Java-SCA-2.0
> Reporter: Greg Dritschler
> Assignee: Simon Laws
> Priority: Minor
> Fix For: Java-SCA-2.0
>
> Attachments: TUSCANY-3907-testbinaries.zip, TUSCANY-3907-testcase.patch
>
>
> I have attached a test case with 2 contributions.
> Contribution export1 contains a deployable composite with a java component.
> Contribution import1 contains a deployable composite with a component that uses export1's composite as its implementation.
> This test fails with message
> SEVERE: [ASM90005] The SCA binding Helloworld on component HelloworldImplJavaComponent service Helloworld should not have a URI and the URI is currently set to /HelloworldImplJavaComponent/Helloworld
> Here is what is happening:
> 1) Contribution export1 is built. BindingURIBuilderImpl computes and sets the binding uri in its component services.
> 2) Contribution import1 is built. ComponentBuilderImpl processes export1's composite again, sees the binding uri is set, and issues the error because binding.sca does not permit external specification of @uri.
> So the code is confusing a runtime update to the model for an external error.
> This may be the tip of the iceberg of what could go wrong. export1 is deployed and could be active.
> If subsequent contributions are going to reprocess export1, a lot of care needs to be taken to not modify the model in a way that breaks active operations. It looks to me like the builder code thinks it has free reign to rebuild export1.
> In other words, this validation error may be the least of the problem.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira