Messages

1

Suggestions and Requests / Re: BUG: Soap / WSDL Headers

« on: October 11, 2006, 04:21:03 am »

Hi,

Thanks for the response, just to be clear it's not the header element as described above that isn't appearing in the resulting WSDL, it's the actual message part to which the header refers that doesn't get generated.

I'll send along a sample.

D.

2

Suggestions and Requests / Re: BUG: Soap / WSDL Headers

« on: October 09, 2006, 03:45:45 am »

Hi,

I'm doing that already - although it seems a little clunky. The problem is that the soap header message doesn't appear in the WSDL even if it is referred to by the soapHeader tag.

For some reason, EA seems to ignore the message - I presume because there isn't a direct reference to it. As such it doesn't appear in the output.

D.

3

Suggestions and Requests / BUG: Soap / WSDL Headers

« on: October 06, 2006, 02:52:52 am »

Hi,

I'm trying to use enterprise architect to generate WSDL with a soap header component, which has thrown up a number of issues.

First - there's no documentation on the soapHeader tag which really doesn't help.

Second - since the soap header element is only supported through a tag, I've to date been unable to force EA to generate the appropriate message element in the WSDL to which the soapHeader tag refers. This I would see as a major bug in the WSDL support. The message exists, it just doesn't make it into the generated WSDL - presumably because it isn't directly supported.


This is really really hurting us right now - is there any hope of getting a fix, or some indication of a workaround?

Thanks,

D

4

Suggestions and Requests / WSDL Generation

« on: May 02, 2007, 07:48:24 am »

Hi,

Using the WSDL generation is there any way to get a message part to reference the generated element rather than the generated type?

So:

Code: [Select]


<wsdl:types>
   <xs:schema targetNamespace="http://www.tmp.com/Tools/HandHistory/Summariser/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:s1="http://www.tmp.com/Tools/HandHistory/Summariser/">
   <xs:element name="SummariseHandsRequest" type="s1:SummariseHandsRequest"/>
   <xs:complexType name="SummariseHandsRequest">
   <xs:sequence>
       <xs:element name="handIds" type="xs:unsignedLong" maxOccurs="unbounded"/>
       <xs:element name="handType" type="xs:string"/>
       <xs:element name="year" type="xs:int"/>
   </xs:sequence>
   </xs:complexType>
   </xs:schema>
</wsdl:types>

<wsdl:message name="SummariseHandsMessage">
   <wsdl:part name="summaryRequest" type="tns:SummariseHandsRequest"/>
</wsdl:message>


In the message part, I'd like the part to use an element attribute rather than the type attribute. This would make it WS-I Basic Profile 1.1 compliant.

Thus it should look like:

Code: [Select]



<wsdl:types>
   <xs:schema targetNamespace="http://www.tmp.com/Tools/HandHistory/Summariser/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:s1="http://www.tmp.com/Tools/HandHistory/Summariser/">
   <xs:element name="SummariseHandsRequest" type="s1:SummariseHandsRequest"/>
   <xs:complexType name="SummariseHandsRequest">
   <xs:sequence>
       <xs:element name="handIds" type="xs:unsignedLong" maxOccurs="unbounded"/>
       <xs:element name="handType" type="xs:string"/>
       <xs:element name="year" type="xs:int"/>
   </xs:sequence>
   </xs:complexType>
   </xs:schema>
</wsdl:types>

<wsdl:message name="SummariseHandsMessage">
   <wsdl:part name="summaryRequest" element="tns:SummariseHandsRequest"/>
</wsdl:message>


D

5

Suggestions and Requests / Re: XSD Schema generation with choices

« on: April 03, 2007, 05:06:00 am »

So I'm back on this one again.

Just wondering if anyone has made any progress on adding the minOccurs and maxOccurs attributes to the choice. I've been modifying it by hand all this time.

I still see that the current version of ea won't allow me to specify these attributes on a complex type with a model group of choice.

Anyone?

D

6

Suggestions and Requests / Re: XSD Schema generation with choices

« on: October 17, 2006, 05:24:47 pm »

Hi,

Thanks for the reply and the effort.

Actually there is a subtle difference with the code generated and the code imported. If you look at where EA has put the minOccurs and maxOccurs attributes you will see that it has shifted them from being attributes on the choice to being attributes on the element that refers to the complex type containing the choice.

This subtle difference makes all the difference in the code that is ultimately generated from the schema. In your case, XSD.exe will generate a single class that can act as an element of an array, and another property that occurs only once. It does not generate an array at all.

Regards,

D

7

Suggestions and Requests / XSD Schema generation with choices

« on: October 11, 2006, 07:35:48 am »

Hi,

I'm trying to generate a schema that will ultimately be transformed into a class that has a property that returns an array of elements.

The schema below (hand coded) correctly does this when pushed through xsd.exe (Microsoft Visual Studio 2005).

<?xml version="1.0"?>
<xs:schema targetNamespace="http://www.testStuff.com/Handler" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:hnd="http://www.testStuff.com/InHand" xmlns:ce="http://www.testStuff.com/CanonicalEvents">
<xs:import namespace="http://www.testStuff.com/CanonicalEvents"/>
<xs:element name="InHand" type="hnd:InHand"/>
<xs:complexType name="InHand">
<xs:sequence>
<xs:element name="inHandDateTime" type="xs:dateTime"/>
<xs:element name="inHandId" type="xs:unsignedLong"/>
<xs:element name="inHandEvents" minOccurs="0" maxOccurs="1" type="hnd:ArrayofEvents"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="ArrayofEvents">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="OpenEvent" type="ce:OpenEvent"/>
<xs:element name="CloseEvent" type="ce:CloseEvent"/>
<xs:element name="WarningEvent" type="ce:WarningEvent"/>
<xs:element name="VoidEvent" type="ce:VoidEvent"/>
<xs:element name="TimeoutEvent" type="ce:TimeoutEvent"/>
<xs:element name="BalanceEvent" type="ce:BalanceEvent"/>
<xs:element name="ReturnEvent" type="ce:ReturnEvent"/>
</xs:choice>
</xs:complexType>
</xs:schema>

The problem that I have is that I can't model this in EA. Even if I import this and roundtrip out, it still doesn't generate this schema. The specific problem appears to be with the unbounded choice. No matter what I use in EA I can't get it to properly generate the array in the form listed above.

I get this instead:

<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema targetNamespace="http://www.testStuff.com/Handler" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:hnd="http://www.testStuff.com/InHand" xmlns:ce="http://www.testStuff.com/CanonicalEvents">
<xs:import namespace="http://www.testStuff.com/CanonicalEvents"/>
<xs:element name="InHand" type="hnd:InHand"/>
<xs:complexType name="InHand">
<xs:sequence>
<xs:element name="handDateTime" type="xs:dateTime"/>
<xs:element name="handId" type="xs:unsignedLong"/>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="OpenEvent" type="ce:OpenEvent"/>
<xs:element name="CloseEvent" type="ce:CloseEvent"/>
<xs:element name="WarningEvent" type="ce:WarningEvent"/>
<xs:element name="VoidEvent" type="ce:VoidEvent"/>
<xs:element name="ValueEvent" type="ce:ValueEvent"/>
<xs:element name="TimeoutEvent" type="ce:TimeoutEvent"/>
<xs:element name="BalanceEvent" type="ce:BalanceEvent"/>
<xs:element name="ReturnEvent" type="ce:ReturnEvent"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
</xs:schema>

Which is close, but no cigar. I've tried introducing an intermediary element, a complex type and just about everthing in between but to no avail.

Anyone seen / fixed / worked around this?

Thanks,

D.

8

General Board / WSDL Transformations and Imports

« on: September 08, 2006, 06:40:57 am »

I'm sure that this has been asked before - but I couldn't find the question on the boards so here goes.

I'm using EA to do contract first development of Web Services. I can model and generate my XML Schema beautifully in EA and am very happy with that.

My issue is this:

In normal XSD development, EA automatically adds an <import> when it sees something from outside the current schema - this works very well.

What I would like to do is to be able to import my data schema into my WSDL generation. I've tried placing the classes on the diagram under the <<types>> section of the WSDL tree - this didn't work. I've tried just referencing the elements in the <<messages>> section of the WSDL but again to no avail.

I'm hoping someone has hit this and has managed to resolve it to a happy conclusion.

9

Automation Interface, Add-Ins and Tools / Re: Accessing cross reference information on an el

« on: January 30, 2006, 01:30:33 am »

Hi,

not quite sure what do you mean by "a diagram that an element cross-references". Do you mean diagrams that the element appears on? If so, look at t_diagramobjects.

Hope this helps!
Bruno

Hi,

There is an option in EA to 'Add a diagram as a reference' you find it by looking at an element and then selecting 'See Also...' from the context menu of that element.

So I found where EA is holding this reference data in the t_xref table, which seems to hold custom properties, swimlanes and this particular type of reference. What I can't find is how to get at this information. If I look at the custom properties of an element I don't see the particular references I'm looking for (arrrgh).

So Sparx people or EA gurus - what's a guy to do to get these

Thanks,

D.

10

Automation Interface, Add-Ins and Tools / Re: Accessing cross reference information on an el

« on: January 29, 2006, 01:22:06 pm »

You might be able to do this with a SQL statement. Sorry that I have not time to look in more detail at this, but it's not too hard to test...

Thanks, I've been looking at this today, and to be honest can't even find where this information might be in the database.

Anyone got any ideas where this type of cross reference information is stored in the DB?

D.

11

Automation Interface, Add-Ins and Tools / Accessing cross reference information on an elemen

« on: January 11, 2006, 03:23:45 pm »

I've been trying to get a list of the diagrams that an element cross references.

I can find direct relationships in the object model, but not the cross referenced ones.

Anyone achieved this via the automation interface?