on tuscany/mail-lists.html - commits list on www.mail-archive.com is not always
complete
Key: TUSCANY-746
URL: http://issues.apache.org/jira/browse/TUSCANY-746
Jeremy,
Can you give a quick status on this? I believe this is related to the issue
discussed in this thread
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg07983.html and I've
upped TUSCANY-648 jira to blocking. This is blocking now progress on BigBank
integration work going
Oops. I forgot to mention, The stuff that I posted to the Wiki about project
work for M.Sc students is at
http://wiki.apache.org/ws/Tuscany/CommunityBuilding
Geoff
On 22/09/06, Geoffrey Winn [EMAIL PROTECTED] wrote:
Raymond,
Thank you, that worked fine.
Geoff.
On 21/09/06, Raymond Feng
[ http://issues.apache.org/jira/browse/TUSCANY-742?page=all ]
Yang ZHONG updated TUSCANY-742:
---
Attachment: BUILDING
BUILDING part of the Release Documentation; please review and I'll incorporate
your inputs.
Release Documentation
-
[ http://issues.apache.org/jira/browse/TUSCANY-742?page=all ]
Yang ZHONG updated TUSCANY-742:
---
Attachment: CHANGES
CHANGES part of the Release Documentation; please review and I'll incorporate
your inputs.
Thank Frank very much for summarizing all the
[ http://issues.apache.org/jira/browse/TUSCANY-712?page=all ]
Frank Budinsky closed TUSCANY-712.
--
recently added file TypeConversionTestCase.java is not compatible with JDK 1.4
If we want interop can't we say use binding.ws since binding.sca
isn't really meant for interop but for optimization and abstraction
of the physical binding? I have a couple of concerns here. The
biggest one is that I don't want to require a web services stack for
the Java runtime (it
Update SDO overview of Tuscany site
--
Key: TUSCANY-751
URL: http://issues.apache.org/jira/browse/TUSCANY-751
Project: Tuscany
Issue Type: Improvement
Components: Website
[ http://issues.apache.org/jira/browse/TUSCANY-751?page=all ]
Yang ZHONG updated TUSCANY-751:
---
Attachment: property.gif
Property Class Diagram; please review and I'll incorporate your inputs.
Update SDO overview of Tuscany site
[ http://issues.apache.org/jira/browse/TUSCANY-751?page=all ]
Yang ZHONG updated TUSCANY-751:
---
Attachment: DataObject.gif
DataObject Class Diagram; please review and I'll incorporate your inputs.
Update SDO overview of Tuscany site
[ http://issues.apache.org/jira/browse/TUSCANY-751?page=all ]
Yang ZHONG updated TUSCANY-751:
---
Attachment: overview.gif
Overview Class Diagram; please review and I'll incorporate your inputs.
Update SDO overview of Tuscany site
[ http://issues.apache.org/jira/browse/TUSCANY-751?page=all ]
Yang ZHONG updated TUSCANY-751:
---
Attachment: ChangeSummary.gif
ChangeSummary Class Diagram; please review and I'll incorporate your inputs.
Update SDO overview of Tuscany site
Thank Andrew for the support
and thank Kelvin and Geoff for the text contribution.
I propose this brief description right after SDO is a natural format ...:
SDO provides flexible data structures that allow data to be organized
as graphs of objects (called data objects) that are composed of
I have posted a set of files as release candidate 1 of Java SDO at
http://people.apache.org/~kelvingoodson/
I'm sure there will be some issues with them. One thing I have run out of
time to figure out is how to get a short
signature file using gpg, so the .asc files are rather big. If anyone
Hi,
I have some minor comments below.
Based on the discussions, I think my initial proposal is at least a
short-term fix. If we all agree, I'll go ahead to commit the changes.
Thanks,
Raymond
- Original Message -
From: Jim Marino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
To allow Python components to handle more than just simple data types,
we need to decide how we present structured data / complex types to
Python components. We'll probably want to support many more data binding
options in the future, but we need one simple solution as a starting point.
For
Yep, I was thinking about this too - I think you're right that we need
something soon (and basing it on an XML technology that's already
available is the right way to do this) and then an SDO API later
(probably wrappering the C++ implementation, in a similar way to the
PHP SDO package).
As
17 matches
Mail list logo
