<Q/> Do I need to use Dreamweaver?
<A/> No. You can build your pages in any editor of your choice. However, by using the Dreamweaver Tagger you will likely be an order of magnitude more productive. You can also see what you are working on at design time; its amazing how much that helps :).
<Q/> Why not an Eclipse based Tagger?
<A/> We love Eclipse and use it for all of our Java development work. However, we feel that for JSP/HTML page authoring Dreamweaver is still miles ahead in terms of ease of use, and productivity. Also, as Page Authors, we don't expect to be using a Java IDE. But, there is nothing at all stopping you from using Eclipse for JSP development. In actual practice, we do the vast majority of our JSP development in Dreamweaver, and occasionally do a bit from within Eclipse.
<Q/> Why does my application fail to re-start using the ANT script and the remote restart?
<A/> Usually it is because the log4j.properties, or the ehcache.xml files are not being found by the class loader. Place these files in your application's WEB-INF/classes folder.
<Q/> Do you have a demo application we can test drive?
<A/> Yes, here is our requirements gathering application. It is a live production app.http://demo.sys-requirements.com.
<Q/> How much code do I need to write?
<A/> Tagger Cat is NOT one of these Generate it All product offerings. We'll never claim, and would never want to claim, that you don't have to write code for any serious app. You still have to write code for your custom actions, and in-depth business logic. So, in that sense this is just like any other framework where you use as much of its functionality as your can, and add the rest with other libraries, and custom code.
However, where we are different is the amount of code that you need to write is drastically smaller.
Tagger Cat's JSP templates are completely customizable, and the JSP code generated is exactly like what you'd write by hand. The generated Java code is based upon Hibernate's code generation tools, and is also completely customizable. We've only tweaked the Hibernate templates a bit for our own needs.
So, the amount of code that you need to hand write depends upon your application's scope and functionality. If you are just building an app that is something a bit more than a CRUD application, you may need to write very little code. The framework, and tag libraries will take care of the bulk of it.
<Q/> What are the limitations of the JSP based design time templates, and how much can they be customized?
<A/> There really aren't any limitations. Basically, if you can code it using JSP, then you should be able to template it. The templates are just another web application. The DW tagger can submit any number of parameters, and also supports multi-value parameters. Using the Tagger Template Tag lib, you have complete access to all of the application's metadata; just as you do at application runtime. You can add any number of your own templates, as well as customize the heck out of the supplied templates. Unlike using say Freemarker, using JSP for templating: is very easy, is web hosted, uses your current skill set, can use any taglib such as JSTL etc.
<Q/> How much of my Business Logic can I implement with your Declarative Rules?
<A/> Of course it depends upon your application. After using Tagger Cat for a while you'll get a good sense of what can be done with Declarative Rules and what can't.
But, we actually find we can implement a LOT of common Business type rules declaratively. After all, Rhino JS is a very complete programming language. Although sand-boxed, you still have access to most of the JDK classes, and all application classes.
Also, since our declarative rules are automatically multi-tenant enabled, we are not writing a bunch of Tenant specific code that would otherwise greatly complicate versioning, builds, and deployments of the application. Also, since the RULEs are actually deployed into the database (where they really belong) it is easy to report on them etc.
<Q/> Why wouldn't I use Tagger Cat?
<A/> Well, there are a couple of reasons. Firstly, Tagger Cat is stateful and makes heavy use of sessions. So, if you want to scale to a zillion users, this is probably
not the framework for you. Alternatively, you can use Tagger Cat with Terracotta and then scale to a zillion users.
See our developer's guide for more pros and cons of using Tagger Cat.
Secondly, Tagger Cat is designed for database backed BUSINESS applications. It is completely, and tightly, coupled with Hibernate. Tagger Cat will not function without a Hibernate model. In otherwords, if you are not willing to use Hibernate, then there is nothing here for you.
Thirdly, if you strongly feel you need to use components like in ASPx and JSF, then this is not for you.
We've tried both of those component based frameworks and feel that Tagger Cat's productivity with specific regards to page authoring is easily just as high. But, unlike the component based frameworks, our pages are super clean, and are easily customized in the most finite of details. Additionaly, when we think of components, we usually look to something developed with jQuery. Lastly, we also use JSP 2.0 tag files for some of our light wieght page components. In the end, we think we are much further ahead by not using a component based framework because we have complete control of what and how the markup is generated.