Hi All,
I am interested in volunteering some time into a development project on
SDO tooling. If any of you can help me identify / define a task that
fits into a 1 Person Month effort, please let me know. I'd be happy to
speak to any one of you if you are interested. I work for IBM at Silicon
I was trying to see how the client code looks like with the new APIs
from the sandbox. With the new architecture, I don't see TuscanyRuntime,
ModuleContext etc.
I do see DefaultBootstrapper, RuntimeComponent, CompositeComponentExtension
etc in the sandbox, But, need some help in understanding
Hi Joel,
I am currently looking into Tuscany management capabilities. Hopefully I can
have an initial proposal for discussion and review by the end of this week. One
of the design objectives for Tuscany management is that Tuscany management
should be protocol neutral, i.e., management will
Hi Rashmi,
Jeremy will be able to answer your question regarding bootstrapping.
For how to locate services, the spec API is evolving to accommodate
the new recursive API. I have some thoughts I have been working on in
the sandbox under jboynes/spec/sca but they are very early which will
Hi Nick,
You should be aware of the Eclipse SOA Tools Project
(http://www.eclipse.org/stp/) since there is a potential overlap with
them...
A suggestion for a simple project could be eclipse plugins to generate SDO
artifacts. I was just about to write an eclipse wizard/plugin to generate
SDO
[ http://issues.apache.org/jira/browse/TUSCANY-429?page=all ]
Andrew Borley updated TUSCANY-429:
--
Attachment: axis2c_wsentrypoint.patch
Here's the latest patch that doesn't trample over existing code so much! This
should build a separate axis2c
Hi Pete,
I agree with this - it's definately cleaner if we build a separate .dll or
.so. to drop into the axis2c services directory. This also has the added
bonus of not requiring existing code to be moved or messed around with so
much. I've just put a new patch on the Jira that should do this,
[
http://issues.apache.org/jira/browse/TUSCANY-292?page=comments#action_12416009
]
Rick Rineholt commented on TUSCANY-292:
---
Well I'm basically looking for some policies regarding logging. Any chance you
know of any? With regard to exceptions, it
Namespaces not generated by scagen
--
Key: TUSCANY-461
URL: http://issues.apache.org/jira/browse/TUSCANY-461
Project: Tuscany
Type: Bug
Components: C++ SCA
Versions: Cpp-current
Reporter: Ed Slattery
Fix For:
Would be nice to generate disable warning for the 'silly' warning on windows
Key: TUSCANY-462
URL: http://issues.apache.org/jira/browse/TUSCANY-462
Project: Tuscany
Type: Bug
Versions:
Doc on how to use context
-
Key: TUSCANY-463
URL: http://issues.apache.org/jira/browse/TUSCANY-463
Project: Tuscany
Type: Task
Components: C++ SCA
Versions: Cpp-current
Reporter: Ed Slattery
Priority: Minor
Fix For:
Nick,
Another thing that might be of interest is a bytecode SDO generator. If
you look in the Tuscany tools subproject, you'll see a command,
Interface2JavaGenerator, that given a Java interface generates an SDO
implementation class for it. It would be nice to have a similar command,
say
Jervis,
There's a weekly Muse development call at the following:
Fridays, 11:00 a.m. Eastern US
Call-in number: 1-866-711-3137
Passcode: 1667643
Would you be able to join us to discuss how to move this forward? I
think we're all eager to make this happen. I'll try and get through the
sandbox
Document XSD - C++ mapping used in WS Entrypoint
-
Key: TUSCANY-464
URL: http://issues.apache.org/jira/browse/TUSCANY-464
Project: Tuscany
Type: Task
Components: C++ SCA
Versions: Cpp-current
Reporter:
Hi Jim,
My personal interest is in SCA-OSGi integration. I listened to your
presentation on the new core architecture, and am going through the
sandbox code trying to gain some understanding of how it all hangs
together. I'd really like to be involved in this area, and would
appreciate any
Frank Budinsky wrote:
Nick,
Another thing that might be of interest is a bytecode SDO generator. If
you look in the Tuscany tools subproject, you'll see a command,
Interface2JavaGenerator, that given a Java interface generates an SDO
implementation class for it. It would be nice to have
SDO calls without error handling
Key: TUSCANY-465
URL: http://issues.apache.org/jira/browse/TUSCANY-465
Project: Tuscany
Type: Bug
Components: C++ SCA
Versions: Cpp-current
Reporter: Ed Slattery
Fix For:
How does one build sandbox code, for example Jeremy's sandbox (which he's
moving to a branch) ?
I tried extracting the sandbox and unzipping over M1, but the Maven build
fails
Project ID: null:tuscany-sca:pom:SNAPSHOT
Reason: Cannot find parent: org.apache.tuscany:tuscany-project for project:
Not sure if this can help and I didn't thoroughly test it, but checked
in tuscany/sandbox/cr22rc/buildm2repo/buildm2repo.zip
http://svn.apache.org/viewvc/incubator/tuscany/sandbox/cr22rc/buildm2repo/buildm2repo.zip?view=markuppathrev=413899
Which if you unzip in the binary distro has poms and a
[DAS] Generate SDO for test cases at build time
---
Key: TUSCANY-466
URL: http://issues.apache.org/jira/browse/TUSCANY-466
Project: Tuscany
Type: Improvement
Components: Java DAS RDB
Reporter: Brent Daniel
Jeremy Boynes wrote:
On IRC this morning it was suggested that we should move the recursive
code in my sandbox to a different location in the tree so that it was
bit clearer about what was there.
If no-one has any issues, I'll plan on moving the tree to
branches/recursive Tuesday morning
Jean-Sebastien Delfino wrote:
I prefer that we keep this code in the sandbox until we make a
collective decision that this is the approach we will adopt for our M2.
I am not sure why moving the code from sandbox to branches/recursive
will make more clear what it contains.
No problem, I'll
[ http://issues.apache.org/jira/browse/TUSCANY-462?page=all ]
Ed Slattery updated TUSCANY-462:
Component: C++ SCA
Would be nice to generate disable warning for the 'silly' warning on windows
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
[
http://issues.apache.org/jira/browse/TUSCANY-292?page=comments#action_12416026
]
Jim Marino commented on TUSCANY-292:
I don't think we need to log a thrown exception at the origin but should let it
propagate up the call stack until it reaches an
Thank you for contacting the Microlab staff of the Cooper Union EE department.
We apologize, but the e-mail address [EMAIL PROTECTED] is no longer in use.
Please direct all inquiries to [EMAIL PROTECTED], or, if you are having a
computing issue, you may open up a trouble ticket on our system
The easiest solution to this is to check the sandbox code out and
build it using the correct poms.
Jim
On Jun 13, 2006, at 7:29 AM, Scott Kurz wrote:
How does one build sandbox code, for example Jeremy's sandbox
(which he's
moving to a branch) ?
I tried extracting the sandbox and
[ http://issues.apache.org/jira/browse/TUSCANY-429?page=all ]
Andrew Borley updated TUSCANY-429:
--
Attachment: axis2c_wsentrypoint_tests.patch
Another replaced patch file! The last tests one missed some stuff out (I blame
TortoiseSVN!), so here's a new
Hi:
I am new to Tuscany and open source in general. I have yet to download the
latest and greatest software, but I intend on doing so shortly. Prior to
downloading, I am wondering if there is a way to determine how many people
have downloaded the software as of yet and what types of issues (if
OK.. doing a find-replace on the sandbox's poms seems to work... just making
sure that was correct... thanks
On 6/13/06, Jim Marino [EMAIL PROTECTED] wrote:
The easiest solution to this is to check the sandbox code out and
build it using the correct poms.
Jim
On Jun 13, 2006, at 7:29 AM,
As a gentle reminder, please can we have discussions on this mailing
list rather than in JIRA. I know it's tempting just to comment on the
issue but that locks up the discussion inside the bug tracking system
rather than getting it into the open. Preferred practice is to have the
discussion on the
You should not unzip the sandbox structure over the M1 structure.
Just do an svn co of the sandbox and then mvn from there. All of the
poms will come down as part of the checkout and dependencies will be
downloaded as part of the maven build.
Jim
On Jun 13, 2006, at 8:58 AM, Scott Kurz
I noticed that the build for the code in the sandbox builds each module
twice - not sure when this started but it didn't use to. Is anyone else
seeing this or is the m2 setup on my machine messed up?
Thanks
--
Jeremy
-
To
Hi all,
Whilst I wait for the Axis2C WS Entrypoint patches to be looked at, I
thought I would take a look at the couple of scagen issues that Ed has
recently raised (TUSCANY-461 and TUSCANY-462). I haven't heard anyone
talking about improving scagen - is that OK if I take a look?
Cheers
Andrew
I've been seeing the same thing for a while and was also going to ask
about it but never got around to it
On Jun 13, 2006, at 9:07 AM, Jeremy Boynes wrote:
I noticed that the build for the code in the sandbox builds each
module
twice - not sure when this started but it didn't use to. Is
I'd like to also extend the alternative Data Access
Service (DAS) implementations
to access collaboration repositories :
-
data on domino servers (NSF files) using XML Services
-
data in Microsoft Exchange repositories using webDav.
I could definitely help and mentor with
my expertise on
Java RMI Binding Extension
--
Key: TUSCANY-467
URL: http://issues.apache.org/jira/browse/TUSCANY-467
Project: Tuscany
Type: New Feature
Components: Java SCA Samples
Reporter: Venkatakrishnan
Priority: Minor
Create Java RMI
IsContainment and getContainmentProperty do not work
Key: TUSCANY-468
URL: http://issues.apache.org/jira/browse/TUSCANY-468
Project: Tuscany
Type: Bug
Components: Java SDO Implementation
Versions: Java-M1
You should be aware of the Eclipse SOA Tools Project
(http://www.eclipse.org/stp/) since there is a potential overlap with
them...
And there's my cue... :)
I'll introduce myself: my name's Oisin Hurley and I'm on the STP PMC.
Some of you on this list might know me already, from the SCA
After some analysis, it looks like a good move to collapse
CommandFactory and CommandGroup. I'll open a JIRA for this.
Kevin Williams wrote:
We should explore collapsing CommandFactory and CommandGroup since
they are really both factories for commands. This new combined
factory could
Collpase CommandFactory and CommandGroup
Key: TUSCANY-469
URL: http://issues.apache.org/jira/browse/TUSCANY-469
Project: Tuscany
Type: Improvement
Components: Java DAS RDB
Versions: Java-Mx
Reporter: Kevin
DataObject.getXXX(aaa.bbb) throws NumerFormatException even if aaa.bbb is
the XSD element name
--
Key: TUSCANY-470
URL: http://issues.apache.org/jira/browse/TUSCANY-470
Project:
Hi,
Taking the SCA 0.9 XSDs as an example, the implementation.java can
substitute implementation.
element name=implementation type=sca:Implementation/
complexType name=Implementation/
element name=implementation.java type=sca:JavaImplementation
substitutionGroup=sca:implementation/
I did some investigation on the EMF implementation and it seems that I need
to test if the property is transient (in EMF term). Do we have the same
capability in SDO?
Thanks,
Raymond
- Original Message -
From: Raymond Feng [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent:
Hi Nick,
Before you go too far down the path of creating your own tools check out
the support from the EMF SDO project on Eclipse
(http://www.eclipse.org/emf/sdo.php). I haven't checked their latest
builds but in the past they had a wizard that will allow you to create an
EMF model based on
53 matches
Mail list logo
