June 2009 - hibernate-commits - Jboss List Archives

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-23 02:03:55 -0400 (Tue, 23 Jun 2009) New Revision: 16883 Removed: hibernate-jdocbook-xslt/ Log: consolidated with hibernate-jdocbook-style

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16882 - hibernate-jdocbook-style.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-23 02:03:16 -0400 (Tue, 23 Jun 2009) New Revision: 16882 Added: hibernate-jdocbook-style/tags/ Log:

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16881 - hibernate-jdocbook-style/trunk.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-23 02:00:00 -0400 (Tue, 23 Jun 2009) New Revision: 16881 Modified: hibernate-jdocbook-style/trunk/pom.xml Log: [maven-release-plugin] prepare release hibernate-jdocbook-style-2.0.0 Modified: hibernate-jdocbook-style/trunk/pom.xml =================================================================== --- hibernate-jdocbook-style/trunk/pom.xml 2009-06-23 05:58:29 UTC (rev 16880) +++ hibernate-jdocbook-style/trunk/pom.xml 2009-06-23 06:00:00 UTC (rev 16881) @@ -1,34 +1,11 @@ - -<project xmlns="http://maven.apache.org/POM/4.0.0" - xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> +<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>org.hibernate</groupId> <artifactId>hibernate-jdocbook-style</artifactId> <packaging>jdocbook-style</packaging> - <version>2.0.0-SNAPSHOT</version> + <version>2.0.0</version> <name>Hibernate jDocBook Style Bundle</name> <description> @@ -73,10 +50,9 @@ </licenses> <scm> - <connection>scm:svn:http://anonsvn.jboss.org/repos/hibernate/hibernate-jdocbook-style...</connection> - <developerConnection>scm:svn:https://svn.jboss.org/repos/hibernate/hibernate-jdocbook-style/trunk - </developerConnection> - <url>http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/hibernate-jdocbook-s...</url> + <connection>scm:svn:http://anonsvn.jboss.org/repos/hibernate/hibernate-jdocbook-style...</connection> + <developerConnection>scm:svn:https://svn.jboss.org/repos/hibernate/hibernate-jdocbook-style/ta...</developerConnection> + <url>http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/hibernate-jdocbook-s...</url> </scm> <dependencies> @@ -142,4 +118,4 @@ </snapshotRepository> </distributionManagement> -</project> +</project> \ No newline at end of file

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16880 - hibernate-jdocbook-style/trunk.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-23 01:58:29 -0400 (Tue, 23 Jun 2009) New Revision: 16880 Modified: hibernate-jdocbook-style/trunk/pom.xml Log: consolidate style+xslt into just style & prep for 2.0.0 release Modified: hibernate-jdocbook-style/trunk/pom.xml =================================================================== --- hibernate-jdocbook-style/trunk/pom.xml 2009-06-23 05:54:56 UTC (rev 16879) +++ hibernate-jdocbook-style/trunk/pom.xml 2009-06-23 05:58:29 UTC (rev 16880) @@ -121,7 +121,7 @@ <plugin> <groupId>org.jboss.maven.plugins</groupId> <artifactId>maven-jdocbook-style-plugin</artifactId> - <version>1.0.1-SNAPSHOT</version> + <version>2.0.0</version> <extensions>true</extensions> </plugin> </plugins>

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16879 - in hibernate-jdocbook-style/trunk: src/main and 5 other directories.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-23 01:54:56 -0400 (Tue, 23 Jun 2009) New Revision: 16879 Added: hibernate-jdocbook-style/trunk/src/main/xslt/ hibernate-jdocbook-style/trunk/src/main/xslt/org/ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/common.xsl hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/eclipse.xsl hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/fop1.xsl hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/pdf.xsl hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-common.xsl hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-single.xsl hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml.xsl Modified: hibernate-jdocbook-style/trunk/pom.xml Log: consolidate style+xslt into just style & prep for 2.0.0 release Modified: hibernate-jdocbook-style/trunk/pom.xml =================================================================== --- hibernate-jdocbook-style/trunk/pom.xml 2009-06-23 05:46:34 UTC (rev 16878) +++ hibernate-jdocbook-style/trunk/pom.xml 2009-06-23 05:54:56 UTC (rev 16879) @@ -1,16 +1,39 @@ -<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> + +<project xmlns="http://maven.apache.org/POM/4.0.0" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> - <modelVersion>4.0.0</modelVersion> + <modelVersion>4.0.0</modelVersion> - <groupId>org.hibernate</groupId> - <artifactId>hibernate-jdocbook-style</artifactId> - <packaging>jdocbook-style</packaging> - <version>2.0.0-SNAPSHOT</version> + <groupId>org.hibernate</groupId> + <artifactId>hibernate-jdocbook-style</artifactId> + <packaging>jdocbook-style</packaging> + <version>2.0.0-SNAPSHOT</version> - <name>Hibernate jDocBook Style Bundle</name> - <description> + <name>Hibernate jDocBook Style Bundle</name> + <description> The jDocBook style bundle for the Hibernate reference documentation. - </description> + </description> <url>http://hibernate.org</url> <organization> @@ -56,39 +79,67 @@ <url>http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/hibernate-jdocbook-s...</url> </scm> - <build> - <extensions> - <extension> - <groupId>org.apache.maven.wagon</groupId> - <artifactId>wagon-webdav</artifactId> - <version>1.0-beta-2</version> - </extension> - </extensions> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-style-plugin</artifactId> + <dependencies> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-jdocbook-style</artifactId> + <version>1.1.0</version> + <type>jdocbook-style</type> + <exclusions> + <exclusion> + <groupId>org.eclipse.wst.css</groupId> + <artifactId>core</artifactId> + </exclusion> + <exclusion> + <groupId>org.eclipse.wst.sse</groupId> + <artifactId>core</artifactId> + </exclusion> + </exclusions> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-docbook-xslt</artifactId> + <version>1.1.0</version> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-fonts</artifactId> + <type>jdocbook-style</type> <version>1.0.0</version> - <extensions>true</extensions> - </plugin> - </plugins> - </build> + </dependency> + </dependencies> - <distributionManagement> - <repository> -  -  -  - <id>repository.jboss.org</id> - <url>file://${maven.repository.root}</url> - </repository> - <snapshotRepository> - <id>snapshots.jboss.org</id> - <name>JBoss Snapshot Repository</name> - <url>dav:https://snapshots.jboss.org/maven2</url> - </snapshotRepository> - </distributionManagement> + <build> + <extensions> + <extension> + <groupId>org.apache.maven.wagon</groupId> + <artifactId>wagon-webdav</artifactId> + <version>1.0-beta-2</version> + </extension> + </extensions> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-style-plugin</artifactId> + <version>1.0.1-SNAPSHOT</version> + <extensions>true</extensions> + </plugin> + </plugins> + </build> + <distributionManagement> + <repository> +  +  +  + <id>repository.jboss.org</id> + <url>file://${maven.repository.root}</url> + </repository> + <snapshotRepository> + <id>snapshots.jboss.org</id> + <name>JBoss Snapshot Repository</name> + <url>dav:https://snapshots.jboss.org/maven2</url> + </snapshotRepository> + </distributionManagement> - </project> Added: hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/common.xsl =================================================================== --- hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/common.xsl (rev 0) +++ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/common.xsl 2009-06-23 05:54:56 UTC (rev 16879) @@ -0,0 +1,49 @@ +<?xml version="1.0"?> + + + +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> + +  + + <xsl:param name="use.simplified.author.group" select="1"/> + + <xsl:param name="callout.graphics.path"> + <xsl:if test="$img.src.path != ''"> + <xsl:value-of select="$img.src.path"/> + </xsl:if> + <xsl:text>images/org/hibernate/docbook/callouts/</xsl:text> + </xsl:param> + + <xsl:param name="admon.graphics.path"> + <xsl:if test="$img.src.path != ''"> + <xsl:value-of select="$img.src.path"/> + </xsl:if> + <xsl:text>images/org/hibernate/docbook/</xsl:text> + </xsl:param> + +</xsl:stylesheet> + Added: hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/eclipse.xsl =================================================================== --- hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/eclipse.xsl (rev 0) +++ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/eclipse.xsl 2009-06-23 05:54:56 UTC (rev 16879) @@ -0,0 +1,43 @@ +<?xml version='1.0'?> + + + +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> + +  + + <xsl:import href="classpath:/xslt/org/jboss/eclipse.xsl"/> + <xsl:import href="common.xsl"/> + <xsl:import href="xhtml-common.xsl"/> + + <xsl:param name="html.stylesheet" select="'css/hibernate-eclipse.css'"/> + + <xsl:param name="eclipse.plugin.name">Hibernate Help</xsl:param> + <xsl:param name="eclipse.plugin.id">org.hibernate.help</xsl:param> + <xsl:param name="eclipse.plugin.provider">Hibernate.org</xsl:param> + +</xsl:stylesheet> + Added: hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/fop1.xsl =================================================================== --- hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/fop1.xsl (rev 0) +++ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/fop1.xsl 2009-06-23 05:54:56 UTC (rev 16879) @@ -0,0 +1,100 @@ +<?xml version='1.0'?> + + + +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" + xmlns:fo="http://www.w3.org/1999/XSL/Format" + version='1.0'> + +  + + <xsl:template match="*" mode="fop1.outline"> + <xsl:apply-templates select="*" mode="fop1.outline"/> + </xsl:template> + + <xsl:template match="set|book|part|reference| + preface|chapter|appendix|article + |glossary|bibliography|index|setindex + |refentry + |sect1|sect2|sect3|sect4|sect5|section" + mode="fop1.outline"> + + <xsl:variable name="id"> + <xsl:call-template name="object.id"/> + </xsl:variable> + <xsl:variable name="bookmark-label"> + <xsl:apply-templates select="." mode="object.title.markup"/> + </xsl:variable> + +  +  + + <xsl:choose> + <xsl:when test="parent::*"> + <fo:bookmark internal-destination="{$id}" starting-state="hide"> + <fo:bookmark-title> + <xsl:value-of select="normalize-space(translate($bookmark-label, $a-dia, $a-asc))"/> + </fo:bookmark-title> + <xsl:apply-templates select="*" mode="fop1.outline"/> + </fo:bookmark> + </xsl:when> + <xsl:otherwise> + <fo:bookmark internal-destination="{$id}" starting-state="hide"> + <fo:bookmark-title> + <xsl:value-of select="normalize-space(translate($bookmark-label, $a-dia, $a-asc))"/> + </fo:bookmark-title> + </fo:bookmark> + + <xsl:variable name="toc.params"> + <xsl:call-template name="find.path.params"> + <xsl:with-param name="table" select="normalize-space($generate.toc)"/> + </xsl:call-template> + </xsl:variable> + + <xsl:if test="contains($toc.params, 'toc') + and (book|part|reference|preface|chapter|appendix|article + |glossary|bibliography|index|setindex + |refentry + |sect1|sect2|sect3|sect4|sect5|section)"> + <fo:bookmark internal-destination="toc...{$id}" starting-state="hide"> + <fo:bookmark-title> + <xsl:call-template name="gentext"> + <xsl:with-param name="key" select="'TableofContents'"/> + </xsl:call-template> + </fo:bookmark-title> + </fo:bookmark> + </xsl:if> + <xsl:apply-templates select="*" mode="fop1.outline"/> + </xsl:otherwise> + </xsl:choose> +  + </xsl:template> + + +</xsl:stylesheet> + Added: hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/pdf.xsl =================================================================== --- hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/pdf.xsl (rev 0) +++ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/pdf.xsl 2009-06-23 05:54:56 UTC (rev 16879) @@ -0,0 +1,133 @@ +<?xml version='1.0'?> + + + +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" + version="1.0" + xmlns="http://www.w3.org/TR/xhtml1/transitional" + xmlns:fo="http://www.w3.org/1999/XSL/Format" + exclude-result-prefixes="#default"> + +  + + <xsl:import href="classpath:/xslt/org/jboss/pdf.xsl"/> + <xsl:import href="common.xsl"/> + <xsl:import href="fop1.xsl" /> + + <xsl:import href="classpath:/xslt/org/jboss/xslt/fonts/pdf/fonts.xsl" /> + + <xsl:param name="title.font.family"> + <xsl:variable name="font"> + <xsl:call-template name="pickfont-sans"/> + </xsl:variable> + <xsl:message> + <xsl:text>Setting 'title.font.family' param =</xsl:text><xsl:copy-of select="$font"/> + </xsl:message> + <xsl:copy-of select="$font"/> + </xsl:param> + + <xsl:param name="body.font.family"> + <xsl:variable name="font"> + <xsl:call-template name="pickfont-sans"/> + </xsl:variable> + <xsl:message> + <xsl:text>Setting 'body.font.family' param =</xsl:text><xsl:copy-of select="$font"/> + </xsl:message> + <xsl:copy-of select="$font"/> + </xsl:param> + + <xsl:param name="monospace.font.family"> + <xsl:variable name="font"> + <xsl:call-template name="pickfont-mono"/> + </xsl:variable> + <xsl:message> + <xsl:text>Setting 'monospace.font.family' param =</xsl:text><xsl:copy-of select="$font"/> + </xsl:message> + <xsl:copy-of select="$font"/> + </xsl:param> + + <xsl:param name="sans.font.family"> + <xsl:variable name="font"> + <xsl:call-template name="pickfont-sans"/> + </xsl:variable> + <xsl:message> + <xsl:text>Setting 'sans.font.family' param =</xsl:text><xsl:copy-of select="$font"/> + </xsl:message> + <xsl:copy-of select="$font"/> + </xsl:param> + +  + <xsl:param name="title.color">#4a5d75</xsl:param> + <xsl:param name="titlepage.color">#4a5d75</xsl:param> + <xsl:param name="chapter.title.color">#4a5d75</xsl:param> + <xsl:param name="section.title.color">#4a5d75</xsl:param> + +  + + <xsl:template name="table.cell.block.properties"> +  + <xsl:if test="ancestor::thead or ancestor::tfoot"> + <xsl:attribute name="font-weight">bold</xsl:attribute> + <xsl:attribute name="background-color">#EDE8DB</xsl:attribute> + <xsl:attribute name="color">black</xsl:attribute> + </xsl:if> + </xsl:template> + +  +  + <xsl:template name="table.row.properties"> + <xsl:variable name="bgcolor"> + <xsl:call-template name="dbfo-attribute"> + <xsl:with-param name="pis" select="processing-instruction('dbfo')" /> + <xsl:with-param name="attribute" select="'bgcolor'" /> + </xsl:call-template> + </xsl:variable> + <xsl:if test="$bgcolor != ''"> + <xsl:attribute name="background-color"> + <xsl:value-of select="$bgcolor" /> + </xsl:attribute> + </xsl:if> + <xsl:if test="ancestor::thead or ancestor::tfoot"> + <xsl:attribute name="background-color">#EDE8DB</xsl:attribute> + </xsl:if> + </xsl:template> + +</xsl:stylesheet> + Added: hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-common.xsl =================================================================== --- hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-common.xsl (rev 0) +++ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-common.xsl 2009-06-23 05:54:56 UTC (rev 16879) @@ -0,0 +1,58 @@ +<?xml version="1.0"?> + + +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> + + <xsl:param name="siteHref" select="'http://www.hibernate.org'"/> + <xsl:param name="docHref" select="'http://hibernate.org/Documentation/DocumentationOverview'"/> + <xsl:param name="siteLinkText" select="'Hibernate.org'"/> + + <xsl:param name="legalnotice.filename">legalnotice.html</xsl:param> + + <xsl:template match="legalnotice" mode="chunk-filename"> + <xsl:value-of select="$legalnotice.filename"/> + </xsl:template> + + <xsl:template name="user.footer.content"> + <HR/> + <a> + <xsl:attribute name="href"> + <xsl:apply-templates select="//legalnotice[1]" mode="chunk-filename"/> + </xsl:attribute> + <xsl:choose> + <xsl:when test="//book/bookinfo/copyright[1]"> + <xsl:apply-templates select="//book/bookinfo/copyright[1]" mode="titlepage.mode"/> + </xsl:when> + <xsl:when test="//legalnotice[1]"> + <xsl:apply-templates select="//legalnotice[1]" mode="titlepage.mode"/> + </xsl:when> + </xsl:choose> + </a> + </xsl:template> + +</xsl:stylesheet> Added: hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-single.xsl =================================================================== --- hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-single.xsl (rev 0) +++ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml-single.xsl 2009-06-23 05:54:56 UTC (rev 16879) @@ -0,0 +1,39 @@ +<?xml version='1.0'?> + + + +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> + +  + + <xsl:import href="classpath:/xslt/org/jboss/xhtml-single.xsl"/> + <xsl:import href="common.xsl"/> + <xsl:import href="xhtml-common.xsl"/> + + <xsl:param name="html.stylesheet" select="'css/hibernate-single.css'"/> + +</xsl:stylesheet> + Added: hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml.xsl =================================================================== --- hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml.xsl (rev 0) +++ hibernate-jdocbook-style/trunk/src/main/xslt/org/hibernate/jdocbook/xslt/xhtml.xsl 2009-06-23 05:54:56 UTC (rev 16879) @@ -0,0 +1,39 @@ +<?xml version='1.0'?> + + + +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0"> + +  + + <xsl:import href="classpath:/xslt/org/jboss/xhtml.xsl"/> + <xsl:import href="common.xsl"/> + <xsl:import href="xhtml-common.xsl"/> + + <xsl:param name="html.stylesheet" select="'css/hibernate.css'"/> + +</xsl:stylesheet> +

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16878 - in core/branches/Branch_3_3/documentation/manual/src/main/docbook: es-ES/content and 5 other directories.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-23 01:46:34 -0400 (Tue, 23 Jun 2009) New Revision: 16878 Added: core/branches/Branch_3_3/documentation/manual/src/main/docbook/es-ES/content/portability.po core/branches/Branch_3_3/documentation/manual/src/main/docbook/fr-FR/content/portability.po core/branches/Branch_3_3/documentation/manual/src/main/docbook/ja-JP/content/portability.po core/branches/Branch_3_3/documentation/manual/src/main/docbook/ko-KR/content/portability.po core/branches/Branch_3_3/documentation/manual/src/main/docbook/pt-BR/content/portability.po core/branches/Branch_3_3/documentation/manual/src/main/docbook/zh-CN/content/portability.po Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/en-US/content/portability.xml Log: HHH-3944 - Document known database portability strategies Modified: core/branches/Branch_3_3/documentation/manual/src/main/docbook/en-US/content/portability.xml =================================================================== --- core/branches/Branch_3_3/documentation/manual/src/main/docbook/en-US/content/portability.xml 2009-06-23 05:46:17 UTC (rev 16877) +++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/en-US/content/portability.xml 2009-06-23 05:46:34 UTC (rev 16878) @@ -90,7 +90,7 @@ database is recognized; etc. To register one or more resolvers, simply specify them (seperated by commas, tabs or spaces) using the 'hibernate.dialect_resolvers' configuration setting (see the <constant>DIALECT_RESOLVERS</constant> constant on - <ooclass><package>org.hibernate.cfg</package><classname>Environment</classname></ooclass>). + <classname>org.hibernate.cfg.Environment</classname>). </para> </sect1> Added: core/branches/Branch_3_3/documentation/manual/src/main/docbook/es-ES/content/portability.po =================================================================== --- core/branches/Branch_3_3/documentation/manual/src/main/docbook/es-ES/content/portability.po (rev 0) +++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/es-ES/content/portability.po 2009-06-23 05:46:34 UTC (rev 16878) @@ -0,0 +1,234 @@ +# Language es-ES translations for Branch package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Branch 3_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-06-16 18:47+0000\n" +"PO-Revision-Date: 2009-06-16 18:47+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: portability.xml:26 +#, no-c-format +msgid "Database Portability Considerations" +msgstr "" + +#. Tag: title +#: portability.xml:29 +#, no-c-format +msgid "Portability Basics" +msgstr "" + +#. Tag: para +#: portability.xml:31 +#, no-c-format +msgid "" +"One of the selling points of Hibernate (and really Object/Relational Mapping " +"as a whole) is the notion of database portability. This could mean an " +"internal IT user migrating from one database vendor to another, or it could " +"mean a framework or deployable application consuming Hibernate to " +"simultaneously target multiple database products by their users. Regardless " +"of the exact scenario, the basic idea is that you want Hibernate to help you " +"run against any number of databases without changes to your code, and " +"ideally without any changes to the mapping metadata." +msgstr "" + +#. Tag: title +#: portability.xml:42 +#, no-c-format +msgid "Dialect" +msgstr "" + +#. Tag: para +#: portability.xml:44 +#, no-c-format +msgid "" +"The first line of portability for Hibernate is the dialect, which is a " +"specialization of the <classname>org.hibernate.dialect.Dialect</classname> " +"contract. A dialect encapsulates all the differences in how Hibernate must " +"communicate with a particular database to accomplish some task like getting " +"a sequence value or structuring a SELECT query. Hibernate bundles a wide " +"range of dialects for many of the most popular databases. If you find that " +"your particular database is not among them, it is not terribly difficult to " +"write your own." +msgstr "" + +#. Tag: title +#: portability.xml:55 +#, no-c-format +msgid "Dialect resolution" +msgstr "" + +#. Tag: para +#: portability.xml:57 +#, no-c-format +msgid "" +"Originally, Hibernate would always require that users specify which dialect " +"to use. In the case of users looking to simultaneously target multiple " +"databases with their build that was problematic. Generally this required " +"their users to configure the Hibernate dialect or defining their own method " +"of setting that value." +msgstr "" + +#. Tag: para +#: portability.xml:64 +#, no-c-format +msgid "" +"Starting with version 3.2, Hibernate introduced the notion of automatically " +"detecting the dialect to use based on the <interfacename>java.sql." +"DatabaseMetaData</interfacename> obtained from a <interfacename>java.sql." +"Connection</interfacename> to that database. This was much better, expect " +"that this resolution was limited to databases Hibernate know about ahead of " +"time and was in no way configurable or overrideable." +msgstr "" + +#. Tag: para +#: portability.xml:72 +#, no-c-format +msgid "" +"Starting with version 3.3, Hibernate has a fare more powerful way to " +"automatically determine which dialect to should be used by relying on a " +"series of delegates which implement the <interfacename>org.hibernate.dialect." +"resolver.DialectResolver</interfacename> which defines only a single method:" +"<programlisting><![CDATA[public Dialect resolveDialect(DatabaseMetaData " +"metaData) throws JDBCConnectionException]]></programlisting>. The basic " +"contract here is that if the resolver 'understands' the given database " +"metadata then it returns the corresponding Dialect; if not it returns null " +"and the process continues to the next resolver. The signature also " +"identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</" +"exceptionname> as possibly being thrown. A JDBCConnectionException here is " +"interpreted to imply a \"non transient\" (aka non-recoverable) connection " +"problem and is used to indicate an immediate stop to resolution attempts. " +"All other exceptions result in a warning and continuing on to the next " +"resolver." +msgstr "" + +#. Tag: para +#: portability.xml:85 +#, no-c-format +msgid "" +"The cool part about these resolvers is that users can also register their " +"own custom resolvers which will be processed ahead of the built-in Hibernate " +"ones. This might be useful in a number of different situations: it allows " +"easy integration for auto-detection of dialects beyond those shipped with " +"HIbernate itself; it allows you to specify to use a custom dialect when a " +"particular database is recognized; etc. To register one or more resolvers, " +"simply specify them (seperated by commas, tabs or spaces) using the " +"'hibernate.dialect_resolvers' configuration setting (see the " +"<constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate." +"cfgEnvironment</classname>)." +msgstr "" + +#. Tag: title +#: portability.xml:98 +#, no-c-format +msgid "Identifier generation" +msgstr "" + +#. Tag: para +#: portability.xml:100 +#, no-c-format +msgid "" +"When considering portability between databases, another important decision " +"is selecting the identifier generation stratagy you want to use. Originally " +"Hibernate provided the <emphasis>native</emphasis> generator for this " +"purpose, which was intended to select between a <emphasis>sequence</" +"emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> " +"strategy depending on the capability of the underlying database. However, an " +"insidious implication of this approach comes about when targtetting some " +"databases which support <emphasis>identity</emphasis> generation and some " +"which do not. <emphasis>identity</emphasis> generation relies on the SQL " +"definition of an IDENTITY (or auto-increment) column to manage the " +"identifier value; it is what is known as a post-insert generation strategy " +"becauase the insert must actually happen before we can know the identifier " +"value. Because Hibernate relies on this identifier value to uniquely " +"reference entities within a persistence context it must then issue the " +"insert immediately when the users requests the entitiy be associated with " +"the session (like via save() e.g.) regardless of current transactional " +"semantics. <note> <para> Hibernate was changed slightly once the implication " +"of this was better understood so that the insert is delayed in cases where " +"that is feasible. </para> </note> The underlying issue is that the actual " +"semanctics of the application itself changes in these cases." +msgstr "" + +#. Tag: para +#: portability.xml:125 +#, no-c-format +msgid "" +"Starting with version 3.2.3, Hibernate comes with a set of <ulink url=" +"\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators " +"targetting portability in a much different way. <note> <para> There are " +"specifically 2 bundled <emphasis>enhanced</emphasis>generators: " +"<itemizedlist> <listitem> <para> <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> </para> </listitem> <listitem> <para> " +"<classname>org.hibernate.id.enhanced.TableGenerator</classname> </para> </" +"listitem> </itemizedlist> </para> </note> The idea behind these generators " +"is to port the actual semantics of the identifer value generation to the " +"different databases. For example, the <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> mimics the behavior of a sequence on " +"databases which do not support sequences by using a table." +msgstr "" + +#. Tag: title +#: portability.xml:154 +#, no-c-format +msgid "Database functions" +msgstr "" + +#. Tag: para +#: portability.xml:157 +#, no-c-format +msgid "" +"This is an area in Hibernate in need of improvement. In terms of portability " +"concerns, this function handling currently works pretty well from HQL; " +"however, it is quite lacking in all other aspects." +msgstr "" + +#. Tag: para +#: portability.xml:164 +#, no-c-format +msgid "" +"SQL functions can be referenced in many ways by users. However, not all " +"databases support the same set of functions. Hibernate, provides a means of " +"mapping a <emphasis>logical</emphasis> function name to a a delegate which " +"knows how to render that particular function, perhaps even using a totally " +"different physical function call." +msgstr "" + +#. Tag: para +#: portability.xml:170 +#, no-c-format +msgid "" +"Technically this function registration is handled through the <classname>org." +"hibernate.dialect.function.SQLFunctionRegistry</classname> class which is " +"intended to allow users to provide custom function definitions without " +"having to provide a custom dialect. This specific behavior is not fully " +"completed as of yet." +msgstr "" + +#. Tag: para +#: portability.xml:177 +#, no-c-format +msgid "" +"It is sort of implemented such that users can programatically register " +"functions with the <classname>org.hibernate.cfg.Configuration</classname> " +"and those functions will be recognized for HQL." +msgstr "" + +#. Tag: title +#: portability.xml:187 +#, no-c-format +msgid "Type mappings" +msgstr "" + +#. Tag: para +#: portability.xml:189 +#, no-c-format +msgid "This section scheduled for completion at a later date..." +msgstr "" Added: core/branches/Branch_3_3/documentation/manual/src/main/docbook/fr-FR/content/portability.po =================================================================== --- core/branches/Branch_3_3/documentation/manual/src/main/docbook/fr-FR/content/portability.po (rev 0) +++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/fr-FR/content/portability.po 2009-06-23 05:46:34 UTC (rev 16878) @@ -0,0 +1,234 @@ +# Language fr-FR translations for Branch package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Branch 3_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-06-16 18:47+0000\n" +"PO-Revision-Date: 2009-06-10 21:02+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: portability.xml:26 +#, no-c-format +msgid "Database Portability Considerations" +msgstr "" + +#. Tag: title +#: portability.xml:29 +#, no-c-format +msgid "Portability Basics" +msgstr "" + +#. Tag: para +#: portability.xml:31 +#, no-c-format +msgid "" +"One of the selling points of Hibernate (and really Object/Relational Mapping " +"as a whole) is the notion of database portability. This could mean an " +"internal IT user migrating from one database vendor to another, or it could " +"mean a framework or deployable application consuming Hibernate to " +"simultaneously target multiple database products by their users. Regardless " +"of the exact scenario, the basic idea is that you want Hibernate to help you " +"run against any number of databases without changes to your code, and " +"ideally without any changes to the mapping metadata." +msgstr "" + +#. Tag: title +#: portability.xml:42 +#, no-c-format +msgid "Dialect" +msgstr "" + +#. Tag: para +#: portability.xml:44 +#, no-c-format +msgid "" +"The first line of portability for Hibernate is the dialect, which is a " +"specialization of the <classname>org.hibernate.dialect.Dialect</classname> " +"contract. A dialect encapsulates all the differences in how Hibernate must " +"communicate with a particular database to accomplish some task like getting " +"a sequence value or structuring a SELECT query. Hibernate bundles a wide " +"range of dialects for many of the most popular databases. If you find that " +"your particular database is not among them, it is not terribly difficult to " +"write your own." +msgstr "" + +#. Tag: title +#: portability.xml:55 +#, no-c-format +msgid "Dialect resolution" +msgstr "" + +#. Tag: para +#: portability.xml:57 +#, no-c-format +msgid "" +"Originally, Hibernate would always require that users specify which dialect " +"to use. In the case of users looking to simultaneously target multiple " +"databases with their build that was problematic. Generally this required " +"their users to configure the Hibernate dialect or defining their own method " +"of setting that value." +msgstr "" + +#. Tag: para +#: portability.xml:64 +#, no-c-format +msgid "" +"Starting with version 3.2, Hibernate introduced the notion of automatically " +"detecting the dialect to use based on the <interfacename>java.sql." +"DatabaseMetaData</interfacename> obtained from a <interfacename>java.sql." +"Connection</interfacename> to that database. This was much better, expect " +"that this resolution was limited to databases Hibernate know about ahead of " +"time and was in no way configurable or overrideable." +msgstr "" + +#. Tag: para +#: portability.xml:72 +#, no-c-format +msgid "" +"Starting with version 3.3, Hibernate has a fare more powerful way to " +"automatically determine which dialect to should be used by relying on a " +"series of delegates which implement the <interfacename>org.hibernate.dialect." +"resolver.DialectResolver</interfacename> which defines only a single method:" +"<programlisting><![CDATA[public Dialect resolveDialect(DatabaseMetaData " +"metaData) throws JDBCConnectionException]]></programlisting>. The basic " +"contract here is that if the resolver 'understands' the given database " +"metadata then it returns the corresponding Dialect; if not it returns null " +"and the process continues to the next resolver. The signature also " +"identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</" +"exceptionname> as possibly being thrown. A JDBCConnectionException here is " +"interpreted to imply a \"non transient\" (aka non-recoverable) connection " +"problem and is used to indicate an immediate stop to resolution attempts. " +"All other exceptions result in a warning and continuing on to the next " +"resolver." +msgstr "" + +#. Tag: para +#: portability.xml:85 +#, no-c-format +msgid "" +"The cool part about these resolvers is that users can also register their " +"own custom resolvers which will be processed ahead of the built-in Hibernate " +"ones. This might be useful in a number of different situations: it allows " +"easy integration for auto-detection of dialects beyond those shipped with " +"HIbernate itself; it allows you to specify to use a custom dialect when a " +"particular database is recognized; etc. To register one or more resolvers, " +"simply specify them (seperated by commas, tabs or spaces) using the " +"'hibernate.dialect_resolvers' configuration setting (see the " +"<constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate." +"cfgEnvironment</classname>)." +msgstr "" + +#. Tag: title +#: portability.xml:98 +#, no-c-format +msgid "Identifier generation" +msgstr "" + +#. Tag: para +#: portability.xml:100 +#, no-c-format +msgid "" +"When considering portability between databases, another important decision " +"is selecting the identifier generation stratagy you want to use. Originally " +"Hibernate provided the <emphasis>native</emphasis> generator for this " +"purpose, which was intended to select between a <emphasis>sequence</" +"emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> " +"strategy depending on the capability of the underlying database. However, an " +"insidious implication of this approach comes about when targtetting some " +"databases which support <emphasis>identity</emphasis> generation and some " +"which do not. <emphasis>identity</emphasis> generation relies on the SQL " +"definition of an IDENTITY (or auto-increment) column to manage the " +"identifier value; it is what is known as a post-insert generation strategy " +"becauase the insert must actually happen before we can know the identifier " +"value. Because Hibernate relies on this identifier value to uniquely " +"reference entities within a persistence context it must then issue the " +"insert immediately when the users requests the entitiy be associated with " +"the session (like via save() e.g.) regardless of current transactional " +"semantics. <note> <para> Hibernate was changed slightly once the implication " +"of this was better understood so that the insert is delayed in cases where " +"that is feasible. </para> </note> The underlying issue is that the actual " +"semanctics of the application itself changes in these cases." +msgstr "" + +#. Tag: para +#: portability.xml:125 +#, no-c-format +msgid "" +"Starting with version 3.2.3, Hibernate comes with a set of <ulink url=" +"\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators " +"targetting portability in a much different way. <note> <para> There are " +"specifically 2 bundled <emphasis>enhanced</emphasis>generators: " +"<itemizedlist> <listitem> <para> <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> </para> </listitem> <listitem> <para> " +"<classname>org.hibernate.id.enhanced.TableGenerator</classname> </para> </" +"listitem> </itemizedlist> </para> </note> The idea behind these generators " +"is to port the actual semantics of the identifer value generation to the " +"different databases. For example, the <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> mimics the behavior of a sequence on " +"databases which do not support sequences by using a table." +msgstr "" + +#. Tag: title +#: portability.xml:154 +#, no-c-format +msgid "Database functions" +msgstr "" + +#. Tag: para +#: portability.xml:157 +#, no-c-format +msgid "" +"This is an area in Hibernate in need of improvement. In terms of portability " +"concerns, this function handling currently works pretty well from HQL; " +"however, it is quite lacking in all other aspects." +msgstr "" + +#. Tag: para +#: portability.xml:164 +#, no-c-format +msgid "" +"SQL functions can be referenced in many ways by users. However, not all " +"databases support the same set of functions. Hibernate, provides a means of " +"mapping a <emphasis>logical</emphasis> function name to a a delegate which " +"knows how to render that particular function, perhaps even using a totally " +"different physical function call." +msgstr "" + +#. Tag: para +#: portability.xml:170 +#, no-c-format +msgid "" +"Technically this function registration is handled through the <classname>org." +"hibernate.dialect.function.SQLFunctionRegistry</classname> class which is " +"intended to allow users to provide custom function definitions without " +"having to provide a custom dialect. This specific behavior is not fully " +"completed as of yet." +msgstr "" + +#. Tag: para +#: portability.xml:177 +#, no-c-format +msgid "" +"It is sort of implemented such that users can programatically register " +"functions with the <classname>org.hibernate.cfg.Configuration</classname> " +"and those functions will be recognized for HQL." +msgstr "" + +#. Tag: title +#: portability.xml:187 +#, no-c-format +msgid "Type mappings" +msgstr "" + +#. Tag: para +#: portability.xml:189 +#, no-c-format +msgid "This section scheduled for completion at a later date..." +msgstr "" Added: core/branches/Branch_3_3/documentation/manual/src/main/docbook/ja-JP/content/portability.po =================================================================== --- core/branches/Branch_3_3/documentation/manual/src/main/docbook/ja-JP/content/portability.po (rev 0) +++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/ja-JP/content/portability.po 2009-06-23 05:46:34 UTC (rev 16878) @@ -0,0 +1,234 @@ +# Language ja-JP translations for Branch package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Branch 3_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-06-16 18:47+0000\n" +"PO-Revision-Date: 2009-06-16 18:47+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: portability.xml:26 +#, no-c-format +msgid "Database Portability Considerations" +msgstr "" + +#. Tag: title +#: portability.xml:29 +#, no-c-format +msgid "Portability Basics" +msgstr "" + +#. Tag: para +#: portability.xml:31 +#, no-c-format +msgid "" +"One of the selling points of Hibernate (and really Object/Relational Mapping " +"as a whole) is the notion of database portability. This could mean an " +"internal IT user migrating from one database vendor to another, or it could " +"mean a framework or deployable application consuming Hibernate to " +"simultaneously target multiple database products by their users. Regardless " +"of the exact scenario, the basic idea is that you want Hibernate to help you " +"run against any number of databases without changes to your code, and " +"ideally without any changes to the mapping metadata." +msgstr "" + +#. Tag: title +#: portability.xml:42 +#, no-c-format +msgid "Dialect" +msgstr "" + +#. Tag: para +#: portability.xml:44 +#, no-c-format +msgid "" +"The first line of portability for Hibernate is the dialect, which is a " +"specialization of the <classname>org.hibernate.dialect.Dialect</classname> " +"contract. A dialect encapsulates all the differences in how Hibernate must " +"communicate with a particular database to accomplish some task like getting " +"a sequence value or structuring a SELECT query. Hibernate bundles a wide " +"range of dialects for many of the most popular databases. If you find that " +"your particular database is not among them, it is not terribly difficult to " +"write your own." +msgstr "" + +#. Tag: title +#: portability.xml:55 +#, no-c-format +msgid "Dialect resolution" +msgstr "" + +#. Tag: para +#: portability.xml:57 +#, no-c-format +msgid "" +"Originally, Hibernate would always require that users specify which dialect " +"to use. In the case of users looking to simultaneously target multiple " +"databases with their build that was problematic. Generally this required " +"their users to configure the Hibernate dialect or defining their own method " +"of setting that value." +msgstr "" + +#. Tag: para +#: portability.xml:64 +#, no-c-format +msgid "" +"Starting with version 3.2, Hibernate introduced the notion of automatically " +"detecting the dialect to use based on the <interfacename>java.sql." +"DatabaseMetaData</interfacename> obtained from a <interfacename>java.sql." +"Connection</interfacename> to that database. This was much better, expect " +"that this resolution was limited to databases Hibernate know about ahead of " +"time and was in no way configurable or overrideable." +msgstr "" + +#. Tag: para +#: portability.xml:72 +#, no-c-format +msgid "" +"Starting with version 3.3, Hibernate has a fare more powerful way to " +"automatically determine which dialect to should be used by relying on a " +"series of delegates which implement the <interfacename>org.hibernate.dialect." +"resolver.DialectResolver</interfacename> which defines only a single method:" +"<programlisting><![CDATA[public Dialect resolveDialect(DatabaseMetaData " +"metaData) throws JDBCConnectionException]]></programlisting>. The basic " +"contract here is that if the resolver 'understands' the given database " +"metadata then it returns the corresponding Dialect; if not it returns null " +"and the process continues to the next resolver. The signature also " +"identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</" +"exceptionname> as possibly being thrown. A JDBCConnectionException here is " +"interpreted to imply a \"non transient\" (aka non-recoverable) connection " +"problem and is used to indicate an immediate stop to resolution attempts. " +"All other exceptions result in a warning and continuing on to the next " +"resolver." +msgstr "" + +#. Tag: para +#: portability.xml:85 +#, no-c-format +msgid "" +"The cool part about these resolvers is that users can also register their " +"own custom resolvers which will be processed ahead of the built-in Hibernate " +"ones. This might be useful in a number of different situations: it allows " +"easy integration for auto-detection of dialects beyond those shipped with " +"HIbernate itself; it allows you to specify to use a custom dialect when a " +"particular database is recognized; etc. To register one or more resolvers, " +"simply specify them (seperated by commas, tabs or spaces) using the " +"'hibernate.dialect_resolvers' configuration setting (see the " +"<constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate." +"cfgEnvironment</classname>)." +msgstr "" + +#. Tag: title +#: portability.xml:98 +#, no-c-format +msgid "Identifier generation" +msgstr "" + +#. Tag: para +#: portability.xml:100 +#, no-c-format +msgid "" +"When considering portability between databases, another important decision " +"is selecting the identifier generation stratagy you want to use. Originally " +"Hibernate provided the <emphasis>native</emphasis> generator for this " +"purpose, which was intended to select between a <emphasis>sequence</" +"emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> " +"strategy depending on the capability of the underlying database. However, an " +"insidious implication of this approach comes about when targtetting some " +"databases which support <emphasis>identity</emphasis> generation and some " +"which do not. <emphasis>identity</emphasis> generation relies on the SQL " +"definition of an IDENTITY (or auto-increment) column to manage the " +"identifier value; it is what is known as a post-insert generation strategy " +"becauase the insert must actually happen before we can know the identifier " +"value. Because Hibernate relies on this identifier value to uniquely " +"reference entities within a persistence context it must then issue the " +"insert immediately when the users requests the entitiy be associated with " +"the session (like via save() e.g.) regardless of current transactional " +"semantics. <note> <para> Hibernate was changed slightly once the implication " +"of this was better understood so that the insert is delayed in cases where " +"that is feasible. </para> </note> The underlying issue is that the actual " +"semanctics of the application itself changes in these cases." +msgstr "" + +#. Tag: para +#: portability.xml:125 +#, no-c-format +msgid "" +"Starting with version 3.2.3, Hibernate comes with a set of <ulink url=" +"\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators " +"targetting portability in a much different way. <note> <para> There are " +"specifically 2 bundled <emphasis>enhanced</emphasis>generators: " +"<itemizedlist> <listitem> <para> <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> </para> </listitem> <listitem> <para> " +"<classname>org.hibernate.id.enhanced.TableGenerator</classname> </para> </" +"listitem> </itemizedlist> </para> </note> The idea behind these generators " +"is to port the actual semantics of the identifer value generation to the " +"different databases. For example, the <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> mimics the behavior of a sequence on " +"databases which do not support sequences by using a table." +msgstr "" + +#. Tag: title +#: portability.xml:154 +#, no-c-format +msgid "Database functions" +msgstr "" + +#. Tag: para +#: portability.xml:157 +#, no-c-format +msgid "" +"This is an area in Hibernate in need of improvement. In terms of portability " +"concerns, this function handling currently works pretty well from HQL; " +"however, it is quite lacking in all other aspects." +msgstr "" + +#. Tag: para +#: portability.xml:164 +#, no-c-format +msgid "" +"SQL functions can be referenced in many ways by users. However, not all " +"databases support the same set of functions. Hibernate, provides a means of " +"mapping a <emphasis>logical</emphasis> function name to a a delegate which " +"knows how to render that particular function, perhaps even using a totally " +"different physical function call." +msgstr "" + +#. Tag: para +#: portability.xml:170 +#, no-c-format +msgid "" +"Technically this function registration is handled through the <classname>org." +"hibernate.dialect.function.SQLFunctionRegistry</classname> class which is " +"intended to allow users to provide custom function definitions without " +"having to provide a custom dialect. This specific behavior is not fully " +"completed as of yet." +msgstr "" + +#. Tag: para +#: portability.xml:177 +#, no-c-format +msgid "" +"It is sort of implemented such that users can programatically register " +"functions with the <classname>org.hibernate.cfg.Configuration</classname> " +"and those functions will be recognized for HQL." +msgstr "" + +#. Tag: title +#: portability.xml:187 +#, no-c-format +msgid "Type mappings" +msgstr "" + +#. Tag: para +#: portability.xml:189 +#, no-c-format +msgid "This section scheduled for completion at a later date..." +msgstr "" Added: core/branches/Branch_3_3/documentation/manual/src/main/docbook/ko-KR/content/portability.po =================================================================== --- core/branches/Branch_3_3/documentation/manual/src/main/docbook/ko-KR/content/portability.po (rev 0) +++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/ko-KR/content/portability.po 2009-06-23 05:46:34 UTC (rev 16878) @@ -0,0 +1,234 @@ +# Language ko-KR translations for Branch package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Branch 3_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-06-16 18:47+0000\n" +"PO-Revision-Date: 2009-06-16 18:47+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: portability.xml:26 +#, no-c-format +msgid "Database Portability Considerations" +msgstr "" + +#. Tag: title +#: portability.xml:29 +#, no-c-format +msgid "Portability Basics" +msgstr "" + +#. Tag: para +#: portability.xml:31 +#, no-c-format +msgid "" +"One of the selling points of Hibernate (and really Object/Relational Mapping " +"as a whole) is the notion of database portability. This could mean an " +"internal IT user migrating from one database vendor to another, or it could " +"mean a framework or deployable application consuming Hibernate to " +"simultaneously target multiple database products by their users. Regardless " +"of the exact scenario, the basic idea is that you want Hibernate to help you " +"run against any number of databases without changes to your code, and " +"ideally without any changes to the mapping metadata." +msgstr "" + +#. Tag: title +#: portability.xml:42 +#, no-c-format +msgid "Dialect" +msgstr "" + +#. Tag: para +#: portability.xml:44 +#, no-c-format +msgid "" +"The first line of portability for Hibernate is the dialect, which is a " +"specialization of the <classname>org.hibernate.dialect.Dialect</classname> " +"contract. A dialect encapsulates all the differences in how Hibernate must " +"communicate with a particular database to accomplish some task like getting " +"a sequence value or structuring a SELECT query. Hibernate bundles a wide " +"range of dialects for many of the most popular databases. If you find that " +"your particular database is not among them, it is not terribly difficult to " +"write your own." +msgstr "" + +#. Tag: title +#: portability.xml:55 +#, no-c-format +msgid "Dialect resolution" +msgstr "" + +#. Tag: para +#: portability.xml:57 +#, no-c-format +msgid "" +"Originally, Hibernate would always require that users specify which dialect " +"to use. In the case of users looking to simultaneously target multiple " +"databases with their build that was problematic. Generally this required " +"their users to configure the Hibernate dialect or defining their own method " +"of setting that value." +msgstr "" + +#. Tag: para +#: portability.xml:64 +#, no-c-format +msgid "" +"Starting with version 3.2, Hibernate introduced the notion of automatically " +"detecting the dialect to use based on the <interfacename>java.sql." +"DatabaseMetaData</interfacename> obtained from a <interfacename>java.sql." +"Connection</interfacename> to that database. This was much better, expect " +"that this resolution was limited to databases Hibernate know about ahead of " +"time and was in no way configurable or overrideable." +msgstr "" + +#. Tag: para +#: portability.xml:72 +#, no-c-format +msgid "" +"Starting with version 3.3, Hibernate has a fare more powerful way to " +"automatically determine which dialect to should be used by relying on a " +"series of delegates which implement the <interfacename>org.hibernate.dialect." +"resolver.DialectResolver</interfacename> which defines only a single method:" +"<programlisting><![CDATA[public Dialect resolveDialect(DatabaseMetaData " +"metaData) throws JDBCConnectionException]]></programlisting>. The basic " +"contract here is that if the resolver 'understands' the given database " +"metadata then it returns the corresponding Dialect; if not it returns null " +"and the process continues to the next resolver. The signature also " +"identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</" +"exceptionname> as possibly being thrown. A JDBCConnectionException here is " +"interpreted to imply a \"non transient\" (aka non-recoverable) connection " +"problem and is used to indicate an immediate stop to resolution attempts. " +"All other exceptions result in a warning and continuing on to the next " +"resolver." +msgstr "" + +#. Tag: para +#: portability.xml:85 +#, no-c-format +msgid "" +"The cool part about these resolvers is that users can also register their " +"own custom resolvers which will be processed ahead of the built-in Hibernate " +"ones. This might be useful in a number of different situations: it allows " +"easy integration for auto-detection of dialects beyond those shipped with " +"HIbernate itself; it allows you to specify to use a custom dialect when a " +"particular database is recognized; etc. To register one or more resolvers, " +"simply specify them (seperated by commas, tabs or spaces) using the " +"'hibernate.dialect_resolvers' configuration setting (see the " +"<constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate." +"cfgEnvironment</classname>)." +msgstr "" + +#. Tag: title +#: portability.xml:98 +#, no-c-format +msgid "Identifier generation" +msgstr "" + +#. Tag: para +#: portability.xml:100 +#, no-c-format +msgid "" +"When considering portability between databases, another important decision " +"is selecting the identifier generation stratagy you want to use. Originally " +"Hibernate provided the <emphasis>native</emphasis> generator for this " +"purpose, which was intended to select between a <emphasis>sequence</" +"emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> " +"strategy depending on the capability of the underlying database. However, an " +"insidious implication of this approach comes about when targtetting some " +"databases which support <emphasis>identity</emphasis> generation and some " +"which do not. <emphasis>identity</emphasis> generation relies on the SQL " +"definition of an IDENTITY (or auto-increment) column to manage the " +"identifier value; it is what is known as a post-insert generation strategy " +"becauase the insert must actually happen before we can know the identifier " +"value. Because Hibernate relies on this identifier value to uniquely " +"reference entities within a persistence context it must then issue the " +"insert immediately when the users requests the entitiy be associated with " +"the session (like via save() e.g.) regardless of current transactional " +"semantics. <note> <para> Hibernate was changed slightly once the implication " +"of this was better understood so that the insert is delayed in cases where " +"that is feasible. </para> </note> The underlying issue is that the actual " +"semanctics of the application itself changes in these cases." +msgstr "" + +#. Tag: para +#: portability.xml:125 +#, no-c-format +msgid "" +"Starting with version 3.2.3, Hibernate comes with a set of <ulink url=" +"\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators " +"targetting portability in a much different way. <note> <para> There are " +"specifically 2 bundled <emphasis>enhanced</emphasis>generators: " +"<itemizedlist> <listitem> <para> <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> </para> </listitem> <listitem> <para> " +"<classname>org.hibernate.id.enhanced.TableGenerator</classname> </para> </" +"listitem> </itemizedlist> </para> </note> The idea behind these generators " +"is to port the actual semantics of the identifer value generation to the " +"different databases. For example, the <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> mimics the behavior of a sequence on " +"databases which do not support sequences by using a table." +msgstr "" + +#. Tag: title +#: portability.xml:154 +#, no-c-format +msgid "Database functions" +msgstr "" + +#. Tag: para +#: portability.xml:157 +#, no-c-format +msgid "" +"This is an area in Hibernate in need of improvement. In terms of portability " +"concerns, this function handling currently works pretty well from HQL; " +"however, it is quite lacking in all other aspects." +msgstr "" + +#. Tag: para +#: portability.xml:164 +#, no-c-format +msgid "" +"SQL functions can be referenced in many ways by users. However, not all " +"databases support the same set of functions. Hibernate, provides a means of " +"mapping a <emphasis>logical</emphasis> function name to a a delegate which " +"knows how to render that particular function, perhaps even using a totally " +"different physical function call." +msgstr "" + +#. Tag: para +#: portability.xml:170 +#, no-c-format +msgid "" +"Technically this function registration is handled through the <classname>org." +"hibernate.dialect.function.SQLFunctionRegistry</classname> class which is " +"intended to allow users to provide custom function definitions without " +"having to provide a custom dialect. This specific behavior is not fully " +"completed as of yet." +msgstr "" + +#. Tag: para +#: portability.xml:177 +#, no-c-format +msgid "" +"It is sort of implemented such that users can programatically register " +"functions with the <classname>org.hibernate.cfg.Configuration</classname> " +"and those functions will be recognized for HQL." +msgstr "" + +#. Tag: title +#: portability.xml:187 +#, no-c-format +msgid "Type mappings" +msgstr "" + +#. Tag: para +#: portability.xml:189 +#, no-c-format +msgid "This section scheduled for completion at a later date..." +msgstr "" Added: core/branches/Branch_3_3/documentation/manual/src/main/docbook/pt-BR/content/portability.po =================================================================== --- core/branches/Branch_3_3/documentation/manual/src/main/docbook/pt-BR/content/portability.po (rev 0) +++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/pt-BR/content/portability.po 2009-06-23 05:46:34 UTC (rev 16878) @@ -0,0 +1,234 @@ +# Language pt-BR translations for Branch package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Branch 3_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-06-16 18:47+0000\n" +"PO-Revision-Date: 2009-06-16 18:47+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: portability.xml:26 +#, no-c-format +msgid "Database Portability Considerations" +msgstr "" + +#. Tag: title +#: portability.xml:29 +#, no-c-format +msgid "Portability Basics" +msgstr "" + +#. Tag: para +#: portability.xml:31 +#, no-c-format +msgid "" +"One of the selling points of Hibernate (and really Object/Relational Mapping " +"as a whole) is the notion of database portability. This could mean an " +"internal IT user migrating from one database vendor to another, or it could " +"mean a framework or deployable application consuming Hibernate to " +"simultaneously target multiple database products by their users. Regardless " +"of the exact scenario, the basic idea is that you want Hibernate to help you " +"run against any number of databases without changes to your code, and " +"ideally without any changes to the mapping metadata." +msgstr "" + +#. Tag: title +#: portability.xml:42 +#, no-c-format +msgid "Dialect" +msgstr "" + +#. Tag: para +#: portability.xml:44 +#, no-c-format +msgid "" +"The first line of portability for Hibernate is the dialect, which is a " +"specialization of the <classname>org.hibernate.dialect.Dialect</classname> " +"contract. A dialect encapsulates all the differences in how Hibernate must " +"communicate with a particular database to accomplish some task like getting " +"a sequence value or structuring a SELECT query. Hibernate bundles a wide " +"range of dialects for many of the most popular databases. If you find that " +"your particular database is not among them, it is not terribly difficult to " +"write your own." +msgstr "" + +#. Tag: title +#: portability.xml:55 +#, no-c-format +msgid "Dialect resolution" +msgstr "" + +#. Tag: para +#: portability.xml:57 +#, no-c-format +msgid "" +"Originally, Hibernate would always require that users specify which dialect " +"to use. In the case of users looking to simultaneously target multiple " +"databases with their build that was problematic. Generally this required " +"their users to configure the Hibernate dialect or defining their own method " +"of setting that value." +msgstr "" + +#. Tag: para +#: portability.xml:64 +#, no-c-format +msgid "" +"Starting with version 3.2, Hibernate introduced the notion of automatically " +"detecting the dialect to use based on the <interfacename>java.sql." +"DatabaseMetaData</interfacename> obtained from a <interfacename>java.sql." +"Connection</interfacename> to that database. This was much better, expect " +"that this resolution was limited to databases Hibernate know about ahead of " +"time and was in no way configurable or overrideable." +msgstr "" + +#. Tag: para +#: portability.xml:72 +#, no-c-format +msgid "" +"Starting with version 3.3, Hibernate has a fare more powerful way to " +"automatically determine which dialect to should be used by relying on a " +"series of delegates which implement the <interfacename>org.hibernate.dialect." +"resolver.DialectResolver</interfacename> which defines only a single method:" +"<programlisting><![CDATA[public Dialect resolveDialect(DatabaseMetaData " +"metaData) throws JDBCConnectionException]]></programlisting>. The basic " +"contract here is that if the resolver 'understands' the given database " +"metadata then it returns the corresponding Dialect; if not it returns null " +"and the process continues to the next resolver. The signature also " +"identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</" +"exceptionname> as possibly being thrown. A JDBCConnectionException here is " +"interpreted to imply a \"non transient\" (aka non-recoverable) connection " +"problem and is used to indicate an immediate stop to resolution attempts. " +"All other exceptions result in a warning and continuing on to the next " +"resolver." +msgstr "" + +#. Tag: para +#: portability.xml:85 +#, no-c-format +msgid "" +"The cool part about these resolvers is that users can also register their " +"own custom resolvers which will be processed ahead of the built-in Hibernate " +"ones. This might be useful in a number of different situations: it allows " +"easy integration for auto-detection of dialects beyond those shipped with " +"HIbernate itself; it allows you to specify to use a custom dialect when a " +"particular database is recognized; etc. To register one or more resolvers, " +"simply specify them (seperated by commas, tabs or spaces) using the " +"'hibernate.dialect_resolvers' configuration setting (see the " +"<constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate." +"cfgEnvironment</classname>)." +msgstr "" + +#. Tag: title +#: portability.xml:98 +#, no-c-format +msgid "Identifier generation" +msgstr "" + +#. Tag: para +#: portability.xml:100 +#, no-c-format +msgid "" +"When considering portability between databases, another important decision " +"is selecting the identifier generation stratagy you want to use. Originally " +"Hibernate provided the <emphasis>native</emphasis> generator for this " +"purpose, which was intended to select between a <emphasis>sequence</" +"emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> " +"strategy depending on the capability of the underlying database. However, an " +"insidious implication of this approach comes about when targtetting some " +"databases which support <emphasis>identity</emphasis> generation and some " +"which do not. <emphasis>identity</emphasis> generation relies on the SQL " +"definition of an IDENTITY (or auto-increment) column to manage the " +"identifier value; it is what is known as a post-insert generation strategy " +"becauase the insert must actually happen before we can know the identifier " +"value. Because Hibernate relies on this identifier value to uniquely " +"reference entities within a persistence context it must then issue the " +"insert immediately when the users requests the entitiy be associated with " +"the session (like via save() e.g.) regardless of current transactional " +"semantics. <note> <para> Hibernate was changed slightly once the implication " +"of this was better understood so that the insert is delayed in cases where " +"that is feasible. </para> </note> The underlying issue is that the actual " +"semanctics of the application itself changes in these cases." +msgstr "" + +#. Tag: para +#: portability.xml:125 +#, no-c-format +msgid "" +"Starting with version 3.2.3, Hibernate comes with a set of <ulink url=" +"\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators " +"targetting portability in a much different way. <note> <para> There are " +"specifically 2 bundled <emphasis>enhanced</emphasis>generators: " +"<itemizedlist> <listitem> <para> <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> </para> </listitem> <listitem> <para> " +"<classname>org.hibernate.id.enhanced.TableGenerator</classname> </para> </" +"listitem> </itemizedlist> </para> </note> The idea behind these generators " +"is to port the actual semantics of the identifer value generation to the " +"different databases. For example, the <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> mimics the behavior of a sequence on " +"databases which do not support sequences by using a table." +msgstr "" + +#. Tag: title +#: portability.xml:154 +#, no-c-format +msgid "Database functions" +msgstr "" + +#. Tag: para +#: portability.xml:157 +#, no-c-format +msgid "" +"This is an area in Hibernate in need of improvement. In terms of portability " +"concerns, this function handling currently works pretty well from HQL; " +"however, it is quite lacking in all other aspects." +msgstr "" + +#. Tag: para +#: portability.xml:164 +#, no-c-format +msgid "" +"SQL functions can be referenced in many ways by users. However, not all " +"databases support the same set of functions. Hibernate, provides a means of " +"mapping a <emphasis>logical</emphasis> function name to a a delegate which " +"knows how to render that particular function, perhaps even using a totally " +"different physical function call." +msgstr "" + +#. Tag: para +#: portability.xml:170 +#, no-c-format +msgid "" +"Technically this function registration is handled through the <classname>org." +"hibernate.dialect.function.SQLFunctionRegistry</classname> class which is " +"intended to allow users to provide custom function definitions without " +"having to provide a custom dialect. This specific behavior is not fully " +"completed as of yet." +msgstr "" + +#. Tag: para +#: portability.xml:177 +#, no-c-format +msgid "" +"It is sort of implemented such that users can programatically register " +"functions with the <classname>org.hibernate.cfg.Configuration</classname> " +"and those functions will be recognized for HQL." +msgstr "" + +#. Tag: title +#: portability.xml:187 +#, no-c-format +msgid "Type mappings" +msgstr "" + +#. Tag: para +#: portability.xml:189 +#, no-c-format +msgid "This section scheduled for completion at a later date..." +msgstr "" Added: core/branches/Branch_3_3/documentation/manual/src/main/docbook/zh-CN/content/portability.po =================================================================== --- core/branches/Branch_3_3/documentation/manual/src/main/docbook/zh-CN/content/portability.po (rev 0) +++ core/branches/Branch_3_3/documentation/manual/src/main/docbook/zh-CN/content/portability.po 2009-06-23 05:46:34 UTC (rev 16878) @@ -0,0 +1,234 @@ +# Language zh-CN translations for Branch package. +# Automatically generated, 2009. +# +msgid "" +msgstr "" +"Project-Id-Version: Branch 3_3\n" +"Report-Msgid-Bugs-To: http://bugs.kde.org\n" +"POT-Creation-Date: 2009-06-16 18:47+0000\n" +"PO-Revision-Date: 2009-06-16 18:47+0000\n" +"Last-Translator: Automatically generated\n" +"Language-Team: none\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#. Tag: title +#: portability.xml:26 +#, no-c-format +msgid "Database Portability Considerations" +msgstr "" + +#. Tag: title +#: portability.xml:29 +#, no-c-format +msgid "Portability Basics" +msgstr "" + +#. Tag: para +#: portability.xml:31 +#, no-c-format +msgid "" +"One of the selling points of Hibernate (and really Object/Relational Mapping " +"as a whole) is the notion of database portability. This could mean an " +"internal IT user migrating from one database vendor to another, or it could " +"mean a framework or deployable application consuming Hibernate to " +"simultaneously target multiple database products by their users. Regardless " +"of the exact scenario, the basic idea is that you want Hibernate to help you " +"run against any number of databases without changes to your code, and " +"ideally without any changes to the mapping metadata." +msgstr "" + +#. Tag: title +#: portability.xml:42 +#, no-c-format +msgid "Dialect" +msgstr "" + +#. Tag: para +#: portability.xml:44 +#, no-c-format +msgid "" +"The first line of portability for Hibernate is the dialect, which is a " +"specialization of the <classname>org.hibernate.dialect.Dialect</classname> " +"contract. A dialect encapsulates all the differences in how Hibernate must " +"communicate with a particular database to accomplish some task like getting " +"a sequence value or structuring a SELECT query. Hibernate bundles a wide " +"range of dialects for many of the most popular databases. If you find that " +"your particular database is not among them, it is not terribly difficult to " +"write your own." +msgstr "" + +#. Tag: title +#: portability.xml:55 +#, no-c-format +msgid "Dialect resolution" +msgstr "" + +#. Tag: para +#: portability.xml:57 +#, no-c-format +msgid "" +"Originally, Hibernate would always require that users specify which dialect " +"to use. In the case of users looking to simultaneously target multiple " +"databases with their build that was problematic. Generally this required " +"their users to configure the Hibernate dialect or defining their own method " +"of setting that value." +msgstr "" + +#. Tag: para +#: portability.xml:64 +#, no-c-format +msgid "" +"Starting with version 3.2, Hibernate introduced the notion of automatically " +"detecting the dialect to use based on the <interfacename>java.sql." +"DatabaseMetaData</interfacename> obtained from a <interfacename>java.sql." +"Connection</interfacename> to that database. This was much better, expect " +"that this resolution was limited to databases Hibernate know about ahead of " +"time and was in no way configurable or overrideable." +msgstr "" + +#. Tag: para +#: portability.xml:72 +#, no-c-format +msgid "" +"Starting with version 3.3, Hibernate has a fare more powerful way to " +"automatically determine which dialect to should be used by relying on a " +"series of delegates which implement the <interfacename>org.hibernate.dialect." +"resolver.DialectResolver</interfacename> which defines only a single method:" +"<programlisting><![CDATA[public Dialect resolveDialect(DatabaseMetaData " +"metaData) throws JDBCConnectionException]]></programlisting>. The basic " +"contract here is that if the resolver 'understands' the given database " +"metadata then it returns the corresponding Dialect; if not it returns null " +"and the process continues to the next resolver. The signature also " +"identifies <exceptionname>org.hibernate.exception.JDBCConnectionException</" +"exceptionname> as possibly being thrown. A JDBCConnectionException here is " +"interpreted to imply a \"non transient\" (aka non-recoverable) connection " +"problem and is used to indicate an immediate stop to resolution attempts. " +"All other exceptions result in a warning and continuing on to the next " +"resolver." +msgstr "" + +#. Tag: para +#: portability.xml:85 +#, no-c-format +msgid "" +"The cool part about these resolvers is that users can also register their " +"own custom resolvers which will be processed ahead of the built-in Hibernate " +"ones. This might be useful in a number of different situations: it allows " +"easy integration for auto-detection of dialects beyond those shipped with " +"HIbernate itself; it allows you to specify to use a custom dialect when a " +"particular database is recognized; etc. To register one or more resolvers, " +"simply specify them (seperated by commas, tabs or spaces) using the " +"'hibernate.dialect_resolvers' configuration setting (see the " +"<constant>DIALECT_RESOLVERS</constant> constant on <classname>org.hibernate." +"cfgEnvironment</classname>)." +msgstr "" + +#. Tag: title +#: portability.xml:98 +#, no-c-format +msgid "Identifier generation" +msgstr "" + +#. Tag: para +#: portability.xml:100 +#, no-c-format +msgid "" +"When considering portability between databases, another important decision " +"is selecting the identifier generation stratagy you want to use. Originally " +"Hibernate provided the <emphasis>native</emphasis> generator for this " +"purpose, which was intended to select between a <emphasis>sequence</" +"emphasis>, <emphasis>identity</emphasis>, or <emphasis>table</emphasis> " +"strategy depending on the capability of the underlying database. However, an " +"insidious implication of this approach comes about when targtetting some " +"databases which support <emphasis>identity</emphasis> generation and some " +"which do not. <emphasis>identity</emphasis> generation relies on the SQL " +"definition of an IDENTITY (or auto-increment) column to manage the " +"identifier value; it is what is known as a post-insert generation strategy " +"becauase the insert must actually happen before we can know the identifier " +"value. Because Hibernate relies on this identifier value to uniquely " +"reference entities within a persistence context it must then issue the " +"insert immediately when the users requests the entitiy be associated with " +"the session (like via save() e.g.) regardless of current transactional " +"semantics. <note> <para> Hibernate was changed slightly once the implication " +"of this was better understood so that the insert is delayed in cases where " +"that is feasible. </para> </note> The underlying issue is that the actual " +"semanctics of the application itself changes in these cases." +msgstr "" + +#. Tag: para +#: portability.xml:125 +#, no-c-format +msgid "" +"Starting with version 3.2.3, Hibernate comes with a set of <ulink url=" +"\"http://in.relation.to/2082.lace\">enhanced</ulink> identifier generators " +"targetting portability in a much different way. <note> <para> There are " +"specifically 2 bundled <emphasis>enhanced</emphasis>generators: " +"<itemizedlist> <listitem> <para> <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> </para> </listitem> <listitem> <para> " +"<classname>org.hibernate.id.enhanced.TableGenerator</classname> </para> </" +"listitem> </itemizedlist> </para> </note> The idea behind these generators " +"is to port the actual semantics of the identifer value generation to the " +"different databases. For example, the <classname>org.hibernate.id.enhanced." +"SequenceStyleGenerator</classname> mimics the behavior of a sequence on " +"databases which do not support sequences by using a table." +msgstr "" + +#. Tag: title +#: portability.xml:154 +#, no-c-format +msgid "Database functions" +msgstr "" + +#. Tag: para +#: portability.xml:157 +#, no-c-format +msgid "" +"This is an area in Hibernate in need of improvement. In terms of portability " +"concerns, this function handling currently works pretty well from HQL; " +"however, it is quite lacking in all other aspects." +msgstr "" + +#. Tag: para +#: portability.xml:164 +#, no-c-format +msgid "" +"SQL functions can be referenced in many ways by users. However, not all " +"databases support the same set of functions. Hibernate, provides a means of " +"mapping a <emphasis>logical</emphasis> function name to a a delegate which " +"knows how to render that particular function, perhaps even using a totally " +"different physical function call." +msgstr "" + +#. Tag: para +#: portability.xml:170 +#, no-c-format +msgid "" +"Technically this function registration is handled through the <classname>org." +"hibernate.dialect.function.SQLFunctionRegistry</classname> class which is " +"intended to allow users to provide custom function definitions without " +"having to provide a custom dialect. This specific behavior is not fully " +"completed as of yet." +msgstr "" + +#. Tag: para +#: portability.xml:177 +#, no-c-format +msgid "" +"It is sort of implemented such that users can programatically register " +"functions with the <classname>org.hibernate.cfg.Configuration</classname> " +"and those functions will be recognized for HQL." +msgstr "" + +#. Tag: title +#: portability.xml:187 +#, no-c-format +msgid "Type mappings" +msgstr "" + +#. Tag: para +#: portability.xml:189 +#, no-c-format +msgid "This section scheduled for completion at a later date..." +msgstr ""

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16877 - core/trunk/documentation/manual/src/main/docbook/en-US/content.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-23 01:46:17 -0400 (Tue, 23 Jun 2009) New Revision: 16877 Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml Log: HHH-3944 - Document known database portability strategies Modified: core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml =================================================================== --- core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml 2009-06-23 02:27:53 UTC (rev 16876) +++ core/trunk/documentation/manual/src/main/docbook/en-US/content/portability.xml 2009-06-23 05:46:17 UTC (rev 16877) @@ -90,7 +90,7 @@ database is recognized; etc. To register one or more resolvers, simply specify them (seperated by commas, tabs or spaces) using the 'hibernate.dialect_resolvers' configuration setting (see the <constant>DIALECT_RESOLVERS</constant> constant on - <ooclass><package>org.hibernate.cfg</package><classname>Environment</classname></ooclass>). + <classname>org.hibernate.cfg.Environment</classname>). </para> </sect1>

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16876 - core/branches/Branch_3_2/src/org/hibernate/loader.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-22 22:27:53 -0400 (Mon, 22 Jun 2009) New Revision: 16876 Modified: core/branches/Branch_3_2/src/org/hibernate/loader/BasicLoader.java core/branches/Branch_3_2/src/org/hibernate/loader/MultipleBagFetchException.java Log: HHH-3980 - Fix for HHH-2980 introduced bug that allows the same bag collection role to be fetched multiple times Modified: core/branches/Branch_3_2/src/org/hibernate/loader/BasicLoader.java =================================================================== --- core/branches/Branch_3_2/src/org/hibernate/loader/BasicLoader.java 2009-06-23 02:27:39 UTC (rev 16875) +++ core/branches/Branch_3_2/src/org/hibernate/loader/BasicLoader.java 2009-06-23 02:27:53 UTC (rev 16876) @@ -1,8 +1,8 @@ //$Id$ package org.hibernate.loader; -import java.util.Set; -import java.util.HashSet; +import java.util.List; +import java.util.ArrayList; import org.hibernate.engine.SessionFactoryImplementor; import org.hibernate.persister.entity.Loadable; @@ -47,14 +47,14 @@ } CollectionPersister[] collectionPersisters = getCollectionPersisters(); - Set bagRoles = null; + List bagRoles = null; if ( collectionPersisters != null ) { String[] collectionSuffixes = getCollectionSuffixes(); collectionDescriptors = new CollectionAliases[collectionPersisters.length]; for ( int i = 0; i < collectionPersisters.length; i++ ) { if ( isBag( collectionPersisters[i] ) ) { if ( bagRoles == null ) { - bagRoles = new HashSet(); + bagRoles = new ArrayList(); } bagRoles.add( collectionPersisters[i].getRole() ); } Modified: core/branches/Branch_3_2/src/org/hibernate/loader/MultipleBagFetchException.java =================================================================== --- core/branches/Branch_3_2/src/org/hibernate/loader/MultipleBagFetchException.java 2009-06-23 02:27:39 UTC (rev 16875) +++ core/branches/Branch_3_2/src/org/hibernate/loader/MultipleBagFetchException.java 2009-06-23 02:27:53 UTC (rev 16876) @@ -23,7 +23,7 @@ */ package org.hibernate.loader; -import java.util.Set; +import java.util.List; import org.hibernate.HibernateException; @@ -34,19 +34,19 @@ * @author Steve Ebersole */ public class MultipleBagFetchException extends HibernateException { - private final Set bagRoles; + private final List bagRoles; - public MultipleBagFetchException(Set bagRoles) { + public MultipleBagFetchException(List bagRoles) { super( "cannot simultaneously fetch multiple bags" ); this.bagRoles = bagRoles; } /** - * Retrieves the set of collection roles for the bags encountered. + * Retrieves the collection-roles for the bags encountered. * * @return The bag collection roles. */ - public Set getBagRoles() { + public List getBagRoles() { return bagRoles; } }

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16875 - core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-22 22:27:39 -0400 (Mon, 22 Jun 2009) New Revision: 16875 Modified: core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/BasicLoader.java core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java Log: HHH-3980 - Fix for HHH-2980 introduced bug that allows the same bag collection role to be fetched multiple times Modified: core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/BasicLoader.java =================================================================== --- core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/BasicLoader.java 2009-06-23 02:27:23 UTC (rev 16874) +++ core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/BasicLoader.java 2009-06-23 02:27:39 UTC (rev 16875) @@ -24,8 +24,8 @@ */ package org.hibernate.loader; -import java.util.Set; -import java.util.HashSet; +import java.util.List; +import java.util.ArrayList; import org.hibernate.engine.SessionFactoryImplementor; import org.hibernate.persister.entity.Loadable; @@ -70,14 +70,14 @@ } CollectionPersister[] collectionPersisters = getCollectionPersisters(); - Set bagRoles = null; + List bagRoles = null; if ( collectionPersisters != null ) { String[] collectionSuffixes = getCollectionSuffixes(); collectionDescriptors = new CollectionAliases[collectionPersisters.length]; for ( int i = 0; i < collectionPersisters.length; i++ ) { if ( isBag( collectionPersisters[i] ) ) { if ( bagRoles == null ) { - bagRoles = new HashSet(); + bagRoles = new ArrayList(); } bagRoles.add( collectionPersisters[i].getRole() ); } Modified: core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java =================================================================== --- core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java 2009-06-23 02:27:23 UTC (rev 16874) +++ core/branches/Branch_3_3/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java 2009-06-23 02:27:39 UTC (rev 16875) @@ -23,7 +23,7 @@ */ package org.hibernate.loader; -import java.util.Set; +import java.util.List; import org.hibernate.HibernateException; @@ -34,19 +34,19 @@ * @author Steve Ebersole */ public class MultipleBagFetchException extends HibernateException { - private final Set bagRoles; + private final List bagRoles; - public MultipleBagFetchException(Set bagRoles) { + public MultipleBagFetchException(List bagRoles) { super( "cannot simultaneously fetch multiple bags" ); this.bagRoles = bagRoles; } /** - * Retrieves the set of collection roles for the bags encountered. + * Retrieves the collection-roles for the bags encountered. * * @return The bag collection roles. */ - public Set getBagRoles() { + public List getBagRoles() { return bagRoles; } }

14 years, 11 months

1
0
0 / 0

Hibernate SVN: r16874 - core/trunk/core/src/main/java/org/hibernate/loader.

by hibernate-commits＠lists.jboss.org

Author: steve.ebersole(a)jboss.com Date: 2009-06-22 22:27:23 -0400 (Mon, 22 Jun 2009) New Revision: 16874 Modified: core/trunk/core/src/main/java/org/hibernate/loader/BasicLoader.java core/trunk/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java Log: HHH-3980 - Fix for HHH-2980 introduced bug that allows the same bag collection role to be fetched multiple times Modified: core/trunk/core/src/main/java/org/hibernate/loader/BasicLoader.java =================================================================== --- core/trunk/core/src/main/java/org/hibernate/loader/BasicLoader.java 2009-06-22 22:00:05 UTC (rev 16873) +++ core/trunk/core/src/main/java/org/hibernate/loader/BasicLoader.java 2009-06-23 02:27:23 UTC (rev 16874) @@ -24,8 +24,8 @@ */ package org.hibernate.loader; -import java.util.Set; -import java.util.HashSet; +import java.util.List; +import java.util.ArrayList; import org.hibernate.engine.SessionFactoryImplementor; import org.hibernate.persister.entity.Loadable; @@ -70,14 +70,14 @@ } CollectionPersister[] collectionPersisters = getCollectionPersisters(); - Set bagRoles = null; + List bagRoles = null; if ( collectionPersisters != null ) { String[] collectionSuffixes = getCollectionSuffixes(); collectionDescriptors = new CollectionAliases[collectionPersisters.length]; for ( int i = 0; i < collectionPersisters.length; i++ ) { if ( isBag( collectionPersisters[i] ) ) { if ( bagRoles == null ) { - bagRoles = new HashSet(); + bagRoles = new ArrayList(); } bagRoles.add( collectionPersisters[i].getRole() ); } Modified: core/trunk/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java =================================================================== --- core/trunk/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java 2009-06-22 22:00:05 UTC (rev 16873) +++ core/trunk/core/src/main/java/org/hibernate/loader/MultipleBagFetchException.java 2009-06-23 02:27:23 UTC (rev 16874) @@ -23,7 +23,7 @@ */ package org.hibernate.loader; -import java.util.Set; +import java.util.List; import org.hibernate.HibernateException; @@ -34,19 +34,19 @@ * @author Steve Ebersole */ public class MultipleBagFetchException extends HibernateException { - private final Set bagRoles; + private final List bagRoles; - public MultipleBagFetchException(Set bagRoles) { + public MultipleBagFetchException(List bagRoles) { super( "cannot simultaneously fetch multiple bags" ); this.bagRoles = bagRoles; } /** - * Retrieves the set of collection roles for the bags encountered. + * Retrieves the collection-roles for the bags encountered. * * @return The bag collection roles. */ - public Set getBagRoles() { + public List getBagRoles() { return bagRoles; } }

14 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-commits June 2009