hibernate-issues

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-147) Caching of Configuration

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Gavin King
    Created: Fri, 20 Jun 2003 10:11 PM
       Body:
I like this idea. I don't think its hard to make Configuration be serializa=
ble.

However, note that there is additional work done in buildSessionFactory(), =
so you could not completely defray the startup cost.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-147


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-147
    Summary: Caching of Configuration
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components:=20
             core

   Assignee:=20
   Reporter: Thorsten Sch=C3=A4fer

    Created: Fri, 20 Jun 2003 8:12 AM
    Updated: Fri, 20 Jun 2003 8:12 AM
Environment: Client applications

Description:
If you use hibernate in a client application, you first have to create a co=
nfiguration. This can take a lot of time (I have four classes and it can ta=
ke up to 30 seconds), because XML processing is quite slow. For small appli=
cations this could be too much.
To solve this problem it would be fine if the created configuration is auto=
matically saved to a file. For the next start, the configuration should loo=
k if a persisted configuration exist and load this instead of parsing the X=
ML mappings again. If such a pre-initialized configuration does not exist, =
the normal approach is taken.

Thorsten


---------------------------------------------------------------------
JIRA INFORMATION:
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/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-147) Caching of Configuration

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Douglas Granzotto
    Created: Wed, 10 Mar 2004 4:31 PM
       Body:
The time to start this type of application,
impedes the use of hibernate in my company.

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?=
key=3DHB-147


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-147
    Summary: Caching of Configuration
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components:=20
             core

   Assignee:=20
   Reporter: Thorsten Sch=C3=A4fer

    Created: Fri, 20 Jun 2003 8:12 AM
    Updated: Wed, 10 Mar 2004 4:31 PM
Environment: Client applications

Description:
If you use hibernate in a client application, you first have to create a co=
nfiguration. This can take a lot of time (I have four classes and it can ta=
ke up to 30 seconds), because XML processing is quite slow. For small appli=
cations this could be too much.
To solve this problem it would be fine if the created configuration is auto=
matically saved to a file. For the next start, the configuration should loo=
k if a persisted configuration exist and load this instead of parsing the X=
ML mappings again. If such a pre-initialized configuration does not exist, =
the normal approach is taken.

Thorsten


---------------------------------------------------------------------
JIRA INFORMATION:
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=
.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-147) Caching of Configuration

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Luis Miguel Hernanz
    Created: Tue, 4 May 2004 5:43 AM
       Body:
Please, see my comments and patch (hibernate.patch) in the bug 492.
---------------------------------------------------------------------
View this comment:
  http://opensource.atlassian.com/projects/hibernate/browse/HB-147?page=3Dc=
omments#action_13059

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/hibernate/browse/HB-147

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-147
    Summary: Caching of Configuration
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components:=20
             core

   Assignee:=20
   Reporter: Thorsten Sch=C3=A4fer

    Created: Fri, 20 Jun 2003 8:12 AM
    Updated: Tue, 4 May 2004 5:43 AM
Environment: Client applications

Description:
If you use hibernate in a client application, you first have to create a co=
nfiguration. This can take a lot of time (I have four classes and it can ta=
ke up to 30 seconds), because XML processing is quite slow. For small appli=
cations this could be too much.
To solve this problem it would be fine if the created configuration is auto=
matically saved to a file. For the next start, the configuration should loo=
k if a persisted configuration exist and load this instead of parsing the X=
ML mappings again. If such a pre-initialized configuration does not exist, =
the normal approach is taken.

Thorsten


---------------------------------------------------------------------
JIRA INFORMATION:
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=
.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-147) Caching of Configuration

[<leg...@at...>]

The following comment has been added to this issue:

     Author: Damien Bonvillain
    Created: Mon, 13 Dec 2004 7:35 AM
       Body:
Can we get rid of all those "this is done in H3"? If we report bugs on H2, =
that is because most of us can't upgrade (cost, time, proofs and so on). Or=
 at least be honest, don't put the resolution to 'Duplicate' but to 'Won't =
fix it'.
---------------------------------------------------------------------
View this comment:
  http://opensource.atlassian.com/projects/hibernate/browse/HB-147?page=3Dc=
omments#action_15173

---------------------------------------------------------------------
View the issue:
  http://opensource.atlassian.com/projects/hibernate/browse/HB-147

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-147
    Summary: Caching of Configuration
       Type: Improvement

     Status: Closed
   Priority: Minor
 Resolution: DUPLICATE

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: Hibernate2
 Components:=20
             core

   Assignee:=20
   Reporter: Thorsten Sch=C3=A4fer

    Created: Fri, 20 Jun 2003 8:12 AM
    Updated: Mon, 13 Dec 2004 7:35 AM
Environment: Client applications

Description:
If you use hibernate in a client application, you first have to create a co=
nfiguration. This can take a lot of time (I have four classes and it can ta=
ke up to 30 seconds), because XML processing is quite slow. For small appli=
cations this could be too much.
To solve this problem it would be fine if the created configuration is auto=
matically saved to a file. For the next start, the configuration should loo=
k if a persisted configuration exist and load this instead of parsing the X=
ML mappings again. If such a pre-initialized configuration does not exist, =
the normal approach is taken.

Thorsten


---------------------------------------------------------------------
JIRA INFORMATION:
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=
.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira