Does Hibern8IDE have a configuration file that the changes made
to the graph can be saved?

Also is there a way to assign a package name to a graph ... so
that instead of seeing :

com.something.somethingelse.hibernate.beans.Employee

you can see Employee only?

BTW, was the graph supposed to be a first step toward a functionality?

In the Hibernate Console (the new name) version that is found in cvs have a toggle saying "Use package names" (or not)

There is not a "save graph position" feature.

And the graph was more a "hey - see this, do you like ?" feature ;)

Please note: we are working on a eclipse plugin version of this

Are there new features planned for the plugin version (or console) ?
I am currently working on a project heavily OO and Hibernate has been a great help. The problem we are facing is that the requester we use to explore the database is not adapted to our needs. Retrieving information in the database is painfull and require multiple joins. I installed Hibern8IDE last week and I was thinking about adding a new page to the 1.0 version. The goal is to provide object exploration capabilities. This explore page represent graphs of packages containing the mapped classes.
From the mapped classes you can associate a request to filter the number of instances you are interested in, and then starting from an instance you can expand the attributes and navigate through them recursively.
Are you working on this kind of feature?
If not, are you interested in?
Let me know.
Regards

is it any difference than from the object graph (acutally a tree) in the cvs version of Hibernate Console (which is its new name) ?

The object graph allow you to select an instance in the result table and show the data for this graph and blue nodes designate stuff that is proxied (not yet fetched/materialized)

Contributions and ideas are very welcome.

The eclipse plugin will have the basic stuff as there is now, and we will start focusing on providing "mapping helping" features to the plugin (more developtime support than runtime exploration).

Hi, Max

I installed and tested the console version and … yes, the object graph (actually a tree, and I think, it should be kept as a tree) is what I was looking for (good job!). BTW, some remarks :

1) I wanted to test the object graph in “real conditions” (not “hello world” conditions). So I used Console with the project I am working on actually (H2.1.4). This project is totalling ~40 mapping files for ~150 persistent objects. To achieve the test, I had to migrate all these files. Not a tremendous work : I just had to change the name of the hibernate mapping dtd file, but… The problem (from my point of view), is that the Console is too tied to Hibernate : tied to Hibernate is normal (Console was made for it) but tied to one version of Hibernate is a pity. The life cycle of Hibernate and Console are not the same.

To use the Console we need to upgrade from Hibernate2 to 3 (Hibernate3 will be alpha, beta, RC for a few months). Then real projects can’t benefit from Console while Hibernate3 is not ready for production. And actual projects will not necessarily migrate from H2 to H3 even if H3 is ready for prod.

AFAICS, using the GOF design patterns Fa

There exist 2 version of Hibernate console!

One in v21branch for H2 and the one in head is for H3.

Putting a "facade" in to support both "strains" were considered, but too cumbersome compared to the easy string replace that could be done (at that time)

So H2 is covered with current functionallity IMHO.

Further enhancements will be done in thread with H3 because that is what we want to have better tool support for.....H2 is covered - we probably just need to make an official release of the Hibernate Console for H2.

Your issues with persistent maps i look forward to hear more about - the console just do whatever a normal application will do.....so it should work :)

Regarding the patches to the gui then I would appreciate to get a patch for it + a screenshot to see what it looks like :)