On the Web As side, I have created an RFC-enabled function named "Z_sampleBean" which I am attempting to call. This a stateless session bean which has been successfully deployed, and the RFC destination has been set up correctly and tests ok.
The JNDI directory contains an entry at the root level for the bean name. (Visual Administrator display shows a little red box icon and under that entries for [class name] and [object value] - not sure what the icons or the specific entries mean...)
When I make the ABAP call to the JCO Provider Service, I get a dump as shown in the subject line.
Is JCO.server saying he can't find it in the JNDI directory, or that he can't find it in the Web AS repository?
I feeel like I must be missing something pretty obvious, but I don't know what.
I note that case is apparently preserved across the RFC call - are there any case considerations?
Any ideas?
8 Answers
-
Former MemberPosted on Jul 23, 2004 at 08:57 PMThanks, Piers - I'll change some stuff to se if it makes any difference. However, I not the the JCO.Server reported his problem in mixed case, so he apparently saw upper and lower?
I'll change everything in sight to upper and we'll see what happens.
Add comment
-
Former MemberPosted on Jul 23, 2004 at 10:10 PM
I changed everything in sight to upper case (but I still don't think that's necessary - I'm just too lazy to find the correct combination of JNDI names, functions names in ABAP, bean names, etc.) and he now appears to find the bean in the JNDI.
However, it now complains that the bean is of the wrong type, because it doesn't have a 'processFunction' method. However, I'm sitting here looking right at it - it's a method on the bean class. Am I missing something simple?
Add comment
-
Former MemberPosted on Jul 24, 2004 at 01:05 AM
Well, I've regressed, so I can't test your latest suggestion.
It's my fault, of course, because I've been changing stuff around, but he seems to ignore my specification of a JNDI name in the session been specification.
It's in the ejb-j2ee-engine.xml file:
<jndi-name>Z_SAMPLE_RFC</jndi-name>
but it doesn't seem to get into the JNDI directory - either at the root or anywhere else. It's really making me mad, because I had that working ok an hour ago! Someplace, I found a secret for getting stuff into the JNDI directory, and now I can't find it!
Got any idea how to do that? Do you have to enable JNDI naming or soemthing, to get a name other than the bean name put into the directory?
Add comment
-
Former MemberPosted on Jul 24, 2004 at 03:09 AM
Well, I got it so that I have an entry in JNDI in the root, and it's all in caps, so apparetnly the TFC engine can find it when I call the RFM. (At least it doesn't ay it can't find it!)
Now it complains about not my not having a processFunction() method in my bean. This is patetnly untrue - it's there and I'm looking at it.
So I still think my problem is tied up the JNDI somehow. I'm going to start a new thread on this to see what I can find out.
Thanks for your help!
Add comment
-
Former MemberPosted on Jul 24, 2004 at 03:58 AM
Piers: I forgot to answer your question: the signature of the method I'm using is a little different than yours - it returns a JCO.Function object. However, these methods were all generated by the EJB wizard in NetWeaver Dev. Studio - I'm just tkaing them the way they were generated...
Add comment
-
Former MemberPosted on Jul 24, 2004 at 03:54 PM
Well, I've got to tell you - this is agonizing!
I've modified my bean and projects, etc. to parallel those that Piers listed. It deploys OK, but after the deployment there's NOTHING in the JNDI directory that refers to either the bean name or the JNDI name associated with the bean.
Now what?
Add comment
-
Former MemberPosted on Jul 26, 2004 at 01:20 AM
Well, with the help of all the good forum folks, I see what was happening: even though I had deployed the bean, I had to ue Visual Administrator to Start the Application. Once I did that, the appropriate entries showed up in the JNDI directory, and I was off and running.
Yee-hah!
Add comment
Add comment