SSDN - SS Crash -log attached

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 10 11 12 13 14 15 16 17 18 19 20

Henry Fang

Subject: SS Crash -log attached
Author: Henry Fang
Date: 16 Feb 2002 06:50 PM

Hi there,

This is Henry from BEA. Things getting bad since last night. First I found out I can't open Mapper panel of my old project, then I try to recreate a new simple map, once I try to click anything other than Mapper, SS just froze, continuous gave "Ding Ding..." noises, and then crashed. See attached log. I found this in my log: "Exception code: C0000005 ACCESS_VIOLATION".
Why? I'm on SS 3.1.BL69M.

Henry Fang

Struzzo(82).log

Minollo I.

Subject: Re: SS Crash -log attached
Author: Minollo I.
Date: 17 Feb 2002 12:22 AM

At 07:00 PM 2/16/2002 -0500, you wrote:
>From: "Henry Fang"
>
>Hi there,
>
>This is Henry from BEA. Things getting bad since last night. First I found
>out I can't open Mapper panel of my old project, then I try to recreate a
>new simple map, once I try to click anything other than Mapper, SS just
>froze, continuous gave "Ding Ding..." noises, and then crashed. See
>attached log. I found this in my log: "Exception code: C0000005
>ACCESS_VIOLATION".
>Why? I'm on SS 3.1.BL69M.

Can you give us some more details about both problems? What does it happen
when you try to switch to the Mapper with your old project? And exactly
following which steps you get the crash you described?

If you are using files you haven't yet attached for other submitted
problems, can you send them to me? Or tell me which files you are using?

Thanks,
Minollo

Henry Fang

Subject: Re: SS Crash -log attached
Author: Henry Fang
Date: 17 Feb 2002 02:49 AM

Minollo,

Let's just focus on the 2nd problem. Attached are the source and target xsd. Mapping rules are simple, Schild1 -> Tchild1, Schild2 -> Tchild2, concat(Schild1, " ", Schild2) -> Tchild3. After I did this in Mapper, I click on source panel, and SS just froze, beep for a while, and crashed.
BTW, I did this mapping several times before in SS, no problem at all. This is just weird.
Can you get any info. from the log file? What does it mean "access violation"?

Henry

SourceXML.xsd
source interface definition

TargetXML.xsd
target interface definition

Minollo I.

Subject: Re: SS Crash -log attached
Author: Minollo I.
Date: 17 Feb 2002 01:32 PM

Henry,
this problem was a regression introduced by the latest changes done on
Mapper. Our tests didn't catch it; sorry.

As this is very critical to you and other users, we've already made a new
BL69n package available (http://www.stylusstudio.com/update)

Let me know also about the 1st problem you mentioned.

Thanks,
Minollo

>...
>Can you get any info. from the log file?

Yes, the log file contained good information; but we couldn't understand
the condition under which that error was happening without the test case.

>What does it mean "access violation"?

That's the generic application error that you get when you try to touch
memory location which is out of the memory range assigned to you by the OS.

Henry Fang

Subject: Re: SS Crash -log attached
Author: Henry Fang
Date: 18 Feb 2002 12:32 AM

I'll download it Mon. morning, and let you know how it goes. I believe the 1st problem is due to the same cause. Let's see on Mon.

Thanks,
Henry

Henry Fang

Subject: Re: SS Crash -log attached
Author: Henry Fang
Date: 22 Feb 2002 05:59 PM

Minollo,

SS 3.1.BL69n doesn't solve the problem of generating invalid XML doc., i.e., missing mandatory elements, etc. My example attached. When validating the result xML against the target XSD, you can see mandatory element "HEADER" is missing.

Your thoughts?

Thanks,
Henry

ML_x.xsl
map

sourceDefinition.xsd
source schema

targetDefinition.xsd
target schema

Henry Fang

Subject: Re: SS Crash -log attached
Author: Henry Fang
Date: 22 Feb 2002 06:10 PM

Minollo,

Here's another example. After I switched to 69n build, the output XML size jumped from 95KB to 1.4MB. But still it's not valid against target DTD. Here's msg I got: required attribute "qualifier' of parent element 'DATETIME' missing. Another issue is lots of optional element got populated even though not necessary, but this is not harmful.
The 1st issue is critical to us.

Henry

danzas.zip
include XSL,source/target DTD,output XML

Minollo I.

Subject: Re: SS Crash -log attached
Author: Minollo I.
Date: 22 Feb 2002 06:17 PM

At 06:20 PM 2/22/2002 -0500, you wrote:
>From: "Henry Fang"
>
>Minollo,
>
>Here's another example. After I switched to 69n build, the output XML size
>jumped from 95KB to 1.4MB. But still it's not valid against target DTD.
>Here's msg I got: required attribute "qualifier' of parent element
>'DATETIME' missing. Another issue is lots of optional element got
>populated even though not necessary, but this is not harmful.
>The 1st issue is critical to us.

Henry,
it is not the goal of Mapper to automatically generate valid XML as the
result of your mapping; it's the user responsibility to ensure that the
stylesheet generates a "valid" output.
Required attributes need to be filled in with some (usually) meaningful
value that requires knowledge of the semantics of the operation you are
doing; Mapper doesn't have that knowledge.

About the problem you have reported earlier, I still have to look into it;
note that Mapper will generate the required sibling elements only when
switch back to source from Mapper (if you have made at least one change
which requires Mapper to regenerate the XSLT document).

Minollo

Henry Fang

Subject: Re: SS Crash -log attached
Author: Henry Fang
Date: 22 Feb 2002 06:45 PM

>>it's the user responsibility to ensure >>that the stylesheet generates a "valid" >>output.
>>Required attributes need to be filled in >>with some (usually) meaningful
>>value that requires knowledge of the >>semantics of the operation you are
>>doing; Mapper doesn't have that knowledge.

Not quite agree. My expectation is if the schema/DTD defines default value for the mandatory field, Mapper should fill in that value if input data doesn't provide value overwrites it, or if there's no default value, it should at least generate empty field for me. I thought you agreed on this when I raised the issue.

>>About the problem you have reported >>earlier, I still have to look into it;
>>note that Mapper will generate the >>required sibling elements only when
>>switch back to source from Mapper (if you >>have made at least one change
>>which requires Mapper to regenerate the >>XSLT document).

The mapper did regenerate XSL doc.

Henry

Minollo I.

Subject: Re: SS Crash -log attached
Author: Minollo I.
Date: 22 Feb 2002 06:51 PM

>...
> >>it's the user responsibility to ensure >>that the stylesheet generates
> a "valid" >>output.
> >>Required attributes need to be filled in >>with some (usually) meaningful
> >>value that requires knowledge of the >>semantics of the operation you are
> >>doing; Mapper doesn't have that knowledge.
>
>Not quite agree. My expectation is if the schema/DTD defines default value
>for the mandatory field, Mapper should fill in that value if input data
>doesn't provide value overwrites it, or if there's no default value, it
>should at least generate empty field for me. I thought you agreed on this
>when I raised the issue.

I agree that the required *structure* needs to be created; not that all its
content fields need to be created. The structure must be there, and it is
somewhat abstracted from the content you are trying to create. The
content is a different thing.

> >>About the problem you have reported >>earlier, I still have to look
> into it;
> >>note that Mapper will generate the >>required sibling elements only when
> >>switch back to source from Mapper (if you >>have made at least one change
> >>which requires Mapper to regenerate the >>XSLT document).
>
>The mapper did regenerate XSL doc.

We will try understanding the problem as soon as we can.

Thanks,
Minollo

Henry Fang

Subject: Re: SS Crash -log attached
Author: Henry Fang
Date: 22 Feb 2002 08:38 PM

>>I agree that the required *structure* >>needs to be created; not that all its
>>content fields need to be created. The >>structure must be there, and it is
>>somewhat abstracted from the content you >>are trying to create. The
>>content is a different thing.

Now we're on the same page.

>>We will try understanding the problem as soon as we can.

Appreciate that.

Henry

Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

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.