hibernate-issues — Hibernate JIRA Notifications

[Hibernate-issues] [Hibernate-JIRA] Assigned: (HB-383) websphere 5 transaction manager lookup

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

Message:

   The following issue has been re-assigned.

   Assignee: Daniel Bradby (mailto:db...@ci...)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-383


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-383
    Summary: websphere 5 transaction manager lookup
       Type: Bug

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: Daniel Bradby
   Reporter: Edina Pimp

    Created: Tue, 7 Oct 2003 11:54 AM
    Updated: Thu, 9 Oct 2003 11:12 PM
Environment: WebSphere Platform 5.0 [BASE 5.0.2]; Win2k; WSAD; JDK1.3.1

Description:
Newest version of the WebSphereTransactionManagerLookup fails under WebSphere 5.  Class com.ibm.ejs.jts.jta.JTSXA - which is the default class - remains available in the classpath so it's found and Hibernate assumes a WAS4 environment.

When 'getTransactionManager' is invoked on the WAS5 version of JTSXA, a NoSuchMethod exception is thrown, caught, and rethrown as a HibernateException.  The correct method is instance().

This worked in 2.1b3 because the exception handling just happened to line up the right way.

Maybe it's reasonable to break out different WebSphere4TransactionManagerLookup and WebSphere5TransactionManagerLookup classes, ugly as it sounds.

 


---------------------------------------------------------------------
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] Created: (HB-390) XmlDatabinder.bindAll() is broken

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-390


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-390
    Summary: XmlDatabinder.bindAll() is broken
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.1

   Assignee: 
   Reporter: Sayeed Anjum

    Created: Thu, 9 Oct 2003 9:37 PM
    Updated: Thu, 9 Oct 2003 9:37 PM

Description:
We have a silly error in the following method:

public Databinder bindAll(Collection objects) {
	objects.addAll(objects);
	return this;
}

we need to change line #1 above to:

	this.objects.addAll(objects);




---------------------------------------------------------------------
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] String byte binary objects and useing byte[] Byte[]

[Hanasaki J. <han...@ha...>]

I need to store a JAR / zip file in a database column.  What is the best 
way to do this?

I have tried a method that returns byte[] and am getting an error from 
the schema parser at startup when it parses the hbm.xml file.

Database is MS-SQL server

for anyone interested.. the end use is to store xml templates or 
jasperreports in the database and create a html web front end to allow 
management.

thanks
-- 
=================================================================
= Management is doing things right; leadership is doing the     =
=       right things.    - Peter Drucker                        =
=_______________________________________________________________=
=     http://www.sun.com/service/sunps/jdc/javacenter.pdf       =
=  www.sun.com | www.javasoft.com | http://www.sun.com/sunone   =
=================================================================

[Hibernate-issues] [Hibernate-JIRA] Commented: (HB-206) Fieldname constants generator, and Http form loader utility.

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

The following comment has been added to this issue:

     Author: Matt Hall
    Created: Thu, 9 Oct 2003 11:26 AM
       Body:
This patch is superceded by HB-357
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-206


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-206
    Summary: Fieldname constants generator, and Http form loader utility.
       Type: Patch

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.2

   Assignee: Max Rydahl Andersen
   Reporter: Matt Hall

    Created: Mon, 21 Jul 2003 12:38 PM
    Updated: Sat, 9 Aug 2003 9:05 AM

Description:
This is a modification to BasicRenderer to generate a series of constants at the top of generated hibernate data objects that represent each property contained in the object.  Looks something like:

    public static String FIELD_ID = "com.whatever.Category.id";
    public static String FIELD_TYPE = "com.whatever.Category.type";
    public static String FIELD_TITLE = "com.whateverCategory.title";

If you then use these constants to name your fields in a web form, you can use the other part of this submissions, HttpFormUtil, to load your hibernate data objects from an HttpServletRequest automatically via reflection.



---------------------------------------------------------------------
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] Created: (HB-389) DTD does not allow 'generator'-tag in 'composite-id', whereas Hibernate does and works perfect

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-389


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-389
    Summary: DTD does not allow 'generator'-tag in 'composite-id', whereas Hibernate does and works perfect
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Jan-Allard Slurink

    Created: Thu, 9 Oct 2003 2:37 AM
    Updated: Thu, 9 Oct 2003 2:37 AM
Environment: W2K SP4, JDK 1.3

Description:
Consider this part of the mapping-file: 

   <class name="AdresModel" table="ADRES"> 
      <composite-id name="adresnr" class="AdresnrModel"> 
         <key-property name="adresnr"/> 
         <generator class="AdresnrPKGenerator"> 
            <param name="sequence">SEQ_ADRES</param> 
         </generator> 
      </composite-id> 
      ... 
      ... 
 

I have a wrapper named AdresnrModel (with only one field) for my custom PK, and I want to use a PK-Generator mapped to an oracle sequence with it. 

The error I get is this: 


2003-10-08 15:00:33,309 ERROR net.sf.hibernate.util.XMLHelper - Error parsing XML: XML InputStream(20) 
org.xml.sax.SAXParseException: Element "composite-id" does not allow "generator" here. 
   void org.apache.crimson.parser.Parser2.error(java.lang.String, java.lang.Object[]) 
 


Despite the SAXParseException, Hibernate WORKS and does perfectly what I want. 

So the bug is: Either the DTD does not support the above Hibernate feature, OR hibernate allows this feature whereas it shouldn't allow it.

My best guess is that the DTD should be updated to the current capabilities of Hibernate


---------------------------------------------------------------------
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-383) websphere 5 transaction manager lookup

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

The following comment has been added to this issue:

     Author: Daniel Bradby
    Created: Thu, 9 Oct 2003 12:33 AM
       Body:
The original patch did actually fix this, but it seems a small refactor actually broke it.

WAS5 does still include JTSXA on it's classpath and is still the actual implementation of JTA TransactionManager, but WAS5 has added on top of this (and WAS4) TransactionManagerFactory. This class uses a property (com.ibm.ws.transaction.WSTxManager=com.ibm.ejs.jts.jta.JTSXA
) to determine which JTA TransactionManager impl to use. 

I would suggest we move the lookup of the Websphere 5 class first and then on the Exception lookup the WAS 4 one if needed. The result of either will then have the same method name.

I have tested this with WAS5 ... and I suppose I can test it on WAS4 unless someone can go so quickly.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-383


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-383
    Summary: websphere 5 transaction manager lookup
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Edina Pimp

    Created: Tue, 7 Oct 2003 11:54 AM
    Updated: Tue, 7 Oct 2003 11:54 AM
Environment: WebSphere Platform 5.0 [BASE 5.0.2]; Win2k; WSAD; JDK1.3.1

Description:
Newest version of the WebSphereTransactionManagerLookup fails under WebSphere 5.  Class com.ibm.ejs.jts.jta.JTSXA - which is the default class - remains available in the classpath so it's found and Hibernate assumes a WAS4 environment.

When 'getTransactionManager' is invoked on the WAS5 version of JTSXA, a NoSuchMethod exception is thrown, caught, and rethrown as a HibernateException.  The correct method is instance().

This worked in 2.1b3 because the exception handling just happened to line up the right way.

Maybe it's reasonable to break out different WebSphere4TransactionManagerLookup and WebSphere5TransactionManagerLookup classes, ugly as it sounds.

 


---------------------------------------------------------------------
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-47) Clustered Read/Write Caching

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

The following comment has been added to this issue:

     Author: John Watkinson
    Created: Wed, 8 Oct 2003 3:57 PM
       Body:
Gavin, is there anything else needed for this patch? Let me know if there are outstanding issues, it would be great to see this in 2.1.
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-47


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-47
    Summary:  Clustered Read/Write Caching
       Type: Patch

     Status: Assigned
   Priority: Critical

    Project: Hibernate2
   Fix Fors:
             2.1

   Assignee: Gavin King
   Reporter: Max Rydahl Andersen

    Created: Sat, 3 May 2003 10:30 AM
    Updated: Thu, 2 Oct 2003 2:18 PM

Description:
Clustered Read/Write Caching
This patch adds the ability to do read-write caching in 
a clustered environment. This is accomplished by way of 
the SwarmCache caching engine. It in turn uses 
Javagroups to implement efficient, multicast-based 
cache communication. You can read a detailed 
description of SwarmCache at http://swarmcache.sf.net. 
Included in the patch is a readme that explains how it 
works and how to apply it. 

John Watkinson 

http://sourceforge.net/tracker/index.php?func=detail&aid=722039&group_id=40712&atid=428710




---------------------------------------------------------------------
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] Updated: (HB-379) IN clause in an HQL query confuses the preprocessor.

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

The following issue has been updated:

    Updater: John Kristian (mailto:jkr...@do...)
       Date: Wed, 8 Oct 2003 2:17 PM
    Comment:
syntax.diff-u (attached) is a patch (relative to 2.1 Beta 4) that mitigates this problem.  It's not optimal: we still see time wasted attempting to interpret property names (e.g. in an "ORDER BY property ASC" clause) as class names.
    Changes:
             Attachment changed to syntax.diff-u
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-379&page=history

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-379


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-379
    Summary: IN clause in an HQL query confuses the preprocessor. 
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0.3

   Assignee: 
   Reporter: Bulent Erdemir

    Created: Fri, 3 Oct 2003 3:52 PM
    Updated: Wed, 8 Oct 2003 2:17 PM

Description:
check the related forum postings for detailed information at:
http://forum.hibernate.org/viewtopic.php?p=2173569&sid=298fed84e2b015aff203a1f1bd83ab80#2173569


For queries having an IN clause, this confuses the preprocessor and causes hibernate to call getImportedClass() in QueryTranslator.concreteQueries() for each token in the query. 

This also causes long parsing time especially noticeable when running hibernate code under Jboss in which a different classloader is used. 



---------------------------------------------------------------------
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] Created: (HB-388) composite id with saveOrUpdate not updating, duplicate key

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-388


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-388
    Summary: composite id with saveOrUpdate not updating, duplicate key
       Type: Bug

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.0 final

   Assignee: 
   Reporter: Michael Lowe

    Created: Wed, 8 Oct 2003 1:28 PM
    Updated: Wed, 8 Oct 2003 1:28 PM
Environment: sql200

Description:
I attempt to update a row with a composite id using saveOrUpdate and get "Violation of PRIMARY KEY constraint: Cannot insert duplicate key in object."

If I change the method to update, it works fine, unless, of course I try to insert, then save works.

I tried all combinations of unsaved-value, to no avail.


---------------------------------------------------------------------
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] Created: (HB-387) hbm2java: addX(T x)/removeX(T x) methods generation in one-to-many relation class

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-387


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-387
    Summary: hbm2java: addX(T x)/removeX(T x) methods generation in one-to-many relation class
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             toolset
   Versions:
             2.0.3

   Assignee: 
   Reporter: venkat dosapati

    Created: Wed, 8 Oct 2003 9:14 AM
    Updated: Wed, 8 Oct 2003 9:14 AM

Description:
I was generating the java source files from mapping. I have two classes Workspace and Asset. Workspace-to-Asset is one-to-many association and Asset-to-Workspace is many-to-one association.
I did the required mapping for these 2 classes in my mapping file. But when I generate the classes the class 'Workspace' is not having the expected methods.
I was expecting 'addAsset(Asset)' & 'removeAsset(Asset)' methods in Workspace class. But the generated class 'Workspace' was not having them.

I feel Workspace class should have the following methods in addition to setAssets(List), getAssets():
public class Workspace {
        private ArrayList assets;
        public void addAsset(Asset _asset){
		if(assets==null) assets=new ArrayList();
		_asset.setWorkspace(this);
		assets.add(_asset);
	}
	
	public void removeAsset(Asset _asset){
		if(assets==null)return;
		_asset.setWorkspace(null);
		assets.remove(_asset);
	}
}

I also feel it is better to have 'getAsset(Object assetId)' method in Workspace class in case of composition relation.

thanks
dosapati


---------------------------------------------------------------------
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] Created: (HB-386) Hibernate crashes while populate large tables

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-386


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-386
    Summary: Hibernate crashes while populate large tables
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1
             2.0.3

   Assignee: 
   Reporter: Jeff Gager

    Created: Wed, 8 Oct 2003 6:18 AM
    Updated: Wed, 8 Oct 2003 6:18 AM
Environment: Dell 2Ghz Pentium 4 512MB RAM Running Windows XP.
Java 1.4.2
Eclipse 2.1.1

Description:
I am trying to write a simple java application that reads a large number of records from a Oracle database (using JDBC) and loads them into a mySQL database through hibernate.

The application crashes with java.lang.OutOfMemoryError.

As the application runs I can see it steadilly using up memory until it eventually falls over. I am commiting the Transaction, closing the Session and creating a new Session and Transaction every 1000 records. I think hibernate is either failing to release some kind of resource, or it is performing some action on the existing data before creating each record which is consuming more memory as more records are created.

I am not sure how to proceed, your help would be much appreciated.

Source follows;

package X
lots of import's

public class XLoader {

	private static Logger log = Logger.getLogger("X.XLoader");
	
	public static void main(String[] args) throws Throwable {

		log.info("Processing starting at " + new Date());

		Connection conn = null; 
		try {
			
			// Create the JDBC Driver
			final OracleDriver driver = new OracleDriver();
				
			// Load the Oracle JDBC driver
			DriverManager.registerDriver(driver);
		
			// Establish Read-only JDBC Connection to the PAS database
			conn = (Connection)DriverManager.getConnection("jdbc:oracle:oci8:@XXX", "XXX", "XXX");
			conn.setAutoCommit(false);

			// Loading...
			loadPerson(conn);

			log.info("Processing completed at " + new Date());

		} catch (Throwable e) {
			log.fatal("Unhandled Exception - processing halted\n" + e.toString());
			throw e;
		} finally {
			conn.close();
			System.exit(1);
			log.info("Finished at " + new Date());
		}
	}
	
	private static void loadPerson(Connection conn) throws Throwable {

		log.info("Processing people at " + new Date());

		// Declare statment and result set
		PreparedStatement stmt = null;
		ResultSet rset = null; 
		Session session = null;
		Transaction tx = null;
		SessionFactory sf = new Configuration().configure("/XX.xml").buildSessionFactory();
		
		try {

			// Load people 
			String sql = "BIG SELECT STATEMENT HERE";
					   
			log.info("Reading people at " + new Date());
			stmt = conn.prepareStatement(sql,
				ResultSet.TYPE_SCROLL_INSENSITIVE, ResultSet.CONCUR_READ_ONLY);
			rset = stmt.executeQuery();

			if (rset.getFetchSize() < 1)
				throw new SQLException("No People found");

			session = sf.openSession();
			tx = session.beginTransaction();
			log.info("Loading people at " + new Date());
			int counter = 0;
			String lastPayroll = "";
			Payroll payroll = null;

			while (rset.next()) {

				// Create new payrolls as we find them
            	String thisPayroll = rset.getString(1);
				if (!thisPayroll.equals(lastPayroll)) {
					payroll = new Payroll();
					payroll.setName(rset.getString(1));
					payroll.setFrequency(rset.getString(2));
					payroll.setStatus(rset.getString(3));
					payroll.setFirstPaydate(rset.getDate(4));
					payroll.setNextPaydate(rset.getDate(5));
					payroll.setPrevPaydate(rset.getDate(6));
					payroll.setRunDate(rset.getDate(7));
					payroll.setAccountName(rset.getString(8));
					payroll.setAccountNumber(rset.getInt(9));
					payroll.setSortcode(rset.getInt(10));
					payroll.setBacsName(rset.getString(11));
					payroll.setBacsNumber(rset.getInt(12));
					ArrayList payrollMemberships = new ArrayList();
					payroll.setMemberships(payrollMemberships);
					session.save(payroll);
            	}
            	lastPayroll = thisPayroll;

				// Create people
				Person person = new Person();
				person.setReference(rset.getString(13));
				person.setSurname(rset.getString(14));
				person.setSex(rset.getString(15).charAt(0));
				person.setForenames(rset.getString(16));
				person.setInitials(rset.getString(17));
				person.setTitle(rset.getString(18));
				person.setNiNumber(rset.getString(19));
				person.setBirth(rset.getDate(20));
				ArrayList personMemberships = new ArrayList();
				person.setMemberships(personMemberships);
				ArrayList personAddresses = new ArrayList();
				person.setAddresses(personAddresses);
				session.save(person);

				// Create memberships
				Membership membership = new Membership();
				membership.setStart(rset.getDate(21));
				membership.setStatus("Paying");
				membership.setPerson(person);
				membership.setPayroll(payroll);
				person.addMembership(membership);
				payroll.addMembership(membership);
				session.save(membership);
				
				// Create addresses
				Address address = new Address();
				address.setStart(new Date());
				address.setLine1(rset.getString(22));
				address.setLine2(rset.getString(23));
				address.setTown(rset.getString(24));
				address.setCounty(rset.getString(25));
				address.setPostcode(rset.getString(26));
				address.setPerson(person);
				person.addAddress(address);
				session.save(address);

				if ((++counter % 1000) == 0) {
					tx.commit();
					long payid = payroll.getId().longValue();
					session.close();
					session = sf.openSession();
					tx = session.beginTransaction();
					payroll = (Payroll)session.load(Payroll.class, new Long(payid));
					log.info("Loaded " + counter);
				}

			}
			
			tx.commit();
			session.close();
			sf.close();
			log.info("Total People Loaded " + counter);

			rset.close();
			stmt.close();

		// Handle errors
		} catch (Throwable e) {
			log.fatal(e.getMessage(), e);
			rset.close();
			stmt.close();
			if (sf != null) sf.close();
			if (session != null) session.close();
			if (tx != null) tx.rollback();
			throw e;
		}
		log.info("Finished processing people at " + new Date());
	}
}



---------------------------------------------------------------------
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] Created: (HB-385) Online hibernate-mapping-2.0.dtd differs from dtd in jar file

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-385


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-385
    Summary: Online hibernate-mapping-2.0.dtd differs from dtd in jar file
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
   Versions:
             2.0.3

   Assignee: 
   Reporter: Lars Hoss

    Created: Wed, 8 Oct 2003 5:11 AM
    Updated: Wed, 8 Oct 2003 5:11 AM

Description:
The online version of the mapping dtd differs from the dtd in the jar file (hibernate 2.0.3). For example the element set has the attribute outer-join in the online version but not in the jar file version. I guess that the online version matches 2.1 beta?


---------------------------------------------------------------------
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-384) Add support for custom collection persisters

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Tue, 7 Oct 2003 2:45 PM
       Body:
Just got word from Gavin - he already has some stuff on this laptop (while driving on train to Florence ;) 

So, if you have patience a more complete impl. will be committed in the next couple of days ;)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-384


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-384
    Summary: Add support for custom collection persisters
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Max Rydahl Andersen

    Created: Tue, 7 Oct 2003 2:14 PM
    Updated: Tue, 7 Oct 2003 2:15 PM

Description:
Add support for Custom collection persisters (for eg. allowing usage of Stored Procedures to persister collections)


---------------------------------------------------------------------
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-384) Add support for custom collection persisters

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Tue, 7 Oct 2003 2:32 PM
       Body:
I've attached a rough refactor for allowing support for custom persisters.

This patch basically just make CollectionPersister an interface and introduces AbstractCollectionPersister and CollectionPersisterImpl.

At the moment all the code is still in AbstractCollectionPersister and every previously public method on CollectionPersister is part of the new interface - this probably need to be "cleaned" before the code goes into hibernate core.

Furthermore i've added methods to PersisterFactory to add support for instantiating a custom class that implements CollectionPersister.

I've also added code to Binder that shows how to configure the mapping metadata via a persister attribute (note: I have not made the necessary changes to the DTD, but that should be pretty straight forward - just add a persister attribute to all relevant collection elements)

I hope this patch illustrate what we talked about - please feel free to ask questions and even better continue 
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-384


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-384
    Summary: Add support for custom collection persisters
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Max Rydahl Andersen

    Created: Tue, 7 Oct 2003 2:14 PM
    Updated: Tue, 7 Oct 2003 2:15 PM

Description:
Add support for Custom collection persisters (for eg. allowing usage of Stored Procedures to persister collections)


---------------------------------------------------------------------
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] Updated: (HB-384) Add support for custom collection persisters

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

The following issue has been updated:

    Updater: Max Rydahl Andersen (mailto:xa...@xa...)
       Date: Tue, 7 Oct 2003 2:15 PM
    Comment:
Very rough refactor draft for showing the basic required changes needed/wanted in Hibernate (this is for you Cisco guys!) 
    Changes:
             Attachment changed to customcollectionpersister.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-384&page=history

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-384


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-384
    Summary: Add support for custom collection persisters
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Max Rydahl Andersen

    Created: Tue, 7 Oct 2003 2:14 PM
    Updated: Tue, 7 Oct 2003 2:15 PM

Description:
Add support for Custom collection persisters (for eg. allowing usage of Stored Procedures to persister collections)


---------------------------------------------------------------------
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] Created: (HB-384) Add support for custom collection persisters

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-384


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-384
    Summary: Add support for custom collection persisters
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Fix Fors:
             2.1
   Versions:
             2.1

   Assignee: Max Rydahl Andersen
   Reporter: Max Rydahl Andersen

    Created: Tue, 7 Oct 2003 2:14 PM
    Updated: Tue, 7 Oct 2003 2:14 PM

Description:
Add support for Custom collection persisters (for eg. allowing usage of Stored Procedures to persister collections)


---------------------------------------------------------------------
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] Updated: (HBI-13) Support for Custom Collection Persister

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

The following issue has been updated:

    Updater: Max Rydahl Andersen (mailto:xa...@xa...)
       Date: Tue, 7 Oct 2003 2:13 PM
    Comment:
Very first refactor draft to illustrate the basic needed changes to hibernate. (this is for you Cisco ;)

    Changes:
             Attachment changed to customcollectionpersister.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-13&page=history

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-13


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HBI-13
    Summary: Support for Custom Collection Persister
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate 1.2

   Assignee: Max Rydahl Andersen
   Reporter: Max Rydahl Andersen

    Created: Tue, 7 Oct 2003 2:11 PM
    Updated: Tue, 7 Oct 2003 2:13 PM

Description:
Add support for making it possible to provide a Custom Collection Persister.


---------------------------------------------------------------------
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] Deleted: (HBI-13) Support for Custom Collection Persister

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

Message:

  The following issue has been deleted from JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-13


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HBI-13
    Summary: Support for Custom Collection Persister
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate 1.2

   Assignee: Max Rydahl Andersen
   Reporter: Max Rydahl Andersen

    Created: Tue, 7 Oct 2003 2:11 PM
    Updated: Tue, 7 Oct 2003 2:13 PM

Description:
Add support for making it possible to provide a Custom Collection Persister.


---------------------------------------------------------------------
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] Created: (HBI-13) Support for Custom Collection Persister

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HBI-13


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HBI-13
    Summary: Support for Custom Collection Persister
       Type: New Feature

     Status: Assigned
   Priority: Major

    Project: Hibernate 1.2

   Assignee: Max Rydahl Andersen
   Reporter: Max Rydahl Andersen

    Created: Tue, 7 Oct 2003 2:11 PM
    Updated: Tue, 7 Oct 2003 2:11 PM

Description:
Add support for making it possible to provide a Custom Collection Persister.


---------------------------------------------------------------------
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] Created: (HB-383) websphere 5 transaction manager lookup

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

Message:

  A new issue has been created in JIRA.

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-383


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-383
    Summary: websphere 5 transaction manager lookup
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1 beta 4

   Assignee: 
   Reporter: Edina Pimp

    Created: Tue, 7 Oct 2003 11:54 AM
    Updated: Tue, 7 Oct 2003 11:54 AM
Environment: WebSphere Platform 5.0 [BASE 5.0.2]; Win2k; WSAD; JDK1.3.1

Description:
Newest version of the WebSphereTransactionManagerLookup fails under WebSphere 5.  Class com.ibm.ejs.jts.jta.JTSXA - which is the default class - remains available in the classpath so it's found and Hibernate assumes a WAS4 environment.

When 'getTransactionManager' is invoked on the WAS5 version of JTSXA, a NoSuchMethod exception is thrown, caught, and rethrown as a HibernateException.  The correct method is instance().

This worked in 2.1b3 because the exception handling just happened to line up the right way.

Maybe it's reasonable to break out different WebSphere4TransactionManagerLookup and WebSphere5TransactionManagerLookup classes, ugly as it sounds.

 


---------------------------------------------------------------------
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-173) Access to <meta> with the API

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Tue, 7 Oct 2003 11:47 AM
       Body:
...and if you could provide the patch as patches instead of complete files - then it would be great ;)
---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-173
    Summary: Access to <meta> with the API
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: xfgdf

    Created: Thu, 10 Jul 2003 7:21 AM
    Updated: Tue, 7 Oct 2003 11:22 AM

Description:
It would be great to access to the <meta> elements with the API. Something like :

String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...

May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.

        Adrien






---------------------------------------------------------------------
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-173) Access to <meta> with the API

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

The following comment has been added to this issue:

     Author: Max Rydahl Andersen
    Created: Tue, 7 Oct 2003 11:46 AM
       Body:
The length attribute is already available in the metadata.

The <meta> tag is not - and i appreciate you contribution, but we should also provide <meta> tag info for non-property elements (such as classes, version, composites etc.)


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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-173
    Summary: Access to <meta> with the API
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: xfgdf

    Created: Thu, 10 Jul 2003 7:21 AM
    Updated: Tue, 7 Oct 2003 11:22 AM

Description:
It would be great to access to the <meta> elements with the API. Something like :

String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...

May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.

        Adrien






---------------------------------------------------------------------
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-173) Access to <meta> with the API

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

The following comment has been added to this issue:

     Author: xfgdf
    Created: Tue, 7 Oct 2003 11:24 AM
       Body:
As I said in the forum, I post here some modifications to allow access to the length and the metadata of property. Hope it's could be usefull.

  Adrien

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-173
    Summary: Access to <meta> with the API
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: xfgdf

    Created: Thu, 10 Jul 2003 7:21 AM
    Updated: Tue, 7 Oct 2003 11:22 AM

Description:
It would be great to access to the <meta> elements with the API. Something like :

String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...

May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.

        Adrien






---------------------------------------------------------------------
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] Updated: (HB-173) Access to <meta> with the API

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

The following issue has been updated:

    Updater: xfgdf (mailto:sa...@ho...)
       Date: Tue, 7 Oct 2003 11:22 AM
    Changes:
             Attachment changed to AbstractEntityPersister.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173&page=history

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-173
    Summary: Access to <meta> with the API
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: xfgdf

    Created: Thu, 10 Jul 2003 7:21 AM
    Updated: Tue, 7 Oct 2003 11:22 AM

Description:
It would be great to access to the <meta> elements with the API. Something like :

String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...

May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.

        Adrien






---------------------------------------------------------------------
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] Updated: (HB-173) Access to <meta> with the API

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

The following issue has been updated:

    Updater: xfgdf (mailto:sa...@ho...)
       Date: Tue, 7 Oct 2003 11:12 AM
    Changes:
             Attachment changed to ClassMetadata.java
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173&page=history

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

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-173


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-173
    Summary: Access to <meta> with the API
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Hibernate2
 Components: 
             core

   Assignee: 
   Reporter: xfgdf

    Created: Thu, 10 Jul 2003 7:21 AM
    Updated: Tue, 7 Oct 2003 11:12 AM

Description:
It would be great to access to the <meta> elements with the API. Something like :

String ClassMetaData.getClassMetaTag(String key);
String ClassMetaData.getPropertyMetaTag(String property, String key);
String ClassMetaData.getCollectionMetaTag(String role, String key);
...

May be their not all usefull. This would help to make our own generator (form JSP, personnal toString(), XML, etc). Hibernate mapping files could be use this way as a repository for all kind of metadata.

        Adrien






---------------------------------------------------------------------
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