Messages

1

Suggestions and Requests / Re: Renaming a class used as an operation argument

« on: January 17, 2005, 05:08:01 pm »

I did so. Thanks, Yves.

2

Suggestions and Requests / Re: Renaming a class used as an operation argument

« on: January 14, 2005, 08:03:49 am »

Hi Thomas,

Sorry to have been so long to reply, I was assigned on a totally different duty for the last 2 weeks or so. Now, here we go...

I should have mentioned in my first message  that the problem occurs for messages used as part of sequence diagrams. When a class modification is done, the messages using this class are not synchronized (namely, return types, maybe others as welll) unless you reselect the message and re-submit the same class method as the message type.

Regards,
Yves.

3

Suggestions and Requests / Renaming a class used as an operation argument

« on: January 04, 2005, 01:24:19 pm »

Hi everyone,

I am pretty new to EA and found that whenever I rename a class that I peviously used as an argument for an operation, the type of the argument will not follow the new class name. Anything I am not doing right?

Thanks,
Yves.

4

General Board / Re: Debugging mixed managed/unmanaged application

« on: October 24, 2014, 04:23:10 am »

Hi Jean-Pierre,

Typically, this kind of behaviour comes from a bad synchronization between your model and your code. Try the "Synchronize Package with code" command on the part of your code where your breakpoints are not bound to your code. Hope it helps...

5

General Board / Import XSD statement into a WSDL file

« on: October 17, 2014, 05:49:06 am »

I'm trying to generate an import statement in a WSDL file following this process:

• create the PIM Classes for Types

• create a PIM Interface representing the service to be exposed

• Transform a PIM Classes into an <<XSDschema>>

• Transform the PIM Interface, bound to the above <<XSDschema>> into an <<WSDL>> Component (by selecting both the <<XSDschema>> Package and the PIM Interface to launch the Transform command)

• Generate the .wsdl file from the <<WSDL>> Component

Doing so, I could achieve to generate the .wsdl file that is using the proper object types but the <types/> section is empty. I suspect to have a problem with the namespaces I am using but couldn't find out so far. Is there any location in the Sparx documentation where this process is documented? Thanks in advance.

6

Automation Interface, Add-Ins and Tools / Re: Direct .dll debugging

« on: October 24, 2014, 07:27:45 am »

OK, at the risk to look a little fuzzy, I will reply to myself for the ones of you that may seek for the same thing as I was. Actually, EA provides a very convenient tool to test DLLs. This is the Execution Analyzer Workbench. You just need to configure your Debug - Workbench script (you enter the path of your .dll file in the required script parameter). Then, you can right-click on any Class of your dll and select the "Execution Analyzer - Create Workbench Instance of Class". The remaining of the process is self explanatory.

7

Automation Interface, Add-Ins and Tools / Direct .dll debugging

« on: October 24, 2014, 04:37:13 am »

Using the Execution Analyzer, I try to launch a Debug session for a .dll file. But since this procedure is not documented in EA (as far as I know...), I read a rather outdated article titled "Visual Execution Analyzer in Enterprise Architect" (2009) that explains that, when debugging a Class library, you can pass the Class name, the method name and the value of the arguments separated by comas as arguments of the command line. I tried so... the Debug session seems to be properly launched but the arguments seem to be totally ignored. The Debug window just shows the Stack depth being used and that's it, nothing else. I never hit a Breakpoint. To confirm, I just deleted the arguments and got the exact same behaviour. Any help would be appreciated.

8

Automation Interface, Add-Ins and Tools / CreateBaselineEx API

« on: October 18, 2014, 04:44:55 am »

I am trying to use the method

Project.CreateBaselineEx(string PackageGUID, string Version, string Notes, EA.CreateBaselineFlag Flags)

When doing so, the Baseline is created and the method returns True, which seems to be OK so far. But when I am trying to reload the Package from the Baseline content, the child Packages are first displayed with the old Package name in the Project Browser. But when I click on the Package icon, its name changes for the new name contained in the Baseline. Even worst, if I reload the Package content from the DB after clicking on the icon to get the new content, the old content re-appears with the same bug (re-clicking on it makes the new content appears).

This definitely looks like a bug to me.

My guess is that it may be related to this "stub" concept referred to in the cbSaveToStub documentation as follows:

cbSaveToStub --  Baseline this package with only immediate children (child packages are included as stubs only).

Thanks in advance for your help.