Java Embedding

Java embedding - that is is java code within the BPEL process. The main purpose for which I used this was database updates as well as logging . Updating the database was a challenge and one of the best ways is to do through the database adapters. But since I am using Eclipse & not JDev, didnt have the database adapters functionality there. As a workaround created a separate BPEL process in JDev and was successful in updating the database. However, wasnt successful in calling this BPEL process created in JDEV from the main BPEL process created in Eclipse.

Hence, ended up using java embedding as a final successful workaround.
Application database updates:
I used java embedding mostly for updating the application database through stored proc calls.

Getting values from dehydration store through api's


Logging:

Logging may be done in opmn logs or you may define your own custom log file.
Example:Using log4j (include the jar file in the lib dir)
Logger logger = Logger.getLogger( "default.com.logs.appllogfile" );
logger.info( "Info using log4j" );

Other levels of logging:
a. Info
b. Debug
c. Audit
...
...
...

Good news - Eclipse Callisto RC4 available!!!

Check it out here! Once I read more about it, I'll post another entry.

Eclipse error: The type java.lang.Object cannot be resolved. It is indirectly referenced from the required .class files

This error popped up the other day when I was copying projects from an old workspace into a new, clean Eclipse workspace. It turned out that the reason the base class java.lang.Object could not be found is because the new workspace did not have Eclipse variables set, and they were referenced by the project in the old workspace. So in the project properties Build Path JRE path. Once I created the Eclipse classpath variables and rebuilt the project, the errors went away.