Web Remote: Annotated method has no JS stub.

[haefti]

Hi!
I have a problem using web remote.

My goal is to have a button which is supposed to open a browser window but only if a bean member has a specific value.
To achieve this I would like to use web remoting. I call a javascript method which makes a call via web remote and decides if it is allowed to open depending on the return value.

I annotated the method on the interface, added the seam-remoting.jar but I do not get a javascript stub for the annotated method.

I even tried it with the sayHello() example but I have the same effect.

My code:

The interface:

@Local
public interface GalleryManagerLocal extends AssetManagerLocal {
        @WebRemote
        public String sayHello(String name);

        // some other methods
}

The session bean:

@Stateful
@Name("galleryManager")
public class GalleryManager extends AssetManager implements GalleryManagerLocal {

        @WebRemote // tried with or without
        public String sayHello(String name) {
                return ("\"Hello World\" von " + name);
        }

        // some other methods
}

The generated interface.js?galleryManager:

Seam.Remoting.type.galleryManager = function() {
  this.__callback = new Object();
}
Seam.Remoting.type.galleryManager.__name = "galleryManager";

Seam.Component.register(Seam.Remoting.type.galleryManager)

Calling

function sayHello() {
        var name = prompt("Name");
        Seam.Component.getInstance("galleryManager").sayHello(name, sayHelloCallback);
}

alway leads to Seam.Component.getInstance(galleryManager).sayHello is not a function

What can I do to get the annotated methods beeing included in the interface.js?
It seems like the annotation is not read.

Thanks!

Michael

[shane.bryzak]

Where did you put seam-remoting.jar?

[haefti]

I put it in ear/lib. (using exploded archive)

I also tried it in /WEB-INF/lib of the WAR file but as I read here

http://seamframework.org/Community/TroubleWithWebRemoteSeam21

it has to be in the EAR.

Is there something special about SFSB because the example uses a SLSB?

[shane.bryzak]

That's the right place.  Could you set a breakpoint in InterfaceGenerator.appendComponentSource() to see what's going on?  Especially the iteration at line 336.

[haefti]

Thanks!
It seems to be a strange caching problem.

Removing the deployed stuff from the JBoss and the exploded-archives directory did help but only until the next deploy.

It's irreproducable when I get the right interface.js but in fact I saw that it could work. ;)

Anyway thanks for the help!