"Ok, Ming, I understand you point now.

But I still thinking that MS VS is another world (you know: a lame Web Server, with a improvised app framework, and ONE very good developer environment for it with a set of technology owned by M$) and that include documentation. We are a lot of Java 2 Enterprise Edition's workers (and its derived), even including all the open source technology around this world. Again, JDeveloper is just the "way" to do several things on this world and it supports almost all frameworks and patterns from Java world and Oracle world. If we want a book about JDeveloper, then we only need to look for books on topics like: EJ3, JPA, JSF, MVC, etc, etc., and go ahead to find how to integrate all this in JDev. Most of people know what to do with the JDeveloper in this way, it's why I think that it's not easy a JDeveloper book instead of other tecnology's books like JDeveloper EJB3 implementation.

Regards,

HayrolR"

I very much agree with Ming. MS VS is indeed a very good tool. Especially it's ability to save my time is quite amazing. It also gives me that extra time to explore into new tec. domains even when working under tight schedules.

@HayrolR, I agree, MS VS is another world, and Java (JDeveloper) offers cleaner ways of doing things. Since it offers the capability of addressing a much larger and more diverse spectrum of technologies and products, useful literature becomes even more necessary. Customers are usually not ready to pay more for a product, if they are offered the option of getting the product developed with a specific technology or tool. But if the developers were to get useful and handy set of information to kickstart a project (especially in a new tech. domain) I am sure it would help using cleaner methodologies to solve practical problems.

Since the spectrum is so broad, literature eg. (JFS with JDeveloper) etc. would be very helpful. (Please note: I really hate fat books :-))

Regards,
Shrirang

0  out of 1 found this valuable. Do you find this valuable? Do you?