-
1. Re: Remoting, first call good, second call bad!
shane.bryzak Sep 18, 2010 9:57 AM (in response to notify)Hmm, could the JavaScript stub for your component possibly be cached? What does it look like when you browse directly to it?
-
2. Re: Remoting, first call good, second call bad!
notify Sep 24, 2010 7:17 AM (in response to notify)How would I browse directly to the WebRemote method?
-
3. Re: Remoting, first call good, second call bad!
lvdberg Sep 24, 2010 11:28 AM (in response to notify)Hi,
As the previous hint states, clear your cache under the configuration menu of your browser. I've had similar problems while adding functions to beans or changing styles in pages and in most caches refreshing/clearing helps.
Leo
-
4. Re: Remoting, first call good, second call bad!
notify Sep 24, 2010 11:35 AM (in response to notify)I clear it everytime in IE and also the various tmp directories in JBoss. It doesn't make a scrap of difference!
What is weird that the same web page (XHTML) calls method1 in EJB1 but it just ignores call method2 in the same EJB1.
-
5. Re: Remoting, first call good, second call bad!
lvdberg Sep 24, 2010 3:05 PM (in response to notify)Hi,
I am not a javascript/webremote expert, but I see you are calling a remote Seam component from within another Seam component. Maybe there things go wrong? (the locationCallback), Can you test (with dummy data) if the second method is called correctly WITHOUT calling it from the first method?
Leo
-
6. Re: Remoting, first call good, second call bad!
notify Sep 25, 2010 6:11 AM (in response to notify)
Leo van den Berg wrote on Sep 24, 2010 15:05:
Can you test (with dummy data) if the second method is called correctly WITHOUT calling it from the first method?Thanks for your suggestions.
I need to call the second method from the CallBack. However .....
I moved the the (2nd.) method I need to call to a new Session EJB and it worked!
So it may/must be calling a method from a CallBack to an EJB that has already been called?
Regards.
-
7. Re: Remoting, first call good, second call bad!
lvdberg Sep 26, 2010 3:28 AM (in response to notify)Hi,
You basically have to deal with the same restriction as within java code: You can´t intercept a already intercepted bean. There are possibilities to find/call components directly but I don't think that's usable for webremote calls.
Leo