To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=61429


User kso changed the following:

                What    |Old value                 |New value
================================================================================
                  Status|NEW                       |STARTED
--------------------------------------------------------------------------------
        Target milestone|OOo Later                 |OOo 3.3
--------------------------------------------------------------------------------




------- Additional comments from k...@openoffice.org Tue Dec 15 09:19:30 +0000 
2009 -------
I see this a little bit different. I don't think that the solution should be to
make XContentCreator a mandatory interface. It is "good" that only resources
that are able to create other resources (usually children of its own) offer the
respective operations. This is like UCB works. UCB contents offer exactly the
functionality (commands) they are actually support.

The problem with the XContentCreator interface: This interface should only be
supported by WebDAV collection resources. The actual problem is that several
operations on UCB objects need a Command Environment, for instance to get an
Interaction Handler for obtaining credentials. The latter might be needed in
order to get access to the resource in order to obtain the DAV resourcetype
property. But it is not possible to supply a Command Environment to a
queryInterface! Thus, queryInterface might not be able to determine the resource
type, thus cannot decide whether XContentCreator should be supported.

What to do? To solve the problem we will deprecate the XContentCreator interface
and offer the needed functionality the usual UCB-way - using commands and
properties.

sequence< ContentInfo> XContentCreator.queryCreatableContentsInfo()
=> optional readonly property: sequence< ContentInfo> CreatableContentsInfo

XContent XContentCreator.createNewContent( ContentInfo )
=> optional command: XContent createNewContent( ContentInfo )

If the new property is supported, the new command must be supported, too.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ucb.openoffice.org
For additional commands, e-mail: issues-h...@ucb.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to