[ http://opensource.atlassian.com/projects/hibernate/browse/HB-1512?page=co... ]
Vitaly Sazanovich commented on HB-1512:
---------------------------------------
In one year I'm having the same problem with ehcache1.1 and hibernate2. My temporary solution is more radical though. I moved the whole project to C:\ and voila, it works. Looks like the guys who wrote this loading routine were on Linux.
> Hibernate 2.1.8 with EhCache 0.9 throws exception on Windows in EhCacheProvider.start if the filepath to ehcache.xml contains spaces.
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HB-1512
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1512
> Project: Hibernate2
> Type: Bug
> Components: core
> Versions: 2.1.8
> Environment: Platform Microsoft Windows XP, Hibernate Version 2.1.8, EhCache 0.9, JBoss 4.0.2. Installed directory "c:\program files"
> Reporter: Sandip Ghosh
>
>
> I have an application deployed in JBoss 4.0.2 using Hibernate 2.1.8 using EhCache 0.9 on Windows platform with the deployment directory off "c:\program files". In EhCacheProvider.start() method the code:
> manager = CacheManager.create();
> throws an exception caused by a FileNotFoundException in net.sf.ehcache.config.Configurator.configure when attempting to parse ehcache.xml file because the file path has spaces in it. I have filed an bug against the Ehcache project at the following URL:
> http://sourceforge.net/tracker/index.php?func=detail&aid=1237017&group_id...
> Ehcache 1.1 has a method to create load the cache from an InputStream to the ehcache.xml object. Modifying the code in EhCacheProvider to call
> net.sf.ehcache.CacheManager.create(InputStream) will work in windows when there are spaces in the deployment directory.
> My temporary solution was to swallow the exception in EhCacheProvider.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
CLONE -Sequences generated in PostgreSQL not respect curent table schema name.
------------------------------------------------------------------------------
Key: HHH-1997
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1997
Project: Hibernate3
Type: Bug
Versions: 3.2.0.cr2
Reporter: Grigoras Cristinel
Priority: Minor
Hi,
I have a table where de ID is generate using sequence.
The table is inside schema "newschema".
The sequence is generate inside public schema. How can i create sequence inside curent table schema.
Cristi
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ]
Frank Grimes commented on HHH-1740:
-----------------------------------
So shouldn't this issue get re-opened until it builds from SVN with the junitinstrument task in SVN?
> Build-time instrumentation breaks lazy="proxy"
> ----------------------------------------------
>
> Key: HHH-1740
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2
> Reporter: Frank Grimes
> Assignee: Steve Ebersole
> Priority: Critical
> Fix For: 3.2.0.ga
> Attachments: 312Document.class, Document.class, HHH-1740.diff
>
>
> I have a mapping that contains a many-to-one lazy="proxy".
> This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load
> Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks.
> Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object)
> This works fine in hibernate-3.1.2.
> This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881
> Please let me know if more info or a test case is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ]
Steve Ebersole commented on HHH-1740:
-------------------------------------
I just made a similiar change to the buildtime instrumentation test and the tests are working for me. I do however have a slightly modified version of the ant script that does not try to instrument non-domain classes...
> Build-time instrumentation breaks lazy="proxy"
> ----------------------------------------------
>
> Key: HHH-1740
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2
> Reporter: Frank Grimes
> Assignee: Steve Ebersole
> Priority: Critical
> Fix For: 3.2.0.ga
> Attachments: 312Document.class, Document.class, HHH-1740.diff
>
>
> I have a mapping that contains a many-to-one lazy="proxy".
> This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load
> Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks.
> Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object)
> This works fine in hibernate-3.1.2.
> This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881
> Please let me know if more info or a test case is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740?page=c... ]
Frank Grimes commented on HHH-1740:
-----------------------------------
Just for completeness, I also ran with the latest from SVN BRANCH_3_2 and encountered exactly the same issues as with TRUNK...
> Build-time instrumentation breaks lazy="proxy"
> ----------------------------------------------
>
> Key: HHH-1740
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1740
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2
> Reporter: Frank Grimes
> Assignee: Steve Ebersole
> Priority: Critical
> Fix For: 3.2.0.ga
> Attachments: 312Document.class, Document.class, HHH-1740.diff
>
>
> I have a mapping that contains a many-to-one lazy="proxy".
> This alone works fine: I see $$EnhancerByCGLIB$$ as the type when I do a load
> Once I add a lazy property to the mapping and do build-time cglib enhancement, it breaks.
> Not only is the lazy property listed in $CGLIB_READ_WRITE_CALLBACK, but also my lazy="proxy" association. (i.e. no more proxy object)
> This works fine in hibernate-3.1.2.
> This was originally brought up here: http://forums.hibernate.org/viewtopic.php?t=958881
> Please let me know if more info or a test case is needed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira