XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Helen HeSubject: Question on validate a sample xml file
Author: Helen He
Date: 07 Mar 2006 05:41 PM
I need a XML schema Editor and I am comparing XMLSPY and Stylus Studio since we are planning to buy one.

Ater comparing these two, I prefer Sytlus Studio. But I got confused when I tried to validate a same xml source file. XMLSPY says the xml file is valid, but Stylus Studio says it has 34 errors.

Since the schema attached is standard in medical area, we can not modify it. Can those errors be ignored if I set up some options? Could someone help me out?

Postnext
Minollo I.Subject: Question on validate a sample xml file
Author: Minollo I.
Date: 07 Mar 2006 05:46 PM
Helen,
feel free to post the XML + XML Schema here, or to email them to stylus-field-report@progress.com

Stylus Studio natively relies on Apache XercesC, which is a well respected XML Schema validation engine; but you can also verify what other validation engines "think" about your XML by clicking on the down arrow next to the validation button and choosing a different one. That should give you a good feeling about what the consensus is about the validity of your document.

Thanks,
Minollo

Postnext
David KarrSubject: RE: Question on validate a sample xml file
Author: David Karr
Date: 07 Mar 2006 06:28 PM
If discussion of this problem occurs privately with Progress support,
I'd appreciate getting a summary of the solution here.

> -----Original Message-----
> From: stylus-studio-tech Listmanager
> [mailto:stylus-studio-tech.listmanager@stylusstudio.com]
> Sent: Tuesday, March 07, 2006 2:57 PM
> Subject: Question on validate a sample xml file
>
>
> From: "Helen He"
>
> I need a XML schema Editor and I am comparing XMLSPY and
> Stylus Studio since we are planning to buy one.
>
> Ater comparing these two, I prefer Sytlus Studio. But I got
> confused when I tried to validate a same xml source file.
> XMLSPY says the xml file is valid, but Stylus Studio says it
> has 34 errors.
>
> Since the schema attached is standard in medical area, we can
> not modify it. Can those errors be ignored if I set up some
> options? Could someone help me out?
>
>
>
> --
> To reply: mailto:stylus-studio-tech.14066@stylusstudio.com
> To start a new topic: mailto:stylus-studio-tech@stylusstudio.com
> To login: http://www.stylusstudio.com/SSDN/
> To (un)subscribe:
> mailto:stylus-studio-tech.list-request@stylusstudio.com
>
>

Postnext
David KarrSubject: Xslt mapper: changing target schema from qualified to unqualified leaves the root element qualified
Author: David Karr
Date: 09 Mar 2006 11:43 AM
I had two XSDs, I created a new XSLT mapper and set them as the source
and target. I started mapping elements, and then I ran a preview. I
noticed that the target elements were qualified, but I had wanted them
to be unqualified. I checked the target schema, and it did have
"elementformdefault" set to "qualified". So, I changed it to
"unqualified". I'm guessing there's no way to magically "reset" the
target schema association, so that the xslt would remove the namespace
prefixes. So, I tried creating a new mapper, and setting the same
source and target schema, and then started mapping elements again.
Oddly enough, the result shows that almost all of the elements from the
target schema are unqualified, except for the root element. For some
reason that is still qualified with the target namespace prefix. I
don't get it.

Postnext
David KarrSubject: What causes the xslt mapper to lose the links from the source to the mapper canvas?
Author: David Karr
Date: 09 Mar 2006 11:49 AM
Yesterday I created a new XSLT mapper. I set the source/target schemas.
I mapped several elements between them. I tested the mapping a few
times. I saved everything, then I exited. I came in this morning and
started up SS again. The XSLT was selected by default. I had to set
the source/target schemas. After I did that, I noticed that the links
from the source schema to the mapper canvas were not there.

The top line in the source schema area that shows the name of the schema
has an icon with a red check mark on it. I seem to remember that has
something to do with the "association" of the schema. The dropdown has
an "Associate with" option, and it's set to "Scenario".

What am I supposed to do to get it to show the links from the source
schema to the mapper canvas? Instead of the links, I see several
function icons in the mapper canvas with no input connections.

Postnext
Minollo I.Subject: What causes the xslt mapper to lose the links from the source to the mapper canvas?
Author: Minollo I.
Date: 09 Mar 2006 12:08 PM
That seems to suggest that mapper is not recognizing mappings from source to target; maybe this is related to the topic you posted above about your switch to unqualified from qualified?

If you feel like the XSLT is correctly mapping from/to the schemas it's currently showing in mapper, please send us the XSLT and schemas you are using, so we can take a closer look at what's going on.

Thanks,
Minollo

Postnext
David KarrSubject: XSLT mapper: If source "elementformdefault" is "unqualified", XSLT still needs to reference ns prefix
Author: David Karr
Date: 09 Mar 2006 12:14 PM
I have two schemas, which we'll call "b" (source) and "a" (target) for
now. Both of them have "elementformdefault" set to "qualified"
initially. My sample message, however, has the elements unqualified. I
also need my result to be unqualified. My initial testing looks ok,
except for the ns prefixes. Note that both schemas have several
elements with the same name, like "UID", for instance. I'm not sure
whether this is relevant. So, I changed both schemas to be
"unqualified" and created a new mapper. I set the same source/target
schemas and mapped my elements, and ran the preview. For some reason,
all the elements were empty. I looked closer at the XSLT, and I noticed
that code that looked like this in the first try:



Now looked like:



For some reason, it left the ns prefix off the "UID" element reference.
I hand-edited it, adding the "b:" back in, and retested it, and it was
fine. It's curious that it mistakenly removed the prefix on the
sub-element, but not on the root element.

It appears that having the elementformdefault set to "unqualified" in
the source schema confused it a bit. That means the XML element will be
unqualified, but that doesn't have anything to do (I believe) with
whether the references in the XSLT should be qualified or not.

Postnext
Minollo I.Subject: XSLT mapper: If source
Author: Minollo I.
Date: 09 Mar 2006 12:40 PM
David, what you are describing didn't come through well in the post; can you please email us the files you are using as attachments so that we can take a look at the real files as you are seeing them? (stylus-field-report@progress.com)

Thanks,
Minollo

Postnext
Minollo I.Subject: XSLT mapper: If source
Author: Minollo I.
Date: 09 Mar 2006 12:50 PM
BTW, qualified vs. unqualified makes a huge different from a mapper/XSLT point of view; you are basically determining if the non-top level elements live in the target namespace defined in the XML Schema or not (top level elements/attributes are always qualified, no matter what the default qualified/unqualified setting is).

Minollo

Postnext
David KarrSubject: RE: XSLT mapper: If source
Author: David Karr
Date: 09 Mar 2006 01:07 PM
I'm a step ahead of you. Already done.

> -----Original Message-----
> From: stylus-studio-tech Listmanager
> [mailto:stylus-studio-tech.listmanager@stylusstudio.com]
> Sent: Thursday, March 09, 2006 9:42 AM
> Subject: XSLT mapper: If source
>
>
> From: Minollo I.
>
> David, what you are describing didn't come through well in
> the post; can you please email us the files you are using as
> attachments so that we can take a look at the real files as
> you are seeing them? (stylus-field-report@progress.com)
>
> Thanks,
> Minollo
>
>
> --
> To reply: mailto:stylus-studio-tech.14144@stylusstudio.com
> To start a new topic: mailto:stylus-studio-tech@stylusstudio.com
> To login: http://www.stylusstudio.com/SSDN/
> To (un)subscribe:
> mailto:stylus-studio-tech.list-request@stylusstudio.com
>
>

Postnext
David KarrSubject: XSLT that calls extension function works in preview mode with Xalan-J 2.5.2, but debugger claims error in function
Author: David Karr
Date: 09 Mar 2006 05:46 PM
I have an XSLT that is referencing extension functions (not Java). I
apparently had to set the processor to Xalan-J 2.5.2 (which is fine) in
order for the preview operation to work. The scenario I have works
fine. However, when I try to run it in the debugger, I get (I love how
^C works in dialogs):

---------------------------
Stylus Studio 2006 XML Enterprise Edition
---------------------------
java.lang.RuntimeException:
javax.xml.transform.TransformerConfigurationException:
javax.xml.transform.TransformerException:
javax.xml.transform.TransformerException: misplaced literal result in a
func:function container.
URL:
file:///c:/cygwin/home/u166705/work/xsltproto/str.padding.function.xsl
Line:27
Col: 17
Jump to location?
---------------------------
Yes No
---------------------------

The line in question is the following (16 characters long):



I can send the relevant files in a field report, if necessary.

Postnext
Minollo I.Subject: XSLT that calls extension function works in preview mode with Xalan-J 2.5.2, but debugger claims error in function
Author: Minollo I.
Date: 09 Mar 2006 08:12 PM
I guess you are using JavaScript extension functions; those will require XalanJ. Yes, if you can send/attach the relevant files it would be great; we would like to understand why there is a different behavior between execution and debug.

Thanks,
Minollo

Posttop
David KarrSubject: Getting error again: I/O error in file url
Author: David Karr
Date: 20 Mar 2006 10:36 PM
I'm getting an error again that I've seen before. The last time this
happened, it seemed like Stylus Studio had taken one scenario and
truncated the file name element from the path to an input file, leaving
only the directory. What's annoying about this problem is that I can't
tell what's referencing this. I only have one scenario on an xslt in
the mentioned directory, and I don't see anything wrong with the
parameters of the scenario, which runs fine when I run it.

---------------------------
Stylus Studio 2006 XML Enterprise Edition
---------------------------
Encountered an I/O error in URL
"file:///c:/cygwin/home/u166705/work/soapcall": Access to
c:\cygwin\home\u166705\work\soapcall was denied.
---------------------------
OK
---------------------------

___________________________________________________
David M. Karr, Technical Specialist Senior
Corporate Shared Services
Application Integration Services
Platforms, Architecture & Production Operations (PAPO)
Enterprise Service Bus (ESB)

Washington Mutual
1201 Third Avenue, WMT0914, Seattle, WA 98101
www.wamu.com

206.490.7289 direct | 206.909.0664 mobile
206.490.2262 fax

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! 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

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
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.