[SOLVED] Re: -[NSInvocation length]: selector not recognized [self = 0x30abd0]

  • Hi Jim,

    This is just to say thanks to Jim Correia. Apparently there wasn't problem
    in my code it was the
    SoapAPI which was giving the problem. So those who are reading this mail can
    take my
    given sample code as a start.

    Best regards

    S

    On 9/24/07, NSTask <nstask...> wrote:
    >
    >
    >
    > On 9/24/07, Jim Correia <jim.correia...> wrote:
    >>
    >> On Sep 24, 2007, at 4:16 AM, NSTask wrote:
    >>
    >>> Your debugging tips have been very helpful to me. I have managed to
    >>> understand the cause of problem but I do not know the solution.
    >>> What I understand is by the time passed object (_sess) using
    >>> following method =>
    >>> [client performSelector:@selector(appendMessageString:)
    >>> withObject:_sess];
    >>> reach to the client it looses its class and displays the object
    >>> class as <NSDistantObject: 0xa27e76e0>, while it should have been
    >>> my defined SOAPSESSION class.
    >>
    >> When you pass an object via DO, you typically get a proxy object
    >> (NSDistantObject) on the other side which acts as a stand-in
    >> replacement or the object and sends messages across the DO connection.
    >>
    >>> Further ahead I tried retrieving values on the client side from
    >>> this _sess variable and it worked fine [_sess
    >>> valueForKey:@"username"] but when I try to use it with soapapi
    >>> because its loosing its class reference, I can not get the soap
    >>> call working.
    >>
    >>
    >
    >
previous month september 2007 next month
MTWTFSS
          1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
Go to today