I would like to hear from anyone who is using Sparx Enterprise Architect in connection with OpenEdge.
I would like to know:* Progress version* EA version* What database you use for a repository, if not the default EAP* A sentence about what you use it for.
Please indicate if you would like me to keep your contact confidential. Respond publicly or privately as strikes your fancy.
This is focused on Sparx support for OpenEdge.
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
We (the customer I'm working for currently) are using OE 11.3.2, EA 10.x (afaik), plain eap files and we're using it for MDA (well, we reverse engineer a lot as well). We're working with IMO, I guess you heard that one before. What are you aiming for precisely?
Architect of the SmartComponent Library and WinKit
My interest is in the level of EA use in the OE community. Sparx stopped supporting OE as a repository with EA 11. For some purposes, the technology of the repository doesn't matter, but it does for direct tool building that manipulates the repository.
You have a point ... but it depends on the service providing what I need. I may have to go that route, but it clearly will be extra work. I don't suppose you have any shareable code that would jump start the process?
That's the bottom-up approach. The other way around: what requirements have you identified so far?
I won't be in Dusseldorf or Orlando.
Given that I am creating tools for other people to use, I can't really build in a requirement for the use of a dataserver.
Bronco ... that is a fairly large question which I will have to defer. I did it all once in the original version, but have just started working on an updated version and ran into this issue.
"A good beer next week may help me finding some ;-)"
They have good beer in Orlando? Wow!
I think that would be a rash assumption, unfortunately.
BTW, the alternative would be to move to generating XMI. I want to do that anyway in order to support other modeling tools, but was trying to put it off in the hopes of having something working faster. So, the alternative to implementing the service interface is to implement XMI with EA compatibility. That won't provide all the things a service could provide, but it will provide support for other modeling tools.