On Jan 20, 3:35 pm, Arved Sandstrom<asandstrom3min...@eastlink.ca>
wrote:
On 11-01-20 12:29 AM, gk wrote:> JCA has a benefit over custom solution because System contracts
defined between application server and EIS resource adapter provides
connection pooling.
Could you please explain what kind of system contract we can think of
here ? Is it like what XML can be transferred OR what sort of
contracts we are after ? I would like to know more information at this
part.
The book or article that you pulled the first paragraph from should have
listed the JCA contracts, seeing as how it mentioned them; if not, toss
the thing in the trash.
JCA system contracts defined in version 1.0 of the JCA spec pertain to
connection management, transaction management, and security management.
"Contract" in this sense simply means a related set of requirements
between J2EE app server and EIS resource adapter.
Could you please provide one real example here. Is it like 30
concurrent connections , 10 minutes timeout etc ? Do you call these a
part of "System Contract" ? What sort of requirements generally takes
place ? I'm not familiar. I'm sure these are not business
requirements ..right ?
I have found System Contract information. I have found this
http://java.sun.com/j2ee/images/Connector.jpg
Could you please be specific at this part.