Re: [Hibernate] FW: [hibernate - Open Discussion] first crack at maven'ization
On 06 Jan (13:25), Gavin King wrote: > Check this out :) I evaluated project tools like Centipede and Maven half a year ago for Hibernate. You see, Maven is primarily used in Apache Group style projects. The amazing thing is: The goal of Maven is to unify the development process so a project can provide quality information/documentation. Aside from some technical issues, one thing I don't like about Apache Group Jakarta projects is the technical documentation! I hate these "Still nothing here" pages you'll find often in Struts, OJB, or the evil, completely undocumented Commons stuff. I don't see where the benefit of using Maven is and certainly don't want to follow the Apache Group road. Is there something wrong with the current build process? -- Christian Bauer [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ANN] Eclipse Plugin - Hibernator - Initial Release
Finally back from holidays and uploaded and released the source/ Go try it out! - http://sourceforge.net/projects/hibernator *** Hibernator - Hibernate plugin for Eclipse *** Provides an Eclipse view to create and edit Hibernate (http://hibernate.sourceforge.net) mapping files (.hbm.xml) Note this plugin will only work with Eclipse 2 (WSAD 5) and above * Installation - Unzip hibernator-0.9.zip into /plugins - Restart Eclipse * Using the plugin Go to menu Window->Show View->Other and select Hibernator Open up some Java source and the plugin will either display the mapping file .hbm.xml or a generated version To save the contents of the mapping file right click in the window and select "Save" Report any bugs / Submit patches to - http://sourceforge.net/projects/hibernator Original code from - Christopher (Jozsa Kristof) <[EMAIL PROTECTED]> (that's all the Sourceforge lists will show me) Contributions from - Gavin King - Daniel Bradby --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Suggestion: Encapsulate SQLException in HibernateException
On Sun, Jan 05, 2003 at 06:39:32PM -1000, Mark Woon wrote: > Gavin King wrote: > > >Has this thread died? > > > >I still havn't got a really good feeling for what other people > >think about this issue > > > > +1, would much prefer SQLException be nested within HibernateException. +1 here too (if that counts :). I'd prefer this way to the current way of handling exceptions. Cleaner, easier, makes sense for me. Christopher -- .Digital.Yearning.for.Networked.Assassination.and.Xenocide --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] [ANN] Eclipse Plugin - Hibernator - Initial Release
hi,
On Mon, 06 Jan 2003 22:43:32 +1100, "Daniel Bradby"
<[EMAIL PROTECTED]> said:
>
> Finally back from holidays and uploaded and released the source/
>
> Go try it out! - http://sourceforge.net/projects/hibernator
>
could you please make it compatible with JDK 1.3? there seems to be some
1.4 specific calls in it, eg. HibWriter.java:24:
String[] parts = name.split("\\.");
i'm stuck with 1.3 at my job, eh...
viktor
--
[EMAIL PROTECTED]
--
http://fastmail.fm - Accessible with your email software
or over the web
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [Hibernate2] suggestion: introduce beforeSave into interceptor...
Would the time now be best for introducing an beforeSave/beforeFlush method to interceptor ? Why ? Just to have a way to directly set properties on the object instead of via an side-effect as it is done know in onSave/onFlush. Just a suggestion :) /max --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Suggestion: Encapsulate SQLException in HibernateException
Im changing my +0 vote to +1 after seeing the arguments and after having
discussed it with my coworkers :)
Reasons:
1. It simplifies the exception handling. (You only got one exception to
catch)
2. Nested exceptions is becoming the defactor standard so no problems here
3. Hibernate can add semantic understanding to the exception.
Bad things:
0. One developer said: I would like to know if the HibernateException
actually originated from an SQLException...before you would know it
directly, in the future you could just "traverse" the chains to the
excpeiton to check the reason - so that is actually not a "bad thing" :)
1. It will break existing code and exception handling code.but if ones
exception handling code is so hairy that they cannot survive this change it
would be a good time to clean up anyway :)
/max
- Original Message -
From: "Gavin King" <[EMAIL PROTECTED]>
To: "Timothy Kettering" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, January 06, 2003 4:48 AM
Subject: RE: [Hibernate] Suggestion: Encapsulate SQLException in
HibernateException
This is exactly the kind of input I was looking for :) And your point
is quite correct; even if we *did* rationalize the Session interface
to throw only HibernateExceptions, in general, we *still* wouldn't be
able to do this:
Session s = sf.openSession()
try {
// do some work
}
catch (HibernateException he) {
// yada yada yada
}
finally {
s.close();
}
Why? because "yada yada yada" needs to happed no matter *what*
kind of exception occurred (even RuntimeExceptions).
However, there is another argument for this change, that no-one has
really brought up. Nested exceptions let us add some contextual
information to the wrapped SQLException. So the developer could
see what Hibernate was doing when the SQLException occurred.
At present you see a stack trace which is somewhat helpful but
probably less helpful than what we could do with nesting.
> This is just my two cents here, and I'm still relatively new to those
> parts, but here goes:
>
> I've been doing development on database backed persistence stuff, and
> after a brief unfullfilling fling with Castor, I ditched that
> and went
> with Hibernate and lets just say that this thing is a whole
> lot better.
>
> But I digress. Regarding SQLExceptions, I wrap everything up in the
> persistence layer with it's own exception, so theres just one
> exception
> to throw in the application when accessing the data, but in the
> persitence class file and with Hibernate, I found myself having to
> catch 4-5 different types of exceptions when doing a hibernate query,
> and I eventually just gave up on that and just put them in a vanilla
> Exception try-catch block and sort it out afterwards.
>
> I guess my point here is that in my case, I'm already catching it all
> with Exception so it doesn't make much difference to me
> because of all
> the other exceptions I have to catch anyway compels me to use this.
> But if the exceptions could be consolidated to just one or two types,
> then i would see a benefit to catching them individually.
>
> I don't know how others do it, they may have a better
> solution or know
> better than I do. But you wanted feelings, man! :)
>
> -tim
>
> On Sunday, January 5, 2003, at 10:09 PM, Gavin King wrote:
>
> > Has this thread died?
> >
> > I still havn't got a really good feeling for what other
> people think
> > about this issue
> >
> >> -Original Message-
> >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> >> Sent: Saturday, 4 January 2003 1:46 AM
> >> To: [EMAIL PROTECTED]
> >> Subject: [Hibernate] Suggestion: Encapsulate SQLException in
> >> HibernateException
> >>
> >>
> >> Hi,
> >>
> >> I was thinking about wrapping SQLException in
> HibernateException, so
> >> that we don't need to worry about catch HibernateException and
> >> SQLException. Since now the work is focused on some changes for
> >> Hibernate 2, this could be the right time to do this kind
> of change.
> >> This would simplify the error handling in the applications.
> >>
> >> Robson
> >>
> >>
> >>
> >> ---
> >> This sf.net email is sponsored by:ThinkGeek
> >> Welcome to geek heaven.
> >> http://thinkgeek.com/sf
> >> ___
> >> hibernate-devel mailing list [EMAIL PROTECTED]
> >> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> >>
> >
> >
> > ** CAUTION - Disclaimer **
> > This message may contain privileged and confidential
> information. If
> > you are not the intended recipient of this message (or
> responsible for
> > delivery of the message to such person) you are hereby
> notified that
> > any use, dissemination, distribution or reproduction of this message
> > is prohibited. If you have received this message in error,
> > you should destroy it and kindly notify the sender by reply
> > e-mail. Please advise immediately if you or your employer
>
[Hibernate] [ hibernate-Patches-662319 ] Codegen for Hibernate 2 - beta
Patches item #662319, was opened at 2003-01-04 21:15 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428710&aid=662319&group_id=40712 Category: Codegen Group: None Status: Open Resolution: None Priority: 5 Submitted By: Max R. Andersen (maxcsaucdk) Assigned to: Nobody/Anonymous (nobody) Summary: Codegen for Hibernate 2 - beta Initial Comment: Hi! Here is my 98% complete patch for Hibernate 2.0's new and improved codegenerator :) I'm submitting this one know in hope that someone might test it and see if they like the new functionallity. Remember to use the hibernate-2.0.dtd and Hibernate2 CVS Things that are new: - tag support. Look at http://hibernate.bluemars.net/57.html for examples of meta tag usage. Currently class, subclass, id and property is allowed to have tags. As soon as I get to it i'll add support for it in the DTD for composite-id, version, timestamp, all the collection types (any others ?) Thing that I have changed/fixed: - fixed timestamp support. It assumed timestamp could support an type via the DTD. It could not. Now it uses java.util.Data as it's default - is this the correct thing to do ? (maybe we should add an type to timestamp in DTD ?) - Uses logging instead of directly to System.out/err (I've modified log4j.properties to have a console-friendly output of the tool logging) ### log for tools output, more console userfriendly. (purely optional) log4j.appender.toolout=org.apache.log4j.ConsoleAppender log4j.appender.toolout.Target=System.out log4j.appender.toolout.layout=org.apache.log4j.PatternLa yout log4j.appender.toolout.layout.ConversionPattern=%p - %m%n log4j.logger.net.sf.hibernate.tool=debug, toolout log4j.additivity.net.sf.hibernate.tool=false -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428710&aid=662319&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Bugs-662501 ] Length af aliases too long
Bugs item #662501, was opened at 2003-01-04 23:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428708&aid=662501&group_id=40712 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Woon (unkyaku) Assigned to: Nobody/Anonymous (nobody) Summary: Length af aliases too long Initial Comment: Does Hibernate doesn't do any checking on the length of the aliases it generates when it creates it's SQL statements, which causes problems. I've went ahead and created a patch against Hibernate1 that resolves this problem. I've moved all the code for figuring out the proper length of the alias to StringHelper.suffix(). This eliminated OuterJoinLoader.aliasColumn(), OuterJoinLoader.aliasCore(), and AbstractEntityPersister.aliasColumn(), which you'd marked as needing to be refactored anyway. The patch also cleans up some unused variables in the affected classes, and adds a bit more information to an exception thrown in ReflectHelper. We might also want to do the same thing for table names, which is handled as a special case in OuterJoinLoader.alias(), where the length is reduced to 5. In either case, I didn't bother to make the max length of column names configurable dependent on Dialect. I just cut it to 20 if it was greater than 20. Anyone know if there are db's out there whose max length for column names is less than 20? -Mark -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428708&aid=662501&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Patches-661750 ] Table.uniqueColumnString
Patches item #661750, was opened at 2003-01-03 09:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661750&group_id=40712
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Benoit Menendez (bmenendez)
Assigned to: Nobody/Anonymous (nobody)
Summary: Table.uniqueColumnString
Initial Comment:
Would it be more appropriate to do:
public String uniqueColumnString(Iterator iterator) {
int result = name.hashCode();
while ( iterator.hasNext() ) result += iterator.next
().hashCode();
return Integer.toHexString(result).toUpperCase();
}
instead of
public String uniqueColumnString(Iterator iterator) {
int result = 0;
while ( iterator.hasNext() ) result += iterator.next
().hashCode();
return ( Integer.toHexString( name.hashCode() ) +
Integer.toHexString(result) ).toUpperCase();
}
This would generate shorter names
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661750&group_id=40712
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Bugs-662501 ] Length af aliases too long
Bugs item #662501, was opened at 2003-01-04 23:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428708&aid=662501&group_id=40712 Category: None Group: None Status: Open Resolution: None >Priority: 7 Submitted By: Mark Woon (unkyaku) Assigned to: Nobody/Anonymous (nobody) Summary: Length af aliases too long Initial Comment: Does Hibernate doesn't do any checking on the length of the aliases it generates when it creates it's SQL statements, which causes problems. I've went ahead and created a patch against Hibernate1 that resolves this problem. I've moved all the code for figuring out the proper length of the alias to StringHelper.suffix(). This eliminated OuterJoinLoader.aliasColumn(), OuterJoinLoader.aliasCore(), and AbstractEntityPersister.aliasColumn(), which you'd marked as needing to be refactored anyway. The patch also cleans up some unused variables in the affected classes, and adds a bit more information to an exception thrown in ReflectHelper. We might also want to do the same thing for table names, which is handled as a special case in OuterJoinLoader.alias(), where the length is reduced to 5. In either case, I didn't bother to make the max length of column names configurable dependent on Dialect. I just cut it to 20 if it was greater than 20. Anyone know if there are db's out there whose max length for column names is less than 20? -Mark -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428708&aid=662501&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Feature Requests-567274 ] byte[] identifier, etc.
Feature Requests item #567274, was opened at 2002-06-11 16:12 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=567274&group_id=40712 Category: None Group: None >Status: Closed Priority: 3 Submitted By: Gavin King (oneovthafew) Assigned to: Nobody/Anonymous (nobody) Summary: byte[] identifier, etc. Initial Comment: There is a fairly straightforward change that could be made which would allow binary type identifiers and composite key classes that do not override equals/hashCode. Instead, the session could use the identifier Type to perform equals/hashCode. -- >Comment By: Gavin King (oneovthafew) Date: 2003-01-06 12:44 Message: Logged In: YES user_id=384580 Its unlikely that this feature will ever be needed. A similar effect can be achieved with a "custom type identifier" pattern and its likely that this change would effect performance (even when NOT using id types that do not override equals). -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=567274&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Feature Requests-512567 ] Mapping Tool
Feature Requests item #512567, was opened at 2002-02-04 12:49 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=512567&group_id=40712 Category: None Group: None >Status: Closed Priority: 1 Submitted By: Daniel Bradby (dbradby) Assigned to: Nobody/Anonymous (nobody) Summary: Mapping Tool Initial Comment: As I've seen with Cocobase, it comes with a tool to do the mappings visually (it had want to for that price). We need something similar. These tools could generate mappings visually or through source parsing of doclets (thanks Paul). Also a way creating the database structure with this tool would be great. I think we can get something simple done very soon. -- >Comment By: Gavin King (oneovthafew) Date: 2003-01-06 12:41 Message: Logged In: YES user_id=384580 We have had extensive discussions of a full rountripping toolset based upon XDoclet and Middlegen. These are MUCH more powerful ideas than a "mapping gui". This feature request is now out of date. -- Comment By: Gavin King (oneovthafew) Date: 2002-10-31 19:24 Message: Logged In: YES user_id=384580 After having spent a little time playing with one of these mapping tools, I've concluded that hand-editing the mapping file is simply _much_ more efficient. Our mapping format is quite readable (it was designed to be edited by hand). I don't think this feature is desirable after all. (Of course some parts of this feature request were done ages ago.) -- Comment By: Christian Meunier (tlvenn) Date: 2002-07-29 08:43 Message: Logged In: YES user_id=583408 Take a look at JRelay too, their GUI is pretty good (better than cocobase imho) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=512567&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Feature Requests-635016 ] lock() a transient object
Feature Requests item #635016, was opened at 2002-11-08 02:26 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=635016&group_id=40712 Category: None Group: None Status: Open >Priority: 1 Submitted By: Gavin King (oneovthafew) Assigned to: Nobody/Anonymous (nobody) Summary: lock() a transient object Initial Comment: It would be very useful to be able to associate a transient object with the session (obtaining an appropriate lock-level by, for example, a version check). Currently the only way to do this is to use update(). That would be overkill if we aren't updating the object. -- >Comment By: Gavin King (oneovthafew) Date: 2003-01-06 12:55 Message: Logged In: YES user_id=384580 Note that there ARE some conceptual difficulties with this. Its most likely an undesirable feature. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=635016&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Feature Requests-650587 ] unsaved-value for
Feature Requests item #650587, was opened at 2002-12-08 14:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=650587&group_id=40712 Category: None Group: None Status: Open Priority: 5 Submitted By: Gavin King (oneovthafew) Assigned to: Nobody/Anonymous (nobody) Summary: unsaved-value for Initial Comment: Currently only the and elements permit the unsaved-value attribute. There are a couple of circumstances where that is *not* convenient; particularly in the case of assigned identifiers. So we should generalize the model and allow unsaved-value for or . -- Comment By: Mark Woon (unkyaku) Date: 2003-01-05 19:19 Message: Logged In: YES user_id=435832 Gavin, this would potentially solve the cascade prolem for objects that have an assigned identifiers. It would be great to be able to specify unsaved-value on either or instead of for this purpose. -- Comment By: Gavin King (oneovthafew) Date: 2003-01-05 17:54 Message: Logged In: YES user_id=384580 This would be *particularly* useful for the and elements; ie. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=650587&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Patches-645169 ] codegen enhancements
Patches item #645169, was opened at 2002-11-28 20:24
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=428710&aid=645169&group_id=40712
Category: Codegen
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 3
Submitted By: Max R. Andersen (maxcsaucdk)
Assigned to: Nobody/Anonymous (nobody)
Summary: codegen enhancements
Initial Comment:
The following patch provides two things (sorry -
had to do both to make it work in my reallife
project :)
1. Codegen now generates getter/setters for
version and timestamps (it did not do it before!)
(a 2 line change)
2. Support for codegenname in the definition of
class/subclasses.
3. Removed an unused and redundant paremter
in the Render interface.
#2 makes it possible to do the following:
..
..
Where the codegen attribute (if provided) will be
used by the codegenerator instead of the name
attribute.
This makes it possible to "extend" the
codegenerated code - and still have the option
of "regenerating" code without messing with your
own "extensions"
so you could have:
class Person extends AutoPerson {
public Object getNonPersistedProperty() {
return "whatever I want":
}
}
This improves hibernates round-trip abilities! :)
--
>Comment By: Gavin King (oneovthafew)
Date: 2003-01-06 17:33
Message:
Logged In: YES
user_id=384580
This patch is now obsolete, I assume?
--
Comment By: Gavin King (oneovthafew)
Date: 2002-12-06 10:47
Message:
Logged In: YES
user_id=384580
Cool. I will integrate this for 1.2.1. Trying to make
as-minimal-as-possible changes before 1.2final.
Thanks :)
--
Comment By: Max R. Andersen (maxcsaucdk)
Date: 2002-12-05 20:28
Message:
Logged In: YES
user_id=18119
and now the patch :)
--
Comment By: Max R. Andersen (maxcsaucdk)
Date: 2002-12-05 20:27
Message:
Logged In: YES
user_id=18119
Ok - now a patch that fixes ALL problems - ah,
almost :)
This time the codegen get's its information from
And now it supports/requires a fully qualified name.
Currently it is only the codegenerator that is aware of
metaattribute tag.
It works for normal classes, and should work for
subclass'es also.
Is this good enough for inclusion now ? :)
--
Comment By: Max R. Andersen (maxcsaucdk)
Date: 2002-11-29 00:06
Message:
Logged In: YES
user_id=18119
btw. the current implementation only support that the
codegenname is in the same package as the "real"
one.
Supporting another packagename requires some
more cumbersome work :(
--
Comment By: Max R. Andersen (maxcsaucdk)
Date: 2002-11-29 00:05
Message:
Logged In: YES
user_id=18119
Fine for me - maybe call it metaattribute/tag/info to
emphasize it has nothing to do with
attributes/properties ?
It would make "future" codegen enhancments easier
- and maybe even make it availiable thorugh the
metadata api ?!!? :)
--
Comment By: Gavin King (oneovthafew)
Date: 2002-11-28 23:42
Message:
Logged In: YES
user_id=384580
I have committed the version/timestamp stuff.
As to the second part, rather than adding a new attribute to
, can we instead add a new metadata element like:
What do you think?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=428710&aid=645169&group_id=40712
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] FW: [hibernate - Open Discussion] first crack at maven'ization
Check this out :)
-Original Message-
From: SourceForge.net [mailto:[EMAIL PROTECTED]
Sent: Monday, 6 January 2003 1:08 PM
To: [EMAIL PROTECTED]
Subject: [hibernate - Open Discussion] first crack at maven'ization
Read and respond to this message at:
https://sourceforge.net/forum/message.php?msg_id=1819063
By: savaki
I've got a first crack of mavenized version of hibernate. How do I send
this to you?
Here's the project site that it currently generates:
http://www.indigoegg.com/hibernate/
The unit test results were based on running hibernate 1.2.1 against
MySQL 4.0.5
Cheers!
__
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit:
https://sourceforge.net/forum/monitor.php?forum_id=128638
** CAUTION - Disclaimer **
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS End of Disclaimer **
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Suggestion: Encapsulate SQLException in HibernateException
Has this thread died?
I still havn't got a really good feeling for what other people
think about this issue
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 4 January 2003 1:46 AM
> To: [EMAIL PROTECTED]
> Subject: [Hibernate] Suggestion: Encapsulate SQLException in
> HibernateException
>
>
> Hi,
>
> I was thinking about wrapping SQLException in
> HibernateException, so that we don't need to worry about
> catch HibernateException and SQLException. Since now the work
> is focused on some changes for Hibernate 2, this could be the
> right time to do this kind of change. This would simplify the
> error handling in the applications.
>
> Robson
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ___
> hibernate-devel mailing list [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>
** CAUTION - Disclaimer **
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS End of Disclaimer **
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Feature Requests-650587 ] unsaved-value for
Feature Requests item #650587, was opened at 2002-12-09 09:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=650587&group_id=40712 Category: None Group: None Status: Open >Priority: 5 Submitted By: Gavin King (oneovthafew) Assigned to: Nobody/Anonymous (nobody) Summary: unsaved-value for Initial Comment: Currently only the and elements permit the unsaved-value attribute. There are a couple of circumstances where that is *not* convenient; particularly in the case of assigned identifiers. So we should generalize the model and allow unsaved-value for or . -- >Comment By: Gavin King (oneovthafew) Date: 2003-01-06 12:54 Message: Logged In: YES user_id=384580 This would be *particularly* useful for the and elements; ie. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=650587&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Suggestion: Encapsulate SQLException in HibernateException
This is exactly the kind of input I was looking for :) And your point
is quite correct; even if we *did* rationalize the Session interface
to throw only HibernateExceptions, in general, we *still* wouldn't be
able to do this:
Session s = sf.openSession()
try {
// do some work
}
catch (HibernateException he) {
// yada yada yada
}
finally {
s.close();
}
Why? because "yada yada yada" needs to happed no matter *what*
kind of exception occurred (even RuntimeExceptions).
However, there is another argument for this change, that no-one has
really brought up. Nested exceptions let us add some contextual
information to the wrapped SQLException. So the developer could
see what Hibernate was doing when the SQLException occurred.
At present you see a stack trace which is somewhat helpful but
probably less helpful than what we could do with nesting.
> This is just my two cents here, and I'm still relatively new to those
> parts, but here goes:
>
> I've been doing development on database backed persistence stuff, and
> after a brief unfullfilling fling with Castor, I ditched that
> and went
> with Hibernate and lets just say that this thing is a whole
> lot better.
>
> But I digress. Regarding SQLExceptions, I wrap everything up in the
> persistence layer with it's own exception, so theres just one
> exception
> to throw in the application when accessing the data, but in the
> persitence class file and with Hibernate, I found myself having to
> catch 4-5 different types of exceptions when doing a hibernate query,
> and I eventually just gave up on that and just put them in a vanilla
> Exception try-catch block and sort it out afterwards.
>
> I guess my point here is that in my case, I'm already catching it all
> with Exception so it doesn't make much difference to me
> because of all
> the other exceptions I have to catch anyway compels me to use this.
> But if the exceptions could be consolidated to just one or two types,
> then i would see a benefit to catching them individually.
>
> I don't know how others do it, they may have a better
> solution or know
> better than I do. But you wanted feelings, man! :)
>
> -tim
>
> On Sunday, January 5, 2003, at 10:09 PM, Gavin King wrote:
>
> > Has this thread died?
> >
> > I still havn't got a really good feeling for what other
> people think
> > about this issue
> >
> >> -Original Message-
> >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> >> Sent: Saturday, 4 January 2003 1:46 AM
> >> To: [EMAIL PROTECTED]
> >> Subject: [Hibernate] Suggestion: Encapsulate SQLException in
> >> HibernateException
> >>
> >>
> >> Hi,
> >>
> >> I was thinking about wrapping SQLException in
> HibernateException, so
> >> that we don't need to worry about catch HibernateException and
> >> SQLException. Since now the work is focused on some changes for
> >> Hibernate 2, this could be the right time to do this kind
> of change.
> >> This would simplify the error handling in the applications.
> >>
> >> Robson
> >>
> >>
> >>
> >> ---
> >> This sf.net email is sponsored by:ThinkGeek
> >> Welcome to geek heaven.
> >> http://thinkgeek.com/sf
> >> ___
> >> hibernate-devel mailing list [EMAIL PROTECTED]
> >> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> >>
> >
> >
> > ** CAUTION - Disclaimer **
> > This message may contain privileged and confidential
> information. If
> > you are not the intended recipient of this message (or
> responsible for
> > delivery of the message to such person) you are hereby
> notified that
> > any use, dissemination, distribution or reproduction of this message
> > is prohibited. If you have received this message in error,
> > you should destroy it and kindly notify the sender by reply
> > e-mail. Please advise immediately if you or your employer
> > do not consent to Internet e-mail for messages of this kind.
> > Opinions, conclusions and other information in this
> > message that do not relate to the official business of
> > Expert Information Services Pty Ltd ("The Company")
> > shall be understood as neither given nor endorsed by it.
> >
> > The Company advises that this e-mail and any attached
> > files should be scanned to detect viruses. The Company accepts no
> > liability for loss or damage (whether caused by negligence or not)
> > resulting from the use of any attached files.
> > **EIS End of Disclaimer **
> >
> >
> >
> > ---
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > ___
> > hibernate-devel mailing list [EMAIL PROTECTED]
> > https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> >
>
>
---
This sf.net email is sponsored by:Th
Re: [Hibernate] Suggestion: Encapsulate SQLException in HibernateException
Gavin King wrote: Has this thread died? I still havn't got a really good feeling for what other people think about this issue +1, would much prefer SQLException be nested within HibernateException. -Mark --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] Suggestion: Encapsulate SQLException in HibernateException
On 06 Jan (14:09), Gavin King wrote: > Has this thread died? > > I still havn't got a really good feeling for what other people > think about this issue I think every distinct layer in a system should throw only one Exception type, possibly wrapping another Exception (this is called Exception Chaining, standard with JDK 1.4 now). So, wrapping an SQLException in a HibernateException is OK. > > I was thinking about wrapping SQLException in > > HibernateException, so that we don't need to worry about > > catch HibernateException and SQLException. Since now the work > > is focused on some changes for Hibernate 2, this could be the > > right time to do this kind of change. This would simplify the > > error handling in the applications. -- Christian Bauer [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Feature Requests-650587 ] unsaved-value for
Feature Requests item #650587, was opened at 2002-12-09 09:38 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=650587&group_id=40712 Category: None Group: None Status: Open Priority: 5 Submitted By: Gavin King (oneovthafew) Assigned to: Nobody/Anonymous (nobody) Summary: unsaved-value for Initial Comment: Currently only the and elements permit the unsaved-value attribute. There are a couple of circumstances where that is *not* convenient; particularly in the case of assigned identifiers. So we should generalize the model and allow unsaved-value for or . -- >Comment By: Gavin King (oneovthafew) Date: 2003-01-06 14:35 Message: Logged In: YES user_id=384580 yep, thats the idea. Its basically pretty easy to implement this . Start by changing ClassPersister.isUnsaved() to have the following signature: public boolean isUnsaved(Serializable id, Object object) That way the persister can also interrogate the object's version property Do you want to create a patch against the Hibernate 2 source tree? -- Comment By: Mark Woon (unkyaku) Date: 2003-01-06 14:19 Message: Logged In: YES user_id=435832 Gavin, this would potentially solve the cascade prolem for objects that have an assigned identifiers. It would be great to be able to specify unsaved-value on either or instead of for this purpose. -- Comment By: Gavin King (oneovthafew) Date: 2003-01-06 12:54 Message: Logged In: YES user_id=384580 This would be *particularly* useful for the and elements; ie. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428711&aid=650587&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Patches-661753 ] Could you please add...
Patches item #661753, was opened at 2003-01-04 05:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661753&group_id=40712 Category: None Group: None Status: Open >Resolution: Postponed Priority: 5 Submitted By: Benoit Menendez (bmenendez) Assigned to: Nobody/Anonymous (nobody) Summary: Could you please add... Initial Comment: The readonly attribute to the map element in the DTD. This is necessary for bidirectional map. Thanks. -- >Comment By: Gavin King (oneovthafew) Date: 2003-01-05 11:56 Message: Logged In: YES user_id=384580 This was already added to hibernate-mapping-2.0.dtd. If you want to add it to your local copy of hibernate-mapping-1.1.dtd, its perfectly safe to do so. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661753&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Patches-661753 ] Could you please add...
Patches item #661753, was opened at 2003-01-03 10:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661753&group_id=40712 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Benoit Menendez (bmenendez) Assigned to: Nobody/Anonymous (nobody) Summary: Could you please add... Initial Comment: The readonly attribute to the map element in the DTD. This is necessary for bidirectional map. Thanks. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661753&group_id=40712 --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Hibernate 2 Transaction API
> Not sure what benefits these methods add, since I don't think
> I'd ever
> use them...
Well, the benefit was supposed to be a slightly cleaner idiom
with no extra local variable holding the transaction, or
test for (tx!=null) in the catch block.
Nevertheless, upon reflection, I'm inclined to NOT make these
changes. Its likely that they would cause confusion for new
users and they certainly do "grow" the API without adding
functionality.
Thanks for your feedback.
** CAUTION - Disclaimer **
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS End of Disclaimer **
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] logo
Ace! Blue Mars webdesign is excellent :)
I'd really appreciate their help. Let them know
we'd like something reasonably scalable so that
we can use the same design in the header of the
Wiki site as we use on the little "powered by"
button
Thanks
> -Original Message-
> From: Christian Bauer [mailto:[EMAIL PROTECTED]
> Sent: Monday, 6 January 2003 10:32 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Hibernate] logo
>
>
> On 06 Jan (10:22), Gavin King wrote:
>
> > I'd love to have a logo but don't know anyone with the
> requisite gfx
> > skills ...
> >
> > Suggestions?
>
> We have designers in our company, maybe one of them has some
> time left.
> My girlfriend's also a graphics designer. I'll see what I can do and
> maybe come up with some suggestions for voting next week.
>
> --
> Christian Bauer
> [EMAIL PROTECTED]
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ___
> hibernate-devel mailing list [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>
** CAUTION - Disclaimer **
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS End of Disclaimer **
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] logo
I'd love to have a logo but don't know anyone with the
requisite gfx skills ...
Suggestions?
> do you have a hibernate logo i can use on
> http://boss.bekk.no/boss/middlegen/ when i commit the
> hibernate plugin? the logo.jpg that figured on the hibenrate
> site in pre-wiki days has gray background and not really
> suitable for "powered by hibernate".
>
> if you don't have one, i suggest you design one. i have
> feeling that many projects would like to have a "powered by
> hibernate" logo in the near future, and it's good pr for you.
>
> aslak
>
>
>
> ---
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> ___
> hibernate-devel mailing list [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>
** CAUTION - Disclaimer **
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS End of Disclaimer **
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Tools (again)
I'm not sure if people noticed, but I submitted an alternate Middlegen
plugin that generates hbm.xml, as discussed here. Theres a few
improvements I need to make to that, but I will try to get onto
"finishing" it in the next few days.
I also understand that Konstantin is adding composite id support to the
XDoclet module and that Max has very nearly finished the patch
for hbm2java.
To complete our full roundtripping I suggest the following additional
toolset features:
(1) create a ant task (easy to do)
(2) add a @hibernate.meta tag to the XDoclet module
(3) add functionality for generation of XDoclet @hibernate.tags to
hbm2java
These new features will allow full reversability of
via and vice versa.
Max has suggested that hbm2java could use a velocity template for code
generation. Particularly now that I have a bit of experience with
velocity, I certainly agree that it would be a nicer way of doing
things. However, from a practical point of view, I wouldn't want someone
to waste time on this if that would mean a big delay in delivering the
"finished" toolset. The #1 advantage I see to using a template is that
users would then be able to easily customize to template to suit their
own preferences. OTOH, if we wanted that, then we would probably need to
clean up the underlying "model" objects that represent the parsed
mapping document. So anyway, lets put that (the template) on the todo
list, but leave implementing (1) and (3), by whatever means, as the top
priority.
Thoughts?
** CAUTION - Disclaimer **
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS End of Disclaimer **
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] [ hibernate-Patches-661750 ] Table.uniqueColumnString
Patches item #661750, was opened at 2003-01-04 04:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661750&group_id=40712
Category: None
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 5
Submitted By: Benoit Menendez (bmenendez)
Assigned to: Nobody/Anonymous (nobody)
Summary: Table.uniqueColumnString
Initial Comment:
Would it be more appropriate to do:
public String uniqueColumnString(Iterator iterator) {
int result = name.hashCode();
while ( iterator.hasNext() ) result += iterator.next
().hashCode();
return Integer.toHexString(result).toUpperCase();
}
instead of
public String uniqueColumnString(Iterator iterator) {
int result = 0;
while ( iterator.hasNext() ) result += iterator.next
().hashCode();
return ( Integer.toHexString( name.hashCode() ) +
Integer.toHexString(result) ).toUpperCase();
}
This would generate shorter names
--
>Comment By: Gavin King (oneovthafew)
Date: 2003-01-05 11:58
Message:
Logged In: YES
user_id=384580
I'd rather *not* change this now, since people are already
using the existing name generation. It destroys the whole
point of having consistent name generation if we keep
changing the algorithm underneath them ;)
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=428710&aid=661750&group_id=40712
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
