There are two types of client stub that can be generated, "executable" stubs and "type" stubs. Executable stubs are behavioural, and are used to execute methods against your session bean components, while type stubs contain state and represent the types that can be passed in as parameters or returned as a result.
The type of client stub that is generated depends on the type of your Seam component. If the component is a session bean, then an executable stub will be generated, otherwise if it's an entity or javabean, then a type stub will be generated. In your example, the component type that would be returned by Seam.getComponentType() for your class is JAVA_BEAN (ie, its not a stateless or stateful session bean, nor an entity bean). So the default client stub that would be generated for this is a "type" stub (ie something that can contain state). I'll ask Gavin if I should change the rules used to determine the stub type. It wouldn't be difficult to test for the existence of the @WebRemote annotation on any of the bean's methods, and if it exists to create an executable stub instead of a type stub. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3938020#3938020 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3938020 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
