Hello David,
First, I need to apologize. When I created my Bugzilla account,
I registered with my private email without entering my name. I now added the
missing information.
Thank you,
Nevena
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf
Of David M Williams
Sent: Friday, August 20, 2010 12:24 AM
To: General discussion of project-wide or architectural issues.
Subject: RE: [wtp-dev] Service Interface & Data Types Editor
Contribution Proposal
I've put in
nominations for 4 of the 5 proposed committers for this proposal.
One to go. The
name, "Nevena Manova", was not found in Eclipse Foundation databases.
They need to find you in bugzilla account, if not an existing committer
somewhere else.
Could a
different name (variant) have been used in Bugzilla account? Have I somehow
mangled the name?
Thanks,
|
From:
|
David
M Williams/Raleigh/IBM@IBMUS
|
|
To:
|
WTP
Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
|
|
Cc:
|
"General
discussion of project-wide or architectural issues."
<wtp-dev@xxxxxxxxxxx>
|
|
Date:
|
08/12/2010
04:34 PM
|
|
Subject:
|
RE:
[wtp-dev] Service Interface & Data Types Editor
Contribution Proposal
|
|
Sent by:
|
wtp-dev-bounces@xxxxxxxxxxx
|
Thanks for this proposal. I wanted to keep you (and community) up to date.
The proposal looks good but one of the people wanting to review it more
is on vacation, so I'd like to be polite and give him a chance to get back and
comment further, if he has any further comments. We should get that feedback
next week.
We normally have these discussion on the WTP Incubator list, so let's move the
thread there, to wtp-incubator-dev@xxxxxxxxxxx.
Thanks again,
|
From:
|
"Simeonov,
Emil" <emil.simeonov@xxxxxxx>
|
|
To:
|
Keith
Chong <kchong@xxxxxxxxxx>
|
|
Cc:
|
"wtp-dev@xxxxxxxxxxx"
<wtp-dev@xxxxxxxxxxx>
|
|
Date:
|
08/03/2010
05:20 AM
|
|
Subject:
|
RE:
[wtp-dev] Service Interface & Data Types Editor Contribution
Proposal
|
|
Sent by:
|
wtp-dev-bounces@xxxxxxxxxxx
|
Hi Keith,
First of all thank you for your interest in our proposal!
Indeed we have thoroughly evaluated the WTP WSDL and XSD editors (as well as
the Netbeans ones and some more) in respect to different functional and
non-functional aspects numerous times.
I would like to emphasize on the fact that the WTP and the proposed editors are
NOT competing in any way and they could be used when appropriately, since all
of the editors work with standard artifacts (*.xsd and *.wsdl files). Hence
once the usage of the existing WTP editors is necessary one could always switch
to them and vice versa.
Yet we also have quite a lot of stakeholders’ feedback regarding what they
need, which we have taken into consideration before going for the design and
development of brand new WSDL and XML Schema editors.
A short summary of our findings as an extract from the latest comparison with
the WTP editors could be found below.
WTP WSDL 1.1 & Service Interface editors
Development Productivity
1. Representation of WSDL 1.1 specifics
a. WTP WSDL editor: exposes all WSDL 1.1 technical
details
b. Service Interface editor: hides WSDL 1.1
complexity
2. Number of open editor / views necessary to edit a WSDL
1.1 document, i.e. navigation
a. WTP WSDL editor: 3 (+1 editor instance for each
data-type which is being viewed in details)
b. Service Interface editor: 1 (using master-details
UI design pattern)
3. Number of ‘clicks’ to do modeling, i.e. time spent
a. Conclusion: Considering the total number of open
views and editor instances as well as the allocation of properties in the WTP
WSDL 1.1 editor the number of clicks necessary for modeling is much higher than
what is necessary in the Service Interface editor
4. Error detection
a. WTP WSDL editor: Optional batch validation
supported. Some values could be invalid as entered by users and others cannot
(E.g. An operation name could not be altered in an invalid way. A part name
could be modified in an invalid way without any warning.). No error decoration
in the design (UI modeling) parts of the editor.
b. Service Interface editor: Supports 2 ways of
error detection in consistent manner, i.e. Live (in-place partial) and batch
(save / load thorough model) validation. Supports problem reporting in both the
UI modeling parts and the Eclipse Problems view.
5. Isolation of single entities (Filtering) when
manipulating large documents
a. WTP WSDL editor: Not supported
b. Service Interface editor: Supported for all
visualized entities
Functional Completeness
1. Basic WSDL modeling (Add / Remove / Alter PortTypes,
Operations, Set types / elements for operation arguments, modification of
inline XSD entities, usage of externally defined XSD entities)
a. Conclusion: Both editors allow for such
kind of manipulations
2. Refactoring capabilities
a. WTP WSDL editor: Renaming of WSDL entities,
switch between synchronous and asynchronous operation modes
b. Service Interface editor:
Renaming of WSDL entities
3. Technical modeling (bindings, services)
a. WTP WSDL editor: Partially supported
(re-generation of bindings and services content necessary)
b. Service Interface editor: Not
supported by design (keep them in sync with PortTypes)
WTP XML Schema & Data Types editors
Development Productivity
1. Representation of XSD specifics
a. WTP XML Schema editor: exposes all XSD technical
details
b. Data Types editor: hides XSD complexity
2. Number of open editor / views necessary to edit a WSDL
1.1 document, i.e. navigation
c. WTP XML Schema editor: 3 (+1 editor instance for
each data-type which is being viewed in details)
d. Data Types editor: 1 (using master-details UI
design pattern)
3. Number of ‘clicks’ to do modeling, i.e. time spent
a. Conclusion: Considering the total number of open
views and editor instances as well as the allocation of properties in the WTP
XML Schema editor the number of clicks necessary for modeling is much higher
than what is necessary in the Data Types editor
4. Error detection
a. WTP XML Schema editor: Optional batch validation
supported. No error decoration in the design (UI modeling) parts of the editor
b. Data Types editor: Supports 2 ways of error
detection in consistent manner, i.e. Live (in-place partial) and batch (save /
load thorough model) validation. Supports problem reporting in both the UI
modeling parts and the Eclipse Problems view.
5. Isolation of single entities (Filtering) when
manipulating large documents
a. WTP XML Schema editor: Not supported
b. Data Types editor: Supported for all visualized
entities
Functional Completeness
1. Basic XSD modeling (Add / Remove / Alter entities with
global scope, i.e. Element declarations, attributes, complex / simple types
definitions; Add / Remove / Alter entities with local scope, i.e. element
declarations / references, attribute declarations / references, re-use of
externally defined XSD entities)
a. Conclusion: Both editors allow for such
kind of manipulations
2. Advanced modeling (Model Groups, Simple
Type Definitions with complex content, anonymous type definitions, etc.
handling)
a. WTP XML Schema editor:
explicitly modeled in technical manner
b. Data Types editor: hides complexity (source
editing possible for expert users, who would like to know all the details)
3. Refactoring capabilities
a. WTP XML Schema editor:
supports XSD entity renaming, inheritance, nillable, cardinalities,
constraints, switching among local and global scope of XSD entities
b. Data Types editor: supports XSD entity
renaming, inheritance, nillable, cardinalities, constraints, copy & paste
of XSD entities
Please, let me know in case you would need further information.
Kind regards,
Emil Simeonov
Emil Simeonov
Development Architect
SOA I Foundation & Studio
SAP Labs Bulgaria
136 A, Tsar Boris III Blv.
1618 Sofia, Bulgaria
T + 359 2 9157 602
E emil.simeonov@xxxxxxx
From:
Keith Chong [mailto:kchong@xxxxxxxxxx]
Sent: Tuesday, 3. August 2010 06:54
To: Simeonov, Emil
Cc: wtp-dev@xxxxxxxxxxx
Subject: Re: [wtp-dev] Service Interface & Data Types Editor
Contribution Proposal
Hi Emil,
Interesting proposal. Have you tried out the existing WSDL and XML Schema
Editors currently in WTP ? For example, see: http://wiki.eclipse.org/index.php/Introduction_to_the_WSDL_Editor
Regards,
Keith Chong
WTP Web Services
|
From:
|
"Simeonov,
Emil" <emil.simeonov@xxxxxxx>
|
|
To:
|
"wtp-dev@xxxxxxxxxxx"
<wtp-dev@xxxxxxxxxxx>
|
|
Date:
|
08/02/2010
07:12 AM
|
|
Subject:
|
[wtp-dev]
Service Interface & Data Types Editor Contribution
Proposal
|
|
Sent by:
|
wtp-dev-bounces@xxxxxxxxxxx
|
Hi guys,
Herewith we declare our will and readiness to contribute the Service Interface
& Data Types Editor as part of the Eclipse WTP Incubator project.
In short these are a WSDL 1.1 and a XSD editors, which aim to provide
exceptional ease of use, development productivity and simplicity while still
being powerful when it comes to the development of such artifacts as part of a
SOA / BPM / Web Service deployments.
The detailed project proposal can be found and reviewed here.
http://wiki.eclipse.org/WTP/Service_Interface_and_Data_Types_Editors/Proposal
Kind regards,
Emil Simeonov
Emil Simeonov
Development Architect
SOA I Foundation & Studio
SAP Labs Bulgaria
136 A, Tsar Boris III Blv.
1618 Sofia, Bulgaria
T + 359 2 9157 602
E emil.simeonov@xxxxxxx
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
