This is something that we have been looking at for a while now.
What are other people on the list think?
Do you want a bundle that includes JDeveloper and a Database with the demo schema tables?
Or do you prefer a separate database and JDeveloper downloads?

I agree, for beginners this would be a very nice feature. Especially if there was very little effort new users would need to put in for getting a simple db app up and running. I've trained users on JDev and reducing the intial number of steps would be very helpful.

Keep them separate!
I would like the packages as small as possible.

Marcel,
embedded databases are usually java libraries that run in the same java process.
Oracle XE for example is a full-flegded standalone database.

I agree with Didier that bundling JDeveloper with Oracle XE would have it's benefits
and also agree with other who want to have it seperate. JDeveloper should be
runnable and installable as a standalone product without any database, I have
5 JDev versions installed and run all in parallel.

Hi,

Just a suggestion; but a simpler alternative would be for JDeveloper to auto-detect an XE install, or any other oracle databses on the current machine for that matter, and populate the Connections page first time it is shown.

This would seem to have the both of best worlds without creating a confusing bundle of different installers,

Gerard

Shay,

The discussion as it's going now is just what I wanted. I think there was some good feedback.

I think until now there is a 50-50 tie for embedding it and keeping it separate.
I'm a little bit surprised because for 'real' JDeveloper users, an embedded database is not really needed as working in projects means that there is central installed database. And I expected thoses users around on this forum.

Personally speaking, when working with JDeveloper on projects an embedded database is not needed. As I said before, most of the times in this case there is a central database server hosting the database.
So for those people I understand they prefer keeping it separately (to keep it small).

But there are cases that it really would add value:
- JDeveloper Starters: starters who want to experience with JDeveloper and e.g. do some ADF tutorials need to install Oracle. Because of this additional installation many of them will bail out; that's not what we want!
- Students: I JDeveloper would have an embedded database it could be used more easily for education on schools; the younger they start, the better!
- Regurlaly/Experienced JDvelopers users who want to try something at home but don't have Oracle installed for some reason.

For me it doesn't have to be Oracle XE, because it's still fairly big. It could also be a embedded Java database like Derby or HSQL. As long as it works with ADF Business Components without problem. (I tried MySQL once, but it didn't worked optimal with BC4J: e.g. primary keys are not added)

Also remember that JDeveloper is shipped with embedded OC4J out-of-the-box. I know you cannot compare this to an embedded database, but it is in and you can choose to use it or not.

Regards,
Marcel

hi there,

it all depends (no, I am not a consultant)

things to ponder : how big is the package(JDeveloper + Oracle XE). How long will it take to install the bundled DB.

pros with XE : that will let your target audience know how to bundle XE with their applications. If you can trim(size) XE to be embeddable (like mysql), then it will make sense for a developer to install the whole package. It will be nice if you can make it easy for developers to create a deployable package(like installShield) including Oracle XE. If that becomes less than a 150/200 MB package with nice screens, etc, then that will be interesting. Your DB division will love you if that can improve Oracle's position in the low-end DB market.

BR,
~A