[snip]
Jean-Sebastien Delfino wrote:
Dennis,
Some comments inline.
Dennis Virt wrote:
Dear Simon and Luciano,
Thank you for your detailed replies and comments. I also got an
impression that trunk is maintained healthy and "buildable".
We have made changes to the trunk recently to make it easier to build.
Could you try the following?
cd tuscany/java
mvn
This should build the SDO, DAS and SCA runtimes. I just tried with
revision r531619 and they all built OK.
You can imagine how much frustration has brought to me my attempt to
build the web service WAR, since I did not know that war plugin was
not operational :-)
We're going to try to make it more clear that modules under
java/sca/contrib (including the WAR plugin) are old and not
operational. I started a discussion on that earlier today on tuscany-dev.
Pure M3 war plugin did not work because of contribution dependency on
2.0alpha tag. I tried to mix M3 SDO/DAS and 2.0alpha-incubating
branch from TSSS demo, M2 SCA and M3 SDO/DAS and finally came back to
all M2 code. The latter yielded the same results as M2 SCA and M3
SDO/DAS (at the very end of this message).
Mixing M3 and M2 will be tricky, I don't recommend that path. M3 SDO
is very close to a release, and we've started to put an SCA release
together, targeting a release in a few weeks, so I suggest that you
try the SCA code in trunk instead of SCA M2.
I want to bundle as WAR just enough SCA runtime needed to 1) feed
data to an AJAX client over a web service
Are you planning to use SOAP or JSON-RPC? Our SOAP binding is
operational now, the JSON-RPC binding is not up and running as of
today but I expect to see it running again later this week.
2) and resolve change summaries from the client to the database.
Ideally I wanted this WAR to be deployable to Tomcat, JBoss, IBM
WebSphere 6.1 and Bea WebLogic. I was aware that WebSphere and
WebLogic would've needed much more attention in preparing descriptors
and crafting dependencies. If I succeeded with proof of concept, I'd
be able to assign further packaging to specialists capable of
WebSphere and WebLogic parts.
Do you need a WAR or would you be OK to start with an embedded Tomcat?
With the embedded Tomcat configuration, we embed a minimal Tomcat
instance and boot it from inside Tuscany, instead of having the
Tuscany runtime installed on top of an existing Tomcat, with the SCA
application running in a WAR.
If you want to see how our embedded configuration works, you can take
a look at the test cases under java/sca/modules/binding-ws-axis2. They
use Jetty instead of Tomcat but I'm going to add a Web Service sample
to java/sca/samples later today which will show how to provide a Web
Service uing Tomcat. I'll post an update to this thread with a link to
the sample when it's ready.
Running an SCA application in a WAR should also be supported again
soon, probably sometime next week, as several Tuscany developers have
already indicated on our dev list that they were interested in getting
this to work for our upcoming release. I'm expecting our new Webapp
packaging story to be much simpler than before and not require a
special Tuscany WAR plugin anymore to create WARs.
Dennis,
I have committed two new modules under java/sca/samples:
- helloworld-ws - A sample showing how to provide a HelloWorld service
with a Web Service binding. The helloworld.HelloWorldServer program
starts Tuscany with an embedded Tomcat server to host the Web service.
- helloworld-wsclient - A sample client. The helloworld.HelloWorldClient
program shows how to start an SCA client and invoke the HelloWorld Web
Service.
The samples work with SVN revision r531727 of the Tuscany trunk.
Hope this helps.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
