Introduction-The Enterprise JavaBeans architecture supports server components. Server components are application components that run in an application server such as CICS. Unlike desktop components, they do not have a visual element and the container they run in is not visual.
Server components written to the Enterprise JavaBeans specification are known as enterprise beans. They are portable across any EJB-compliant application server.Some of the benefits of using enterprise beans are:
Component portability:-The EJB architecture provides a simple, elegant component container model. Java™ server components can be developed once and deployed in any EJB-compliant server.
Architecture independence:The EJB architecture is independent of any specific platform, proprietary protocol, or middleware infrastructure. Applications developed for one platform can be redeployed on other platforms.
Developer productivity:The EJB architecture improves the productivity of application developers by standardizing and automating the use of complex infrastructure services such as transaction management and security checking. Developers can create complex applications by focusing on business logic rather than environmental and transactional issues.
Customization:-Enterprise bean applications can be customized without access to the source code. Application behaviour and runtime settings are defined through attributes that can be changed when the enterprise bean is deployed.
Multitier technology:-The EJB architecture overlays existing infrastructure services.Versatility and scalabilityThe EJB architecture can be used for small-scale or large-scale business transactions. As processing requirements grow, the enterprise beans can be migrated to more powerful operating environments.
In addition to these general benefits of using EJB technology, there are specific benefits of using enterprise beans with CICS®. For example:
Superior workload management:You can balance client connections across a set of cloned listener regions.You can use CICSPlex SM or the CICS distributed routing program to balance OTS transactions across a set of cloned AORs.
Superior transaction management:Enterprise beans in a CICS EJB server benefit from CICS transaction management services—for example:
• Shunting•
System log management
• Performance optimizations
• Runaway detection
• Deadlock detection
• TCLASS management
• Monitoring and statistics
Access to CICS resourcesYou can, for example, use JCICS or the CCI Connector for CICS TS to build enterprise beans that make use of the power of existing (non-Java) CICS programs. The developer of a Java client application can use your server components to access CICS—without needing to know anything about CICS programming.
Friday, February 22, 2008
Friday, February 8, 2008
Advantages and Limitations of Dreamweaver
Advantages of Using Dreamweaver
There are many advantages with using Dreamweaver for designing and maintaining web sites.
1. Building and editing web sites is fast. A user may start with one of many supplied css templates and quickly modify it for their purposes. The GUI interface allows for simultaneous designing and coding. The user can see what their html looks like immediately after writing the code.
2. The split view interface allows the user to quickly build a page in the design view and then refine the html in the coding view. Also, code that needs to be modified may be located quickly by selecting the corresponding element in the design pane. The code pane automatically scrolls to the html for the selected element and highlights the code. The ability to work form one interface also speeds up web development.
3. Dynamic features may be added to a site through the use of page behaviors, Dreamweaver's JavaScript interface, and server behaviors, Dreamweaver's database connection interface.
4. Also, basic image optimization may be accomplished within Dreamweaver and more advanced image processing may be accomplished through the close integration between Dreamweaver and Fireworks. Finally, Flash buttons and other basic Flash elements may be added within the Dreamweaver interface.
5. Hundreds of third party extensions that add functionality may be downloaded for free or purchased. Extensions are usually written in html, JavaScript, or C. Most extensions do one or more of the following: automate changes to a document, interact with Dreamweaver to open or close windows or documents, connect to a data source, insert or manage a block of server code.
6. Dreamweaver offers both a JavaScript API and a Utility API.
7. Dreamweaver is customizable. The user may set preferences controlling how and to what extent accessibility is coded. The user may adjust code coloring, what fonts are used for coding, and how code is highlighted. The user may also set which browsers to use for previewing a page.
8. Besides setting preferences, the user may also directly edit the configuration files. In this way, menus may be rearranged to suite individual taste. Tabs may be added or removed. The names of commands may be changed, added, or removed. Anything about the look and feel of Dreamweaver may be customized within the configuration files.
Limitations of Dreamweaver:
1. Dreamweaver has a steep learning curve. It is a complex program that is difficult to master. In the time it takes to learn Dreamweaver, an individual could be productively hand coding web pages.
2. Many of the existing features could be improved. The check in/check out feature has problems. When checking in multiple files, some files remain checked out. The user must review their file list for missed files and check them in once more.
3. Pages built from complex nested templates sometimes become corrupt during use and must be rebuilt. The visual interface for building tables does not always work.
4. The user must switch between code views and various design views in order to optimize table construction.
5. Although for the most part, Dreamweaver generates efficient html code, the code usually needs to be touched up by hand after making several subsequent changes in the design view.
6. The site map feature needs a great deal of refinement in order to really be useful. Rather than showing a true site map, this feature shows to which pages each page links. The user may continue to follow the link structure in circles.
7. Finally, even though Dreamweaver is very flexible, the interface suggests a particular workflow. Dreamweaver reflects its origins as a wysiwyg web design tool by favoring visual methods of coding pages.
Conclusion :
1) Although far from perfect, Dreamweaver MX 2004 is the best tool of its type and gets a little better, with each new version.
2) Dreamweaver's flexibility facilitates its use by all members of a multidisciplinary Web design team.
3) Dreamweaver is arguably the best stand alone tool to use for developing today's complex Web sites that incorporate multiple technologies, integration with databases and content management systems and that strive for increased usability and use of web standards.
There are many advantages with using Dreamweaver for designing and maintaining web sites.
1. Building and editing web sites is fast. A user may start with one of many supplied css templates and quickly modify it for their purposes. The GUI interface allows for simultaneous designing and coding. The user can see what their html looks like immediately after writing the code.
2. The split view interface allows the user to quickly build a page in the design view and then refine the html in the coding view. Also, code that needs to be modified may be located quickly by selecting the corresponding element in the design pane. The code pane automatically scrolls to the html for the selected element and highlights the code. The ability to work form one interface also speeds up web development.
3. Dynamic features may be added to a site through the use of page behaviors, Dreamweaver's JavaScript interface, and server behaviors, Dreamweaver's database connection interface.
4. Also, basic image optimization may be accomplished within Dreamweaver and more advanced image processing may be accomplished through the close integration between Dreamweaver and Fireworks. Finally, Flash buttons and other basic Flash elements may be added within the Dreamweaver interface.
5. Hundreds of third party extensions that add functionality may be downloaded for free or purchased. Extensions are usually written in html, JavaScript, or C. Most extensions do one or more of the following: automate changes to a document, interact with Dreamweaver to open or close windows or documents, connect to a data source, insert or manage a block of server code.
6. Dreamweaver offers both a JavaScript API and a Utility API.
7. Dreamweaver is customizable. The user may set preferences controlling how and to what extent accessibility is coded. The user may adjust code coloring, what fonts are used for coding, and how code is highlighted. The user may also set which browsers to use for previewing a page.
8. Besides setting preferences, the user may also directly edit the configuration files. In this way, menus may be rearranged to suite individual taste. Tabs may be added or removed. The names of commands may be changed, added, or removed. Anything about the look and feel of Dreamweaver may be customized within the configuration files.
Limitations of Dreamweaver:
1. Dreamweaver has a steep learning curve. It is a complex program that is difficult to master. In the time it takes to learn Dreamweaver, an individual could be productively hand coding web pages.
2. Many of the existing features could be improved. The check in/check out feature has problems. When checking in multiple files, some files remain checked out. The user must review their file list for missed files and check them in once more.
3. Pages built from complex nested templates sometimes become corrupt during use and must be rebuilt. The visual interface for building tables does not always work.
4. The user must switch between code views and various design views in order to optimize table construction.
5. Although for the most part, Dreamweaver generates efficient html code, the code usually needs to be touched up by hand after making several subsequent changes in the design view.
6. The site map feature needs a great deal of refinement in order to really be useful. Rather than showing a true site map, this feature shows to which pages each page links. The user may continue to follow the link structure in circles.
7. Finally, even though Dreamweaver is very flexible, the interface suggests a particular workflow. Dreamweaver reflects its origins as a wysiwyg web design tool by favoring visual methods of coding pages.
Conclusion :
1) Although far from perfect, Dreamweaver MX 2004 is the best tool of its type and gets a little better, with each new version.
2) Dreamweaver's flexibility facilitates its use by all members of a multidisciplinary Web design team.
3) Dreamweaver is arguably the best stand alone tool to use for developing today's complex Web sites that incorporate multiple technologies, integration with databases and content management systems and that strive for increased usability and use of web standards.
Subscribe to:
Posts (Atom)