![]() |
Telelogic System Architect (steve huntington) | ![]() |
Topic Title: XSD Support in SA Topic Summary: Created On: 24-Oct-2007 10:21 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Peter, Thanks for your reply. Telelogic Australia have validated our findings. ie - we can't use SA to manage XSD's - and also aligns to your reply. We will do the same as you - use the metadata to associate to other definitions within SA for the time being. The Telelogic consultants also inform us that Tau can manage XSDs and there will be seamless integration on release of SA 11.0 due December 07. They will both utilise the common repository to manage metadata. As we are a heavy XSD user, this is good news. Regards Ross McAdam | |
![]() |
|
I'm wondering if there any users who successfully maintain XSDs in System Architect. Telelogic spiel indicate it has been available since version 10.4: "SYSTEM ARCHITECT 10.4´s new XSD Management (XML Schema) capability ultimately enables linking of schema to BPEL messages via its (Business Process Modeling Notation) BPMN and UML modeling notations, an integral step in any SOA implementation". I have reversed engineered a few of our existing XSD schemas but have found the diagrammatic presentation within UML is unusable with medium and large sized schemas. This can't compare with other tools such as Eclipse and XML Spy which have purpose built diagrammatic interfaces for XSD and XML. The existing SA diagram to manage the XML schema would have been acceptable but this means converting the XSDs to XML in another tool before reverse engineering to SA which means I can't maintain XSD within SA. Does anyone have any experience in this area to provide a bit of guidance? |
|
![]() |
|
![]() |
|
We've done different things in connection with XSD's and XML.
Don't think you should use SA as the TOOL for making the things. But as the repository for XML,XSD, WSDL and so on.
Telelogic have advised us to use SA as the repository for these things - not as the tool for making these often very complex things.
Tools as XML-spy and ecplise are tools in that area.
These tools can't do what SA can do: Connect very complex things they can't connect themselves.
We're considering upgrading to version 10.8 because xml, xsd and the like are becoming more and more central in our set-up. We've had some problems with version 10.4.18: You can't see the link between 2 class-diagrams after importing a xml-schema(but it is there(SA told us)). Should be fixed in a later release.
Hope you can use the answer. Or some of the hints.
------------------------- Best regards Peter Gøtz www.organisator.dk |
|
![]() |
|
![]() |
|
Peter,
Thanks for your reply. Telelogic Australia have validated our findings. ie - we can't use SA to manage XSD's - and also aligns to your reply. We will do the same as you - use the metadata to associate to other definitions within SA for the time being. The Telelogic consultants also inform us that Tau can manage XSDs and there will be seamless integration on release of SA 11.0 due December 07. They will both utilise the common repository to manage metadata. As we are a heavy XSD user, this is good news. Regards Ross McAdam |
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.