If an enterprise web application has some of its sub systems fully implemented . What questions should be considered when thinking of extending the functionality of the System by adding(plugging) a subsystem. Please , all ideas are welcomed ...
Originally posted by Gabriel Fox: If an enterprise web application has some of its sub systems fully implemented . What questions should be considered when thinking of extending the functionality of the System by adding(plugging) a subsystem. Please , all ideas are welcomed ...
Development of framework that supports easy component integration. Something like JCA? Alex
Formerly JCA, now officially known as J2EE Connector Architecture since the JCA TLA is already taken by the Java Communications API, defines a standard architecture for connecting J2EE systems to enterprise information systems, such as ERP, mainframe transaction processing and database systems. You can think of the Connector Architecture as JDBC for EIS Systems.
Here is what I think : [if I understand your ? correctly] What is the probability of the subsystem being replaced with a better/enhanced/moreCompatible system in future ? If its very high or even moderate I will go with a design that will provide me minimal coupling. E.g., you may add an abstract layer that will be implemented by the future submodule design to interface with the system you are designing. For using the current submodule you will have to write adaptor(s). As indicated previously JCA is an abstract layer that provides you (& containers) a universal access mechanism to data sources. JCA may be done for RDBMS and thus replace JDBC. Yes that is an abstract layer already available for use. But writing the implementation for JCA for accessing your sub module will not be a trivial task. And ask yourself is it really required to be so general I will prefer to create my own simple to implement/use layer whenever possible.
In terms of the exam, it would be more likely that it would ask you how should you wrap the access to the legacy component. Would you use a stateless session bean, or use JMS? that sort of thing. Connector Architecture doesn't get touched on at all, from what I have seen.