Re: [stp-dev] Component Java Projects versus Composite Projects

["Johnson Ma" <johnson.ma@xxxxxxxx>]

Hi Mark,

Yes, that is a good question.
> From the end user point of view, i think there will be two different usage 
scenarios for STP:

1. User want to user the tool the create SCA component.
> From sca spec, the component implementations may depend on services provided 
by other components - those
dependencies are called references.

The current SCA component project wizard need to be improved to support 
references. I think that is the way
to create 'middle-sized' composites. In that case, a tab based editor should 
be enough (just like the plugin.xml editor
in Eclipse.). We can have a reference tab, which allow user to set reference 
to other components.

2. User want to user the tool to create SOA system (SOA System project 
wizard?)
In that case, they can start from user requirements, which can be mapped to 
bpmn.
Then they will design the system using the SCA assembly editor by drag and 
drop
components and links. Until then, all components are not implemented yet, 
they will follow
step1 to create each component.


Regards

Johnson

----- Original Message ----- 
From: "Mark Walker" <mwalker@xxxxxxxxxxxxxxxxxxxx>
To: "STP Dev list" <stp-dev@xxxxxxxxxxx>
Sent: Monday, April 02, 2007 5:52 PM
Subject: RE: [stp-dev] Component Java Projects versus Composite Projects


Hi Johnson,

I'm concerned a little about your use of the term "big picture".

Given that SCA composites can be infinitely nested (theoretically,
anyway). What about those SCA composites that are internal to other
composites (i.e. being used as component implementations)? So what do we
do about these "middle-sized picture" ;-) composites?

Even more concerning might be the issue of where do we locate composite
service interfaces that have be redefined within the composite (as per
the SCA 1.0 spec, pp. 34-35)?

Please note, I am not advocating that we do have a combination SCA
component and composite project -- I can a logical division --, rather I
am concerned with how we deal with these "edge/corner" cases.


Ciao,
Mark Walker,
mwalker@xxxxxxxxxxxxxxxxxxxx
Technical Architect (Tools),
Cardiff.



-----Original Message-----
From: stp-dev-bounces@xxxxxxxxxxx [mailto:stp-dev-bounces@xxxxxxxxxxx]
On Behalf Of Johnson Ma
Sent: 02 April 2007 09:25
To: STP Dev list
Cc: Owen Williams
Subject: Re: [stp-dev] Component Java Projects versus Composite Projects


Hi Mark

Yes, we will have a separate composite project.

The current SCA Java component project wizard is used to create a
standard
service component following SCA java spec.
It is just like the jax-ws project wizard, which is used to create a
jax-ws
service component.

> From my understanding, we will have a soa network project type
> (Composite
projects), which is mainly a SCDL assembly editor.
It will allow user to connect multiple components by adding wire/links
to
setup the big picture of the SOA infrastructure.
Each component in the the assembly editor may come from stp service
component project within workspace (sca java or jax-ws), external sca
component, or it maybe a bpel component...etc


Regards

Johnson

----- Original Message ----- 
From: "Mark Walker" <mwalker@xxxxxxxxxxxxxxxxxxxx>
To: <stp-dev@xxxxxxxxxxx>
Cc: "Owen Williams" <owilliams@xxxxxxxxxxxxxxxxxxxx>
Sent: Friday, March 30, 2007 6:59 PM
Subject: [stp-dev] Component Java Projects versus Composite Projects


Hi All,

Is STP going to have a separate composite project type for containing
SCDL? Or is everything going to be part of the main SCA Java Component
Project? If, so how do we handle SCDL only projects (they just reference
components available elswhere), and Java only (i.e. annotation only)
component projects?

Further to the above: what will be our output archive format for
contributions, the SCA 1.0 spec mentions all kinds of output format?

Ciao,
Mark Walker,
mwalker@xxxxxxxxxxxxxxxxxxxx
Technical Architect (Tools),
Cardiff.




Information contained in this e-mail and any attachments are intended
for
the use of the addressee only, and may contain confidential information
of
Ubiquity Software Corporation. All unauthorized use, disclosure or
distribution is strictly prohibited.  If you are not the addressee,
please
notify the sender immediately and destroy all copies of this email.
Ubiquity
Software Corporation plc, a company registered under the laws of England
and
Wales, Registration 2719723, registered offices at Eastern Business
Park,
Building 3, Wern Fawr Lane, St. Mellons, Cardiff CF3 5EA, Wales, United
Kingdom.

_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/stp-dev

_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/stp-dev
_______________________________________________
stp-dev mailing list
stp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/stp-dev