Book a Demo

Author Topic: Stereotype of operation parameters  (Read 6020 times)

Thomas Mercer-Hursh

  • EA User
  • **
  • Posts: 386
  • Karma: +0/-0
  • Computing Integrity
    • View Profile
Stereotype of operation parameters
« on: January 01, 2008, 01:47:13 pm »
In the Help on the Parameter object type it says:
---------------------
public Class

A Parameter object represents a method argument and is accessed through the Method Parameters collection.

Associated table in .EAP file: t_operationparams
---------------------
Among the list of attributes is Stereotype and StereotypeEx, but, if I look at the actual data structure, there is no Stereotype column in the t_OperationParams table.  The presence of StereotypeEx suggests that this might be implemented via some joined table to allow more than one to apply to an instance, but I'm not seeing another table which looks like it might contain this information.  I also see no way to set this information through the EA interface.

The purpose here is to record some information about the fields which compose an index, including whether or not each component is ascending or descending.  I see that there is t_operationtags where I could put a list of the fields and the values, but that seems like the wrong spot ... and also has no direct EA interface other than that this is where the Delete Cascade and Update Cascade values are kept.

PY

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
  • I love Python
    • View Profile
Re: Stereotype of operation parameters
« Reply #1 on: April 15, 2008, 03:05:41 am »
Hi Thomas,
thanks for the report. In my project I came across to the issue and now I am looking for a workaround..

does someone have any suggestion?

currently I have:
(Python, EA 7.0.818)

            aNode = theMethod.Parameters.AddNew(strName,strType)
            aNode.Default = strValue_Default
            aNode.Stereotype = strStereotype
            aNode.Notes = strNotes
            aNode.Kind = strKind

            aNode.Update
            theMethod.Parameters.Refresh
            theMethod.Update

at the end all values are filled in model, except strStereotype as the only one missing....

thanks for any help in advance!

Pablo
« Last Edit: April 15, 2008, 03:06:03 am by PY »

thomas.kilian

  • Guest
Re: Stereotype of operation parameters
« Reply #2 on: April 15, 2008, 03:28:56 am »
Just another case of EAUI, I guess.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Stereotype of operation parameters
« Reply #3 on: April 15, 2008, 08:20:11 am »
Yes, parameter stereotypes are stored in the t_xref table.  (As are multiple stereotypes for anything else.)

Just a guess.  Try getting around the issue by saving the parameter, adding the stereotype and saving again.

PY

  • EA User
  • **
  • Posts: 20
  • Karma: +0/-0
  • I love Python
    • View Profile
Re: Stereotype of operation parameters
« Reply #4 on: April 15, 2008, 09:35:57 pm »
hi,

thanks for the idea, but it doesn't work. :(

any idea if newer EA versions >7.0.818 can handle this issue?

Best Regards and thanks in advance again,

Pablo


Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Stereotype of operation parameters
« Reply #5 on: April 16, 2008, 08:07:40 am »
All I can recommend is sending in a bug report using the link at the bottom of this page.

Manfred Kröpfli

  • EA User
  • **
  • Posts: 31
  • Karma: +0/-0
    • View Profile
Re: Stereotype of operation parameters
« Reply #6 on: September 22, 2011, 09:01:29 pm »
Hi @Sparx,

Is this issue still not fixed in EA8.0.864?

I experience
Code: [Select]
Parameter.Stereotype = "abc" or
Code: [Select]
Parameter.StereotypeEx = "abc" not working as expected. A followup
Code: [Select]
Parameter.Update() will not propagate a stereotype change for an operation parameter to the database.

Please confirm or provide any workaround

brgs Manfred
Cheers
Manfred