|
|
Related Products | ||||||||||||||||||||||||||||||||||||||
MaintainJ Plugin 2.1
Publisher's Description:MaintainJ Plugin - MaintainJ, an Eclipse plug-in, generates runtime UML sequence and class diagrams for a given use case, helping the users to quickly understand a complex Java or J2EE application.MaintainJ logs runtime method call trace to a file and uses that trace file to render sequence and class diagrams. MaintainJ is the tool to turn to when : ---You want to find out what exactly happens in the application when you run a use case. ---You need to quickly understand large, complex Java applications. ---You want to reduce the maintenance costs by more than 20%. MaintainJ is different from any reverse engineering tools you have seen before. a) Forget Static Reverse Engineering - UML diagrams from source code can take you only so far. Run a use case and generate UML sequence and class diagrams for that use case to debug and understand complex systems. b) Debuggers are Tiresome - Debuggers help. But they are tiresome. Save the time you must spend in the debugger by first reading the runtime UML diagrams to get an overview. c) Explore the Diagrams - MaintainJ sequence diagrams are a pleasure to read. You can expand and collapse the calls while exploring a complex sequence diagram. d) Focus on What You Need - Only application classes (no API classes) in specified packages are shown. All loop calls and recursive calls are removed from sequence diagrams. e) From Code or Jar - Diagrams are generated at runtime. You don't really need to have the source code. f) Save Maintenance Costs - Development costs 10%. Maintenance costs 90%. Understanding code costs 50% of maintenance costs. Save by generating UML diagrams that help you to quickly understand code. g) Open Source Based - MaintainJ is an Eclipse based, $20/year product. Buy it or just use and blog it. Or tell us about a more useful product for those who support and maintain complex Java applications. Check the demo videos at http://maintainj.com/head.jsp?param=demos User License Agreement:PLEASE READ THIS LICENSE CAREFULLY BEFORE USING OR EVALUATING THE SOFTWARE. USING THE SOFTWARE SHALL INDICATE YOUR ACCEPTANCE OF THE TERMS AND CONDITIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT DOWNLOAD, INSTALL, EVALUATE OR USE THE SOFTWARE. This is a legal agreement between you, the end user, and MaintainJ Inc. (the "Licensor"). MaintainJ set of Eclipse plug-ins (the "Software") is owned by the Licensor and is protected by copyright law. Upon acceptance of the terms of this License Agreement, your rights and obligations with respect to use of the Software are as follows. Show Full LicensePLEASE READ THIS LICENSE CAREFULLY BEFORE USING OR EVALUATING THE SOFTWARE. USING THE SOFTWARE SHALL INDICATE YOUR ACCEPTANCE OF THE TERMS AND CONDITIONS CONTAINED IN THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS AND CONDITIONS OF THIS AGREEMENT, DO NOT DOWNLOAD, INSTALL, EVALUATE OR USE THE SOFTWARE. This is a legal agreement between you, the end user, and MaintainJ Inc. (the "Licensor"). MaintainJ set of Eclipse plug-ins (the "Software") is owned by the Licensor and is protected by copyright law. Upon acceptance of the terms of this License Agreement, your rights and obligations with respect to use of the Software are as follows. Licensor grants you a non-exclusive right to use the Software on a single computer for evaluation of the Software. Evaluators of the Software are therefore granted the right to use it themselves on one computer. No other license is given. You may not reverse engineer, decompile or disassemble the Software. RUNTIME RIGHTS AND LIMITATIONS: You agree to indemnify, hold harmless and defend the Licensor from and against any claims or lawsuits, including attorneys' fees, that arise or result from the use or distribution of the Software. The Software is built using Eclipse and related plug-ins, which are distributed under the following license. Eclipse Public License (EPL) 1.0 available at http://www.eclipse.org/legal/epl-v10.html IT IS YOUR OBLIGATION TO READ AND ACCEPT ALL SUCH TERMS AND CONDITIONS OF THE ABOVE LICENSES PRIOR TO USE OF THE SOFTWARE. COPYRIGHT: The Software and Documentation are copyrighted by the Licensor and are protected by Canadian and international copyright laws and treaties. The product contains copyrighted software of the Licensor. All rights reserved. IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY LOSS OF PROFIT OR ANY OTHER DAMAGE, INCLUDING BUT NOT LIMITED TO SPECIAL, INCIDENTAL, CONSEQUENTIAL OR OTHER DAMAGES. THE SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. LICENSOR SPECIFICALLY DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. LICENSOR DOES NOT WARRANT THAT THE SOFTWARE WILL MEET YOUR REQUIREMENTS OR THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE. GOVERNING LAW: This Agreement shall be governed by and construed in accordance with the laws of Canada. You agree not to use, ship, or export the Software in violation of law. ENTIRE AGREEMENT: You agree that this Agreement expresses the entire understanding between you and the Licensor, and supersedes all other communications, oral or written, relating to the Software.
Social bookmarks: RSS:
Latest User Reviews:Class diagramI was just looking to create the class diagrams from the package. MY OPINIONUtil but not so integrated with Eclipse. Could you elaborate what you mean by 'Util but not so integrated with Eclipse.'? Are you referring to the aspect weaving part for J2EE applications? For J2SE and Eclipse applications, MaintainJ is tightly integrated with Eclipse. For J2EE applications, it you can deploy and run the web application from Eclipse, you can import MaintainJ.war into Eclipse workspace and do the aspect weaving also from Eclipse. That leaves nothing out of Eclipse. >>I suggest to permit user to specify in filter menu also no source classes but in classpath of project. Are you saying that user should be able to choose the jar files or class folders in classpath to instrument rather than the packages? Please elaborate. If that is what you are saying, you can somewhat achieve that in build-time instrumentation, where you can choose the projects to instrument. Runtime instrumentation filters can't be set by the jar file names. >>Furthermore, the file tracking mechanism (with start/stop dialog) is quite complex and seem almost heuristic... Could you please elaborate how it is complex? Good to know that you liked the product. Feel free to join the MaintainJ forums (http://maintainj.com/smf)to discuss any issues. Regards Choudary Kothapalli http://www.MaintainJ.com Social bookmarks: RSS:
Write a Review and Rate MaintainJ Plugin |
|||||||||||||||||||||||||||||||||||||||