-
15. Re: Deploying Seam (Servers and Runtimes)
I installed WTP 2.0.2 in my 3.3.2 Eclipse, but I got the same error. So there is still some other issue.
-
16. Re: Deploying Seam (Servers and Runtimes)
I meant to say I installed the patch for WTP 2.0.2, but it didn't work.
-
17. Re: Deploying Seam (Servers and Runtimes)
Hi redbird:
I haven't gotten to play with your drop yet, but I will today. WTP 2.0.2 is the broken wtp and wtp 2.0.1 is the one which SHOULD work.
I feel that your problem may be different but i'm not sure yet. I'll be looking into it today. -
18. Re: Deploying Seam (Servers and Runtimes)
Thanks Rob. I just did one more test. I removed the jar files from the modules in the application.xml. I saw where you had said this is a workaround for the WTP problem. That actually got the project to deploy within Eclipse with no errors.
However when I changed the project to deploy outside of eclipse, it still didn't work. Nothing was copied over. So there does appear to be some issue with that. Maybe it's related to WTP too. Or some configuration problem.
I do have one question I hope you can answer. How do you downgrade the WTP version from 2.0.2 to 2.0.1? Is that even possible? -
19. Re: Deploying Seam (Servers and Runtimes)
redbird:
you'd basically have to go in to your plugins folder and delete any of the 2.0.2 plugins / patches. It's a long tedious process as far as I know.
I know this is easier said for someone like me (who installs eclipse once or twice a day) but you could just unzip / untar / whatever a new build. This sounds like a lot of trouble, (and it is, i'm not going to pretend it isn't a hassle), but you could still make sure you use the same workspace so you don't need to reset all your preferences and stuff.
Good luck. I'm heading to the office now to pull my 8 or 9 hours =] -
20. Re: Deploying Seam (Servers and Runtimes)
However when I changed the project to deploy outside of eclipse, it still didn't work.
redbird: What exactly do you mean by "deploy outside of eclipse"? This confuses me. -
21. Re: Deploying Seam (Servers and Runtimes)
I probably should say running JBoss outside of Eclipse (deploy only). That's what I meant by deploying outside of Eclipse. When I run JBoss within Eclipse, it seems to deploy the files correctly (after I deleted all the jar module statements in the application.xml). But when I run JBoss outside of Eclipse, nothing is deployed when I build it or try and run it.
-
22. Re: Deploying Seam (Servers and Runtimes)
It now seems that, even running JBoss within Eclipse, it only deploys the application the first time I build it and do a Run As/Run on Server. If I change code, it does not redeploy. I have to shut down JBoss, and redo the whole procedure to get the new code to be picked up.
-
23. Re: Deploying Seam (Servers and Runtimes)
Hi redbird:
Browsing the code, it only autopublishes if the server is "started". I realize the deploy-only server doesn't NEED to be started (as it wouldn't effectively start anything =P ) and in fact, clicking run on the deploy-only server will do nothing at all other than set its state to started.
So try that. If the state is started, it will try to autopublish on any changes. I realize it's kinda silly but that's how it works ;)
The alternative is to click on the "publish" icon in the servers view or jboss servers view whenever you want to publish. -
24. Re: Deploying Seam (Servers and Runtimes)
Hey Rob,
That's the exact opposite of the behavior I'm seeing. If the JBoss server is running, no code updates ever get published. I can change the code and rebuild everything, but nothing gets deployed. I have to stop the server, then restart it to get any code changes published (and nothing publishes at all if JBoss is running outside of Eclipse).
How do you get to the servers view or jboss servers view? Maybe I can click on the "publish" icon to do what I need. I just don't know where it is. Thanks. -
25. Re: Deploying Seam (Servers and Runtimes)
I found the JBoss server views. However, I get the same behavior. If the server is already started, nothing gets published. I tried using the Publish button, but nothing happened. In order to get new code to JBoss, I still have to stop the JBoss server, then do a Run As/Run On Server for the new code to get picked up. At least I have a workaround, but it takes a long time to check out new code changes.
I'm still thinking there must be something wrong in my environment. -
26. Re: Deploying Seam (Servers and Runtimes)
hey redbird:
In hte JBoss Server's view, you can click on your server and expand hte "Event Log" to see what's being published and when. (you may need to right-click on "Event Log" and click "refresh" after a publish.)
Then you can click the publish icon and see what's happening. Any errors will be displayed there and it should tell you how many files it's publishing, how many files were changed, etc. -
27. Re: Deploying Seam (Servers and Runtimes)
Okay. Thanks. I'm deleting everything and starting over. There is something messed up in my environment. I'll give this a shot.