oXygen does not autocomplete from included schemas

Post by **nsushkin** » Mon Jul 31, 2006 8:39 pm

I have a schema that xs:includes another schema. In the including schema, the types
defined in the included schema do not appear in the dropdowns for the base attribute of the xs:extension element. If I flatten the schema, all the types become available. There appears to be no errors in either modularized of flattened schemas.

Is this a bug, a feature to be implemented, or my misunderstanding?

Thanks.

Post by **george** » Mon Jul 31, 2006 10:14 pm

Hi,

The dynamic content completion proposals get information only from the edited document, thus I think the best way to characterize this is that support looking into included/imported files for dynamic proposals information is a feature to be implemented.

Best Regards,
George

Post by **nsushkin** » Mon Jul 31, 2006 11:34 pm

george wrote: The dynamic content completion proposals get information only from the edited document...

My document does not define xsd:string, yet I can use it. Anyway, it's a pity,
my schemas are all modularized using xsd:include. I guess I'll have to use another
editor for my development.

Post by **george** » Mon Aug 07, 2006 11:28 am

Hi,

The built-in schema types are presented by oXygen so that is why xs:string appears.
When we implemented this support for presenting dynamic content completion proposals a few month ago oXygen was the only editor AFAIK with this feature.

Best Regards,
George

Post by **nsushkin** » Wed Aug 23, 2006 3:28 am

george wrote:Hi,
When we implemented this support for presenting dynamic content completion proposals a few month ago oXygen was the only editor AFAIK with this feature.

George, I am currently using Tibco (former Extensibility) Turbo XML. When I am extending an existing type, I get autocompletion no matter where the type is defined, in the currently opened document or in an included one.