[
http://issues.ops4j.org/browse/QI-202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12133#action_12133
]
Tonny Kohar commented on QI-202:
--------------------------------
Ignore the above comment, browsing the mailing list, I got the definition of
SPI and API
"API would be defined as "All service interfaces which are visible for layer
or application" and SPI would be defined as "All service dependencies which
are not satisfied from within the module". And then similar for Layer. This
way you can select a Module/Layer and immediately see what it produces as
output and requires as input. This is also very very nice for documentation
purposes."
The next question, is there any public api in the model to query the above ? If
there is no public api in the model, I think I will just traverse the model and
collect that info
> Layer and Module detail tab info
> --------------------------------
>
> Key: QI-202
> URL: http://issues.ops4j.org/browse/QI-202
> Project: Qi4j
> Issue Type: Improvement
> Components: Envisage
> Reporter: Tonny Kohar
> Assignee: Tonny Kohar
>
> Layer and Module detail tab info.
> So what will be the implementation
> - new tabs (API and SPI)
> - or reuse existing tab (Dependency and ???)
> Mailing list opinion
> "I think this would fall under "Dependencies" (Required and Provided).
> The General tab for a Layer could list Modules present, and for a
> Module could list registered Composites and Objects. Or Not be present
> at all."
> "This is on Module and Layer, so a new pane and then new tabs for "API" and
> "SPI" respectively, would be good."
> WDYT ? which one I should implement ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
