hot deployment is an implementation detail, but I'm talking about identifying a directory vs an archive (exploded or not) for other purposes as well. The VFS alone cannot determine this. What I was suggesting was adding an attributes or perhaps simply a properties accessor to the VFS api to allow additional information to be built up from the structure deployer, etc.
The complication with this is keeping it around. This should not be too hard for in memory usage that is built up only for the current runtime. Persisting such info across restarts is a little more involved as its a security issue to need write access to the filesystem.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163118#4163118
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163118
Ales suggested I ask this question here:
Currently, if I want to replace hsqldb with another database, (among many other things) I need to edit the ejb3-timer-service.xml file because that file contains information specific to Hypersonic. This is in contrast to the situation with messaging where alternate messaging persistence files are (finally) provided (in CR1) at docs/examples/jms, in which case I only have to copy the desired configuration file.
Are there any plans to provide alternate configuration files for other databases, say at docs/example/ejb3-timer? If so, I could contribute the MySQL and PostgreSQL files...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4163102#4163102
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4163102