You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since the solution of #1121 (commit: d60ddcf), there is no way to override implementation version name in an outbound association.
In my application I override the implementation UID with my own one, and it causes the situation that the UID and the name logically points to a different application.
Is there any clean and suggested way to set our own ImplClassUID and ImplVersionName in an outbound association? I'm out of ideas, because:
Implementation.getVersionName is a static method which returns a static field.
AAssociateRQAC.setImplVersionName() is a final method so can not be overriden.
To Reproduce
Steps to reproduce the behavior:
2. create AAssociateRQ
3. use setImplClassUID() and setImplVersionName() methods on AAssociateRQ to override implementation UID and Version name with your own one to better recognize communication parties
4. use ApplicationEntity.connect() to establish remote association
Expected behavior
implClassUID and implVersionName (even if the second one is optional) can be overriden and stays consistent.
The text was updated successfully, but these errors were encountered:
Describe the bug
Since the solution of #1121 (commit: d60ddcf), there is no way to override implementation version name in an outbound association.
In my application I override the implementation UID with my own one, and it causes the situation that the UID and the name logically points to a different application.
So such situations may occur:
Is there any clean and suggested way to set our own ImplClassUID and ImplVersionName in an outbound association? I'm out of ideas, because:
To Reproduce
Steps to reproduce the behavior:
2. create AAssociateRQ
3. use setImplClassUID() and setImplVersionName() methods on AAssociateRQ to override implementation UID and Version name with your own one to better recognize communication parties
4. use ApplicationEntity.connect() to establish remote association
Expected behavior
implClassUID and implVersionName (even if the second one is optional) can be overriden and stays consistent.
The text was updated successfully, but these errors were encountered: