SSDN - Stylus XML Schema issue

XML Editor

Sign Up

Search

Options

Chat

Help

News

Log in

Not Logged in

Topic

Topic Page 1 2 3 4 5 6 7 8 9

Romin Irani

Subject: Stylus XML Schema issue
Author: Romin Irani
Date: 01 Apr 2005 07:37 AM

I am trying to load two different XML Schemas - one for source
and the other for the target. The issue is that the XML Schema definitions
that I have are huge and they have been defined in different directories
and with appropriate ref's.

What happens is that the ref's are not getting expanded. It simply remains
at the root. Because of this problem I am not able to expand the
elements and map the child elements accordingly.

I am attaching the XSD definitions.. one is a Purchase Order Request
and the other is a Purchase Order Confirmation. You will find the two
definitions under the XML/Interchange folder.

Please throw some more light on why Stylus cannot display the child elements
-- it seems to be ok with XMLSpy.

PIP3A4_R11.00.00A_RequestPurchaseOrder.zip
PurchaseOrderRequest & Confirmation XSD

(Deleted User)

Subject: Stylus XML Schema issue
Author: (Deleted User)
Date: 01 Apr 2005 10:23 AM

Hi, Romini

We assume you are using mapper and want to load the schema ebBPSS1.01.xsd into source or
target schema tree. To better help you, we need to confirm a few things with you.

1. When you open the ebBPSS1.01.xsd in mapper schema tree, Stylus ask you to pick
A root from a dialog box. What did you choose? Based on your xml instance, it should be processSpecification.
Are you saying Mapper just displayed a root without any children in the tree?

2. You mentioned refs not get expanded. I see Documentation is defined as ref in schema and it does get expanded in the tree (it shows an attribute named 'uri'.
Can you give an example here telling us what you would expect and what mapper showed.

3. What is the Stylus version you are using. You can check form help/about menu.
The latest version should be 6.0, build 287J.

If this issue keep you from proceeding, you can use the xml instance(in your case
P3A4RequestPurchaseOrder_BPSS.xml) in the schema tree. Mapper will infer structure from xml instance file.

Hope this helps.

Song.

Romin Irani

Subject: Stylus XML Schema issue
Author: Romin Irani
Date: 01 Apr 2005 11:35 AM

Hi,

Thanks for the response. The xsd that I am talking about is not the eBPSS - thing.

There are two XSD files and they are present in the XML/Interchange directory. They are
PurchaseOrderRequest.xsd and PurchaseOrderConfirmation.xsd. You will
find that for ref elements which are referenced from other directories,
it does not expand them. I tried even in the latest version of Stylus
Studio.

As you suggested, I did load the XML instances on both sides and I did
try that before -- I know that is ok -- but I dont want to be doing my mapping
based on the XML instances because in case there are some optional elements
not present in my source XML then they will not get mapped because
I will not see them in the first place.

Please advise.

Thanks
Romin.

(Deleted User)

Subject: Stylus XML Schema issue
Author: (Deleted User)
Date: 01 Apr 2005 01:26 PM

You refered to the PurchaseOrderRequest.xsd and PurchaseOrderConfirmation.xsd,
do you mean you choose them directly in mapper source and target schema tree. if so, waht is the root
you picked?

If this is not what you mean, can you give me a specific path that you think should be expanded but it doesn't.
This will help us to dignose the problem much quicker.

Thanks

Song.

Topic Page 1 2 3 4 5 6 7 8 9

Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!

Go to Conference:

Log In Options Username: Password:

Site Map | Privacy Policy | Terms of Use | Trademarks

Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.