Again, if it appears that I am sounding stupid, please accept the fact that I'm am stupid in technology. However, we wanted to create a "browser-based" system and Tapestry was decided as the best solution. The CMS backend of Slide was selected for the repository. Now, as we go into more intense development and see the Projector release, we are torn whether or not there is a way to integrate Projector with our current system design. Does anyone have any recommendations?
Here is the outline of our system structure. I am happy to share some development costs if anyone is interested.
On this page internal structure of the BIG System at the end of phase I (Release 1.5) is depicted.
The BIG system consists of the following Java packages:
* *auth* (interface |User| and it's implementations |VisitorUser|,
|GuestUser| and |MemberUser|) These classes represent different
"levels" or "roles" of BIG system users.
* *authorizenet* (class |AuthorizeNet| which is a specific
implementation of |PaymentGateway| interface)
* *cms* (interfaces |AccessControlList|, |AccessLevel|, |Document|,
|Folder|, |Project|) -- These interfaces represent "generic" CMS
functionality and do not depend on Slide specifics.
o *memory* -- "In-memory" implementation of CMS interfaces for
testing purpoces.
o *slide* (|SlideDocument|, |SlideFolder|, |SlideProject|) --
Implementations of core CMS interfaces, based on Slide
framework
* *email* (classes |EmailAddress|, |EmailMessage|, and
|EmailSender|) -- functionality for sending emails
* *model* -- (classes |Guest| and |Member|) -- These classes
implement the most of business logic.
o *basic* (classes |Address|, |CreditCard|, |Person|) --
simple classes for better data structuring.
o *payment* (interface |PaymentGateway|) -- generic interface
for accepting CC payments online.
* *tapestry* -- Tapestry classes customized for BIG system
o *components* -- custom Tapestry components developed for BIG
System
o *pages* -- all web pages generated by BIG and shown in browser
o *validators* -- classes to process user input from web forms
and ensure that entered data are corect./Note: a few less important packages and most of the classes were ommited for clarity/
smime.p7s
Description: S/MIME Cryptographic Signature
