[
https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug...
]
Brian Fitzpatrick commented on TOOLSDOC-250:
--------------------------------------------
If you do it backwards (i.e. import the example and then create the server), you'd
have to fix the project build path by hand (i.e. tweak the ESB and server library entries
to point to the new server)...
1. Right-click on the project, select Build Path->Configure Build Path
2. Select the Libraries tab on the "Java Build Path" property page.
3. Select the JBoss Enterprise Application Platform 5.x Runtime library.
4. Click Edit...
5. Select the runtime you want from the list.
6. Click Finish.
7. Select the JBoss ESB Runtime library.
8. Click Edit...
9. Select the "Server Contained" entry in the list that matches the server
picked in step 5.
10. Click Finish.
11. Click OK.
That should take care of most, if not all, problems with the project so that it builds and
can deploy.
Does that help?
Document SOA 5.2 examples update site in release notes
------------------------------------------------------
Key: TOOLSDOC-250
URL:
https://issues.jboss.org/browse/TOOLSDOC-250
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Release Notes
Affects Versions: 3.2.2.Final
Reporter: Len DiMaggio
Assignee: Isaac Rooskov
Fix For: 3.2.2.Final
Add SOA-P 5.2 example information and update site for JBDS 4.1.1 into the Release Notes
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira