I have a 30-day trial license for Dynamo and so far am very impressed. In a just a few days, I was able to build a prototype web-app version of a client for our product. More important, I feel good about the code I wrote dynamo; my prototype wasn't one of those things where you step through a wizard and it generates a lot of code that is hard to customize or extend. It is true that the basic Dynamo page-compilation system is different from JSP, though it may be that Dynamo supports JSP. Personally, I prefer the Dynamo system, and since the rest of the Dynamo is based on the Java-standard technologies -- beans, properties files, servlets -- I don't feel that we would be buying into proprietary technology to use it. It seems like it should be pretty easy to retarget the beans and jhtml files to JSP later. What I like about Dynamo page-compilation is that it seems easier to separate the display from the logic without having to use special tags. As Mark says they use servlet beans to provide flow control in the HTML page, and I prefer the idea of extending the system by writing my own servlet beans, rather than by changing the "language" by creating my own tags. I also really like Dynamo's Nucleus. It's a properties file based system for instantiating beans and hooking them up to each other (and your Java html pages) without the beans having to know about each other. I imagine that the biggest drawback to Dynamo for the subscribers of this list is probably cost -- it is definitely priced for the commercial market. Yours, JonTom At 12:32 PM 4/29/99 +0100, Mark Hughes wrote: >Hi, > >I thought it might be interesting to see how Dynamo implements these >(code snippet below - simply switches the usertype profile attribute and >includes a page depending on its value). >This allows the developer to 'extend' the tags available without having >to use 'scriptlets'. Certain 'droplets' are provided by Dynamo (for, >foreach, >switch etc). > >Are there any Dynamo users on this list? I believe the new version is JSP >0.91 >compliant - but the droplet (servlet bean) concept is very powerful - and >has >been used in some large applications. The chances are we will be developing >some applications with Dynamo and whilst i'd prefer to use a standard, the >flexibility of droplets may be necessary in order to seperate logic and >presentation. > >I'd be very interested to hear other opinions on this. > ><IMPORTBEAN BEAN="/atg/userprofiling/Profile"> ><DROPLET BEAN="/atg/dynamo/droplet/Switch"> > > <PARAM NAME="value" VALUE="bean:Profile.usertype"> > > <OPARAM NAME="broker"> > <droplet src="brokerhome.jhtml"></droplet> > </OPARAM> > > <OPARAM NAME="investor"> > <droplet src="myhome.jhtml"> </droplet> > </OPARAM> > > <OPARAM NAME="default"> > <droplet src="guesthome.jhtml"></droplet> > </OPARAM> ></DROPLET> > >Ta, >Mark. > >=========================================================================== >To unsubscribe, send email to [EMAIL PROTECTED] and include in the body >of the message "signoff JSP-INTEREST". For general help, send email to >[EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JSP-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
