StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Open the Servers view in Eclipse so you can see your jboss server. Right click on your JBoss server and choose Add and Remove. This lets you choose which application to add to your server. </p> <p>Okay I was able to recreate the issue you have I believe. You should see the errors in the Console in eclipse. Is your console displaying anything from JBoss? I'm getting an error because my workspace has a space in it. I'm going to try to fix that and see if it works.</p> <hr> <p>I finally got this to work on JBoss 6.1. Apparently there is a bug between JBoss 6.1 and those Spring libraries the project uses the 3.0.1 libraries.</p> <p>You need to download newer libraries for Spring. You have to changes these to fix some deployment issues even after you get it to deploy to the right location. I found them all here: <a href="http://ebr.springsource.com/repository/app/library/version/detail?name=org.springframework.spring&version=3.1.3.RELEASE" rel="nofollow noreferrer">Spring 3.1.3</a></p> <p>So once I saved those, I copied them to the lib folder and removed the 3.0.1 files. The next issue I had was getting eclipse to use the right Deploy folder. I have jboss installed in c:\jboss-6.1-final. In Eclipse you have to double click on your jboss server to open the JBoss Overview Page, there is a tab at the bottom of that labeled Deployment. On that screen I had to choose, Use the JBoss deploy folder, which uses the one on my C: drive instead of the one Eclipse defines with the JBoss Tools. When you choose run on server, it should then create a folder in your c:\jboss-6.1-final\server\default\deploy folder now. </p> <p><img src="https://i.stack.imgur.com/MUcrn.png" alt="JBoss Overview/Deployment Screen"></p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload