Announcement Announcement Module
Collapse
No announcement yet.
HttpInvokerProxy not calling exposed bean Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • HttpInvokerProxy not calling exposed bean

    We have client-server app where the client accesses the servers services through HttpInvokerProxy .
    Recently we started getting problems.
    When logging into the client, it first asks the server for a object representing the logged in person(class Person), then getting a list of objects from the same service.

    However, there seems to be some caching or something happening.
    When trying to get this list, a castException is thrown. If the service is invoked with at method that should return a Person, it returns the same object as last time it was invoked.
    When in debug mode, the same happens if we resume to program immediately. But if we wait at the breakpoint for a little while the correct value is returned.

    In the cases where the "old" value is returned, the service is not invoked on the server side.

  • #2
    Hah!
    Never mind. This is not strange at all.
    Just a caching filter that was matching to much of the url namespace we use.

    Comment

    Working...
    X