http://blog.xebia.com/2006/01/10/jdeveloper1013-early-access-edition%e2%80%a6-mission-impossible/ Software development done right! Wed, 08 Feb 2012 14:41:38 +0000 hourly 1 http://wordpress.org/?v=3.3.1 http://blog.xebia.com/2006/01/10/jdeveloper1013-early-access-edition%e2%80%a6-mission-impossible/#comment-4 Duncan Mills Tue, 10 Jan 2006 00:47:53 +0000 http://blog.xebia.com/2006/01/10/jdeveloper1013-early-access-edition%e2%80%a6-mission-impossible/#comment-4 You'll be glad to know that things have improved for the better between the EA version and what will come out in production. Particularly in this area of how you bind to TopLink or EJB entities via a Session Facade we've been hitting on this combination a lot in the demos and so have gone through several iterations to try and improve the experience. This will all certainly benefit from a closer look when production hits the streets. The most important thing you'll find is the documentation in the new Developers guide which discusses the Session bean > ADF Binding > JSF stack in particular. This should help clear up a lot of mysteries. The new demo we'll be shipping with the product also comes in an incarnation that uses this stack so you'll have something of substance to work off. On the Project Structure issue - 10.1.3 now has "dynamic projects". The project file no longer maps each and every file that makes up the project, instead it maps the root directory(ies) for say your source and only records exceptions to that. This means you can happily have multiple projects as "views" on the same directory structure. It's also a good fit if you do you multiple IDEs or a mix of say Ant and JDev to manage your projects. You can make changes externally such as adding files and the IDE will know about them without you haveing to explicitly having to do an "Add" to get it visible to the project. The only difficultly of all this is appreciating the difference of deleting from the project (which effectively just excludes the file from your view) and erasing from disk (on the file menu or from) which physically blows the file away. You’ll be glad to know that things have improved for the better between the EA version and what will come out in production. Particularly in this area of how you bind to TopLink or EJB entities via a Session Facade we’ve been hitting on this combination a lot in the demos and so have gone through several iterations to try and improve the experience. This will all certainly benefit from a closer look when production hits the streets.
The most important thing you’ll find is the documentation in the new Developers guide which discusses the Session bean > ADF Binding > JSF stack in particular. This should help clear up a lot of mysteries.
The new demo we’ll be shipping with the product also comes in an incarnation that uses this stack so you’ll have something of substance to work off.
On the Project Structure issue – 10.1.3 now has “dynamic projects”. The project file no longer maps each and every file that makes up the project, instead it maps the root directory(ies) for say your source and only records exceptions to that. This means you can happily have multiple projects as “views” on the same directory structure. It’s also a good fit if you do you multiple IDEs or a mix of say Ant and JDev to manage your projects. You can make changes externally such as adding files and the IDE will know about them without you haveing to explicitly having to do an “Add” to get it visible to the project. The only difficultly of all this is appreciating the difference of deleting from the project (which effectively just excludes the file from your view) and erasing from disk (on the file menu or from) which physically blows the file away.

]]>