Cute Designer Error case

Designer 3.0 M3, on WinXP Sp2, 4GB RAM.

This was cute.  someone said there was a cool post-schema mapping rule 
attached to the schema map, that uses rename operation attribute and 
that I should leverage that notion in a rule.  (PS: Cool idea, I did not 
use it in this case, but I never thought of doing what it does before... 
  Could have possibilities...)

Ok, so the beauty of Designer is I import the GW driver, look at the 
rule, then delete it.  Except I left the rule open in a tab.

Then I deleted the GW driver object and saved.  Noticed the Tab was 
still open, went to close it, and Designer errored (cleanly and correctly).

My point is that I should not have been allowed to get to that error 

I'm going to need some steps to duplicate this one. When I delete an open
policy, a message appears stating the policy is open in an editor.

>>> On 5/14/2008 at 6:47 AM, in message
<VbBWj.12404$Dh4.2879@kovat.provo.novell.com>, Geoffrey
Carman<geoffreycarman@gmail.com> wrote:
> Designer 3.0 M3, on WinXP Sp2, 4GB RAM.
> 
> This was cute.  someone said there was a cool post-schema mapping rule 
> attached to the schema map, that uses rename operation attribute and 
> that I should leverage that notion in a rule.  (PS: Cool idea, I did not 
> 
> use it in this case, but I never thought of doing what it does before... 
> 
>   Could have possibilities...)
> 
> Ok, so the beauty of Designer is I import the GW driver, look at the 
> rule, then delete it.  Except I left the rule open in a tab.
> 
> Then I deleted the GW driver object and saved.  Noticed the Tab was 
> still open, went to close it, and Designer errored (cleanly and 
> correctly).
> 
> My point is that I should not have been allowed to get to that error 

I imported a driver, opened a policy.

(I probably quit Designer overnight and reopened in the morning but my 
laptop was suspended a couple of times in between).

Then from the modeler I deleted the entire driver object.

The Tab with the open rule went weird and errored (correctly) when I 
tried to look at it.


Brady Rogers wrote:
> I'm going to need some steps to duplicate this one. When I delete an open
> policy, a message appears stating the policy is open in an editor.
> 
>>>> On 5/14/2008 at 6:47 AM, in message
> <VbBWj.12404$Dh4.2879@kovat.provo.novell.com>, Geoffrey
> Carman<geoffreycarman@gmail.com> wrote:
>> Designer 3.0 M3, on WinXP Sp2, 4GB RAM.
>>
>> This was cute.  someone said there was a cool post-schema mapping rule

>> attached to the schema map, that uses rename operation attribute and 
>> that I should leverage that notion in a rule.  (PS: Cool idea, I did
not 
>>
>> use it in this case, but I never thought of doing what it does
before... 
>>
>>   Could have possibilities...)
>>
>> Ok, so the beauty of Designer is I import the GW driver, look at the 
>> rule, then delete it.  Except I left the rule open in a tab.
>>
>> Then I deleted the GW driver object and saved.  Noticed the Tab was 
>> still open, went to close it, and Designer errored (cleanly and 
>> correctly).
>>
>> My point is that I should not have been allowed to get to that error 

I've logged a bug for this problem.

https://bugzilla.novell.com/show_bug.cgi?id=390562 

Thanks.

>>> On 5/14/2008 at 3:57 PM, in message
<CfJWj.12645$Dh4.10133@kovat.provo.novell.com>, Geoffrey
Carman<geoffreycarman@gmail.com> wrote:
> I imported a driver, opened a policy.
> 
> (I probably quit Designer overnight and reopened in the morning but my 
> laptop was suspended a couple of times in between).
> 
> Then from the modeler I deleted the entire driver object.
> 
> The Tab with the open rule went weird and errored (correctly) when I 
> tried to look at it.
> 
> 
> Brady Rogers wrote:
>> I'm going to need some steps to duplicate this one. When I delete an 
> open
>> policy, a message appears stating the policy is open in an editor.
>> 
>>>>> On 5/14/2008 at 6:47 AM, in message
>> <VbBWj.12404$Dh4.2879@kovat.provo.novell.com>, Geoffrey
>> Carman<geoffreycarman@gmail.com> wrote:
>>> Designer 3.0 M3, on WinXP Sp2, 4GB RAM.
>>>
>>> This was cute.  someone said there was a cool post-schema mapping
rule 
>>> attached to the schema map, that uses rename operation attribute
and 
>>> that I should leverage that notion in a rule.  (PS: Cool idea, I
did not

> 
>>>
>>> use it in this case, but I never thought of doing what it does
before...

> 
>>>
>>>   Could have possibilities...)
>>>
>>> Ok, so the beauty of Designer is I import the GW driver, look at
the 
>>> rule, then delete it.  Except I left the rule open in a tab.
>>>
>>> Then I deleted the GW driver object and saved.  Noticed the Tab was

>>> still open, went to close it, and Designer errored (cleanly and 
>>> correctly).
>>>
>>> My point is that I should not have been allowed to get to that
error