Messages

1

General Board / Re: Export/Import packages between models

« on: March 21, 2006, 01:55:14 am »

Exp with no DTD did the trick.

2

General Board / Re: Export/Import packages between models

« on: March 20, 2006, 02:55:10 am »

<UML:Device name="Cisco PIX 501" xmi.id="EAID_F9DA9978_73E0_400c_9A87_E4F3D37D69CB" visibility="public" namespace="EAPK_CD98AA0D_EF64_45cb_A6EF_E049FF02139E" isRoot="false" isLeaf="false" isAbstract="false">

Char pos 218 is at the end of the word isAbstract

3

General Board / Export/Import packages between models

« on: March 20, 2006, 02:39:44 am »

I'm trying to move a package from one model to another. When I try to import I get:

Error:
Code = 0c00ce014
Source = Line : 367; Char : 218
Error Description = Element content is invalid ccording to the DTD/schema
Expectng: {ULM}ModelElement, {UML}Comment, {UML}Namespace, {UML}GeneralizableElement, {UML}Feature, {UML}Paramater, {UML}Constraint. {....

4

Automation Interface, Add-Ins and Tools / Re: XSD Attribute Group also XSDSimpleType

« on: June 22, 2005, 10:21:03 pm »

Hello vkumar

That would be great. Any chance the ability to model an attribute group can also be supported? Say, by using an <XSDAttributeGruop> stereotype on a class and using an association to include it hwere required?

Regards, Paul

5

Automation Interface, Add-Ins and Tools / Re: XSD Attribute Group also XSDSimpleType

« on: June 21, 2005, 11:38:48 pm »

Hello vkumer

I understand about <XSDattribute> on an element. It results in an attribute group referenced by the containing class. What I need is a attriubute group that I can reference from a number of classes. I had hoped the using the <XSDattribute> stereotype on a class might give me this.

Cheers, Paul

6

Automation Interface, Add-Ins and Tools / XSD Attribute Group also XSDSimpleType

« on: June 21, 2005, 12:42:10 am »

Dear Team

1. I'm getting to grips with XSD generation and have not been able to fgiure out how to set up an attribute group that can then include in an elements as and when required.

2. Having failed to do this, I thought of creating some <<XSDSimpleType>> clases and then using an <<XSDattribute>> association to include them type as attributes wherever required. This sort of worked but I have not been able to set the type. I want "xs:decimal" but the generated schema always uses "xs:string" as the base of my SimpleType.

Can the team help on either count?