Zach suggested:
> That is a pretty unique way to solve this problem, and I am glad you
> posted it because I think it is a common problem. There is one
> alternative you may consider. Since chiba allows for separate instance
> and XForm documents, and I believe each of them can be a URI that it
> will resolve for you, you could pre-process both the instance and the
> XForm documents through some separate code (using a mod_python -- since
> you are from fourthought of course, a cocoon pipeline, a servlet filter, or
> whatever you want) which updates the appropriate lists of options dynamically
> (database query, a separate XML DOM include, random number generator, web
> service call, whatever). That would be a really easy way to initially to
> accomplish it, but may lead to some interesting debugging because of the
> increased number of parts. Just a thought. If I am totally off target, feel
> free to let me know.
This is basically what I have done for my application, however, it only works
if the instance data that drives the select items is fixed throughout the
process. That is, if the instance data can change (say based on some other
events in the UI) then this won't work, since the original source is only
queried at the beginning of an XForms session!
So if you use tabbed forms, per the examples, and some values selected on one
tab need to change the items displayed on a different tab, this technique
will not work.
At least not with Chicoon under Cocoon. Maybe the servlet-only version of
Chiba is different.
Andrzej Jan Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
|
