Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Module handle null after edit()
Topic Summary:
Created On: 8-Jan-2009 23:13
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 8-Jan-2009 23:13
User is offline View Users Profile Print this message


Bob Beck

Posts: 1
Joined: 8-Jan-2009

Module m = edit( "module name" ) or edit( "module name", false )

Most of the time this works. However, sometimes "m" is null.

Why?

Bob Beck
beck@assurtech.com
Report this to a Moderator Report this to a Moderator
 9-Jan-2009 02:57
User is offline View Users Profile Print this message


David Jakad

Posts: 94
Joined: 20-Jul-2007

Off the top of my head, it could be a few things....

1.) The user running the DXL does not have edit privilege to that module
2.) Someone else has the same module open in shareable or exclusive edit mode, preventing you from opening the module in exclusive edit
3.) Incorrect module name and/or path

Ideally, you should always add checks to your DXL for null Modules (and null Objects), as these result in DXL errors to the user. Although, that can be a tedious chore.
Report this to a Moderator Report this to a Moderator
 9-Jan-2009 16:14
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

I've got lots of DXL that plow through modules, and I can safely say that my DXL has opened module's invisibly for edit perhaps a million times. I've never noticed a case where the module actually opened yet the returned Module parameter was null.

If the return Module is null it means the module did not open. If the Module is not null, you should still use "if (!isEdit(mod))", to make sure its is Edit and not open Read or Shared.

Of course, if you misspell the module name or you lack Read access, you cannot open it. Of course, if instead of an absolute path (e.g. /"MyProject/MyFolder/MyModule") you use a relative path (e.g. "MyModule") and you are not in MyFolder, you also cannot open the module.

v8 DXL has the ability to bypass the "Its open by someone else, open Read?" message you get when your dxl tries to open a module edit; no doubt it is open Edit by someone else and your DXL is not opening it read.

- Louie
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.