• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WSAD / Optimistic Update Failed Exception

 
Ranch Hand
Posts: 208
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'm getting the following exception and I don't understand why:



This is the case: In my SessionBean, I have two methods, one called createRuntimeDependency and one called createRuntimeParameter, similar methohds which both create CMP entity beans and return similar resultObjects. The problem is, createRuntimeDependency throws the exception, whereas createRuntimeParameter works just fine.

Debugging reveals that the exception is not thrown from the entity beans, or from the session bean that calls them, but from a WSAD-generated stub of an EJSfacade-bean which extends com.ibm.ejs.container.EJSWrapper.

I have checked all property-files I cah think of, gone through the deployment descriptor, and am at a loss at where to look next.

I'm using WebSphere Studio Application Developer (Windows) Version: 5.1.2
Build id: 20040506_1735 and database is Teradata
[ September 08, 2005: Message edited by: �dne Brunborg ]
 
Ådne Brunborg
Ranch Hand
Posts: 208
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Problem solved.

Added



to "Resource properties defined in the data source selected above" under Node Settings in Data Source in the Test Environment, in case anyone else comes across the problem. Phew!

Apparently someone have used a scandinavian character (������) somewhere...
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic