This can be a little disconcerting if you aren't expecting it. The first time you call the web console you get a notice that it is deploying. Once you get over the shock and think about it, this actually makes a lot of sense. The console for a managed server is rarely (if ever) accessed, so why use up resources deploying it? Also, there are lots of IT shops where they don't use the console in the Administration server, either. Instead, they use WLST, custom JMX, or some combination of those and ANT. WLST gets a new method in this version, too makes it even easier for those who forgo the web UI.
This is one among many changes made in this release to improve performance. In case you are wondering why performance improvements is not in the list of factors to consider for upgrading, it is because they are included in every release
There are always developers chomping at the bit to use the latest APIs, so here you go. While the majority of new features since 1.2 have to been to make Java more palatable to developers who are deep in other languages and lower the bar for entry-level developers, Sun has managed to add something valuable to the enterprise in each release, too.
In the case of 1.6, many of the key features are also utilized as part of WLS 10.3, such as improved monitoring and management tools that are easier to attach at run time; greater use of annotations for web services; and JDBC 4.0. On its own, 1.6 adds more interoperability with Microsoft Technologies.The truth is, the odds are really good that someone on your development team has been building things that need Java 6 support, so now you can find out what it is and if you really need it.
Thursday, June 4, 2009
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment