-1. Till we get the LGPL policy cleared from Apache Legal, we should not introduce any dependency on LGPL. They are going to publish a policy sometime "soon".
thanks, dims On 11/2/05, Paul Fremantle <[EMAIL PROTECTED]> wrote: > Sanka > > I think that would be one approach. If we do that I would suggest creating a > set of Data Access Object interfaces, and put the Hibernate specific > implementations of them in a separate JAR. That way we could reimplement > those DAOs another way and remove the dependency on Hibernate at a later > stage if we desire. This is the model that Spring uses > http://www.springframework.org/docs/reference/orm.html and > is very effective. > > So the idea is: > > [Sandesha.jar] depends on [HDAO.jar] which depends on [ Hibernate.jar] > > but > > [Sandesha.jar] does not depend on [Hibernate.jar] > > Paul > > > On 11/2/05, Sanka Samaranayake <[EMAIL PROTECTED]> wrote: > > Hi Everyone, > > > > I want to know whether we can put java codings (which use the hibernate > > API) in repository and not include the hibernate.jar with the main > > distribution. Those classes wont compile unless hibernate.jar is present > > - hence the user is allowed to download it separately and recompile the > > code if support for persistence storage is needed > > > > If I recall correctly Axis1 did the same thing by not including the > > activation.jar in the main distribution and allowing the user to > > download it separately if they wanted the support. > > > > Best, > > Sanka > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- Davanum Srinivas : http://wso2.com/blogs/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
