[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Isaac Rooskov updated TOOLSDOC-250: ----------------------------------- Reporter: Len DiMaggio (was: Isaac Rooskov) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Isaac Rooskov commented on TOOLSDOC-250: ---------------------------------------- Thanks Brian, I'll wait for further info ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Brian Fitzpatrick commented on TOOLSDOC-250: -------------------------------------------- Isaac - pushed up the final download URL to - http://download.jboss.org/jbosstools/examples/soa-p-5.x-samples.xml -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Brian Fitzpatrick commented on TOOLSDOC-250: -------------------------------------------- That's different. Here we're talking about project examples files - and project examples XML files for both JBoss Tools and JBDS appear at that same location - http://download.jboss.org/jbosstools/examples/ (you can see some explicitly have "jbds" in the title). We're simply moving these files to a common location so folks can find and add them quickly to the tooling. Does that help? Do you need steps to document for the user here 'cause I can do that... (added below) Let me know if you need anything else. Happy to help! ----------------------- To add the examples in JBDS 4.1.0 or JBDS 4.1.1, do the following: 1. Go to Windows->Preferences and look for the JBoss Tools->Project Examples page. 2. Click Add 3. Give the new example site a name and this url: http://download.jboss.org/jbosstools/examples/soa-p-5.x-samples.xml 4. Click OK to close the dialog, then apply and close the preference change. 5. Go to Help->Project Examples 6. Click "Show Experimental Sites" at the top of the dialog. 7. Select your new examples site, select one of the newly available examples: aggregator business_service custom_action fun_cbr helloworld_action helloworld simple_cbr static_router transform_XML2POJO Each of these is suffixed with "_eclipse" when imported to differentiate them from the quickstarts included with the runtime itself. Each example includes one or more deployable ESB projects and a test project. Once you have the project(s) imported, if your server was created ahead of time, the example projects should be ready to go with no additional changes. You can then deploy the non "_test" projects and run the ESB or JMS message testers from the "_test" project after a successful deployment. ----------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Brian Fitzpatrick commented on TOOLSDOC-250: -------------------------------------------- Always happy to help! :D -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ 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? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Isaac Rooskov commented on TOOLSDOC-250: ---------------------------------------- Hey Brian, just confirming that the runtime library would be a JBoss SOA-P one and not a EAP one? I thought they actually showed up as being different, but I could be wrong so that's why I'm asking ;) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Isaac Rooskov resolved TOOLSDOC-250. ------------------------------------ Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-250?page=com.atlassian.jira.plug... ] Isaac Rooskov closed TOOLSDOC-250. ---------------------------------- Closing due to QE signoff -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira