Reproducing error :
Deploying process were fine. Seems no problem at all.
But, when i start the application and login to it -which did a database process-, it threw ClassNotFoundException.

org.springframework.orm.hibernate3.HibernateQueryException: ClassNotFoundException: org.hibernate.hql.ast.HqlToken

This error threw when I was utilizing any HQL things.
The conflicting antlr.jar files seem to be the cause of the problem.

There is a conflict between antlr.jar which is included in the TopLink folder of the oc4j distribution and antlr-2.7.6.jar in my application library classpath which is used by Hibernate.

It seems OC4J prioritize to use the TopLink version.

Two solving solutions :
1. Unless you are using toplink, just delete the entire toplink folder. (avoid this one !)
2. Doug Clarke show me the better one :
The better solution for handling conflicts between TopLink and other libraries when TopLink is not being used
is to remove it as a shared library for you application.
- Modify orion-application.xml under web-apps’ application-deployments folder.
This can be done by adding with the following:

<imported-shared-libraries>
<remove-inherited name="oracle.toplink"/>
</imported-shared-libraries>

- Restart OC4j instance.

It worked like a charm.

Different approach solution in production environment by oreo_masta.
Above configuration worked out slick for OC4J standalone server.
When it came time to deploy to OAS production server, the configuration did not stick.
Follow this instructions of this article to remove the import upon deploying time.

Environment
- OC4J 10g 10.1.3.5.0 (Standalone)
- Hibernate3
- Spring 2.5.x
- JDK 1.5

References : 1, 2

Lately i got my feet wet with jBpm.
I will write several posts about it.

v

I was using Hibernate to do some CRUD-things to AS/400 DB2 tables.
And then, i got this message error on stacktrace of the Hibernate exception :

java.sql.SQLException: [SQL7008] MY_TABLE in MY_DATABASE not valid for operation.

After googling by using the error codes.
Got the clue that i was dealing with the object journal issue.
It’s like, you must journal the table before you do some CRUD-things on it.

It says that you should did some kicking-ass AS/400 commands for journaling table :
1. Create the journal receiver by using the Create Journal Receiver (CRTJRNRCV) command, as follows:

CRTJRNRCV JRNRCV(LIB_NAME/JOURNAL_RECEIVER_NAME) THRESHOLD(100000) TEXT('PUT_WHATEVER_TEXT_DESC_HERE')

2. Create a journal for your object file by using the Create Journal (CRTJRN) command:

CRTJRN JRN(LIB_NAME/JOURNAL_NAME) JRNRCV(LIB_NAME/JOURNAL_RECEIVER_NAME) MNGRCV(*SYSTEM) DLTRCV(*YES) TEXT('PUT_WHATEVER_TEXT_DESC_HERE')

3. Start journaling the physical file by using the Start Journal Physical File (STRJRNPF) command:

STRJRNPF FILE(LIB_NAME/TABLE_SYS_NAME) JRN(LIB_NAME/JOURNAL_NAME) OMTJRNE(*OPNCLO)

Voila. It solved.

Since i’m not an AS/400 engineer, i did not write the detail about AS/400 commands that i was used above. Feel free to google it.
And again, Google has saved my weekend.

v

Did anyone here ever set Timezone properties for Java Webstart application ?

I’ve tried it using VM argument ‘user.timezone’. And yes, it was going smoothly when i tested it as an standalone Java application argument (using -Duser.timezone).

But, when it was applied at JNLP script, it did nothing. It didn’t change application timezone to my pre-define ‘user.timezone’ value. Still using my OS timezone. It seems JNLP ignored that properties.

FYI, i was using JRE 1.4.2.05.

I prefer modifying the JNLP script rather than modifying the java code, since i do not need to build a new jar file for my app. But it seems it didn’t work unless i modify the java code.

So, I added this code to the main class which was loaded in a first priority.

TimeZone.setDefault(TimeZone.getTimeZone("Asia/Bangkok"));

And it worked. No matter what type of timezone was set in client terminal, our apps still using the new-predefined one.

I think the “user.timezone” is considered as an ’something-unsafe’ property and can not be set by JNLP script.

It seems there is a bug in the previous version of JRE 1.5 due to this link.

Hi lad.

Welcome to victoroctavski.wordpress.com.

This is my first post.

I modify this post from the default one.

Let see if i can blog faster than my shadow.