On Mon, May 24, 2004 at 10:36:45AM +0200, Vincent Massol wrote: > I was more thinking about a Java API rather than properties. My need is > to embed openEjb in java code so it's easier to call a Java API than to > use some properties. For example: > > public void addEjbJar(File ejbjar); > public void createContainer(...); > etc > > > How would you feel about two system properties for this, something > like: > > openejb.conf.deployment.dirs=<classpath-style dir list> > > openejb.conf.deployment.jars=<classpath-style jar list> > > > > Sure, but I think it would be even better to have: > > public void addEjbJar(File ejbjar);
Well, we do have methods that look like that in our code, but it's very hard to support them for integration purposes as they are what I would call "dirty internals" and have more to do with Castor XML usage and generated objects than OpenEJB. That code is already gone in OpenEJB 2. What about using DOM to create the four or five XML tags required in an openejb.xml file? -David
