![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: DOORS Analyst DXL error Topic Summary: Created On: 10-Jun-2005 18:11 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: Sorry for not posting to this in awhile. After the issue has been a problem for over two months - we ended up removing DOORS analyst and deleting the trigger. Let me know what you have done to solve the problem Christopher. | |
![]() |
|
Description
---------------------- Our users that DO NOT have analyst installed are getting the following error when opening one module. DXL: (integrations/tau/analyst/includes/anlyst_uml_icons.inc (no such file or directory) If you click ok, it lets you in the module but when you close it and reopen, you get the error again. The cause of the problem is that every time a user with analyst opens these modules, a trigger is created. When users who do not have analyst open the modules, they get an error. Telelogic offered two suggestions - (not really very good solutions). 1. delete the triggers : but since the triggers are made everytime and our users are constantly opening modules, this would be VERY cumbersome, and our own customized triggers would also be deleted 2. disable analyst and when a user with analyst wants to use a feature of analyst, they will have to manually enable analyst themselves Has anyone encountered this issue and if so, how did you handle it? Any help/advice would be greatly appreciated. Thanks! ------------------------- Hello |
|
![]() |
|
![]() |
|
Have one of your non-TAU users create a doors icon with the following switch: -l c:\Doors_LogFile.txt. This should trap the DXL errors to the file and not bother the user about them.
Icon "target" may look like this: c:\Program Files\Telelogic\DOORS 7.1\bin\doors.exe -l c:\Doors_LogFile.txt If you have access to the triggers themselves or the code that sets them, some of us could debug them. - Louie |
|
![]() |
|
![]() |
|
This same problem is caused by the Artisan DOORS Synchroniser (ADS).
It also occurs quite frequently when modules containing attribute and layout DXL are restored to other database. Another common cause of run-time errors is accessing non-system attributes directly without first checking if they exist. The function probeAttr_() get round this one. Unless you are absolutely certain that a file will be there, then the DXL should check for the existence of #include files before trying to include them. This is however easier said than done. It is not enough to simply put the #include inside an if statement because the file is included when the DXL is loaded, before execution. The only way I have found to achieve this is to check for the existence of the file to be included and then put the actual #include inside an eval_() call. The attached example is code that I add to the startup.dxl to get round errors caused when a user opens a module that was created by the ADS on a client that does not have the ADS installed. The function isFile() uses stat to determine if the file exists and can be read okay. I have not tried using this technique anywhere else yet. There are issues with the fact that code inside the eval_() is executed within its own context after the current DXL completes. ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
I added the switch: -l c:\Doors_LogFile.txt to a doors icon. It does trap the error in a log file, but when I open an analyst-enabled module, a message box appears on the screen saying that "DXL contains 1 error" with an OK button. Hitting OK still allows the user to enter the module, but the message box is still not very user friendly.
Tony, I am not sure if your recommendations will work for us. The script that is looking for the file is provided by Telelogic, we do not own it. ------------------------- Hello Edited: 13-Jun-2005 at 17:45 by Maria Manco |
|
![]() |
|
![]() |
|
I just looked at our Telelogic profiles. Small world: what's the chances we are both from Alberta, Andorra. Stop in sometime: I live in the yellow house with the brown porch just north of the stop sign.
- Louie |
|
![]() |
|
![]() |
|
Maria, looks like you are stuck with having to install analyst on all your clients.
Did telelogic suggest this? ------------------------- Tony Goodman http://www.smartdxl.com |
|
![]() |
|
![]() |
|
No - Telelogic did not suggest this - or tell us about the problem. We are considering just getting rid of analyst all together. Thanks for all your suggestions!
------------------------- Hello |
|
![]() |
|
![]() |
|
We are having the exact same problem with Analyst here. Only some users have it installed and when non-analyst users go to modify the module, they get a DXL error.
|
|
![]() |
|
![]() |
|
Edited: 21-Jul-2005 at 10:04 by Philippe Lugagne |
|
![]() |
|
![]() |
|
Sorry for not posting to this in awhile. After the issue has been a problem for over two months - we ended up removing DOORS analyst and deleting the trigger. Let me know what you have done to solve the problem Christopher.
------------------------- Hello |
|
![]() |
Telelogic DOORS
» General Discussion
»
DOORS Analyst DXL error
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.