[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-3453) Deployed jar list files needed to be modified for remoting to work correctly in a newly generated project.

Deployed jar list files needed to be modified for remoting to work correctly in a newly generated project. ---------------------------------------------------------------------------------------------------------- Key: JBSEAM-3453 URL: https://jira.jboss.org/jira/browse/JBSEAM-3453 Project: Seam Issue Type: Bug Affects Versions: 2.0.2.CR2, 2.0.2.GA, 2.0.2.SP1, 2.0.3.CR1, 2.1.0.A1, 2.1.0.BETA1 Reporter: Jeremy Fox Assignee: Pete Muir Priority: Minor Fix For: 2.1.0.CR1 If you create a new project via seamgen right now, there are extra steps needed to get remoting working properly. There are some changes needed in the deployed-jars-ear.list and the deployed-jars-war.list files that were added to clean up the generated build script. There is no mention of this in the documentation, and the origin of the issue and it's solution can be tricky to spot. In the deployed-jars-war.list, I changed the line that read "jboss-seam-*.jar" and just put in "jboss-seam-ui.jar" in it's place. In the deployed-jars-ear.list, I added "jboss-seam-remoting.jar". Before making this change, when I tried to use seam remoting, I would get an empty stub with no methods. (The @WebRemote methods just didn't show up, so I got the "xxx is not a function" error from my Javascript. That is what makes it hard to diagnose.) I looked at how the remoting examples were packaged (because they did work correctly for me in 2.1.0 BETA, while my own application did not), and this is where those classes were placed by their respective build scripts. It is likely that other files should be included for general use, but I am unsure about what should be there. For reference, the list files were added to clean up the build script in JBSEAM-2897. According to 2897, 2.1.0.BETA1, 2.0.2.CR2 both had the list files added to them.