Hi
Johnson,
I have some questions on the SCA java
creation part. Taking the example of creating a SCA Java service with
RMI binding , we we run the "SCA java Component project" wizard we generate
the following artifacts:
1. The java interface, implementation and server
class. ( We need to fill in the imports for the annotation )
2. The
default composite file
3. The wsdl is generated once we clean the
project
I am not clear on how we would like these artifacts to be used
from here on.
Basically the user may modify the base interface
class and create additional services which are references. This should
ideally modify the composite and add the new references. This is not
currently happening. Is this something that we still need to add?
The
wsdl file does change, but in the context of the new tuscany java sca runtime,
how would the generated wsdl be used, since we now use the composite
file.
The Server class that is generated should be loading the composite
using SCADomain.newInstance().
Now this just represents the server part
of the code. How should a client access this service using a RMI
binding?
regards
chandra
-----
Original Message ----
From: Johnson Ma <johnson.ma@xxxxxxxx>
To:
stp-dev@xxxxxxxxxxx
Sent: Friday, September 14, 2007 2:36:43 PM
Subject:
[stp-dev] Status updates on STP 0.7.0 release
Hi All,
We just created a integration build for
stp 0.7.0, it can be downloaded from [1].
According to our discussion yesterday,
we will do some test and bug fix next week, and create the 0.7.0 M1 release on
next Friday.
The 0.7.0 release includes following
features/changes:
* ServiceCreation -- New Policy Editor plugin
(org.eclipse.stp.cxf) [2]
The STP policy editor is an Eclipse editor for
editing WS-Policy content or other XML content that is based on XML-Schema
with a graphical editor. It is based on the XML Editing Framework(XEF), which
also part of STP.
* BPMN modeler updates to support
EMF2.3
* JAX-WS API plugins
The new version requires jaxws api plugins,
which can be downloaded from [3]
* ServiceCreation -- CXF and Tuscany Dependency
Structure Refactor [4]
We removed the org.apache.cxf and
org.apache.tuscany plugins. The runtime integration is done
by calling command line tools to decoupled from runtime
classes.
*
ServiceCreation--Runtime refactor [5]
Added runtime information
to SOA project. The runtime is extended from runtime extension point defined
in WTP.
Defined three
runtime extensions:Apache CXF2.0 for jaxws, Sun Jax-WS RI 2.1.2 for jaxws and
Apache Tuscany 0.99 for SCA
*
ServiceCreation--Support JAX-WS Reference Implementation from Sun
[6]
User can create and run
jaxws project with JAX-WS RI runtime now.
* SOAS -- WTP Integration
[7]
We can
create/deploy/debug the JAX-WS service, and start/stop tomcat server all
within Eclipse now.
* SOAS -- Removed DTP
dependency. [8]
The Connection Profile
has been replaced by WTP server framework.
* Build--All dependencies have been updated to
3.3 final release.
* Build--STP all-in-one package
[9]
The build system has been updated
to generate stp-all-in-one package, which includes stp and all it is
dependencies.
Anything missing from the list?
Regards
Johnson Ma
