Problem- java.lang.NoClassDefFoundError: javax/el/ValueExpression

Possibly
you are using different set of jars at runtime and compile time. In
case of tomcat you might be using some of the jars. Try adding jars
like el-api.jar, javaee.jar, jstl-1.2.jar from your development
environment to the Tomcat/common/lib folder, one by one and it should
solve the problem

Powered by ScribeFire.

This is continuation of my earlier post on org.hibernate.TransientObjectException. Let me write the scenario again

<class name=”com.xxx.A” table=”A” schema=”TESTSCHEMA”>
<id name=”aId” type=”java.lang.Long”>
<column name=”A_ID” precision=”29″ scale=”0″ />
</id>

…………………..
some more mapping elements
…………………..
…………………..
<many-to-one name=”bId” class=”com.xxx.B” fetch=”select”>
<column name=”B_ID” precision=”29″ scale=”0″ />
</many-to-one>

…………………..

A is referring to B using a primary key column of bId of B.

In that post I have mentioned that if B is a transient object and you don’t want to persist the value of B to A then just tell the hibernate to ignore that value by saying
update=”false” insert=”false” in the many to one mapping.

But what if you want to persist the value of foreign key in A.

Then the approach is different. You have to make sure that instance B is persistent not transient.

That is if your code says something like

A a = new A();
B b = new B();
a.setB(b);
…..
…..

session.save(a);

you are in trouble. Because B is in transient state. You have to attach b to the session.
There may be other ways of attaching this transient object to session. The approach I am following is simple. I am reading the value of B from the database using Hibernate. That way, hibernate attaches B to session and it is then a persistent object.

That is I do something like

A a = new A();
B b = session.get(B.class, new Long(1));
a.setB(b);
…..
…..

session.save(a);

I won’t get any exception because this time there is no transient object to save. All the objects are persistent.

Powered by ScribeFire.

Spring transaction management, Hibernate transaction management in Spring

There was a problem/defect in the MyEclipse tutorial on Hibernate Spring. It was not a major problem. The tutorial demonstrates the Spring and Hibernate functionality pretty well. The only problem was that the code does seems to work properly. Because of absence of proper transaction management in code the data was not getting persisted in the database. Because of the caching in Hibernate it seems to the user that the data is being written to the database and then read back.

There are two solutions to the problem. One is to write the transaction management code in the java class itself. Another is to manage transaction via Spring’s transaction management. The second solution makes more sense because it shows of the Spring’s capability of managing transaction in Hibernate. You can see both the solutions here.

I am writing the Spring’s configuration for Hibernate transaction management again.

<?xml version=”1.0″ encoding=”UTF-8″?>
<!DOCTYPE beans PUBLIC “-//SPRING//DTD BEAN//EN” “http://www.springframework.org/dtd/spring-beans.dtd”>

<beans>
<bean id=”sessionFactory”
class=”org.springframework.orm.hibernate3.LocalSessionFactoryBean”>
<property name=”configLocation”
value=”file:src/hibernate.cfg.xml”>
</property>
</bean>
<bean id=”userDAOTarget” class=”com.myeclipse.hibernatespring.UserDAO”>
<property name=”sessionFactory”>
<ref bean=”sessionFactory” />
</property>
</bean>
<bean id=”userDAOService” class=”org.springframework.transaction.interceptor.TransactionProxyFactoryBean”>
<property name=”transactionManager” ref=”transactionManager”/>
<property name=”transactionAttributes”>
<props>
<prop key=”add*”>PROPAGATION_REQUIRED</prop>
<prop key=”update*”>PROPAGATION_REQUIRED</prop>
<prop key=”delete*”>PROPAGATION_REQUIRED</prop>
</props>
</property>
<property name=”target”><ref local=”persistenceLayer”/></property>
</bean>

<bean id=”persistenceLayer”
class=”com.myeclipse.hibernatespring.PersistenceLayer”
abstract=”false” singleton=”true” lazy-init=”default”
autowire=”default” dependency-check=”default”>
<property name=”userDAO”>
<ref bean=”userDAOTarget” />
</property>
</bean>
<bean id=”transactionManager” class=”org.springframework.orm.hibernate3.HibernateTransactionManager”>
<property name=”sessionFactory”><ref bean=”sessionFactory”/></property>
</bean>
</beans>

I had really a very tough time today while installing MySQL on vista. All the steps in the installation are simple and self-explanatory. I just want to mention two things from my experience

Before starting installation

1) If you want to install MySQL after uninstall your current MySQL fuly and properly. After uninstallation you should manually delete the installation folder at c:\Program Files\MySQL or at any location your MySQL is installed.

2) Turn off UAC(the nasty part of Windows Vista)

3) Turn off Windows Firewall.

4) Restart your PC.

5) Try now. This time the installation should be smooth and easy

Today I got this error.

ORA-01747: invalid user.table.column, table.column, or column specification.

There could be many reasons why you can get this error. But the basic reason is the query which is finally getting executed to your database is wrong in some way. In my case, I had a column with column name as DESC. I got rid of this problem by simply dropping the table and creating a new one with column name DESCRIPTION instead of DESC. You may not be able to do that if the table is already existing with many records in it.

Other reason could be that, if you are using named query your named query is not syntactically right.

No matter how the you get this error or for that matter any DB error in Hibernate, the best approach is to enable the show_sql variable in hibernate configuration and get the final query which hibernate is firing against the database.

Get this query and try running it directly in your database client. You can easily find out the culprit part of the query from there. Once you find out root cause of the problem you can think of workarounds or solution for this problem.

And yes, don’t forget to turn off the show_sql parameter after you are done with it. It will unnecessarily clutter your logs.

When you query the database in Hibernate using NamedQuery you may run into this error

org.hibernate.QueryParameterException: could not locate named parameter [parm1]

Chances are that you are either trying to set a parmeter to the query which infact doesn’t exist in your query. For example

you are trying to do

query.setParameter(”parm1″, new Long(parm1Value));

whereas, in query there is no parameter like parm1

i.e. query might be just “from Item item”

Or you might be committing some spelling mistake in your code

Eg. query.setParameter(”pram1″, new Long(parm1Value));

and query is “from Item item item.desc like :parm1″

Do note that your parameter name in Java Class is misspelt as pram1 instead of parm1.

AJAX(Asynchronous JavaScript + XML) got its name because of its ability to interact asynchronously. This makes Ajax famous for the Rich Internet Applications aka RIAs.

But sometimes you purposefully need synchronization in your code. I needed it once. I was calling the same business method consecutively from my ajax code for two different fields. Even after synchronizing the business method and making it thread safe,I was not able to guarantee that the first method was fully finished before the second starts. Sometimes the first DWR call was processing the returned values and in the meantime second DWR call will return and mess with the original returned values. I had to synchronize the calls to make sure that both the calls get fired and completed in a proper order.

Starting from DWR1.1 you can synchronize your method calls at various levels.

I synchronized at the method level. My normal ajax code looked like myBusinessManagerImpl.getValues(’param1′, setValuesInDWR);

Where

myBusinessManagerImpl - business layer class

getValues - the method called by Ajax

param1 - the parameter passed to the business method

setValuesInDWR - the function variable, which was defined somewhere in the code like

var setValuesInDWR = function(data){
//….DWR Code…..
};

To make the method calls synchronized I modified the method call like this

myBusinessManagerImpl.getValues(’param1′, {callback:setValuesInDWR, async:false});

This way I was able to make two consecutive calls to the same method synchronously.

Have you ever wondered why the addOptions is not working in DWR even after reading the specs carefully. It happened to me recently. First, of all, the API or specs or documentation for DWR(addOptions Documentation) are not detailed and sufficient. Especially, for the new and impatient learners like me, who don’t want to go through each and every page of the spec before using the technology. Second, if you are impatient and new learner then probably you might have missed some of the part. Problem: I was trying to populate the Select box from a list of Objects using the addOptions method of DWR. I have followed the documentation fully but my drop down was not being populated. (It was my second day with DWR so I didn’t know some of the complexities which ultimately solved the problem)

Solution:- I will take one example to explain this Let your select field something like this



<select id=”statesList” />



And the class whose list of Objects you are trying to add is something like this



package testPackage.dwr;
public class State{
private String stateId;
private String stateName;
…………
//getter and setter methods
…………
}



and you want to populate this using DWR after some user action. Make sure that your callback function looks like this



var setValuesInDWR = function(data){
var fieldId = ’statesList’;
var valueText = ’stateId’;
var nameText = ’stateName’;
dwr.util.removeAllOptions(fieldId);// step 1
dwr.util.addOptions(fieldId, data, valueText, nameText);//step 2
};


All the above steps are important

Step 1 - Actually removes the already existing values from your select list. If you don’t do this. the addOptions method will simply append the list.

Step 2 - This will actually add the values to the drop-down list.

I forgot/missed/didn’t know that you have to add the following line in dwr.xml

<convert converter=”bean” match=”testPackage.dwr.State”/>

Reason is, unless you don’t explicitly specify in your dwr.xml the user defined beans will not be converted in DWR. If your bean consists of supported datatypes which DWR can automatically convert then you can just add this declaration. After following all these steps carefully the problem of Dropdown not getting populated in DWR should be solved.