JBossDeveloper

I understand your needs, but there are many much more important things before adding this specific feature. If you really want this feature right now, you can implement it yourself or you can pay to make it a high priority.

Hi Dain,

okey, I understand your position and to this thread this will be my last reply. But what I still want to say is that it is really NOT a specific feature. I'm also an independent consultant and sometimes involved in the decision process of companies they intend to setup a J2EE plattform. You will know it's not the best time the IT has ever seen. So in the companies the budget is accordingly. But this should be a good situation for JBoss to get still more popularity. May be that I am wrong but I think in the most cases JBoss is used for education purposes or small to medium projects starting up on a green field. Why don't "conquer" the rest of the world ;-) ?

Best regards
Udo

I am encouraged to hear that multi-table entity mapping is on the plate for the JBoss 4.0 release. This should certainly help its adoptance in a wider variety of real world applications.

This is actually a "specific feature", in my view, but a fairly important one.

Thanks, Dain, for pointing out the option for paid development in case any users want this feature more quickly prioritized.

Chad

> Maybe that I am wrong but I think in the most cases
> JBoss is used for education purposes or small to
> medium projects starting up on a green field. Why
> don't "conquer" the rest of the world ;-) ?

Take a quick look at the JBoss customer list. There are a lot of huge companies using JBoss for huge applications. You can work around this issue with most databases using updateable views, which is what this feature effectively is. Anyway, good things come to those who wait.

IMHO there is a major misunderstanding regarding the requested feature and legacy systems or "real world applications" respectively.

To those who think this feature is necessary. Consider an arbitrary table-scheme. If you think some tables are to flat, well use an arbitrary number beans to map them. If you want a information of a number of tables under one umbrella, well use EJB's and relationships or updateable views (any realworld database will offer that). The latter offers the necessary real-world-performance.

I'm just writing this to people reading this thread and becoming unsure about the capabilities of JBoss. JBoss is a very suitable appserver for state of the art real world application. May they are build on the green field or if they have to integrate legacy systems.