Home » Archived » XML Schema Definition (XSD) » Resource notifications
|
| Re: Resource notifications [message #44628 is a reply to message #44597] |
Mon, 17 May 2004 15:15   |
Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Lance,
The resource delta support is part of the platform so you'll need to ask them
about it.
Lance Phillips wrote:
> Ed,
> I am pretty sure this is not an XSD specific issue, but it is
> manifesting itself with XSDResources, so we'll start there. If I right
> click an XSDResource in the workspace and bring up the resource properties.
> Changing the read only status of the resource does not seem to produce any
> notifications. I have breakpoints is the delta processor for the resources
> as well as the notification processor... neither receive anything when I
> change that state. Is that expected, or are we missing something?
>
> thanks,
>
> lp
|
|
| |
| Re: Resource notifications [message #45470 is a reply to message #44659] |
Tue, 25 May 2004 15:24 |
 Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Ed,
I finally got a chance to get back to this. Here is the problem... the
events ARE getting processed, but the resource is never marked as dirty and
no notifications come out of the change.
The method in question is elementAttributeChanged on
XSDConcreteComponentImpl. It seems that notifications need to fired here
and at a minimum the resource needs to be marked as dirty???
thanks,
lp
"Lance Phillips" <lphillips@metamatrix.com> wrote in message
news:c8amte$f8h$1@eclipse.org...
> Thanks Ed!
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40A8D71D.33FC8542@ca.ibm.com...
> > Lance,
> >
> > The resource delta support is part of the platform so you'll need to ask
> them
> > about it.
> >
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > I am pretty sure this is not an XSD specific issue, but it is
> > > manifesting itself with XSDResources, so we'll start there. If I
right
> > > click an XSDResource in the workspace and bring up the resource
> properties.
> > > Changing the read only status of the resource does not seem to produce
> any
> > > notifications. I have breakpoints is the delta processor for the
> resources
> > > as well as the notification processor... neither receive anything when
I
> > > change that state. Is that expected, or are we missing something?
> > >
> > > thanks,
> > >
> > > lp
> >
>
>
|
|
|
| Re: Resource notifications [message #45588 is a reply to message #45470] |
Tue, 25 May 2004 16:16 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Lance,
The sample editor doesn't do resource delta listening. Is that what you are
getting at?
Lance Phillips wrote:
> Ed,
> I finally got a chance to get back to this. Here is the problem... the
> events ARE getting processed, but the resource is never marked as dirty and
> no notifications come out of the change.
>
> The method in question is elementAttributeChanged on
> XSDConcreteComponentImpl. It seems that notifications need to fired here
> and at a minimum the resource needs to be marked as dirty???
>
> thanks,
>
> lp
>
> "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> news:c8amte$f8h$1@eclipse.org...
> > Thanks Ed!
> >
> > lp
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:40A8D71D.33FC8542@ca.ibm.com...
> > > Lance,
> > >
> > > The resource delta support is part of the platform so you'll need to ask
> > them
> > > about it.
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > Ed,
> > > > I am pretty sure this is not an XSD specific issue, but it is
> > > > manifesting itself with XSDResources, so we'll start there. If I
> right
> > > > click an XSDResource in the workspace and bring up the resource
> > properties.
> > > > Changing the read only status of the resource does not seem to produce
> > any
> > > > notifications. I have breakpoints is the delta processor for the
> > resources
> > > > as well as the notification processor... neither receive anything when
> I
> > > > change that state. Is that expected, or are we missing something?
> > > >
> > > > thanks,
> > > >
> > > > lp
> > >
> >
> >
|
|
|
| Re: Resource notifications [message #45618 is a reply to message #45588] |
Tue, 25 May 2004 17:01 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Wrong thread.... sorry.
My issue was actually with changing the value of one of the DOM attributes
we've added to our objects. When we change one of those values in the
property editor we don't get a notification or resource dirty change. As
refresher for you, we hang some user properties as DOM Attr entities under
the XSDAnotation for our XSDSimpleTypeDefinitions. We see the properties
fine in our editor and are able to change them fine. It gets into the
method mentioned above fine, but we end up with no notifications and the
resource still shows as not dirty.
Sorry for the confusion.
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:40B3715B.F66AC009@ca.ibm.com...
> Lance,
>
> The sample editor doesn't do resource delta listening. Is that what you
are
> getting at?
>
>
> Lance Phillips wrote:
>
> > Ed,
> > I finally got a chance to get back to this. Here is the problem...
the
> > events ARE getting processed, but the resource is never marked as dirty
and
> > no notifications come out of the change.
> >
> > The method in question is elementAttributeChanged on
> > XSDConcreteComponentImpl. It seems that notifications need to fired
here
> > and at a minimum the resource needs to be marked as dirty???
> >
> > thanks,
> >
> > lp
> >
> > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > news:c8amte$f8h$1@eclipse.org...
> > > Thanks Ed!
> > >
> > > lp
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > Lance,
> > > >
> > > > The resource delta support is part of the platform so you'll need to
ask
> > > them
> > > > about it.
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > Ed,
> > > > > I am pretty sure this is not an XSD specific issue, but it is
> > > > > manifesting itself with XSDResources, so we'll start there. If I
> > right
> > > > > click an XSDResource in the workspace and bring up the resource
> > > properties.
> > > > > Changing the read only status of the resource does not seem to
produce
> > > any
> > > > > notifications. I have breakpoints is the delta processor for the
> > > resources
> > > > > as well as the notification processor... neither receive anything
when
> > I
> > > > > change that state. Is that expected, or are we missing something?
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > >
> > >
> > >
>
|
|
|
| Re: Resource notifications [message #45678 is a reply to message #45618] |
Tue, 25 May 2004 17:09 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Lance,
Did you modify the DOM without using a command?
Lance Phillips wrote:
> Wrong thread.... sorry.
>
> My issue was actually with changing the value of one of the DOM attributes
> we've added to our objects. When we change one of those values in the
> property editor we don't get a notification or resource dirty change. As
> refresher for you, we hang some user properties as DOM Attr entities under
> the XSDAnotation for our XSDSimpleTypeDefinitions. We see the properties
> fine in our editor and are able to change them fine. It gets into the
> method mentioned above fine, but we end up with no notifications and the
> resource still shows as not dirty.
>
> Sorry for the confusion.
>
> thanks,
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40B3715B.F66AC009@ca.ibm.com...
> > Lance,
> >
> > The sample editor doesn't do resource delta listening. Is that what you
> are
> > getting at?
> >
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > I finally got a chance to get back to this. Here is the problem...
> the
> > > events ARE getting processed, but the resource is never marked as dirty
> and
> > > no notifications come out of the change.
> > >
> > > The method in question is elementAttributeChanged on
> > > XSDConcreteComponentImpl. It seems that notifications need to fired
> here
> > > and at a minimum the resource needs to be marked as dirty???
> > >
> > > thanks,
> > >
> > > lp
> > >
> > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > news:c8amte$f8h$1@eclipse.org...
> > > > Thanks Ed!
> > > >
> > > > lp
> > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > Lance,
> > > > >
> > > > > The resource delta support is part of the platform so you'll need to
> ask
> > > > them
> > > > > about it.
> > > > >
> > > > >
> > > > > Lance Phillips wrote:
> > > > >
> > > > > > Ed,
> > > > > > I am pretty sure this is not an XSD specific issue, but it is
> > > > > > manifesting itself with XSDResources, so we'll start there. If I
> > > right
> > > > > > click an XSDResource in the workspace and bring up the resource
> > > > properties.
> > > > > > Changing the read only status of the resource does not seem to
> produce
> > > > any
> > > > > > notifications. I have breakpoints is the delta processor for the
> > > > resources
> > > > > > as well as the notification processor... neither receive anything
> when
> > > I
> > > > > > change that state. Is that expected, or are we missing something?
> > > > > >
> > > > > > thanks,
> > > > > >
> > > > > > lp
> > > > >
> > > >
> > > >
> >
|
|
|
| Re: Resource notifications [message #45997 is a reply to message #45678] |
Wed, 26 May 2004 14:40 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Yes! Could you point me at a code example of how to use a set command for a
DOM entity?
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:40B37DDF.3FF74443@ca.ibm.com...
> Lance,
>
> Did you modify the DOM without using a command?
>
>
> Lance Phillips wrote:
>
> > Wrong thread.... sorry.
> >
> > My issue was actually with changing the value of one of the DOM
attributes
> > we've added to our objects. When we change one of those values in the
> > property editor we don't get a notification or resource dirty change.
As
> > refresher for you, we hang some user properties as DOM Attr entities
under
> > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
properties
> > fine in our editor and are able to change them fine. It gets into the
> > method mentioned above fine, but we end up with no notifications and the
> > resource still shows as not dirty.
> >
> > Sorry for the confusion.
> >
> > thanks,
> >
> > lp
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:40B3715B.F66AC009@ca.ibm.com...
> > > Lance,
> > >
> > > The sample editor doesn't do resource delta listening. Is that what
you
> > are
> > > getting at?
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > Ed,
> > > > I finally got a chance to get back to this. Here is the
problem...
> > the
> > > > events ARE getting processed, but the resource is never marked as
dirty
> > and
> > > > no notifications come out of the change.
> > > >
> > > > The method in question is elementAttributeChanged on
> > > > XSDConcreteComponentImpl. It seems that notifications need to fired
> > here
> > > > and at a minimum the resource needs to be marked as dirty???
> > > >
> > > > thanks,
> > > >
> > > > lp
> > > >
> > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > news:c8amte$f8h$1@eclipse.org...
> > > > > Thanks Ed!
> > > > >
> > > > > lp
> > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > Lance,
> > > > > >
> > > > > > The resource delta support is part of the platform so you'll
need to
> > ask
> > > > > them
> > > > > > about it.
> > > > > >
> > > > > >
> > > > > > Lance Phillips wrote:
> > > > > >
> > > > > > > Ed,
> > > > > > > I am pretty sure this is not an XSD specific issue, but it
is
> > > > > > > manifesting itself with XSDResources, so we'll start there.
If I
> > > > right
> > > > > > > click an XSDResource in the workspace and bring up the
resource
> > > > > properties.
> > > > > > > Changing the read only status of the resource does not seem to
> > produce
> > > > > any
> > > > > > > notifications. I have breakpoints is the delta processor for
the
> > > > > resources
> > > > > > > as well as the notification processor... neither receive
anything
> > when
> > > > I
> > > > > > > change that state. Is that expected, or are we missing
something?
> > > > > > >
> > > > > > > thanks,
> > > > > > >
> > > > > > > lp
> > > > > >
> > > > >
> > > > >
> > >
>
|
|
|
| Re: Resource notifications [message #46030 is a reply to message #45997] |
Wed, 26 May 2004 15:09 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Lance,
You need to write your own command to do this. You can follow the way the
emf.edit commands are written.
Lance Phillips wrote:
> Yes! Could you point me at a code example of how to use a set command for a
> DOM entity?
>
> thanks,
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40B37DDF.3FF74443@ca.ibm.com...
> > Lance,
> >
> > Did you modify the DOM without using a command?
> >
> >
> > Lance Phillips wrote:
> >
> > > Wrong thread.... sorry.
> > >
> > > My issue was actually with changing the value of one of the DOM
> attributes
> > > we've added to our objects. When we change one of those values in the
> > > property editor we don't get a notification or resource dirty change.
> As
> > > refresher for you, we hang some user properties as DOM Attr entities
> under
> > > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
> properties
> > > fine in our editor and are able to change them fine. It gets into the
> > > method mentioned above fine, but we end up with no notifications and the
> > > resource still shows as not dirty.
> > >
> > > Sorry for the confusion.
> > >
> > > thanks,
> > >
> > > lp
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40B3715B.F66AC009@ca.ibm.com...
> > > > Lance,
> > > >
> > > > The sample editor doesn't do resource delta listening. Is that what
> you
> > > are
> > > > getting at?
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > Ed,
> > > > > I finally got a chance to get back to this. Here is the
> problem...
> > > the
> > > > > events ARE getting processed, but the resource is never marked as
> dirty
> > > and
> > > > > no notifications come out of the change.
> > > > >
> > > > > The method in question is elementAttributeChanged on
> > > > > XSDConcreteComponentImpl. It seems that notifications need to fired
> > > here
> > > > > and at a minimum the resource needs to be marked as dirty???
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > > >
> > > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > > news:c8amte$f8h$1@eclipse.org...
> > > > > > Thanks Ed!
> > > > > >
> > > > > > lp
> > > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > > Lance,
> > > > > > >
> > > > > > > The resource delta support is part of the platform so you'll
> need to
> > > ask
> > > > > > them
> > > > > > > about it.
> > > > > > >
> > > > > > >
> > > > > > > Lance Phillips wrote:
> > > > > > >
> > > > > > > > Ed,
> > > > > > > > I am pretty sure this is not an XSD specific issue, but it
> is
> > > > > > > > manifesting itself with XSDResources, so we'll start there.
> If I
> > > > > right
> > > > > > > > click an XSDResource in the workspace and bring up the
> resource
> > > > > > properties.
> > > > > > > > Changing the read only status of the resource does not seem to
> > > produce
> > > > > > any
> > > > > > > > notifications. I have breakpoints is the delta processor for
> the
> > > > > > resources
> > > > > > > > as well as the notification processor... neither receive
> anything
> > > when
> > > > > I
> > > > > > > > change that state. Is that expected, or are we missing
> something?
> > > > > > > >
> > > > > > > > thanks,
> > > > > > > >
> > > > > > > > lp
> > > > > > >
> > > > > >
> > > > > >
> > > >
> >
|
|
|
| Re: Resource notifications [message #46060 is a reply to message #46030] |
Wed, 26 May 2004 18:04 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
OK... I've written my own command to perform this change within a command.
I modeled my command after the SetCommand.
What do I have to do in my doExecute method to cause some notifications to
get fired? I have the XSDSimpleType definition that owns the Annotation.
But, it does not think that it has changed at the end of this process.
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:40B4B330.F7C465DB@ca.ibm.com...
> Lance,
>
> You need to write your own command to do this. You can follow the way the
> emf.edit commands are written.
>
>
> Lance Phillips wrote:
>
> > Yes! Could you point me at a code example of how to use a set command
for a
> > DOM entity?
> >
> > thanks,
> >
> > lp
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:40B37DDF.3FF74443@ca.ibm.com...
> > > Lance,
> > >
> > > Did you modify the DOM without using a command?
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > Wrong thread.... sorry.
> > > >
> > > > My issue was actually with changing the value of one of the DOM
> > attributes
> > > > we've added to our objects. When we change one of those values in
the
> > > > property editor we don't get a notification or resource dirty
change.
> > As
> > > > refresher for you, we hang some user properties as DOM Attr entities
> > under
> > > > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
> > properties
> > > > fine in our editor and are able to change them fine. It gets into
the
> > > > method mentioned above fine, but we end up with no notifications and
the
> > > > resource still shows as not dirty.
> > > >
> > > > Sorry for the confusion.
> > > >
> > > > thanks,
> > > >
> > > > lp
> > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > news:40B3715B.F66AC009@ca.ibm.com...
> > > > > Lance,
> > > > >
> > > > > The sample editor doesn't do resource delta listening. Is that
what
> > you
> > > > are
> > > > > getting at?
> > > > >
> > > > >
> > > > > Lance Phillips wrote:
> > > > >
> > > > > > Ed,
> > > > > > I finally got a chance to get back to this. Here is the
> > problem...
> > > > the
> > > > > > events ARE getting processed, but the resource is never marked
as
> > dirty
> > > > and
> > > > > > no notifications come out of the change.
> > > > > >
> > > > > > The method in question is elementAttributeChanged on
> > > > > > XSDConcreteComponentImpl. It seems that notifications need to
fired
> > > > here
> > > > > > and at a minimum the resource needs to be marked as dirty???
> > > > > >
> > > > > > thanks,
> > > > > >
> > > > > > lp
> > > > > >
> > > > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > > > news:c8amte$f8h$1@eclipse.org...
> > > > > > > Thanks Ed!
> > > > > > >
> > > > > > > lp
> > > > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > > > Lance,
> > > > > > > >
> > > > > > > > The resource delta support is part of the platform so you'll
> > need to
> > > > ask
> > > > > > > them
> > > > > > > > about it.
> > > > > > > >
> > > > > > > >
> > > > > > > > Lance Phillips wrote:
> > > > > > > >
> > > > > > > > > Ed,
> > > > > > > > > I am pretty sure this is not an XSD specific issue,
but it
> > is
> > > > > > > > > manifesting itself with XSDResources, so we'll start
there.
> > If I
> > > > > > right
> > > > > > > > > click an XSDResource in the workspace and bring up the
> > resource
> > > > > > > properties.
> > > > > > > > > Changing the read only status of the resource does not
seem to
> > > > produce
> > > > > > > any
> > > > > > > > > notifications. I have breakpoints is the delta processor
for
> > the
> > > > > > > resources
> > > > > > > > > as well as the notification processor... neither receive
> > anything
> > > > when
> > > > > > I
> > > > > > > > > change that state. Is that expected, or are we missing
> > something?
> > > > > > > > >
> > > > > > > > > thanks,
> > > > > > > > >
> > > > > > > > > lp
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
>
|
|
|
| Re: Resource notifications [message #46088 is a reply to message #46060] |
Wed, 26 May 2004 18:21 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Nevermind... I've got it.
Thanks for the help Ed!
lp
"Lance Phillips" <lphillips@metamatrix.com> wrote in message
news:c92lpf$p8$1@eclipse.org...
> OK... I've written my own command to perform this change within a command.
> I modeled my command after the SetCommand.
>
> What do I have to do in my doExecute method to cause some notifications to
> get fired? I have the XSDSimpleType definition that owns the Annotation.
> But, it does not think that it has changed at the end of this process.
>
> thanks,
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40B4B330.F7C465DB@ca.ibm.com...
> > Lance,
> >
> > You need to write your own command to do this. You can follow the way
the
> > emf.edit commands are written.
> >
> >
> > Lance Phillips wrote:
> >
> > > Yes! Could you point me at a code example of how to use a set command
> for a
> > > DOM entity?
> > >
> > > thanks,
> > >
> > > lp
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40B37DDF.3FF74443@ca.ibm.com...
> > > > Lance,
> > > >
> > > > Did you modify the DOM without using a command?
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > Wrong thread.... sorry.
> > > > >
> > > > > My issue was actually with changing the value of one of the DOM
> > > attributes
> > > > > we've added to our objects. When we change one of those values in
> the
> > > > > property editor we don't get a notification or resource dirty
> change.
> > > As
> > > > > refresher for you, we hang some user properties as DOM Attr
entities
> > > under
> > > > > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
> > > properties
> > > > > fine in our editor and are able to change them fine. It gets into
> the
> > > > > method mentioned above fine, but we end up with no notifications
and
> the
> > > > > resource still shows as not dirty.
> > > > >
> > > > > Sorry for the confusion.
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > news:40B3715B.F66AC009@ca.ibm.com...
> > > > > > Lance,
> > > > > >
> > > > > > The sample editor doesn't do resource delta listening. Is that
> what
> > > you
> > > > > are
> > > > > > getting at?
> > > > > >
> > > > > >
> > > > > > Lance Phillips wrote:
> > > > > >
> > > > > > > Ed,
> > > > > > > I finally got a chance to get back to this. Here is the
> > > problem...
> > > > > the
> > > > > > > events ARE getting processed, but the resource is never marked
> as
> > > dirty
> > > > > and
> > > > > > > no notifications come out of the change.
> > > > > > >
> > > > > > > The method in question is elementAttributeChanged on
> > > > > > > XSDConcreteComponentImpl. It seems that notifications need to
> fired
> > > > > here
> > > > > > > and at a minimum the resource needs to be marked as dirty???
> > > > > > >
> > > > > > > thanks,
> > > > > > >
> > > > > > > lp
> > > > > > >
> > > > > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > > > > news:c8amte$f8h$1@eclipse.org...
> > > > > > > > Thanks Ed!
> > > > > > > >
> > > > > > > > lp
> > > > > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > > > > Lance,
> > > > > > > > >
> > > > > > > > > The resource delta support is part of the platform so
you'll
> > > need to
> > > > > ask
> > > > > > > > them
> > > > > > > > > about it.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Lance Phillips wrote:
> > > > > > > > >
> > > > > > > > > > Ed,
> > > > > > > > > > I am pretty sure this is not an XSD specific issue,
> but it
> > > is
> > > > > > > > > > manifesting itself with XSDResources, so we'll start
> there.
> > > If I
> > > > > > > right
> > > > > > > > > > click an XSDResource in the workspace and bring up the
> > > resource
> > > > > > > > properties.
> > > > > > > > > > Changing the read only status of the resource does not
> seem to
> > > > > produce
> > > > > > > > any
> > > > > > > > > > notifications. I have breakpoints is the delta
processor
> for
> > > the
> > > > > > > > resources
> > > > > > > > > > as well as the notification processor... neither receive
> > > anything
> > > > > when
> > > > > > > I
> > > > > > > > > > change that state. Is that expected, or are we missing
> > > something?
> > > > > > > > > >
> > > > > > > > > > thanks,
> > > > > > > > > >
> > > > > > > > > > lp
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> >
>
>
|
|
|
| Re: Resource notifications [message #587138 is a reply to message #44597] |
Mon, 17 May 2004 15:15 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Lance,
The resource delta support is part of the platform so you'll need to ask them
about it.
Lance Phillips wrote:
> Ed,
> I am pretty sure this is not an XSD specific issue, but it is
> manifesting itself with XSDResources, so we'll start there. If I right
> click an XSDResource in the workspace and bring up the resource properties.
> Changing the read only status of the resource does not seem to produce any
> notifications. I have breakpoints is the delta processor for the resources
> as well as the notification processor... neither receive anything when I
> change that state. Is that expected, or are we missing something?
>
> thanks,
>
> lp
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
| |
| Re: Resource notifications [message #587497 is a reply to message #44659] |
Tue, 25 May 2004 15:24 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Ed,
I finally got a chance to get back to this. Here is the problem... the
events ARE getting processed, but the resource is never marked as dirty and
no notifications come out of the change.
The method in question is elementAttributeChanged on
XSDConcreteComponentImpl. It seems that notifications need to fired here
and at a minimum the resource needs to be marked as dirty???
thanks,
lp
"Lance Phillips" <lphillips@metamatrix.com> wrote in message
news:c8amte$f8h$1@eclipse.org...
> Thanks Ed!
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40A8D71D.33FC8542@ca.ibm.com...
> > Lance,
> >
> > The resource delta support is part of the platform so you'll need to ask
> them
> > about it.
> >
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > I am pretty sure this is not an XSD specific issue, but it is
> > > manifesting itself with XSDResources, so we'll start there. If I
right
> > > click an XSDResource in the workspace and bring up the resource
> properties.
> > > Changing the read only status of the resource does not seem to produce
> any
> > > notifications. I have breakpoints is the delta processor for the
> resources
> > > as well as the notification processor... neither receive anything when
I
> > > change that state. Is that expected, or are we missing something?
> > >
> > > thanks,
> > >
> > > lp
> >
>
>
|
|
|
| Re: Resource notifications [message #587562 is a reply to message #45470] |
Tue, 25 May 2004 16:16 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Lance,
The sample editor doesn't do resource delta listening. Is that what you are
getting at?
Lance Phillips wrote:
> Ed,
> I finally got a chance to get back to this. Here is the problem... the
> events ARE getting processed, but the resource is never marked as dirty and
> no notifications come out of the change.
>
> The method in question is elementAttributeChanged on
> XSDConcreteComponentImpl. It seems that notifications need to fired here
> and at a minimum the resource needs to be marked as dirty???
>
> thanks,
>
> lp
>
> "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> news:c8amte$f8h$1@eclipse.org...
> > Thanks Ed!
> >
> > lp
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:40A8D71D.33FC8542@ca.ibm.com...
> > > Lance,
> > >
> > > The resource delta support is part of the platform so you'll need to ask
> > them
> > > about it.
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > Ed,
> > > > I am pretty sure this is not an XSD specific issue, but it is
> > > > manifesting itself with XSDResources, so we'll start there. If I
> right
> > > > click an XSDResource in the workspace and bring up the resource
> > properties.
> > > > Changing the read only status of the resource does not seem to produce
> > any
> > > > notifications. I have breakpoints is the delta processor for the
> > resources
> > > > as well as the notification processor... neither receive anything when
> I
> > > > change that state. Is that expected, or are we missing something?
> > > >
> > > > thanks,
> > > >
> > > > lp
> > >
> >
> >
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Resource notifications [message #587570 is a reply to message #45588] |
Tue, 25 May 2004 17:01 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Wrong thread.... sorry.
My issue was actually with changing the value of one of the DOM attributes
we've added to our objects. When we change one of those values in the
property editor we don't get a notification or resource dirty change. As
refresher for you, we hang some user properties as DOM Attr entities under
the XSDAnotation for our XSDSimpleTypeDefinitions. We see the properties
fine in our editor and are able to change them fine. It gets into the
method mentioned above fine, but we end up with no notifications and the
resource still shows as not dirty.
Sorry for the confusion.
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:40B3715B.F66AC009@ca.ibm.com...
> Lance,
>
> The sample editor doesn't do resource delta listening. Is that what you
are
> getting at?
>
>
> Lance Phillips wrote:
>
> > Ed,
> > I finally got a chance to get back to this. Here is the problem...
the
> > events ARE getting processed, but the resource is never marked as dirty
and
> > no notifications come out of the change.
> >
> > The method in question is elementAttributeChanged on
> > XSDConcreteComponentImpl. It seems that notifications need to fired
here
> > and at a minimum the resource needs to be marked as dirty???
> >
> > thanks,
> >
> > lp
> >
> > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > news:c8amte$f8h$1@eclipse.org...
> > > Thanks Ed!
> > >
> > > lp
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > Lance,
> > > >
> > > > The resource delta support is part of the platform so you'll need to
ask
> > > them
> > > > about it.
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > Ed,
> > > > > I am pretty sure this is not an XSD specific issue, but it is
> > > > > manifesting itself with XSDResources, so we'll start there. If I
> > right
> > > > > click an XSDResource in the workspace and bring up the resource
> > > properties.
> > > > > Changing the read only status of the resource does not seem to
produce
> > > any
> > > > > notifications. I have breakpoints is the delta processor for the
> > > resources
> > > > > as well as the notification processor... neither receive anything
when
> > I
> > > > > change that state. Is that expected, or are we missing something?
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > >
> > >
> > >
>
|
|
|
| Re: Resource notifications [message #587591 is a reply to message #45618] |
Tue, 25 May 2004 17:09 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Lance,
Did you modify the DOM without using a command?
Lance Phillips wrote:
> Wrong thread.... sorry.
>
> My issue was actually with changing the value of one of the DOM attributes
> we've added to our objects. When we change one of those values in the
> property editor we don't get a notification or resource dirty change. As
> refresher for you, we hang some user properties as DOM Attr entities under
> the XSDAnotation for our XSDSimpleTypeDefinitions. We see the properties
> fine in our editor and are able to change them fine. It gets into the
> method mentioned above fine, but we end up with no notifications and the
> resource still shows as not dirty.
>
> Sorry for the confusion.
>
> thanks,
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40B3715B.F66AC009@ca.ibm.com...
> > Lance,
> >
> > The sample editor doesn't do resource delta listening. Is that what you
> are
> > getting at?
> >
> >
> > Lance Phillips wrote:
> >
> > > Ed,
> > > I finally got a chance to get back to this. Here is the problem...
> the
> > > events ARE getting processed, but the resource is never marked as dirty
> and
> > > no notifications come out of the change.
> > >
> > > The method in question is elementAttributeChanged on
> > > XSDConcreteComponentImpl. It seems that notifications need to fired
> here
> > > and at a minimum the resource needs to be marked as dirty???
> > >
> > > thanks,
> > >
> > > lp
> > >
> > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > news:c8amte$f8h$1@eclipse.org...
> > > > Thanks Ed!
> > > >
> > > > lp
> > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > Lance,
> > > > >
> > > > > The resource delta support is part of the platform so you'll need to
> ask
> > > > them
> > > > > about it.
> > > > >
> > > > >
> > > > > Lance Phillips wrote:
> > > > >
> > > > > > Ed,
> > > > > > I am pretty sure this is not an XSD specific issue, but it is
> > > > > > manifesting itself with XSDResources, so we'll start there. If I
> > > right
> > > > > > click an XSDResource in the workspace and bring up the resource
> > > > properties.
> > > > > > Changing the read only status of the resource does not seem to
> produce
> > > > any
> > > > > > notifications. I have breakpoints is the delta processor for the
> > > > resources
> > > > > > as well as the notification processor... neither receive anything
> when
> > > I
> > > > > > change that state. Is that expected, or are we missing something?
> > > > > >
> > > > > > thanks,
> > > > > >
> > > > > > lp
> > > > >
> > > >
> > > >
> >
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Resource notifications [message #587685 is a reply to message #45678] |
Wed, 26 May 2004 14:40 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Yes! Could you point me at a code example of how to use a set command for a
DOM entity?
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:40B37DDF.3FF74443@ca.ibm.com...
> Lance,
>
> Did you modify the DOM without using a command?
>
>
> Lance Phillips wrote:
>
> > Wrong thread.... sorry.
> >
> > My issue was actually with changing the value of one of the DOM
attributes
> > we've added to our objects. When we change one of those values in the
> > property editor we don't get a notification or resource dirty change.
As
> > refresher for you, we hang some user properties as DOM Attr entities
under
> > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
properties
> > fine in our editor and are able to change them fine. It gets into the
> > method mentioned above fine, but we end up with no notifications and the
> > resource still shows as not dirty.
> >
> > Sorry for the confusion.
> >
> > thanks,
> >
> > lp
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:40B3715B.F66AC009@ca.ibm.com...
> > > Lance,
> > >
> > > The sample editor doesn't do resource delta listening. Is that what
you
> > are
> > > getting at?
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > Ed,
> > > > I finally got a chance to get back to this. Here is the
problem...
> > the
> > > > events ARE getting processed, but the resource is never marked as
dirty
> > and
> > > > no notifications come out of the change.
> > > >
> > > > The method in question is elementAttributeChanged on
> > > > XSDConcreteComponentImpl. It seems that notifications need to fired
> > here
> > > > and at a minimum the resource needs to be marked as dirty???
> > > >
> > > > thanks,
> > > >
> > > > lp
> > > >
> > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > news:c8amte$f8h$1@eclipse.org...
> > > > > Thanks Ed!
> > > > >
> > > > > lp
> > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > Lance,
> > > > > >
> > > > > > The resource delta support is part of the platform so you'll
need to
> > ask
> > > > > them
> > > > > > about it.
> > > > > >
> > > > > >
> > > > > > Lance Phillips wrote:
> > > > > >
> > > > > > > Ed,
> > > > > > > I am pretty sure this is not an XSD specific issue, but it
is
> > > > > > > manifesting itself with XSDResources, so we'll start there.
If I
> > > > right
> > > > > > > click an XSDResource in the workspace and bring up the
resource
> > > > > properties.
> > > > > > > Changing the read only status of the resource does not seem to
> > produce
> > > > > any
> > > > > > > notifications. I have breakpoints is the delta processor for
the
> > > > > resources
> > > > > > > as well as the notification processor... neither receive
anything
> > when
> > > > I
> > > > > > > change that state. Is that expected, or are we missing
something?
> > > > > > >
> > > > > > > thanks,
> > > > > > >
> > > > > > > lp
> > > > > >
> > > > >
> > > > >
> > >
>
|
|
|
| Re: Resource notifications [message #587696 is a reply to message #45997] |
Wed, 26 May 2004 15:09 |
Ed Merks
Messages: 33137
Registered: July 2009 |
Senior Member |
|
|
Lance,
You need to write your own command to do this. You can follow the way the
emf.edit commands are written.
Lance Phillips wrote:
> Yes! Could you point me at a code example of how to use a set command for a
> DOM entity?
>
> thanks,
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40B37DDF.3FF74443@ca.ibm.com...
> > Lance,
> >
> > Did you modify the DOM without using a command?
> >
> >
> > Lance Phillips wrote:
> >
> > > Wrong thread.... sorry.
> > >
> > > My issue was actually with changing the value of one of the DOM
> attributes
> > > we've added to our objects. When we change one of those values in the
> > > property editor we don't get a notification or resource dirty change.
> As
> > > refresher for you, we hang some user properties as DOM Attr entities
> under
> > > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
> properties
> > > fine in our editor and are able to change them fine. It gets into the
> > > method mentioned above fine, but we end up with no notifications and the
> > > resource still shows as not dirty.
> > >
> > > Sorry for the confusion.
> > >
> > > thanks,
> > >
> > > lp
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40B3715B.F66AC009@ca.ibm.com...
> > > > Lance,
> > > >
> > > > The sample editor doesn't do resource delta listening. Is that what
> you
> > > are
> > > > getting at?
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > Ed,
> > > > > I finally got a chance to get back to this. Here is the
> problem...
> > > the
> > > > > events ARE getting processed, but the resource is never marked as
> dirty
> > > and
> > > > > no notifications come out of the change.
> > > > >
> > > > > The method in question is elementAttributeChanged on
> > > > > XSDConcreteComponentImpl. It seems that notifications need to fired
> > > here
> > > > > and at a minimum the resource needs to be marked as dirty???
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > > >
> > > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > > news:c8amte$f8h$1@eclipse.org...
> > > > > > Thanks Ed!
> > > > > >
> > > > > > lp
> > > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > > Lance,
> > > > > > >
> > > > > > > The resource delta support is part of the platform so you'll
> need to
> > > ask
> > > > > > them
> > > > > > > about it.
> > > > > > >
> > > > > > >
> > > > > > > Lance Phillips wrote:
> > > > > > >
> > > > > > > > Ed,
> > > > > > > > I am pretty sure this is not an XSD specific issue, but it
> is
> > > > > > > > manifesting itself with XSDResources, so we'll start there.
> If I
> > > > > right
> > > > > > > > click an XSDResource in the workspace and bring up the
> resource
> > > > > > properties.
> > > > > > > > Changing the read only status of the resource does not seem to
> > > produce
> > > > > > any
> > > > > > > > notifications. I have breakpoints is the delta processor for
> the
> > > > > > resources
> > > > > > > > as well as the notification processor... neither receive
> anything
> > > when
> > > > > I
> > > > > > > > change that state. Is that expected, or are we missing
> something?
> > > > > > > >
> > > > > > > > thanks,
> > > > > > > >
> > > > > > > > lp
> > > > > > >
> > > > > >
> > > > > >
> > > >
> >
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
| Re: Resource notifications [message #587704 is a reply to message #46030] |
Wed, 26 May 2004 18:04 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
OK... I've written my own command to perform this change within a command.
I modeled my command after the SetCommand.
What do I have to do in my doExecute method to cause some notifications to
get fired? I have the XSDSimpleType definition that owns the Annotation.
But, it does not think that it has changed at the end of this process.
thanks,
lp
"Ed Merks" <merks@ca.ibm.com> wrote in message
news:40B4B330.F7C465DB@ca.ibm.com...
> Lance,
>
> You need to write your own command to do this. You can follow the way the
> emf.edit commands are written.
>
>
> Lance Phillips wrote:
>
> > Yes! Could you point me at a code example of how to use a set command
for a
> > DOM entity?
> >
> > thanks,
> >
> > lp
> > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > news:40B37DDF.3FF74443@ca.ibm.com...
> > > Lance,
> > >
> > > Did you modify the DOM without using a command?
> > >
> > >
> > > Lance Phillips wrote:
> > >
> > > > Wrong thread.... sorry.
> > > >
> > > > My issue was actually with changing the value of one of the DOM
> > attributes
> > > > we've added to our objects. When we change one of those values in
the
> > > > property editor we don't get a notification or resource dirty
change.
> > As
> > > > refresher for you, we hang some user properties as DOM Attr entities
> > under
> > > > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
> > properties
> > > > fine in our editor and are able to change them fine. It gets into
the
> > > > method mentioned above fine, but we end up with no notifications and
the
> > > > resource still shows as not dirty.
> > > >
> > > > Sorry for the confusion.
> > > >
> > > > thanks,
> > > >
> > > > lp
> > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > news:40B3715B.F66AC009@ca.ibm.com...
> > > > > Lance,
> > > > >
> > > > > The sample editor doesn't do resource delta listening. Is that
what
> > you
> > > > are
> > > > > getting at?
> > > > >
> > > > >
> > > > > Lance Phillips wrote:
> > > > >
> > > > > > Ed,
> > > > > > I finally got a chance to get back to this. Here is the
> > problem...
> > > > the
> > > > > > events ARE getting processed, but the resource is never marked
as
> > dirty
> > > > and
> > > > > > no notifications come out of the change.
> > > > > >
> > > > > > The method in question is elementAttributeChanged on
> > > > > > XSDConcreteComponentImpl. It seems that notifications need to
fired
> > > > here
> > > > > > and at a minimum the resource needs to be marked as dirty???
> > > > > >
> > > > > > thanks,
> > > > > >
> > > > > > lp
> > > > > >
> > > > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > > > news:c8amte$f8h$1@eclipse.org...
> > > > > > > Thanks Ed!
> > > > > > >
> > > > > > > lp
> > > > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > > > Lance,
> > > > > > > >
> > > > > > > > The resource delta support is part of the platform so you'll
> > need to
> > > > ask
> > > > > > > them
> > > > > > > > about it.
> > > > > > > >
> > > > > > > >
> > > > > > > > Lance Phillips wrote:
> > > > > > > >
> > > > > > > > > Ed,
> > > > > > > > > I am pretty sure this is not an XSD specific issue,
but it
> > is
> > > > > > > > > manifesting itself with XSDResources, so we'll start
there.
> > If I
> > > > > > right
> > > > > > > > > click an XSDResource in the workspace and bring up the
> > resource
> > > > > > > properties.
> > > > > > > > > Changing the read only status of the resource does not
seem to
> > > > produce
> > > > > > > any
> > > > > > > > > notifications. I have breakpoints is the delta processor
for
> > the
> > > > > > > resources
> > > > > > > > > as well as the notification processor... neither receive
> > anything
> > > > when
> > > > > > I
> > > > > > > > > change that state. Is that expected, or are we missing
> > something?
> > > > > > > > >
> > > > > > > > > thanks,
> > > > > > > > >
> > > > > > > > > lp
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > >
>
|
|
|
| Re: Resource notifications [message #587713 is a reply to message #46060] |
Wed, 26 May 2004 18:21 |
Lance Phillips
Messages: 210
Registered: July 2009 |
Senior Member |
|
|
Nevermind... I've got it.
Thanks for the help Ed!
lp
"Lance Phillips" <lphillips@metamatrix.com> wrote in message
news:c92lpf$p8$1@eclipse.org...
> OK... I've written my own command to perform this change within a command.
> I modeled my command after the SetCommand.
>
> What do I have to do in my doExecute method to cause some notifications to
> get fired? I have the XSDSimpleType definition that owns the Annotation.
> But, it does not think that it has changed at the end of this process.
>
> thanks,
>
> lp
> "Ed Merks" <merks@ca.ibm.com> wrote in message
> news:40B4B330.F7C465DB@ca.ibm.com...
> > Lance,
> >
> > You need to write your own command to do this. You can follow the way
the
> > emf.edit commands are written.
> >
> >
> > Lance Phillips wrote:
> >
> > > Yes! Could you point me at a code example of how to use a set command
> for a
> > > DOM entity?
> > >
> > > thanks,
> > >
> > > lp
> > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > news:40B37DDF.3FF74443@ca.ibm.com...
> > > > Lance,
> > > >
> > > > Did you modify the DOM without using a command?
> > > >
> > > >
> > > > Lance Phillips wrote:
> > > >
> > > > > Wrong thread.... sorry.
> > > > >
> > > > > My issue was actually with changing the value of one of the DOM
> > > attributes
> > > > > we've added to our objects. When we change one of those values in
> the
> > > > > property editor we don't get a notification or resource dirty
> change.
> > > As
> > > > > refresher for you, we hang some user properties as DOM Attr
entities
> > > under
> > > > > the XSDAnotation for our XSDSimpleTypeDefinitions. We see the
> > > properties
> > > > > fine in our editor and are able to change them fine. It gets into
> the
> > > > > method mentioned above fine, but we end up with no notifications
and
> the
> > > > > resource still shows as not dirty.
> > > > >
> > > > > Sorry for the confusion.
> > > > >
> > > > > thanks,
> > > > >
> > > > > lp
> > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > news:40B3715B.F66AC009@ca.ibm.com...
> > > > > > Lance,
> > > > > >
> > > > > > The sample editor doesn't do resource delta listening. Is that
> what
> > > you
> > > > > are
> > > > > > getting at?
> > > > > >
> > > > > >
> > > > > > Lance Phillips wrote:
> > > > > >
> > > > > > > Ed,
> > > > > > > I finally got a chance to get back to this. Here is the
> > > problem...
> > > > > the
> > > > > > > events ARE getting processed, but the resource is never marked
> as
> > > dirty
> > > > > and
> > > > > > > no notifications come out of the change.
> > > > > > >
> > > > > > > The method in question is elementAttributeChanged on
> > > > > > > XSDConcreteComponentImpl. It seems that notifications need to
> fired
> > > > > here
> > > > > > > and at a minimum the resource needs to be marked as dirty???
> > > > > > >
> > > > > > > thanks,
> > > > > > >
> > > > > > > lp
> > > > > > >
> > > > > > > "Lance Phillips" <lphillips@metamatrix.com> wrote in message
> > > > > > > news:c8amte$f8h$1@eclipse.org...
> > > > > > > > Thanks Ed!
> > > > > > > >
> > > > > > > > lp
> > > > > > > > "Ed Merks" <merks@ca.ibm.com> wrote in message
> > > > > > > > news:40A8D71D.33FC8542@ca.ibm.com...
> > > > > > > > > Lance,
> > > > > > > > >
> > > > > > > > > The resource delta support is part of the platform so
you'll
> > > need to
> > > > > ask
> > > > > > > > them
> > > > > > > > > about it.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Lance Phillips wrote:
> > > > > > > > >
> > > > > > > > > > Ed,
> > > > > > > > > > I am pretty sure this is not an XSD specific issue,
> but it
> > > is
> > > > > > > > > > manifesting itself with XSDResources, so we'll start
> there.
> > > If I
> > > > > > > right
> > > > > > > > > > click an XSDResource in the workspace and bring up the
> > > resource
> > > > > > > > properties.
> > > > > > > > > > Changing the read only status of the resource does not
> seem to
> > > > > produce
> > > > > > > > any
> > > > > > > > > > notifications. I have breakpoints is the delta
processor
> for
> > > the
> > > > > > > > resources
> > > > > > > > > > as well as the notification processor... neither receive
> > > anything
> > > > > when
> > > > > > > I
> > > > > > > > > > change that state. Is that expected, or are we missing
> > > something?
> > > > > > > > > >
> > > > > > > > > > thanks,
> > > > > > > > > >
> > > > > > > > > > lp
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > >
> >
>
>
|
|
|
Goto Forum:
Current Time: Fri Apr 19 14:59:50 GMT 2024
Powered by FUDForum. Page generated in 0.03275 seconds |
] 
Search
Help
Register
Login
Home
