/tuscany/java/sca/tools/eclipse/plugins/core/.classpath
Hi,
An Eclipse newsgroup named SCA Tools was created to discuss about the
Eclipse SCA Tools project:
news://news.eclipse.org/eclipse.stp.sca-tools
You need a password to access the newsgroup server [0].
SCA Tools is proposed as a sub-project under the top level project Eclipse
SOA Tools Platform
Hi Jean-Sebastien, all,
Thanks for your comments.
On Wed, Apr 9, 2008 at 8:34 PM, Jean-Sebastien Delfino [EMAIL PROTECTED]
wrote:
The proposal looks pretty good to me. I have a few comments/questions:
- Are you going to have tools to create SCA contributions,
imports/exports, contribution
. Introduction: the proposition of the transformation of the
STP/SCA
component into a sub-project named SCA Tools under the top level
project
STP.
2. Background: presentation of STP + presentation of the existing
STP/SCA
component.
3. Description
Stéphane Drapeau wrote:
Hi,
I created an entry [0] in the Eclipse bugzilla with the proposal.
Your comments are welcome.
Best regards
Stéphane Drapeau
Obeo
[0]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=225956
The proposal looks pretty good to me. I have a few comments/questions:
-
describing the scope/intent of the
proposed project.
The outline is:
1. Introduction: the proposition of the transformation of the STP/SCA
component into a sub-project named SCA Tools under the top level
project
STP.
2. Background: presentation of STP + presentation of the existing
STP/SCA
component
of the transformation of the STP/SCA
component into a sub-project named SCA Tools under the top level
project
STP.
2. Background: presentation of STP + presentation of the existing
STP/SCA
component.
3. Description: the goals of the new sub-project are to develop a set
:
Stéphane Drapeau wrote:
Hi,
I'm Stéphane Drapeau from Obeo. I work on tools for SCA and I lead the
Eclipse SCA component which is a component of the STP project [1].
Currently, I'm writing a proposal to change the status of the STP SCA *
component* to STP/SCA Tools *sub project*.
I
Hi Jean-Sebastien, Haleh, all,
The proposal is a 3 pages document describing the scope/intent of the
proposed project.
The outline is:
1. Introduction: the proposition of the transformation of the STP/SCA
component into a sub-project named SCA Tools under the top level project
STP.
2
named SCA Tools under the top level project
STP.
2. Background: presentation of STP + presentation of the existing STP/SCA
component.
3. Description: the goals of the new sub-project are to develop a set of
tools for SCA developers and SCA users. Another goal is also to link this
sub-project
Hi,
I'm Stéphane Drapeau from Obeo. I work on tools for SCA and I lead the
Eclipse SCA component which is a component of the STP project [1].
Currently, I'm writing a proposal to change the status of the STP SCA *
component* to STP/SCA Tools *sub project*.
I would like know if I can refer Tuscany
Stéphane Drapeau wrote:
Hi,
I'm Stéphane Drapeau from Obeo. I work on tools for SCA and I lead the
Eclipse SCA component which is a component of the STP project [1].
Currently, I'm writing a proposal to change the status of the STP SCA *
component* to STP/SCA Tools *sub project*.
I would like
Raymond Feng [EMAIL PROTECTED] wrote:
I wonder if it's too heavy to develop a maven plugin to merge the
definitions.xml file. BTW, I don't like the all-in-one jar too much as it
breaks the modularity and extensibility story.
+1 to that.
Simon Laws wrote:
If we are going to stick using the
On Mon, Mar 3, 2008 at 10:08 PM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
Raymond Feng [EMAIL PROTECTED] wrote:
I wonder if it's too heavy to develop a maven plugin to merge the
definitions.xml file. BTW, I don't like the all-in-one jar too much as
it
breaks the modularity and
- in
/incubator/tuscany/java/sca/tools/maven/maven-definitions: ./ src/
src/main/
src/main/java/ src/main/java/org/ src/main/java/org/apache/
src/main/java/org/apache/tuscany/ src/main/java/org/apache/tuscany/sca/
src/main/java/org/...
Author: svkrish
Date: Sat Mar 1 11:15:54 2008
New Revision
On Jan 11, 2008 4:50 AM, [EMAIL PROTECTED] wrote:
Author: lresende
Date: Thu Jan 10 20:50:35 2008
New Revision: 611046
URL: http://svn.apache.org/viewvc?rev=611046view=rev
Log:
TUSCANY-1936
Modified:
incubator/tuscany/java/sca/tools/wsdl2java/pom.xml
Modified: incubator/tuscany
, 2008 4:50 AM, [EMAIL PROTECTED] wrote:
Author: lresende
Date: Thu Jan 10 20:50:35 2008
New Revision: 611046
URL: http://svn.apache.org/viewvc?rev=611046view=rev
Log:
TUSCANY-1936
Modified:
incubator/tuscany/java/sca/tools/wsdl2java/pom.xml
Modified: incubator/tuscany/java/sca/tools/wsdl2java
11, 2008 4:50 AM, [EMAIL PROTECTED] wrote:
Author: lresende
Date: Thu Jan 10 20:50:35 2008
New Revision: 611046
URL: http://svn.apache.org/viewvc?rev=611046view=rev
Log:
TUSCANY-1936
Modified:
incubator/tuscany/java/sca/tools/wsdl2java/pom.xml
Modified: incubator
://svn.apache.org/viewvc?rev=611046view=rev
Log:
TUSCANY-1936
Modified:
incubator/tuscany/java/sca/tools/wsdl2java/pom.xml
Modified: incubator/tuscany/java/sca/tools/wsdl2java/pom.xml
URL:
http://svn.apache.org/viewvc/incubator/tuscany/java/sca/tools/wsdl2java/pom.xml?rev=611046r1=611045r2
Mike Edwards wrote:
Folks,
The real problem here is that the testcase for wsdl2java is cr*p. I'll
raise a JIRA to track this.
Basically, the testcase runs the wsdl2java tool a number of times and
produces some output. Nothing wrong with that, except that all that is
being tested is that
ant elder wrote:
On 10/28/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
We currently have a bunch of tools modules under sca/modules.
I'm thinking about moving them to sca/tools as follows:
sca/tools/wsdl2java
sca/tools/java2wsdl
sca/tools/maven/maven-wsdl2java
sca/tools/maven/maven
modules under sca/modules.
I'm thinking about moving them to sca/tools as follows:
sca/tools/wsdl2java
sca/tools/java2wsdl
sca/tools/maven/maven-wsdl2java
sca/tools/maven/maven-java2wsdl
sca/tools/maven/maven-ant-generator
I think it'll better reflect that they are tools and not runtime
On 10/28/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
We currently have a bunch of tools modules under sca/modules.
I'm thinking about moving them to sca/tools as follows:
sca/tools/wsdl2java
sca/tools/java2wsdl
sca/tools/maven/maven-wsdl2java
sca/tools/maven/maven-java2wsdl
sca
Makes sense to me. +1
- Venkat
On 10/28/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
We currently have a bunch of tools modules under sca/modules.
I'm thinking about moving them to sca/tools as follows:
sca/tools/wsdl2java
sca/tools/java2wsdl
sca/tools/maven/maven-wsdl2java
sca
Jean-Sebastien,
Seems a good idea to me...
Mike.
Jean-Sebastien Delfino wrote:
We currently have a bunch of tools modules under sca/modules.
I'm thinking about moving them to sca/tools as follows:
sca/tools/wsdl2java
sca/tools/java2wsdl
sca/tools/maven/maven-wsdl2java
sca/tools/maven/maven
Jeremy,
I think where these should end up is dependent how the tools are
positioned within the Tuscany project.
While the wsdl2java tool currently generates interfaces with SDO
parameters, will there ever be extensions to support other data binding
types? Considering WSDL is a first class
On Dec 20, 2006, at 8:19 AM, Matthew Sykes wrote:
Jeremy,
I think where these should end up is dependent how the tools are
positioned within the Tuscany project.
While the wsdl2java tool currently generates interfaces with SDO
parameters, will there ever be extensions to support other
Looking at modularizing the tree, it seems to me that the tools and
java2wsdl/wsdl2java plugins don't actually have any dependency on SCA
- they are tools for generating java/wsdl interfaces with SDO
DataObjects.
In light of that, I think they might be better off as part of the SDO
tree
Jeremy,
on the face of it that sounds logical but I don't really know the code
that well. I'd like to understand the full extent of the function,
particularly whether in both directions of the mappings (WSDL2Java and
Java2WSDL) we could substitue the word SDO for the word Java and still
...
Thanks.
Update headers for files in sca tools, sca javascript, sca ruby and sca rmi
projects
Key: TUSCANY-809
URL: http://issues.apache.org/jira/browse/TUSCANY-809
[ http://issues.apache.org/jira/browse/TUSCANY-809?page=all ]
ant elder closed TUSCANY-809.
-
Resolution: Fixed
Update headers for files in sca tools, sca javascript, sca ruby and sca rmi
projects
Update headers for files in sca tools, sca javascript, sca ruby and sca rmi
projects
Key: TUSCANY-809
URL: http://issues.apache.org/jira/browse/TUSCANY-809
Project
Repository entry missing in SCA tools
--
Key: TUSCANY-723
URL: http://issues.apache.org/jira/browse/TUSCANY-723
Project: Tuscany
Issue Type: Bug
Components: Java SCA Tools
Affects Versions
[ http://issues.apache.org/jira/browse/TUSCANY-723?page=all ]
Lee Surprenant updated TUSCANY-723:
---
Attachment: SCAToolsPomUpdate.patch
pom.xml with the apped eclipse repository
Repository entry missing in SCA tools
[ http://issues.apache.org/jira/browse/TUSCANY-723?page=all ]
Jeremy Boynes closed TUSCANY-723.
-
Resolution: Fixed
Patch applied - thanks
Repository entry missing in SCA tools
-
Key: TUSCANY-723
On Jul 31, 2006, at 10:16 PM, Venkata Krishnan wrote:
Hi Jeremy / Jim / Rick / Ant and others
What is the decision about the sca-tools that existed in M1? Do we
plan to
make it a part of the current Tuscany-Java as well?
I think tooling in general is a good thing to have (as long as it's
, Venkata Krishnan wrote:
Hi Jeremy / Jim / Rick / Ant and others
What is the decision about the sca-tools that existed in M1? Do we
plan to
make it a part of the current Tuscany-Java as well?
I think tooling in general is a good thing to have (as long as it's
not required
On Aug 1, 2006, at 12:43 AM, Venkata Krishnan wrote:
Jim :-)))..
Please help me understand the scope of not required. If
something is not
required then why have it in the first place? Are these things no
longer
relevant to the current Tuscany-Java?
Jim is echoing a goal that SCA
Hi Jeremy / Jim, first thanks for those answers.
I am able to understand your perspectives. But just that one more
question. If we do not generate a WSDL what do we publish for clients who
which to connect to this component's service? How would client applications
know about the service's
On Aug 1, 2006, at 10:24 AM, Venkata Krishnan wrote:
Hi Jeremy / Jim, first thanks for those answers.
I am able to understand your perspectives. But just that one more
question. If we do not generate a WSDL what do we publish for
clients who
which to connect to this component's service?
Hi Jeremy / Jim / Rick / Ant and others
What is the decision about the sca-tools that existed in M1? Do we plan to
make it a part of the current Tuscany-Java as well? There is another thread
where David Wheeler was talking about samples around the Axis2 binding.
Wouldn't the sca tools
[ http://issues.apache.org/jira/browse/TUSCANY-194?page=all ]
Jean-Sebastien Delfino closed TUSCANY-194:
--
Fix eclipse warnings for sca/tools
--
Key: TUSCANY-194
URL: http
Fix eclipse warnings for sca/tools
--
Key: TUSCANY-194
URL: http://issues.apache.org/jira/browse/TUSCANY-194
Project: Tuscany
Type: Improvement
Components: Java SCA Tools
Reporter: Daniel Kulp
Priority: Minor
Attachments
[ http://issues.apache.org/jira/browse/TUSCANY-194?page=all ]
Daniel Kulp updated TUSCANY-194:
Attachment: sca_tools.patch
Fix eclipse warnings for sca/tools
--
Key: TUSCANY-194
URL: http
[ http://issues.apache.org/jira/browse/TUSCANY-194?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-194:
Resolution: Fixed
Assign To: Jean-Sebastien Delfino
Thanks for the patch, applied it.
Fix eclipse warnings for sca/tools
I need to drop 2 new sub-projects for our wsdl2java command-line tool
and maven plugin. I'm thinking about using a structure similar to what
we have under sdo.
java/sca/tools
java/sca/plugin
We have a java/tools folder but I would prefer to have these tools under
java/sca, and then just
.
Yours, Mike.
Jean-Sebastien Delfino wrote:
I need to drop 2 new sub-projects for our wsdl2java command-line tool
and maven plugin. I'm thinking about using a structure similar to what
we have under sdo.
java/sca/tools
java/sca/plugin
We have a java/tools folder but I would prefer to have
47 matches
Mail list logo
