hmm - you should be able to create the project and then deploy it to another server - but be aware there might be some configuration files that needs changing.
Have you tried using a more uptodate version of JBoss Tools ?
Cool, is that all there is too it ?
would have assumed some config changes were needed to actually having it working when deploying !?
Well actually there are some additional configurations we needed to do in order to actually get the code to run. Mind you we're just exploring Seam at the moment, and haven't tried to deploy it anywhere other than a local WAS server yet, but the attached info seems to work fine locally.
cool Eric - thanks for taking the time to write these up!
I assume the reference to psu-base.jar and xmlrpc-2.0.jar is something you just need for your own apps and not seam related?
btw. besides the need for putting @JndiName on every ejb (yuck! how come?) it looks like things can work well for you guys!
The JndiName you could probably work around by updating the templates for it in the seam-gen directories? then you at least don't have to manually type it in everytime.
You're correct about the psu-base.jar and xmlrpc-2.0.jar being specific to our code base.
I'm not certain of the deatails of the @JndiName entry other than it was needed to work. I think it has something to do about a differencec between how WebSphere looks up EJBs vs other containers.