|
|
 next
|
  Subject: Why I use the Studio only for XSLT
Author: Vern DeHaven
Date: 20 Aug 2004 10:58 AM
|
>>1) Web service calls: The only elements available in the
>>envelope are those which are fully defined within themselves,
>>i.e. are not based on a user-defined type.
>>Why is this?
>
>Web Service Call Composer, is
>designed to provide
>auto-complete for all
>schema definitions defined in
>the WSDL or in the imported
>schemata.
>Could you provide an example
>with a more accurate
>description?
Attached: NoParseTest.wsdl
The extractRequest element in the schema is of a user-defined type defined outside the element declaration. The SOAP I get is:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SOAP-ENV:Envelope xmlns:SOAPSDK1="http://www.w3.org/2001/XMLSchema" xmlns:SOAPSDK2="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAPSDK3="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body xmlns:tae="http://tempURI.edu/extract" xmlns:trans="http://transfer.org/AdmissionsApp" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xs="http://www.w3.org/2001/XMLSchema">
<tae:extractRequest/>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
It will not parse into the schema to further define extractRequest.
>>2) XML differencer: I've tried
>>all three perfomance settings
>>on
>>the engine and cannot get a
>>good comparison. In the 2
>>schemas I
>>was comparing, I cannot get it
>>to compare types by name. It
>>seemed
>>to compare text top-down
>>regardless of the engine
>>setting.
>
>I tried a simple test
>comparing 2 XSD (attached
>image). It seems to make sense
>to me.
>If could provide an example
>with expected result would be
>great.
Attached: Diff.jpg, CoreMain.xsd, CoreMain_v1.0.0.xsd
In the left pane of the JPEG, the complexType "RaceEthnicityType" is highlighted; its supposed "matching" type in the right pane is "ResidencyType". The actual matching "RaceEthnicityType" simpleType is considered added. Also in the left pane, the complexType "ResidencyType" is considered removed.
>>3) I can only drag-and-drop
>>items in XML documents in text
>>view.
>
>Could give provide examples of
>d&d you would like to do?
I would love to be able to do this in Tree view.
Some examples: I want to wrap a set of elements underneath a parent element, I want to reorder elements within a xsd:sequence, ...
I thought of a few other items:
Are you going to offer a WSDL builder?
Stronger context-sensitive right-click functionality would be a big help. For exaple, when I right-click on a sequence in a schema, I would like to be able to add at least a child element. If I right-click on a complexType, I would like to be able to add a sequence, choice or all.
Ooh, a dockable non-modal window selector window would be good as well for us standard MDI folks. (See TextPad - the tab selection for standard MDI windows is pretty darn neat too)
 Diff(1).JPG
Differencer oddity
 NoParseTest(1).wsdl
Non-parsed WSDL example
CoreMain(1).xsd
Source schema
CoreMain_v1.0.0(1).xsd
Destination schema
|
|
next
|
  Subject: Why I use the Studio only for XSLT
Author: Ivan Pedruzzi
Date: 20 Aug 2004 03:09 PM
|
>>>1) Web service calls: Could you provide an example with a more accurate description?
>
>Attached: NoParseTest.wsdl
>The extractRequest element in the schema is of a user-defined type defined
>outside the element declaration.
>It will not parse into the schema to further define extractRequest.
This is because the schema element overrides the default namespace;
To workaround change the WSDL definition to
<xs:element name="extractRequest" type="tae:ExtractRequestType"/>
>>>2) XML differencer: I've tried all three performance settings
>>>on the engine and cannot get a good comparison. In the 2 schemas I >was comparing, I
>cannot get it to compare types by name. It seemed to compare text top-down regardless of the
>engine setting.
>>
>>I tried a simple test comparing 2 XSD (attached image).
>>It seems to make sense to me.
>>If could provide an example with expected result would be great.
>In the left pane of the JPEG, the complexType "RaceEthnicityType" is highlighted; its supposed
>"matching" type in the right pane is "ResidencyType".
>The actual matching "RaceEthnicityType" simpleType is considered added.
In this case a complextype has been changed to simpleType,
there is now way to correlate this change from an XML standpoint,
unless the algorithm is designed to be schema aware, which is not.
>>>3) I can only drag-and-drop items in XML documents in text view.
>>Could give provide examples of d&d you would like to do?
>I would love to be able to do this in Tree view.
>Some examples: I want to wrap a set of elements underneath a parent element,
Noted.
>I want to reorder elements within a xsd:sequence, ...
Use the command "Move Up/Down" in the toolbar/context menu.
>I thought of a few other items:
>Are you going to offer a WSDL builder?
I am very interested to this topic.
Could you provide a scenario where you start the design from the WSDL definition?
How do you correlate the WSDL development to the web service implementation?
If you change the WSDL how do you re-factor the changes in the code?
>Stronger context-sensitive right-click functionality would be a big help.
>For example, when I right-click on a sequence in a schema, I would like to be able to add
>at least a child element.
>If I right-click on a complexType, I would like to be able to add a sequence, choice or all.
Tree View has a main menu (XMLSchema->Tree Editing) that replicates the toolbar functionalities and is context sensible.
>Ooh, a dockable non-modal window selector window would be good as well for us>standard MDI folks.
>TextPad - the tab selection for standard MDI windows is pretty darn neat too)
It looks a bit awkward.
To switch between documents you can use the Windows menu.
Thank You
Ivan
|
|
next
|
Subject: Why I use the Studio only for XSLT
Author: Vern DeHaven
Date: 20 Aug 2004 03:52 PM
|
>>>>1) Web service
>calls: Could you provide an
>example with a more accurate
>description?
>>
>>Attached: NoParseTest.wsdl
>>The extractRequest element
>in the schema is of a
>user-defined type defined
>>outside the element
>declaration.
>>It will not parse into the
>schema to further define
>extractRequest.
>
>This is because the schema
>element overrides the default
>namespace;
>To workaround change the WSDL
>definition to
>
><xs:element
>name="extractRequest"
>type="tae:ExtractRequestType"/
>>
Well, this isn't necessarily true. I removed the redefinition and the parameters are listed correctly. See the attached NoParseTestNoRedefine.wsdl. All other tools I have used don't have an issue with this.
>>>>2) XML
>differencer: I've tried all
>three performance settings
>>>>on the engine and
>cannot get a good comparison.
>In the 2 schemas I >was
>comparing, I
>>cannot get it to compare
>types by name. It seemed to
>compare text top-down
>regardless of the
>>engine setting.
>>>
>>>I tried a simple test
>comparing 2 XSD (attached
>image).
>>>It seems to make sense
>to me.
>>>If could provide an
>example with expected result
>would be great.
>
>
>>In the left pane of the
>JPEG, the complexType
>"RaceEthnicityType" is
>highlighted; its supposed
>>"matching" type in the
>right pane is "ResidencyType".
>>The actual matching
>"RaceEthnicityType" simpleType
>is considered added.
>
>
>In this case a complextype has
>been changed to simpleType,
>there is now way to correlate
>this change from an XML
>standpoint,
>unless the algorithm is
>designed to be schema aware,
>which is not.
Hence why I need XMLSpy around.
>>I want to reorder elements
>within a xsd:sequence, ...
>
>Use the command "Move Up/Down"
>in the toolbar/context menu.
Thanks!
>>I thought of a few other
>items:
>>Are you going to offer a
>WSDL builder?
>
>
>I am very interested to this
>topic.
>Could you provide a scenario
>where you start the design
>from the WSDL definition?
>How do you correlate the WSDL
>development to the web service
>implementation?
>If you change the WSDL how do
>you re-factor the changes in
>the code?
All of my Web services are built WSDL-first. I have found it is the only way to practically guarantee cross-platform interoperability. The WSDL is your contract, your interface, and should not change. But, if it does, both .NET and the JWSDP offer tools to build and rebuild server skeletons from WSDLs making refactoring simpler.
>>Stronger context-sensitive
>right-click functionality
>would be a big help.
>>For example, when I
>right-click on a sequence in a
>schema, I would like to be
>able to add
>>at least a child element.
>>If I right-click on a
>complexType, I would like to
>be able to add a sequence,
>choice or all.
>
>Tree View has a main menu
>(XMLSchema->Tree Editing)
>that replicates the toolbar
>functionalities and is context
>sensible.
>
>>Ooh, a dockable non-modal
>window selector window would
>be good as well for
>us>standard MDI folks.
>>TextPad - the tab
>selection for standard MDI
>windows is pretty darn neat
>too)
>
>It looks a bit awkward.
>To switch between documents
>you can use the Windows menu.
These are minor ease-of-use requests anyway.
Here's a couple more:
Have you taken a look at BizTalk 2004's mapper in VS.NET? The tabbed and scrollable mapper canvas is very nice. Tell me what you think.
When hand-coding XSLT, I love the Sense:X functionality. When I pick an element, could you also give me skeletons of the usual child elements as well? For example, when I select say <xsl:choose>, it would give me skeletons of <xsl:when> and <xsl:otherwise>.
HTH,
Vern
NoParseTestNoRedefine(1).wsdl
No redefinition WSDL
|
|
|
|
|
top