| Feature proposal: Class Loader Viewer [message #43706] |
Mon, 13 September 2004 10:51 |
Eclipse User |
|
|
|
Originally posted by: hugues.bellerive.fleetmind.com
My suggestion to you is that whatever tool / plug-in / etc you might come
up with, it has to be able to show what is going on at the deployment
level. Most of the existing frameworks and third party libraries / jars
will react differently than advertised (because of existing configuration,
conflict with already running jars,
). In my short experience in Web
development, deployment is where all hell breaks loose, hence the need for
a tool that would assist the developer.
For one, the Web Tools Platform project would benefit greatly from a tool
that could describe what the class loader is seeing. Conflicts between
jars would be easily identified. This alone would gain you acceptance.
It is no news to Java developers that deployment is more of an issue in
object-oriented projects since the complexity is moved from code to
configuration. Than why is there no tools available to clearly state what
the virtual machine is seeing / using? Is it because no one dares tackling
the infamous class loader?
From what I can read of the projects mission and goals (in the charter
and requirements pages), the first release will be some form of big
interface between web technologies. I doubt that this will be concrete /
tangible to small companies (while starting projects at big software
companies will benefit from tough).
|
|
|
Powered by
FUDForum. Page generated in 0.03025 seconds
Home