dcancro
|
| Posted: 10/31/2002, 10:48 AM |
|
I'm just starting to evaluate CodeCharge, and I have a question. Is it possible to use CodeCharge to develop a multi-tier, Model-View-Controller model 2 application with this? I'd like to not have my webpages coupled to my database tables & fields, but instead have a decoupled model tier containing the business logic and Data Access Objects. I'd also like a controller tier that maps request urls to actions and then determines the appropriate view based on the action's outcome. Here's an illustration of what I'm talking about:
http://members.telocity.com/dcancro/images/eng/Struts_MVC.gif
While you're there, could you also let me know if CodeCharge provides a standard best practice for implementing the items listed on the left side of the image?
From the provided examples, it looks like CodeCharge would be good for garden variety CRUD apps (which most apps are), but would break down when you need complex business logic and persistence strategies.
Thanks,
Dan
|
|
|
 |
xbill
|
| Posted: 10/31/2002, 12:10 PM |
|
The servlet target generation language
in CCS generates a basic MVC model servlet app.
I haven't done a feature by feature comparison
with Struts- but I don't think that CCS is
actually using any Struts code.
The CCS generated code is fairly easy to follow
if you are familiar with Java- and there
is support for some more advanced features like
Jakarta ORO and JDBC datasources.
The best way to get familiar with the CCS generated
code is to take several samples and drill down into
the generated classes to see exactly how CCS produces
the model.
For large apps- I usually lay down the framework in CCS
and then hand tweak any code or parts of the application
that can't be generated easily.
If you really need to use advanced features (complex persistance,etc)
you can try to isolate that functionality and hand
code / test the routines that you need, and then integrate
them back into the overall project.
In some cases- I have used a CCS generated front end
in co-operation with a more complex Java backend tool.
The real advantages of CCS over any hand coding are
the quick time to prototype, cross language support (prototype in
one language, deploy in another), and reduced cost on
longer term maintenance of an app.
-bill
|
|
|
|
dcancro
|
| Posted: 10/31/2002, 2:35 PM |
|
Thanks, I'll look into it. I don't see any .class's or .java's in the sample app -- just .jsp's and .html's, so from this it appears to only support two layer applications.
Another question: Is it conceivable to extend CCS to generate .jsp's with custom tag libaries, or to generate any other framework-specific items like Struts Actions or ActionForms?
|
|
|
|
|
