You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Sanka Samaranayake <ss...@gmail.com> on 2005/11/02 07:51:45 UTC
[Sadesha2] Using Hibernate API to implement the Persistence Storage
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: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [Sadesha2] Using Hibernate API to implement the Persistence Storage
Posted by Davanum Srinivas <da...@gmail.com>.
-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 <pz...@gmail.com> 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 <ss...@gmail.com> 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:
> sandesha-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [Sadesha2] Using Hibernate API to implement the Persistence Storage
Posted by Davanum Srinivas <da...@gmail.com>.
-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 <pz...@gmail.com> 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 <ss...@gmail.com> 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:
> sandesha-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: sandesha-dev-help@ws.apache.org
> >
> >
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: sandesha-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: sandesha-dev-help@ws.apache.org
Re: [Sadesha2] Using Hibernate API to implement the Persistence Storage
Posted by Paul Fremantle <pz...@gmail.com>.
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 <ss...@gmail.com> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>
Re: [Sadesha2] Using Hibernate API to implement the Persistence Storage
Posted by Paul Fremantle <pz...@gmail.com>.
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 <ss...@gmail.com> 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: sandesha-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: sandesha-dev-help@ws.apache.org
>
>