Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Install and run the snapshot build"
(→All-in-One package) |
(→All-in-One package) |
||
Line 44: | Line 44: | ||
You can download the STP all in one package from here:[http://www.foomnet.org/stp_all_in_one04092007.zip stp_all_in_one04092007.zip] | You can download the STP all in one package from here:[http://www.foomnet.org/stp_all_in_one04092007.zip stp_all_in_one04092007.zip] | ||
− | + | Just copy all plugins from that package to your eclipse3.2 installation. | |
Please notice: | Please notice: | ||
Line 52: | Line 52: | ||
Three known issues: | Three known issues: | ||
− | * Can't set the JAX-WS runtime directory and | + | * Can't set the JAX-WS runtime directory and soap12 binding from project's properties. But set from Preference page works fine. |
* The Document/Lit/Bare doesn't work. This is caused by a [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176783 bug] in Apache CXF runtime. | * The Document/Lit/Bare doesn't work. This is caused by a [https://bugs.eclipse.org/bugs/show_bug.cgi?id=176783 bug] in Apache CXF runtime. | ||
So If you are following Tyler's article, please give @SoapBinding(Document/Literal/Wrapped) annotation on web service class. | So If you are following Tyler's article, please give @SoapBinding(Document/Literal/Wrapped) annotation on web service class. | ||
* The HTTP/REST style client has problem, will give HTTP 500 error in the runtime. But the standalone client run from Eclipse works fine. | * The HTTP/REST style client has problem, will give HTTP 500 error in the runtime. But the standalone client run from Eclipse works fine. |
Revision as of 00:54, 12 April 2007
This wiki page is used to explain how to install and use the latest snapshot build. Since the current 0.4.0 S-build (http://www.eclipse.org/stp/downloads/downloads.php) has some major problems, we suggest to use the snapshot build instead.
For user's convenience, i created a all-in-one package to download at the end of this wiki page.
Johnson Ma (Apr 09, 2007)
Contents
Where to get stp build
Setup pre-requisites
Pre-requisites plugins
Plugins from other Eclipse projects
- Eclipse EMF-SDO-XSD SDK
- Eclipse GEF SDK
- Eclipse JEM SDK
- Eclipse WTP SDK
- Eclipse GMF Runtime
- Eclipse DTP SDK
3rd-party plugins
- Apache CXF plugin for JAX-WS development: http://people.apache.org/repo/m2-snapshot-repository/org/apache/cxf/cxf-eclipse3.1-plugin/2.0-incubator-RC-SNAPSHOT/cxf-eclipse3.1-plugin-2.0-incubator-RC-20070306.200920-6.zip
- Apache Tuscany plugin for SCA development:
http://www.eclipse.org/stp/sc/plugins/tuscany-eclipse-plugin-1.0-incubator-M2.zip
Pre-requisites SOA runtime
- JAX-WS runtime: Apache CXF
- SCA runtime: Apache Tuscany SCA Java
- Apache Tomcat (Install only if you want to deploy the generated service to Tomcat Container)
Run it
Tyler Anderson wrote a good article about Use the Eclipse SOA Tools Platform plug-in to build and deploy a Web service
About the update sites
We are still working on those update sites:
- Eclipse STP update site, coming soon...
- Apache CXF update site, coming soon...
- Apache Tuscany update site. ?
All-in-One package
You can download the STP all in one package from here:stp_all_in_one04092007.zip
Just copy all plugins from that package to your eclipse3.2 installation.
Please notice:
* We only support eclipse3.2 for now. * Please set the java compiler to jdk 1.5 in preference page (1.4 and 1.6 are not supported) * Need to install CXF runtime to test the JAX-WS functions.
Three known issues:
* Can't set the JAX-WS runtime directory and soap12 binding from project's properties. But set from Preference page works fine. * The Document/Lit/Bare doesn't work. This is caused by a bug in Apache CXF runtime. So If you are following Tyler's article, please give @SoapBinding(Document/Literal/Wrapped) annotation on web service class. * The HTTP/REST style client has problem, will give HTTP 500 error in the runtime. But the standalone client run from Eclipse works fine.