Hmm...the remote method can throw a NamingException--just figured this out. It must have been throwing a NamingException, and trying to package up the dirContext into the exception and send it over the wire. I removed that silly exception and handled it internally, and that fixed it.
Now--I am getting a NameNotFoundException on an item I know is in the directory, so I've still got some work to do. Thanks for getting my head into gear...
-Jason
| Scott M Stark <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 06/22/2001 01:58 PM
|
To: [EMAIL PROTECTED] cc: Subject: Re: [JBoss-user] search LDAP via federated JNDI |
But the stack trace is coming from Client.java:28 which is not inside of
the JBoss server. The trace shows that your trying to return an
com.sun.jndi.ldap.LdapCtx object through an RMI call and this is failing
because a Serializable object is required. Where is the server side problem?
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 22, 2001 11:13 AM
Subject: Re: [JBoss-user] search LDAP via federated JNDI
> No, the code fragment I showed below is within the EJB. I have methods in
> my EJB which perform a directory lookup, populate a serializable value
> object and return that object to the client. (that part works fine)
>
> -Jason
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
