RE: [hibernate-dev] User defined EntityMode
by Steve Ebersole
It is just on my wish list. Feel free to create an enhancement request.
Assign it to me if you can...
-----Original Message-----
From: hibernate-dev-bounces(a)lists.jboss.org
[mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Matt Veitas
Sent: Thursday, August 17, 2006 2:36 PM
To: hibernate-dev(a)lists.jboss.org
Subject: [hibernate-dev] User defined EntityMode
I saw a few weeks back some discussion about user defined entity modes.
Is there a JIRA issue that I can watch about this, or is this just on
someone's wish list for now?
"b) allow user defined entity modes. The infrastructure for allowing
this is now in place in HEAD. However, there are currently a lot of
places in the code base that assume the entity modes are enums and do ==
type comparisions. We either need to change all those, or somehow make
the user register their custom entity modes. Plus the DTD then needs to
be updated to support this."
Thanks,
-Matt
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
20 years, 1 month
User defined EntityMode
by Matt Veitas
I saw a few weeks back some discussion about user defined entity modes.
Is there a JIRA issue that I can watch about this, or is this just on
someone's wish list for now?
"b) allow user defined entity modes. The infrastructure for allowing
this is now in place in HEAD. However, there are currently a lot of
places in the code base that assume the entity modes are enums and do ==
type comparisions. We either need to change all those, or somehow make
the user register their custom entity modes. Plus the DTD then needs to
be updated to support this."
Thanks,
-Matt
20 years, 1 month
RE: [hibernate-dev] New build structure
by Steve Ebersole
Well the exceptions can get thrown (and wrapped) back to the clients...
-----Original Message-----
From: Max Andersen
Sent: Thursday, August 17, 2006 2:04 PM
To: Steve Ebersole
Cc: hibernate-dev(a)lists.jboss.org
Subject: Re: [hibernate-dev] New build structure
On Thu, 17 Aug 2006 20:45:34 +0200, Steve Ebersole
<steve.ebersole(a)jboss.com> wrote:
> Actually, regarding hibernate-client.jar, scratch that...
>
> It's not that it bundles javassist and forgets about cglib. It is
> simply pulling in all exceptions. Our custom javassist code does
define
> one custom bytecode-related exception, which is what you see getting
> pulled in.
i'm surprised the exception is needed but the interfaces in those
packages
are not ?
/max
>
> -----Original Message-----
> From: hibernate-dev-bounces(a)lists.jboss.org
> [mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Steve
> Ebersole
> Sent: Thursday, August 17, 2006 1:32 PM
> To: Max Andersen
> Cc: hibernate-dev(a)lists.jboss.org
> Subject: RE: [hibernate-dev] New build structure
>
> Regarding the docbook stuff, I think it probably makes more sense to
> move all the support stuff off to a separate project. Then we can
make
> use of svn:externals to pull it into each subproject. Probably the
same
> can be said for the javadoc style sheet. Probablly when we finally do
> get around to breaking up the layout of the svn repo, all these
"common"
> things go into a "common" subproject; revolutionary, I know... ;)
> Perhaps even the standard libs can go that route also.
>
> I can get the core build to generate these docs outputs for you as
well.
> Get me the target defs, etc.
>
> That was just cut-n-pasted from JBoss. I guess since they only care
> about javassist, they did not include cglib. Yes, I'll fix that.
>
>
> -----Original Message-----
> From: hibernate-dev-bounces(a)lists.jboss.org
> [mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
> Andersen
> Sent: Thursday, August 17, 2006 5:43 AM
> To: hibernate-dev(a)lists.jboss.org
> Subject: [hibernate-dev] New build structure
>
> Hi guys,
>
> Couple of things to document/talk about what dependencies hibernateext
> and
> the eclipse plugins have on a hibernate distribution and on hibernate3
> src
> it self.
>
> hibernateext/eclipse plugins just use hibernate distribution for the
> following things:
> 1) being able to run ant (ant-launcher.jar etc.)
> 2) the shared libs (including hsqldb.jar which are in different
> locations
> depending wether it is dist or src)
> 3) hibernate3.jar
> 4) javadoc/jdstyle.css
>
> It uses the hibernate3 src for:
> 5) docbook DTD references
>
("../../../../../Hibernate3/doc/reference/support/docbook-dtd/docbookx.d
> td"
> is to be found in all the docs)
> 6) docbook sources to build the eclipse hibernate help file.
>
> I've made the prepare-up-dir so it now includes #4 and everything
(that
> I
> know of) that depends seem to work fine with the prepare-up-dir.
>
> #5 would be great to fix so all the shared doc (dtd's AND build.xml)
> would
> be the same.
>
> #6 I could actually see being made part of the hibernate3 core build
(it
>
> is just basically applying a set of xsl files on the docbook to get a
> .zip)
>
> The best thing of course would be to make these dependencies more
> explicit....
>
>
> btw. hibernate-client.jar only contains bytecode.javassist should it
> not
> also contain bytecode.cglib in case the user is running with cglib?
>
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
20 years, 1 month
RE: [hibernate-dev] New build structure
by Steve Ebersole
Actually, regarding hibernate-client.jar, scratch that...
It's not that it bundles javassist and forgets about cglib. It is
simply pulling in all exceptions. Our custom javassist code does define
one custom bytecode-related exception, which is what you see getting
pulled in.
-----Original Message-----
From: hibernate-dev-bounces(a)lists.jboss.org
[mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Steve
Ebersole
Sent: Thursday, August 17, 2006 1:32 PM
To: Max Andersen
Cc: hibernate-dev(a)lists.jboss.org
Subject: RE: [hibernate-dev] New build structure
Regarding the docbook stuff, I think it probably makes more sense to
move all the support stuff off to a separate project. Then we can make
use of svn:externals to pull it into each subproject. Probably the same
can be said for the javadoc style sheet. Probablly when we finally do
get around to breaking up the layout of the svn repo, all these "common"
things go into a "common" subproject; revolutionary, I know... ;)
Perhaps even the standard libs can go that route also.
I can get the core build to generate these docs outputs for you as well.
Get me the target defs, etc.
That was just cut-n-pasted from JBoss. I guess since they only care
about javassist, they did not include cglib. Yes, I'll fix that.
-----Original Message-----
From: hibernate-dev-bounces(a)lists.jboss.org
[mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
Andersen
Sent: Thursday, August 17, 2006 5:43 AM
To: hibernate-dev(a)lists.jboss.org
Subject: [hibernate-dev] New build structure
Hi guys,
Couple of things to document/talk about what dependencies hibernateext
and
the eclipse plugins have on a hibernate distribution and on hibernate3
src
it self.
hibernateext/eclipse plugins just use hibernate distribution for the
following things:
1) being able to run ant (ant-launcher.jar etc.)
2) the shared libs (including hsqldb.jar which are in different
locations
depending wether it is dist or src)
3) hibernate3.jar
4) javadoc/jdstyle.css
It uses the hibernate3 src for:
5) docbook DTD references
("../../../../../Hibernate3/doc/reference/support/docbook-dtd/docbookx.d
td"
is to be found in all the docs)
6) docbook sources to build the eclipse hibernate help file.
I've made the prepare-up-dir so it now includes #4 and everything (that
I
know of) that depends seem to work fine with the prepare-up-dir.
#5 would be great to fix so all the shared doc (dtd's AND build.xml)
would
be the same.
#6 I could actually see being made part of the hibernate3 core build (it
is just basically applying a set of xsl files on the docbook to get a
.zip)
The best thing of course would be to make these dependencies more
explicit....
btw. hibernate-client.jar only contains bytecode.javassist should it
not
also contain bytecode.cglib in case the user is running with cglib?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
20 years, 1 month
RE: [hibernate-dev] New build structure
by Steve Ebersole
Regarding the docbook stuff, I think it probably makes more sense to
move all the support stuff off to a separate project. Then we can make
use of svn:externals to pull it into each subproject. Probably the same
can be said for the javadoc style sheet. Probablly when we finally do
get around to breaking up the layout of the svn repo, all these "common"
things go into a "common" subproject; revolutionary, I know... ;)
Perhaps even the standard libs can go that route also.
I can get the core build to generate these docs outputs for you as well.
Get me the target defs, etc.
That was just cut-n-pasted from JBoss. I guess since they only care
about javassist, they did not include cglib. Yes, I'll fix that.
-----Original Message-----
From: hibernate-dev-bounces(a)lists.jboss.org
[mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Max Rydahl
Andersen
Sent: Thursday, August 17, 2006 5:43 AM
To: hibernate-dev(a)lists.jboss.org
Subject: [hibernate-dev] New build structure
Hi guys,
Couple of things to document/talk about what dependencies hibernateext
and
the eclipse plugins have on a hibernate distribution and on hibernate3
src
it self.
hibernateext/eclipse plugins just use hibernate distribution for the
following things:
1) being able to run ant (ant-launcher.jar etc.)
2) the shared libs (including hsqldb.jar which are in different
locations
depending wether it is dist or src)
3) hibernate3.jar
4) javadoc/jdstyle.css
It uses the hibernate3 src for:
5) docbook DTD references
("../../../../../Hibernate3/doc/reference/support/docbook-dtd/docbookx.d
td"
is to be found in all the docs)
6) docbook sources to build the eclipse hibernate help file.
I've made the prepare-up-dir so it now includes #4 and everything (that
I
know of) that depends seem to work fine with the prepare-up-dir.
#5 would be great to fix so all the shared doc (dtd's AND build.xml)
would
be the same.
#6 I could actually see being made part of the hibernate3 core build (it
is just basically applying a set of xsl files on the docbook to get a
.zip)
The best thing of course would be to make these dependencies more
explicit....
btw. hibernate-client.jar only contains bytecode.javassist should it
not
also contain bytecode.cglib in case the user is running with cglib?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
20 years, 1 month
