Issue 77298 - Exported interfaces does not include XTablesSupplier
Summary: Exported interfaces does not include XTablesSupplier
Status: ACCEPTED
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL: http://api.openoffice.org/docs/common...
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-13 06:10 UTC by whitey04
Modified: 2013-02-24 21:07 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description whitey04 2007-05-13 06:10:08 UTC 
"::com::sun::star::sdbcx::XTablesSupplier" cross reference lists
"::com::sun::star::sdb::Connection" as a supporting service but Connection does
not list XTablesSupplier as an exported interface.
Comment 1 jsc 2007-05-15 15:13:49 UTC 
jsc -> fs: can you please check this issue
Comment 2 Frank Schönheit 2007-05-16 08:56:08 UTC 
fs->np:

Indeed,
http://api.openoffice.org/docs/common/ref/com/sun/star/sdbcx/XTablesSupplier-xref.html
claims that the css.sdb.Connection would support this interface, but
http://api.openoffice.org/docs/common/ref/com/sun/star/sdb/Connection.html does
not list it.

However, css.sdb.Connection includes the service
css.sdbcx.DatabaseAccessConnection, which in fact *does* include XTablesSupplier.

I'm not sure (and don't have an opinion about) whether it's correct behaviour
for autodoc to add the Connection to the "services supporting this interface"
section ... Please decide (together with JSC?).
Comment 3 whitey04 2007-05-17 04:55:53 UTC 
From a newbie:  I would expect the cross reference to exactly mirror the
exported interfaces.  However, having a reference to all services that
indirectly support it would be useful but it should be noted.
Comment 4 nikolai.pretzell 2007-05-21 12:26:44 UTC 
This is of course intended and seen as an additional service: "Services
supporting this interface" lists not only the directly supporting services, but
also those, that support it indirectly. The assumption being: The user just
wants to know, if the service does provide the interface or not. 

I don't know, if it would be useful to differentiate between those Services that
support the interface directly and those, that support it indirectly.

np->jsc, what is your opinion about this?
Comment 5 jsc 2007-05-21 12:41:30 UTC 
well, when i take a look to javadoc it is of course useful to differentiate from
where inherited methods come. I think that it can make sense to differentiate
and the info should be available. Why not simply make it visible in the
generated docu. I would suggest to change the issue in an enhancement task.
Comment 6 nikolai.pretzell 2007-05-21 14:13:26 UTC 
Okay, so I understand this as:

Task Statement:
1. In Cross-reference: Differentiate between directly and indirectly supporting
Services.
2. In Service Docu: List indirectly exported Interfaces. (np->whitey04: This
should fulfill your expectation of both lists mirroring each other?)
Comment 7 whitey04 2007-05-21 23:28:41 UTC 
Sounds great to me!
Comment 8 Martin Hollmichel 2007-11-09 17:28:21 UTC 
set target from 2.x to 3.x according to
http://wiki.services.openoffice.org/wiki/Target_3x