Hi all,

I would like to use confugration in pico, and if configuration would provide
constructors, which resemble various configure() methods, my life would be easier.

Now I have to write subclass it and write those constructors myself.

Any chance that you can provide those constructors?

eh - do you want approx. N+1 constructors on Configuration ?

You will have to present two things for this to happen:

1. the constructors you think you are missing

2. a very good reason for having such a possible complex constructors when the current system works perfectly with anything else ;)

1. all the same paameters as various configure(whatever) methods
2. being able to use Configuration as pico component without writing
a wrapper myself.

I would be glad to contribute those 15 lines of code to hibernate team,
and not to put them intopicocontainer code.

This way it's better in synch.

What I would like to avoid to commit to nanocontainer:
---%<-------------------
/*****************************************************************************
* Copyright (c) PicoContainer Organization. All rights reserved. *
* ------------------------------------------------------------------------- *
* The software in this package is published under the terms of the BSD *
* style license a copy of which has been included with this distribution in *
* the license.html file. *
* *
* Idea by Rachel Davies, Original code by Aslak Hellesoy and Paul Hammant *
*****************************************************************************/
package org.nanocontainer.hibernate;

import net.sf.hibernate.cfg.Configuration;
import net.sf.hibernate.HibernateException;

import java.net.URL;
import java.io.File;

/**
* constructable hibernate configuration. not a rocket science, just a wrapper aroung
* various configure() methods... see respective hibernate javadocs.
* @author Konstantin Pribluda
* @version $Revision:$
*/
public class ConstructableConfiguration extends Configuration {

public ConstructableConfiguration() throws HibernateException {
configure();
}

public ConstructableConfiguration(URL url) throws HibernateException {
configure(url);
}
public ConstructableConfiguration(String resource) throws HibernateException {
configure(resource);
}

public ConstructableConfiguration(File configFile) throws HibernateException {
configure(configFile);
}
}
---%<-----------------

if is only those few methods with a single parameter to the constructor then we might be convinced ;)

if you submit it as a patch against Configuration.java on the JIRA there is
a higher probability for it being integrated..

to be hones, I have my problems to provide patch against newest hibernate version.

Im not sure against which one.

HEAD is not used ( was not ) , and I do not know which branch to take....


For now I will commit it into nanocontainer-hibernate, and you may pick it up if you like.
( like velocity people did so there is no "nanocontainer-velocity" yet.)

v21branch => v21.x

HEAD => hibernate 3

Max, you still have the old tags :)

Hibernate2 HEAD => Hibernate 2.1.x
Hibernate3 HEAD => Hibernate 3.0 alpha