[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [ve-dev] Contributing to registry prior tocomponentinstantia tion?
|
Good
point. I'll look into that.
Sorry
to be a nuisance, but another thing I'm having trouble with is that I
wish to be able to call code in the target VM prior to
termination of the target VM (when it is known that it is about to
close). This is for the purposes of cleaning up, as this process is remotely
connected to a server, and needs to do some logging off
operations.
I thought that I could just implement the
ProxyFactoryRegistry.IRegistryListener,
and
add a listener that when invoked calls my logging off code on the target
VM.
However, this method has the following javadoc
comment:
'Method registryTerminated. The registry has
been terminated. When this is called the registry is no longer valid. It should
not be assumed any calls can be made to the registry. '
Is there any way I can do
what I want?
Thanks,
Darren
Hurt
Hi,
Make sure the errors are not due to
static initializations of your classes. Those can sometimes occur earlier
before the actual instances are created.
Rich
Darren Hurt
<darren.hurt@xxxxxxxxxx> Sent by: ve-dev-bounces@xxxxxxxxxxx
05/11/2006 10:57 AM
Please respond
to Discussions people developing code for the Visual Editor
project
<ve-dev@xxxxxxxxxxx> |
|
To
| "'Discussions people developing
code for the Visual Editor project'"
<ve-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [ve-dev] Contributing to
registry prior to componentinstantia
tion? |
|
Well I have error logs that appear to come from attempts to
instantiate components in the target VM (presumably the components
corresponding to the GEF edit parts), before the registry contribution method
is called.
I will look again, but i'm pretty sure that this is what is
happening.
Darren Hurt
-----Original
Message-----
From: ve-dev-bounces@xxxxxxxxxxx
[mailto:ve-dev-bounces@xxxxxxxxxxx]On Behalf Of Rich
Kulp
Sent: 11 May 2006 14:12
To: Discussions people
developing code for the Visual Editor project
Subject: Re: [ve-dev]
Contributing to registry prior to componentinstantiation?
Hi,
That shouldn't be how it works. The configuration
contributor is called before it returns with a registry to the rest of the
code. The should not be able to instantiate anything else before all of the
contribute to registry methods are called.
Rich
Darren Hurt
<darren.hurt@xxxxxxxxxx> Sent by:
ve-dev-bounces@xxxxxxxxxxx
05/11/2006 07:27 AM
Please respond
to Discussions people developing code for the Visual Editor
project <ve-dev@xxxxxxxxxxx> |
|
To
| "'Discussions people
developing code for the Visual Editor project'"
<ve-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| [ve-dev] Contributing to registry
prior to component instantiation? |
|
I have noticed
one thing about this registry contribution mechanism.
The code does not get
called until the component instances have been created.
It would be nice if the
contributor had a method that was called prior to instantiation of
the
component instances (as well as the current method of course).
This means
that some configuration changes do not take effect immediately, and you need
first
to
open and close an editor.
For example, if you change the look and feel
configurations, the first time you open up an editor,
it still has the
previous look and feel.
I am working with the 1.1.0 visual editor.
1) Is there
any way around this?
2) Has this been resolved in later versions, or if not are there
any plans to resolve it?
Thanks,
Darren Hurt
-----Original Message-----
From:
ve-dev-bounces@xxxxxxxxxxx [mailto:ve-dev-bounces@xxxxxxxxxxx]On Behalf Of
Rich Kulp
Sent: 08 May 2006 18:29
To: Discussions
people developing code for the Visual Editor project
Subject: RE:
[ve-dev] Passing extra information to a customizer
Hi,
There is a difference between
adding to the customize action and just calling something on the proxy factory
registry after it has been created.
We already have ways of doing the registry
stuff. Have you read
http://eclipse.org/articles/Article-VE-Custom-Widget/customwidget.html
This discusses extending VE. You would be using a special extension
point. There is an example in org.eclipse.ve.jfc's plugin.xml:
<extension
point="org.eclipse.jem.proxy.contributors">
<contributor
container="org.eclipse.jdt.launching.JRE_CONTAINER"
class="org.eclipse.ve.internal.jfc.core.JFCVisualContributor">
</contributor>
</extension>
This says that if the container org.eclipse.jdt.launching.JRE_CONTAINER is in the classpath then the contributor class org.eclipse.ve.internal.jfc.core.JFCVisualContributor will be instantiated and called to allow it to
contribute to the remote vm. The method you would implement to modify
the remote vm at creation time is contributeToRegistry(ProxyFactoryRegistry registry)
Thanks,
Rich
Darren Hurt
<darren.hurt@xxxxxxxxxx> Sent by:
ve-dev-bounces@xxxxxxxxxxx
05/08/2006 12:48 PM
Please respond
to Discussions people developing code for the Visual Editor
project
<ve-dev@xxxxxxxxxxx> |
|
To
| "'Discussions people
developing code for the Visual Editor project'"
<ve-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [ve-dev] Passing extra
information to a customizer |
|
I have
managed to accomplish what I want by subclassing the JavaVisualEditorPart and
CustomizeJavaBeanAction
classes, and using the target VM API to set a couple of String
properties on a singleton class in the target VM.
This is all I wanted to do, as
my customizers can pick up this information from the singleton
class.
I
am aware that what I have done is far from conforming to the API, and would
like to be able to do this kind of thing in
a proper way.
All I need is a hook
to be able to call some arbitrary code after a JavaVisualEditorPart has set up
it's ProxyFactoryRegistry.
Is there a way I can get involved to make this happen,
either by requesting the change or doing it myself and commiting
it?
Darren Hurt
-----Original Message-----
From:
ve-dev-bounces@xxxxxxxxxxx [mailto:ve-dev-bounces@xxxxxxxxxxx]On Behalf Of
Rich Kulp
Sent: 08 May 2006 14:44
To: Discussions
people developing code for the Visual Editor project
Subject: Re:
[ve-dev] Passing extra information to a customizer
Hello,
There isn't any way. The customizer is on a separate Java VM
than the Eclipse IDE. The customizer doesn't know anything about the
workspace. And there isn't anyway to tell it that info. The Customize action
isn't extensible to allow that.
Sorry,
Rich_______________________________________________
ve-dev mailing
list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev
_______________________________________________
ve-dev
mailing
list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev
_______________________________________________
ve-dev mailing
list
ve-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ve-dev