It might be worth having a look at the struts-bsf library at http://struts.sourceforge.net/ It would allow rapid development using scripting languages to write actions while still providing a more future-proof "interface" between your view and your controller. That is, the JSPs wouldn't have to change no matter how your controller evolves.

I have a lot of hope for the BSF libraries, but haven't yet had many chances to integrate it into our development cycle. I'm expecting to use it for prototyping, so that we can lock the view down early and then elaborate the business model without having to make many changes to the view and as few as possible to the controller (Struts Actions)

It's very easy to plug struts-bsf in, although you may or may not find it easy to write scripts -- but BSF supports JavaScript, Jython, JRuby, and several other scripting languages.

Joe


At 9:05 AM -0700 4/22/04, Gogineni, Pratima wrote:
I am designing an interface to interact with our proprietary servers. For a
clean application you would typically make calls to this interface through
struts actions that you would write that are specific to your application &
have form beans that are specific to your view.

Now we also have some customers that might for the purposes of quick
development not want to write any struts-actions. Since our servers can be
used in many domains & applications we cannot create form beans that
correspond to the view. What we decided was to design the input/output
objects from our interfaces as "java beans" and allow the use of these beans
directly in the view layer & submit to our interface through a
single-generic action.


This allows the quick (& definitely dirty) development that some customers
require. We also plan to have custom tags that help in the creation of our
propietary inputbeans and submission to our server so as to parallel our old
non-jsp-proprietary tag library that our customers are used to. In someways
I guess we are building a framework for our applications on top of struts?

Unfortunately this adds a lot of complexity in the view - because the form
bean  is not specific to the View and could be bulky. Which is why in need
bean population tags etc to make life easier.

I am curious if anyone else has tried to do something similar &/ anyone has
any views/inputs for this kind of development.


--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining."
-- Jef Raskin


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to