Which is current configuration? (eclipse plugin question)

blaw · **Joined:** Wed Jun 16, 2004 5:53 am **Posts:** 4

Hi,

I've hacked the eclipse plugin to show @NamedQuery values in the Configuration/Entity view thus :

It's very dirty (I've never worked on an eclipse plugin, and only had half a day).

Does anyone know how to obtain the current ConsoleConfiguration that is being opened in the panel? From for example

Code:

org.hibernate.eclipse.console.workbench.PersistentClassWorkbenchAdapter

Code:

KnownConfigurations.getInstance().getConfigurations()

gives me them all, but I can't find out how to tell which is the one being worked on.

Any hints would be appreciated.

max · **Posted:** Fri Oct 17, 2008 1:58 am

Each node in the tree is created with the proper info; so the parent of the node injects the Console configuration into the child nodes.

I assume you do something similar to get that query node shown up in there ?

The code for this is in the *WorkBenchAdapters which create the children.

p.s. sorry for the late reply - but I had to get married before I could answer ;)

blaw · **Joined:** Wed Jun 16, 2004 5:53 am **Posts:** 4

Hi, thanks for the reply, and Congratulations!

in PersistentClassWorkbenchAdapter.getChildren(...) i'm doing :

Code:

         ConsoleConfiguration[] cs = KnownConfigurations.getInstance().getConfigurations();
         ConsoleConfiguration consoleConfiguration = cs[0];
         Configuration config = consoleConfiguration.getConfiguration();

         Map namedQueryMap = config.getNamedQueries();

and then looking for the right queries based on the PersistentClass instance passed to getChildren

It's horrid I know and will not work with more than one configuration, but there is no priority on this and I just found it useful to have the list of named queries in the configuration view.

I'm sure there is a way to get the current config from the Adapter, but I can't find it.

max · **Posted:** Sun Oct 19, 2008 8:23 am

None of the other PersistentClass children ever needed the Configuration hence it does not know it.

so no easy solution...needs updating the api