kwame Iwegbue

Sorry, dumb question. Its supposed to say:

<fmt:formatDate dateStyle="medium" type="both" value="${actionBean.time}" timeZone="[B]US/Eastern[/B]"/>

I need some help.

I have this code:

<fmt:formatDate dateStyle="medium" type="both" value="${actionBean.time}" timeZone="EST"/>

this displays: Nov 2, 2007 1:30:21 PM

Unfortunately it is 1 hr off! The correct time should be Nov 2, 2007 2:30:21 PM

if I change the timeZone attribute to "EDT", it's: Nov 2, 2007 6:30:51 PM

Any thoughts?
[ November 02, 2007: Message edited by: kwame Iwegbue ]

I'm new to Spring, but i've read a lot of documentation, but still can't figure this one out. need help from anyone with experience with @Transactional using <tx:annotation-driven>

I have this:
... <bean id="transactionManager" class="org.springframework.orm.hibernate3.HibernateTransactionManager"> <property name="sessionFactory" ref="sessionFactory"/> </bean> <tx:annotation-driven/> ...



"sessionFactory" is correctly defined.
Then my service class (Which uses Hibernate 3.1) has this:


... @Transactional(propagation=Propagation.REQUIRES_NEW, readOnly=true) public User getUserByUsername(String username) { return ((User) getSession() .[B]createQuery[/B]("from User u where u.username like :un") .setString("un", username) .setMaxResults(1) .uniqueResult()); } ...


then this is from the stack trace:


... 09:51:11,491 ERROR AutoHandler:30 - createQuery is not valid without active transaction org.hibernate.HibernateException: [B]createQuery is not valid without active transaction[/B] at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:297) at $Proxy39.createQuery(Unknown Source) at net.ehosp.model.daoImpl.UserDAOHibernate.getUserByUsername(UserDAOHibernate.java:61) at net.ehosp.controller.LoginActionBean.login(LoginActionBean.java:136) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


Any ideas? is this a problem with hibernate?

I have a new remote mysql database, and I would like to run an Ant target from my local machine to build a hibernate database schema on the remote site.
my jdbc settings are something like:

<!-- Settings for a MySQL database (on <a href="http://www.domain.com%29" target="_blank" rel="nofollow">www.domain.com)</a> --> <property name="dialect">org.hibernate.dialect.MySQLInnoDBDialect</property> <property name="connection.driver_class">com.mysql.jdbc.Driver</property> <property name="connection.url">jdbc:mysql://domain.com/db_name</property> <property name="connection.username">un</property> <property name="connection.password">pw</property>

but I keep getting this error:

[hibernatetool] Error #1: java.sql.SQLException: Connections could not be acquired from the underlying database!

I know the database exists, and that I have the right un and pw. this tools works fine when building the schema on localhost on my machine.
any ideas please?

I agree with you about detached objects, but my feeling was that with Open Session in View Pattern (which is what I'm using) , the persistence-context (unit of work) is wrapped by the request-responce cycle (in a servlet filter) so you application objects never get detached on their own, unless I close the persistence context prematurely. So I'm not sure this is the problem.

The Code for my VisitDAO is

public class VisitDAOHibernate extends GenericHibernateDAO<Visit, Long> implements VisitDAO { ...

the actual method is from GenericHibernateDAO, which is

public class GenericHibernateDAO<T, ID extends Serializable> implements GenericDAO<T, ID> { ... @SuppressWarnings("unchecked") public T findById(ID id, boolean lock) { T entity; if(lock) entity = (T) getSession() .load(getPersistentClass(), id, LockMode.UPGRADE); else entity = (T) getSession() .load(getPersistentClass(), id); return entity; }

The rest of the methods in the DAO are simply database queries.

detached huh?, Well I'm using the Open session in View pattern, i.e the whole request-response cycle is wrapped in a Hibernate Session. So I guess it could be detached after the delete method exits or something. But why would that be a problem. Do I need to re-attach it after the loop or what?

Post sample of your Person class. I think Hibernate will use all the properties to make the composite key. Therefore they should be not null, unless you use idbag.

Thanks.
All other properties of the containing Entity (Visit) are managed correctly by hibernate, including other Collections, which are Collections of Entities mapped by one-to-many association. Even this particular troublesome Collection of Value type objects (Diagnoses) is managed correctly in every way, except when it comes to delete. According to everything I've read so far, removing a Value type object from a Collection should cause it to be deleted as well.

visitDAO is a data access object that loads the Entity, Visit from the database.

Has no one out there using Hibernate, run into this type of situation that I describe in this question, or is it still unclear what I'm asking, or is it just a dumb question. Can some hibernate guru please help me with this!!

Here's whats going on:

@Entity @org.hibernate.annotations.Entity(dynamicInsert = true, dynamicUpdate = true) @Table(name = "VISIT") public class Visit implements Serializable { @Id @GeneratedValue @Column(name="VISIT_ID") private Long id; ... @org.hibernate.annotations.CollectionOfElements @JoinTable(name = "DIAGNOSES", joinColumns = @JoinColumn(name = "VISIT_ID")) private Set<Diagnosis> diagnoses = new HashSet<Diagnosis>(); ...

So Visit is an Entity (has database identity) and Diagnosis is a Value type (has no database identity).

I can manage a Visit object with

getSession().saveOrUpdate(visit); getSession().delete(visit);

However, this won't work with Diagnosis. So if I want to delete a DIagnosis object, which is in a Set that is mapped to a Visit object, I do this:

... Visit v = visitDAO.findById(getVisit_id(), true); Set<Diagnosis> diagnoses = v.getDiagnoses(); for (Iterator iter = diagnoses.iterator(); iter.hasNext(); ) { Diagnosis element = (Diagnosis) iter.next(); v.getDiagnoses().remove(element); } ...

So this works, and removes the Diagnosis from the Collection, however, when Visit is loaded again, the "deleted" Diagnosis is still present in the Collection!
[ August 23, 2007: Message edited by: kwame Iwegbue ]

Can someone please help with this problem. Its been over a week, and I still can't figure it out. Let me rephrase the question:
Is there a special way of handling Collections of objects in Hibernate, when those objects do not have a database identity. I know that Objects with identiy, mapped in a Collection with *-to-many, are managed by the Hibernate session and can be removed by session.remove() etc; but how about regular objects?

When I try to remove them like from the Collection, they are reloaded from the database when the Collection is again accessed. Please help!!!
[ August 22, 2007: Message edited by: kwame Iwegbue ]

I think I've found the solution.
Someone had a similar issue on this forum, and they are using
Ostermiller utils

I'm going to give it a shot.
[ August 22, 2007: Message edited by: kwame Iwegbue ]

I'd like some help with parsing a csv file to put the info into a database. I have some crude way of doing this using StringTokenizer and then persisting the fragments one by one. I was wondering if there is a more elegant way to do this, since my technique might lead to corrupted data.

Thanks.

Thanks Shailesh,

The thing is, the Diagnoses object is not an entity, but a Collection of value types without a database identity. They are embedded in another class, which is an Entity. When I remove one of the objects in the List, it is deleted from the List as expected, but when the List is called from the JSP, it is again loaded from the database. How can I overcome this? I can't call session.delete() because I dont want to delete the Entity.
[ August 16, 2007: Message edited by: kwame Iwegbue ]

In that case you can initialize the List with a call like myList.size() or something like that. That would usually load the Collection from the database. Or, you can change the class mapping to make it eager loaded. With Annotations, you would write something like this:

//This code goes in the Entity class @Entity("myclass") @Table("MY_CLASS") public class MyEntity { ... private Long id; ... @OneToMany(mappedBy = "myclass", cascade = { CascadeType.ALL }, fetch = FetchType.EAGER) List<MyCollection> coll = new ArrayList<MyCollection>(): ... }