Wednesday, May 30, 2012

oracle.jbo.InvalidOperException: JBO-25221

This is a rather simple one, but it took me an hour to finally realize what was going on.

I got this error when trying to execute a custom method on my AM from a backing bean.
To execute the method, I got the OperationBinding from the binding container and called execute on it.
When testing I got this error.

oracle.jbo.InvalidOperException: JBO-25221

The error ,message basically explains that the method could not be found or is not supported. That should have been a good indicator, but I "knew" the method existed. What happened was that I had created the binding first, then changed the method signature on the AM and the client interface, but forgot to re-create the binding. So the parameters(in my case) that the binding had no longer was available on the AM's client interface.

Another thing to note here is the use of generics.


7 comments:

  1. This comment has been removed by a blog administrator.

    ReplyDelete
  2. Substantially the article is really the best on this laudable topic. I concur with your conclusions and will eagerly look forward to your future updates.Just saying thank you will not just be enough for the wonderful lucidity in your writing.
    we buy houses fast

    ReplyDelete
  3. I remember everything I needed was in the Mail. Oracle Database Appliance Please use the Oracle Chat Help in your Oracle Cloud Account.

    ReplyDelete
  4. This is a great blog post. Thank you very much for the fantastic insight and we really appreciate the time you took to write this. Thanks again.
    Sell Home Quick San Antonio

    ReplyDelete
  5. Thanks .Give me great information .I have one serves .If you need help contact Emergency Exchange Support with me .

    ReplyDelete
  6. Appreciate your time.. this is a good catch.

    ReplyDelete