Java Database Programming Bible ...

[Jim Caprioli]

... contains several chapters which explain how to code a "Framework" of type Atris.

That makes Atris even better documented than it already is.

I don't think the coder of Atris, mr. Self has understood what the generally accepted definition of a framework is. I would rather call Atris a template.

Anyway, I advice everyone who landed here to read the Database Programming Bible as it will save you the frustration of
- working with Atris
- dealing with the void Kevin Selfproclaimed Guru

Take my advice as I rarely give it for free.

Thanks

[Kevin Self]

In response to your comments. Thanks you for taking the time to review the project.

I am quite sure I understand the meaning of a framework, in the context of developing applications designed for n-tier architectures. A template is a much simpler concept, designed to allow you to fill in the blanks, and get boiler plate code. A Framework provides built in capability, and does much of the thinking for you. Templates are significantly more primative than a Framework, and it is unlikely that a template would give you GUI based features and pre-defined logic at all. Also templates are not designed to be a complete solution, but just assist in coding.

There is no generally accepted definition of a Framework. It is a word that has specific meaning to a specific group of developers. I hope you are not confusing 'plugable' frameworks, like Eclipse to the more general development frameworks around today.

Frameworks require a higher level of programming sophistication and skill, as well as an understanding of the reason for their use, hence the extensive documentation. If you are more comfortable with the simpler concepts and principals of Templates, then perhaps Atris is not for you.

I have not read the 'Database Programming Bible', but it certainly sounds like it wants to be declared the database Guru. I have read many other books related to database development, architecture, design etc., and none of them proclaim to be the answer to all things data related. Databases are hardly the answer anymore (go look up cost effective scalability and performance) to large scale applications, which is why the DB vendors are all rushing into the Application Server market.

I would hardly call your comments advice. More like someone who does not actually understand a great deal about software development, and found the framework just too much to handle. As always with advice, you get what you pay for.