Hi Benson,

We don't support your use case in current STP, but it is on the way...

The current Pojo/java first support in stp is using cxf w2j and j2w tools, which are based on jaxb binding. I think CXF guys are going to provide a new java2service tool to directly support Pojo. That tool will generate client and server from Pojo class, and the default binding will be Aegis.

Once that added to cxf, we will integrate it into STP java first project wizard.

For the deployment side, the current stp deployment is based on individual project. We are going to support user to select services from workspace, thus they can deploy the whole soa network in one step. We are also working on fully integrate the STP deployment framework with WTP server framework. Hence you can start/stop/debug your application deployed on servlet container within Eclipse.


Regards

Johnson

----- Original Message ----- From: "Benson Margulies" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, July 23, 2007 8:11 PM
Subject: RE: Eclipse STP installation process


Johnson,

I hate to be a grump, and I'd prefer to help you refine this thing.

Here's my vision of the local architecture:

1) A large body of POJO code, including some classes that will
eventually travel across web service interfaces. My approach has been to
use Aegis on these classes to supply annotations to avoid introducing
dependencies on JAX-WS annotation classes. These POJOs are scattered
across several ordinary Eclipse java projects, and then built in
production in ant.

2) For each distinct lump of functionality, a web service defined with
JAX-WS annotations on the interface and implementation class. Each lump
has it's own Eclipse project to hold the web service.

3) A single project that pulls all of these together as a spring-wired
web application, delivering a WAR for deployment in a servlet container.

Are you trying to support the likes of me, or does my fondness for Aegis
or any other aspect of this story disqualify me? If not, no hard
feelings. If so, I'll reconstruct an installation of the whole business
and try again to feed you good bugzillas.

--benson

Reply via email to