[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5546: -------------------------------------- Denny, thanks for that - I didn't know about these Project Examples. Good to know more of them will be coming. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5546: -------------------------------------- You're right, the problem is not in the editor but in the quickstarts which weren't made to work with JBDS. I made a bug in both JBIDE and SOA to make sure it is tracked. It hasn't been decided yet how to resolve this, but probably the quickstarts will need to be modified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5546: -------------------------------------- Hi Brian, sorry for the delay. Yes, it is pretty much all of them. At the server side, it seems like it always expects a soa-p 4.3 runtime and OpenJDK - see the screenshots. Occurs in: helloworld helloworld_action helloworld_file_action webservice_consumer1 webservice_producer transform_CSV2XML transform_XML2POJO transform_XML2XML_date_manipulation transform_XML2XML_simple (So all of them.) As for the clients, some have problems in SendJMSMessage.java and SendEsbMessage.java: helloworld_client helloworld_action_client webservice_consumer1_client webservice_producer_client transform_CSV2XML_client transform_XML2POJO_client transform_XML2XML_date_manipulation_client transform_XML2XML_simple_client The only one that seems fine is: (But I couldn't test it anyway, since the server didn't work.) helloworld_file_action_client -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Martin Malina updated JBIDE-5546: --------------------------------- Attachment: client_part.jpg -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Dominik Pospisil resolved JBIDE-5546. ------------------------------------- Fix Version/s: (was: 3.2.next) Resolution: Deferred SOA-P quickstart will not be updated for this release. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5546: -------------------------------------- For instance in the helloworld_testclient example, these classes are missing: In org.jboss.soa.esb.samples.quickstart.helloworld.test.SendJMSMessage.java: import javax.jms.JMSException; import javax.jms.ObjectMessage; import javax.jms.Queue; import javax.jms.QueueConnection; import javax.jms.QueueConnectionFactory; import javax.jms.QueueSender; import javax.jms.QueueSession; In org.jboss.soa.esb.samples.quickstart.helloworld.test.SendEsbMessage.java: import org.jboss.soa.esb.message.Message; import org.jboss.soa.esb.message.format.MessageFactory; import org.jboss.soa.esb.client.ServiceInvoker; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Martin Malina commented on JBIDE-5546: -------------------------------------- Workaround from Brian: For example, to run the Project Example - JBoss ESB HelloWorld Example, I follow these simple steps in a new JBT workspace: 1) In the tooling, create a new server instance for your SOA-P 5.0 runtime in the Servers view (I've been using the EAP 5.0 version and just renaming it SOA-P 5). 2) In the tooling, go to Help->Project Examples. Select the ESB -> JBoss ESB HelloWorld Example - ESB. Click Finish. 3) In the Quick Fix dialog, select the "Unbound classpath container: JRE System Library [java-1.6.0-openjdk-..." item. Click "Quick Fix". 4) Select "Replace with other library". In the "Add Library" dialog, select JRE System Library and step through selecting a different JRE (such as Sun's JRE jdk1.6.0_14). Click Finish. 5) Now you see additional things to fix. Select "Target runtime jboss-soa-p.4.3.0 Runtime is not defined.". Click Quick Fix. 6) Select Configure Target Runtimes. In the Targeted Runtimes property page, select your SOA-P 5.0 runtime server. Click OK. 7) Select any of the "The import x cannot be resolved" messages and click Quick Fix. 8) Select "Fix project setup..." and click Finish. 9) You should see a "Project Setup Fixes" dialog come up with a message - "No proposals have been found..." In the message is a "Click here to manually configure the build path..." Click the hyperlink. 10) Now you're in the Build path properties for the project. Select the "Libraries" tab. CLick on the "JBoss ESB Runtime" library and select "Edit..." 11) You should see the Edit Library dialog come up with "Select a ESB runtime to add to the project classpath" - select the one associated with the SOA-P 5 runtime server. Click Finish. 12) Back in the Build path properties, now select "Server Library" and click "Edit..." 13) You should see another Edit Library dialog. Select your SOA P 5.0 runtime server. Click Finish. 14) Click OK on the Build path properties dialog. You should come back to the Quick Fix dialog with no markers. Click Finish. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Brian Fitzpatrick updated JBIDE-5546: ------------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Assignee: Denny Xu Denny, can you look into this with Snjezana to see if you can get these examples working a bit better with the SOA-P 5 runtime? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Brian Fitzpatrick reopened JBIDE-5546: -------------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-5546: -------------------------------------------- We need to create on at download.jboss.org since anonsvn.jboss.org is not a stable location. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Denny Xu commented on JBIDE-5546: --------------------------------- I added a new ESB category named "ESB for SOA-P 5.0", all examples in the category are changed to work out of box with soa-p5.0, once there is a runtime point to a soa-p5.0 and named "jboss-soa-p.5.0 Runtime" in the workspace, there will be no compile when import the esb examples. As suggested in JBIDE-5665, I added the examples to http://anonsvn.jboss.org/repos/jbosstools/workspace/examples/project-exam... for testing, once all of them works, it should be copied to http://download.jboss.org/jbosstools/examples/project-examples-jbds30.xml Martin, for what's the best way to import ESB examples, I suggest to create a soa-p5.0 runtime by naming it "jboss-soa-p.5.0 Runtime" before import any ESB project examples, if so, we can avoid most of the 14 steps you mentioned above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBIDE-5546?page=com.atlassian.jira.plu... ] Martin Malina closed JBIDE-5546. -------------------------------- JBIDE-5659 got reopened, so the rest will be solved there. This issue can be closed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira