> > This could be solved by having OpenEJB aggressively boot your spring > application for your at deploy time while it's booting your application. > Then the same import/export could be done and all things would work > bi-directionally. We could potentially look for a Spring file named > META-INF/openejb-spring.xml (or something like that) and boot it with the > application. Then all the existing import/export code we have could be > executed things would work fine. > Or openejb-spring.xml could be the default file name and then also allow the user to specify the file name/s in the conf file <Resource type="Spring"> ConfigFiles context-file1.xml,context-file2.xml </Resource>
-- Karan Singh Malhi
