Framework for Application Data and Sources

A framework for reading and writing data in multiple formats to multiple destinations; it can be beneficial in creating application simulators.

Date Posted: October 26, 2004

Overview Requirements Download FAQs Forum Reviews 1. How do I use the Framework for Application Data and Sources (FADS)? 2. When I start FADS, I get a message on the console that says "Unable to create initial context." What's wrong? 3. The File -> Start menu is disabled. What's wrong? 4. My simulator is running. Why can't I send or receive data? 5. I received data from one destination source in a comma-delimited format and tried to send it out to another destination source as XML. The XML doesn't look right. What's wrong? 6. What other data formats and/or data sources do you plan on supporting? 7. My edits aren't being saved to my data. What's happening? 8. What are your future plans for FADS? 9. Some other feature isn't working. What's wrong? 1. How do I use the Framework for Application Data and Sources (FADS)? Please see the included user's guide. Back to top 2. When I start FADS, I get a message on the console that says "Unable to create initial context." What's wrong? Nothing is wrong. This message comes from having the JmsDestination enabled in your fads.properties file but no JMS-related information in your JNDI directory. Either specify the JMS-related information (using a tool such as jmsadmin) or disable the JmsDestination in fads.properties (using the destination.class.n property). Back to top 3. The File -> Start menu is disabled. What's wrong? Enabling the Start menu requires two steps: Set one of your sources (via Configuration -> Data Target/Source) to use a data format (other than "None"). Select a simulator to use (via Configuration -> Application Chooser). Also, if you have already started the simulator, the menu will be disabled. Back to top 4. My simulator is running. Why can't I send or receive data? If you're talking about the Send... and Receive... buttons on the App Data tab, you likely are set up for automatic mode (via File -> Auto Send/Receive) and sending and receiving of data will take place automatically. Note that you can send data only when you have data loaded (that is, visible on the App Data tab). To load data, you must create it from whatever facilities the simulator gives you or import the data from the local file system (via File -> Run Style -> Import Data). When importing data, your Configuration -> Local Data Format settings are used. Other things that could impede the sending or receiving of data are problems with the destination source(s) you're using (either the system itself or your configuration of how to talk to that system) the business logic encoded in the preSendProcess() and preRetrieveProcess() methods of your simulator application. Check your logging output for clues on what the problem is. Back to top 5. I received data from one destination source in a comma-delimited format and tried to send it out to another destination source as XML. The XML doesn't look right. What's wrong? This is a known problem (converting from non-XML format to XML). Frankly, I didn't think this situation would arise often enough to warrant fixing yet (although I do plan on fixing it in the future). If I recieve enough feedback asking me to fix it, I'll move it up on my schedule. Back to top 6. What other data formats and/or data sources do you plan on supporting? I don't have any plans for other data formats at the moment. I am currently adding a Web Services source that I'm about 85% done with. I welcome feedback on any other formats and sources you think I should add (and I'll add them as time permits). Of course, I've provided some technical guidance on adding new formats and sources in the documentation, so you could always take a stab at adding them yourself and sending them to me to include in future versions of FADS. Back to top 7. My edits aren't being saved to my data. What's happening? It depends on where you are. If you're editing data on the App Data tab in the tree view, what version of Java are you running? If you're using 1.3.x, then I'm not sure what the problem is. If you're using 1.4.x, then that's a known problem that I haven't had a chance to address. The workaround is to tab out of the text field you're editing before choosing another element in the tree to edit. If you're using any other version, then you're on your own; I haven't tested with any other versions. If you're editing data in a table (such as what might be provided with a simulator to create data), then you're likely running into a similar problem. Just tab out of the cell in which you're editing before clicking on any widget to save your data and close the editor. Back to top 8. What are your future plans for FADS? I don't have any concrete plans for FADS. I developed it as part of a project I was working on in my group to support our deliverables. I am adding Web Services support to it as a second version of that project (though I am not officially a part of this version of the project). It turns out that other projects our group was working on could use FADS, too. All development that I've done was a direct result of these projects, so, unless the project I'm working on at a given moment leaves me time to make enhancements, most future changes will be driven by feedback (and, most specifically, contributions) I get from those using FADS. That being said, ideas for enhancements that I've had include the following: porting FADS to be SWT-based instead of Swing-based, turning FADS into an Eclipse plug-in, and adding a rules engine that could be used by the simulators. Back to top 9. Some other feature isn't working. What's wrong? Well, it's possible you've encountered a bug! I wrote FADS to support a set of deliverables from our group, so I've likely tested a subset of execution paths through the system. Send me (through the discussion forum) as much detailed info as you can (including any changes to FADS that you may have made), and I'll do my best to help you figure out what's wrong -- though I can't make any promises. Back to top