Aaron, I my opinion, the multiple SwingEngine approach is the way to go. We have been doing this on a larger UI (Server Administration Console) successfully; the SwingEngine is built with that in mind, I guess. Also, look at SwixML's built-in "include" attribute to merge SwixML descriptor files - the current distribution contains a sample for how to use it.
The way Action are being linked to Widgets at runtime is certainly not optimal but very efficient. However, I agree, it would not be hard at all to add support for classes. Let me know if you want to provide a spec. and/or code. (Look for the handling of the SwixML-proprietary "initclass" attribute for ideas) Wolf -- Wolf Paulus C a r l s b a d C u b e s mailto:[EMAIL PROTECTED] CONFIDENTIALITY NOTICE: This message is intended only for the use of the individual or entity to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Aaron Anderson Sent: Saturday, July 19, 2003 5:14 PM To: Forum@carlsbadcubes.com Subject: [Forum] Agregation and actions questions I am working on a large UI and would like to use multiple swixml files instead of one large one for greater modularity and reusability. What is the prefered way to achieve this, create an XSLT and merge several files into one or create a new SwingEngine for each file and programatically add them together at runtime? Also, I noticed that the action attributes in the swixml files must match field names on a client object registered with the SwingEngine at runtime. For large UI's, what is the best way to avoid "god" mediators/controllers? Looking at the source code, it wouldn't be too difficult for me to change the action attribute code to support classes in addition to field names and it would make the swixml file similar to the struts xml controller file. Are there any reasons not to do it? TIA
