 next
|
  Subject: Re: xcbl 4 schema - include problems
Author: (Deleted User)
Date: 08 Jun 2004 12:45 PM
|
At 11.27 08/06/2004 -0400, stylus-studio-tech Listmanager wrote:
>From: Kevin Lentle
>
>Hmmm,
>
>So you're saying that I need to edit roughly 700 files to get this to
>work ? And I'll need to do it each time the xCBL schema changes ?
>
>Surely as XML-spy correctly handles these includes stylus studio should,
>or are you saying that the xCBL files are not correct, and therefore
>XML-spy is incorrectly handling them ?
I am sorry for the bad wording of my message: what I was trying to say was
the reason why the workaround you found was working. That is, xCBL has not
been designed to be included in pieces, like you were saying in your
message (e.g. include just two files out of the "catalog" directory), but
has to be used as a whole as the single pieces are, taken alone, invalid.
Quoting from the readme file:
"Note on Import, Include and Tools Support: [...]
The problem with this approach is that the
component files in the namespace, other than the
root schema, are often invalid when opened alone.
So when using xCBL 4.0 with an XML tool, one much
always open or reference the "root" schema for the
namespace involved. (e.g. ordermanagement.xsd)."
The current algorithm used by Stylus to navigate from one type definition
to another assumes that each schema is valid, and knows how to find the
definition for all the components it shows. Clearly this assumption is
wrong with xCBL and the various "goto to definition" commands fail to work
as expected. We will fix this issue in a future version of the product.
Hope this clarifies the matter,
Alberto
|
|
top