Re: [Hibernate] eclipse chokes on current annotations code
That is a rather basic generics error that is a bug in javac since Properties is typed as MapObject,Object, not MapString,String. You are asking to be able to do (replacing ? with String to be more concrete): MapObject,Object m1 = ...; MapString,String m2 = (MapString,String) m1; javac disallows this as it should since one would be able to do the following otherwise: m1.put(one, new Integer(1)); String one = m2.get(one); // CCE since Integer !instanceof String In the Properties case javac must be getting lost in the non-trivial inheritance tree. See the following for discussions of the less intuitive aspects of generics: http://java.sun.com/j2se/1.5/pdf/generics-tutorial.pdf -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Wednesday, July 12, 2006 3:57 AM To: Hibernate development Subject: [Hibernate] eclipse chokes on current annotations code javac works fine, but eclipse chokes on casting Properties to MapString, ? I've bugged eclipse about it to see what they provide as explanation. https://bugs.eclipse.org/bugs/show_bug.cgi?id=150362 - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] eclipse chokes on current annotations code
This is the issue with generics. I have seen both javac and eclipse with compiler bugs that allowed unsafe usage of collections. There still really are no guarentees, only better static analysis of possible misuse. -Original Message- From: Max Andersen Sent: Wednesday, July 12, 2006 10:40 AM To: Scott M Stark; Hibernate development Subject: Re: [Hibernate] eclipse chokes on current annotations code yes, i realized this (also explained on the bug). What tricked me was that neither I or emmanuel must have been using the latest javac ;) /max - Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] questions regarding development setup
Its more a limitation of the testing environment than project structure. One should be able to annotate known tests as failing at either the test or ci layer to achieve a simple boolean overall result as to whether the testsuite is in an expected state. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Friday, June 09, 2006 10:03 AM To: Szczepan Faber Cc: hibernate-devel@lists.sourceforge.net Subject: Re: [Hibernate] questions regarding development setup The day you write a (needed and usefull!) unittest that is not possible in our current setup then lets talk ;) I've already created patch with couple testcases using same package layout on purpose. ok. No reason to change what just works. reasons: every time the developer cannot unit test non-public method / class w/o public constructor. (every day :) ?) well, it has never been an issue since we have more than enough tests that does this, so again it just works. Anyway I will just contribute a patch and let's see what you say... ok. PS Whatever you say, the failing tests / unreasonable test packaging just impact the project credibility. But it's just my opinion and my collegues. unreasonable test packaging ? Nothing *prevents* you from using another layout - and since our testsuite contains considerable more test than I've seen compared to other applications/frameworks it doesn't seem to be an issue in real life vs. theoretical rants. And do you rather want us to remove tests for known issues ? That sounds like you want us to hide the fact we know some part has a bug/issue ? how is that for credibility ? /max ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
which it isn't afaik. the antlr version started to include more data in the exception over time. Including additional data is not an incompatible serialzable change generally. Its optional data that will be ignored and cannot affect the legacy implementation. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. well, for me that is showing the exception message in a dialog in the ui I would be very disappointed to have a full stack trace in the message output. True, but this can be handled by wrapping the stacktrace in a generic exception whose msg is the cause stacktrace. And bytecode manipulation or simple modification of the exception in the jboss serialization/remoting layer have that option, correct ? Dealing with incorrect serialization implementation via hacks at the serialization layer is not a scalable solution. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
Right. The issue is we can't have the infinite web of project implementation details leaking to users unncessarily. Hibernate is a little different in that its used both in Java SE and Java EE profiles. My concern is that a pure Java EE client should not care about that antlr happens to be used for the ejb3 query language parser. Antlr should not be a required jar in the jboss client jars for ejb3 usage. -Original Message- From: Steve Ebersole Sent: Wednesday, February 08, 2006 6:52 AM To: Max Andersen; Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: RE: [Hibernate] Do antlr exception leak to users? Well I think the distinction here is that Hibernate constitutes a hard dependency on Antlr. The users choice to use Oracle is completely within their control. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Release naming conventions
This has nothing to do with the actual jar names. The version in the jar name is a poor convention as it propagates the version to users unnecessarily, and is not verifiable via a signed manifest. The jars checked into the repository should not have any explicit version information in the name. I don't care what naming conventions are used by projects elsewhere. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Tuesday, February 07, 2006 10:01 AM To: Christian Bauer; development Hibernate; [EMAIL PROTECTED] Subject: Re: [Hibernate] Release naming conventions I'm not a big fan of all minor releases needing to append '.ga' (i.e. 3.1.3.ga.jar). I really wish there was a way to define ordering amongst qualifiers. AFAIK these conventions are for package names and not necessarily library names? it's the version branded into the application - meaning what goes into MANIFEST.MF and distribution name; for me it would make sense to have that on the jar file too... And yes, would be great with an ordering that said 3.1.3 is newer than 3.1.3.alpha, 3.1.3.beta..but what is 3.1.3.2 then ? p.s. i'm planning on following this in the eclipse plugins too since it actually is very usefull there to have the update manager functionallity work together with alpha/beta/etc. /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=1216 42 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486; dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Release naming conventions
Any place the version is actually used. This is the manifest headers (these should also be spelled out and standardized including the osgi conventions for projects that need to comply with these headers), the repository component-info.xml, and the project build files. Really only the project build file should be where a project makes version changes and this should just propagated to artifacts based on the build tools. -Original Message- From: Max Andersen Sent: Tuesday, February 07, 2006 10:14 AM To: Scott M Stark; Christian Bauer; development Hibernate; [EMAIL PROTECTED] Subject: Re: [Hibernate] Release naming conventions so where do you want the name applied ? in the eclipse plugins it make sense for the jar's since that is the part being used to identify it + the plugin.xml/MANIFEST.MF osgi version part. /max This has nothing to do with the actual jar names. The version in the jar name is a poor convention as it propagates the version to users unnecessarily, and is not verifiable via a signed manifest. The jars checked into the repository should not have any explicit version information in the name. I don't care what naming conventions are used by projects elsewhere. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Max Rydahl Andersen Sent: Tuesday, February 07, 2006 10:01 AM To: Christian Bauer; development Hibernate; [EMAIL PROTECTED] Subject: Re: [Hibernate] Release naming conventions I'm not a big fan of all minor releases needing to append '.ga' (i.e. 3.1.3.ga.jar). I really wish there was a way to define ordering amongst qualifiers. AFAIK these conventions are for package names and not necessarily library names? it's the version branded into the application - meaning what goes into MANIFEST.MF and distribution name; for me it would make sense to have that on the jar file too... And yes, would be great with an ordering that said 3.1.3 is newer than 3.1.3.alpha, 3.1.3.beta..but what is 3.1.3.2 then ? p.s. i'm planning on following this in the eclipse plugins too since it actually is very usefull there to have the update manager functionallity work together with alpha/beta/etc. /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121 6 42 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486; dat=121642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
I'm a little concerned that this will lead to unnecessary coupling of client and server versions of antlr then. How often does an antlr exception as a cause show up in practise as an exception seen by an external client? -Original Message- From: Max Andersen Sent: Monday, February 06, 2006 11:53 AM To: Scott M Stark; jboss-development@lists.sourceforge.net; Hibernate development Subject: Re: [Hibernate] Do antlr exception leak to users? On Mon, 06 Feb 2006 20:49:08 +0100, Scott M Stark [EMAIL PROTECTED] wrote: I'm seeing some incompatible serial version uid changes in the latest antlr, but I don't know if antlr exceptions every leak to users outside of the vm such that this is an issue. Do the ql grammar exception get exposed or are they always converted to a hibernate exception? it is always converted, but of course it can be inside as a cause exception. /max --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
The problem is the source of the cause not providing a stable api for
the exception, not the inclusion of the cause itself. The solution is to
fix the antlr exceptions to specify the serialVersionUID to avoid
trivial changes showing up as version incompatibilities.
You can always work around this by explicitly incorporating the cause
into the exception message string:
try
{
...
}
catch(Exception e)
{
StringWriter sw = new StringWriter();
PrintWriter pw = new PrintWriter();
pw.println(... cause:);
e.printStackTrace(pw);
pw.close();
String msg = sw.toString();
throw new Xception(msg);
}
-Original Message-
From: Max Andersen
Sent: Tuesday, February 07, 2006 10:34 AM
To: Scott M Stark; jboss-development@lists.sourceforge.net;
Hibernate development
Subject: Re: [Hibernate] Do antlr exception leak to users?
On Tue, 07 Feb 2006 19:24:38 +0100, Scott M Stark
[EMAIL PROTECTED]
wrote:
I'm a little concerned that this will lead to unnecessary
coupling of
client and server versions of antlr then. How often does an antlr
exception as a cause show up in practise as an exception seen by an
external client?
hmm..whenever a syntax error occur in a HQL/EJBQL statement.
But how else can we provide the cause of an exception ?
This is a pretty critical part of debugging hibernate applications.
Not just for antlr exceptions, but jdbc driver exceptions,
sqlexceptions and any other external cause.
/max
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642
___
hibernate-devel mailing list
hibernate-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Release naming conventions
I added a Practices and Jar Manifest Headers section to the JBossProductVersioning page to discuss issues such as how nightly builds could be versioned. The headers section still needs to be completed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott M Stark Sent: Tuesday, February 07, 2006 10:22 AM To: Max Andersen; Christian Bauer; development Hibernate; [EMAIL PROTECTED] Cc: jboss-development@lists.sourceforge.net Subject: RE: [Hibernate] Release naming conventions Any place the version is actually used. This is the manifest headers (these should also be spelled out and standardized including the osgi conventions for projects that need to comply with these headers), the repository component-info.xml, and the project build files. Really only the project build file should be where a project makes version changes and this should just propagated to artifacts based on the build tools. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Do antlr exception leak to users?
fixing the antlr exception svuid won't help us if the client is using an older version, right ? It will if the serialVersionUID is set to the implicit value from the previous version. This can be done if the version is still serializable compatible. calling printStackTrace() on every exception sounds overkill for me...and will turn basic logging into something very verbose. Should be no different from now as logging generally includes the cause. I understand the issue, but don't find the suggested solutions any good ;( Would be nice to have an option to have any exposed remote exception do the serialization of the cause. Would make it a non-issue where it actually matters. This can't be done without modifying the exception either via source or bytecode manipulation. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Is Proxol actually needed in the dist?
Is the Proxool library actually used? It uses the old bsd style license that has a silly requirement regarding all advertising acknowledgment: http://proxool.sourceforge.net/licence.html 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: This product includes software developed by the Proxool Project (http://proxool.sourceforge.net/). --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] jacc-1_0-fr.jar source
Where did the jacc-1_0-fr.jar come from? --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Do antlr exception leak to users?
Im seeing some incompatible serial version uid changes in the latest antlr, but I dont know if antlr exceptions every leak to users outside of the vm such that this is an issue. Do the ql grammar exception get exposed or are they always converted to a hibernate exception? serialVersionUID error for antlr.ANTLRException, 402 7031854369222456415, current: -3185796504902623848 serialVersionUID error for antlr.TokenStreamException, 402 -6645096224442002282, current: -8659971349776228514
RE: [Hibernate] ClassLoader injection
Because the there may be serveral class loaders associated with a deployment. I'm missing the exact context of this discussion and how it correlates with the entity manager spi. Has there been a definition of what the tcl must be for the entity manager spi lifecycle? I don't see it browsing through the current ejb3 spec. -Original Message- From: Max Andersen Sent: Thursday, February 02, 2006 3:09 PM To: Scott M Stark; Emmanuel Bernard; Bill Burke Cc: Hibernate development Subject: Re: [Hibernate] ClassLoader injection hi, Why is the tcl not the right one even when generating classes ? if we don't use the same how can you have consistent resource loading, annotation searching and code invocation ? /max The general problem is that the thread context class loader can be too generic when you have a mesh of class loaders. As is mentioned in latter replies in this thread, if classes from a given package namespace have already been loaded via one class loader, generally all subsequent classes in the same package should be loaded/defined using the same class loader. Not doing so will lead to security and type consistency problems. In the case of the ejb3 entity manager spi, it does make sense that you would ask it for the correct class loader for byte code manipulation vs a class loader to query for resources and do annotation searching. -Original Message- From: Max Andersen Sent: Tuesday, January 31, 2006 11:53 PM To: Emmanuel Bernard; Bill Burke Cc: Hibernate development; Scott M Stark Subject: Re: [Hibernate] ClassLoader injection Hi, to bill, yes I know ctx current thread is the only way, that was my whole point (using ctx current thread in hibernate was actually the first patch i provided to hibernate core ;) and yes, having a third classloader concept in the spec sounds like a very broken thing. I would love to hear why it is needed. /max The RI team is going to creak, but I'm inclined to remove it as well. AS for your first remark, what's wrong with doing getResource with the regular classloader? I don't get it. Bill Burke wrote: I understand the need for PUInfo.getNewTempClassLoader() as getResource(META-INF/persistence.xml) may/will return multiples. Also, you may want to introspect the class for annotations before you decide what needs to be bytecode massaged. As for getClassLoader()? I'm not sure of the reasoning. I know Scott has some spec input on this. Maybe we should get it removed? Emmanuel Bernard wrote: Year I'm aware of that Bill :-) But in this case, and like Max said, why on earth the PersistenceUnitInfo has a getClassLoader() method instead of using the context CL? Bill Burke wrote: Max Rydahl Andersen wrote: If it is for the spec then I would argue that the spec is very wrong since it will break all other kind of stuff. Like how will you convince all the external libraries hibernate uses to use your magic classloader ? (e.g. log4j, dom4j, cglib, yada, yada) Thread.getContextCL() is the only way. If a library doesn't use Thread.getCCL() then it is a poorly written library. App server and J2EE in general require this because of classloader isolation (scoped ears or wars). If you are within Hibernate code and call Class.forName() it will use the classloader that loaded Hibernate to load the class. (read the javadocs) and you could get CCE, CNF exceptions. If you already know this, then apologies. The same issues effect the loading of resources. Bill -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: [Hibernate] Hibernate 3.1.2 released
This has been added to the repository.jboss.com contents and the org.jboss.test.hibernate.test.HibernateIntgUnitTestCase is now passing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Ebersole Sent: Saturday, January 28, 2006 6:47 AM To: hibernate-devel@lists.sourceforge.net Subject: [Hibernate] Hibernate 3.1.2 released Hibernate 3.1.2 has just been released: http://sourceforge.net/project/showfiles.php?group_id=40712package_id=1 27784release_id=388971 This release fixes, amongst other minor bugs/enhancements, bugs with Session closure checking, some potential bugs in HQL parameter binding, and issues with borrowed connections (i.e. Session.connection()) with agressive connection releasing. For a full list of changes, see the change log in the dist or check out: http://sourceforge.net/project/shownotes.php?release_id=388971group_id= 40712 --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
Re: [Hibernate] you just gotta love sf.net....
We should move the cvs repo to the jboss hosted one. Max Rydahl Andersen wrote: ...when you do an update and their sucky cvs server is suddenly in lock-mode and I lose 5 files and can't compile my hibernate3 anymore FYI http://sourceforge.net/tracker/?group_id=1atid=21 has about the first 40-50 cases about read-only cvs at the moment but noone with an answer. yippie! I'll just go look at the foggy view instead... Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss Inc [EMAIL PROTECTED] --- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42 plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Is this dependency realistic?
Bill created a dependency on a hibernate 3.1 final release for the jboss-4.0.3 release: http://jira.jboss.com/jira/browse/JBAS-1951 I would guess this also affects the har deployer. We want to get jboss-4.0.3 out end of this week, no latter than end of next week. Is this dependency realistic? --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
RE: Fw: RE: [Hibernate] Complex class loaders hierarchy
The class loading structure of a j2ee app is vendor specific. For any given component the correct starting point is the thread context class loader. That class loader should have visibility into parent class loaders as needed. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of baliuka juozas Sent: Thursday, June 16, 2005 12:12 AM To: [EMAIL PROTECTED]; hibernate-devel@lists.sourceforge.net Subject: Re: Fw: RE: [Hibernate] Complex class loaders hierarchy I do not think it is possible to find the the best way for this stuff, but we expected hibernate (and cglib) classes will be in the same or in the parent classloader (asumption is based on j2ee container class loading stuff). It must be better to use this asumption, it has more chances to be maintained. --- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77alloc_id492op=click ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
[Hibernate] Safe Query Objects
From a potential JOSF member: We're very keen to promote a standardization of a truly object-oriented, native API for both, ORMs and ODBMS, distinct from JDO and JDBC. Hibernate and db4o have similar, but proprietary interfaces. If there was a standardized API, people could switch back from ORM to ODBMS, depending of the nature of the application. We believe that the safe query proposal of William Cook (http://www.cs.utexas.edu/users/wcook/papers/SafeQuery/SafeQueryICSEv2.p df) is a very powerful platform for such an initiative. As we know that you have many projects on your Hibernate roadmap, we'd be happy to contribute an implementation of safe queries to Hibernate ... Does this make sense? --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ hibernate-devel mailing list hibernate-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hibernate-devel
