Hi, I'm a recent convert to the Avalon train, and I've been having a decent run at implementing server applications using the framework and Phoenix. Of recent, I was attempting to implement a data submission system that combined Phoenix and Torque (http://db.apache.org/torque); the catch being that I wanted to do the datasource configuration using the Excalibur components but access it in Torque via JNDI. There were a couple of issues that arose that I was wondering if anyone had clues about: 1. Has anyone done this already? If so, could I please please please get some pointers: I jacked the JNDI implementation from Jakarta Tomcat (which for some strange reason is not in the Jakarta Commons), and finally managed to merge Torque's properties file configuration stuff with Avalon so the entire system configures and runs without throwing any obvious errors, but for some reason the database operations fail silently. I may have the JNDI configuration wrong, but Torque seems to find the Excalibur datasource I placed in the JNDI tree just fine. The general Torque configuration works just fine: I can use Torque's built in JDBC datasource and the communication with the database works perfectly, but I'd like to consolidate it into one place and only have to change my application configuration file. 2. Is there any reason why Phoenix doesn't provide a JNDI tree by default? The code to implement it is definitely available from Catalina, and it would strike me as another useful way to have components publish themselves for retrieval by other components that don't fall into the standard frameworks (such as Torque or Hibernate or any of the other database O/R mapping frameworks). 3. On a general note, there seemed to be massive duplication of code in the Commons with code in the Excalibur tree: Configuration, Pooling, Collections, Datasources, Logging, and CLI. Is there any reason for this much duplication, or is this a redundant question and is a port already in progress of the common stuff (I could understand wrappers to support the framework lifecycle methods, but the packages are all roughly the same size!). Thanks, Femi.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
