Hi, Venkata.
Please see my comments below.
Thanks,
Raymond
- Original Message -
From: "Venkata Krishnan" <[EMAIL PROTECTED]>
To:
Sent: Monday, September 25, 2006 2:52 AM
Subject: Re: Queries related to Component Property Loading
Hi Jeremy, Raymond,
Hi Jeremy / Raymond,
- Here is
+1
On 26/09/06, Andrew Borley <[EMAIL PROTECTED]> wrote:
+1 from me
On 9/26/06, Jim Marino <[EMAIL PROTECTED]> wrote:
> I would like to nominate Ignacio as a committer. He has done a great
> deal of work adding non-blocking support into the Java SCA runtime
> and is active in the community thr
+1 from me
On 9/26/06, Jim Marino <[EMAIL PROTECTED]> wrote:
I would like to nominate Ignacio as a committer. He has done a great
deal of work adding non-blocking support into the Java SCA runtime
and is active in the community through things such as list discussions.
Here's my +1.
Jim
--
On Sep 25, 2006, at 6:47 PM, scabooz wrote:
Sebastien did a good job enumerating the rationale for why the
exists in the specifications. Perhaps your concern is over the
name of the
binding, and not the specific reason for its existence? I could be
convinced that "default" is a bad name,
I would like to nominate Ignacio as a committer. He has done a great
deal of work adding non-blocking support into the Java SCA runtime
and is active in the community through things such as list discussions.
Here's my +1.
Jim
-
Thank Frank for suggesting to make note to get addressed in the spec.
Here's a candidate (it's rather XML generic, *not* ChangeSummary specific
during which work I happened to discover the issue):
XSD defines how XML formats.
For XSD
the XML should be
the XML should be
xmlns:global=""
Thank Frank very much for opening spec issue 120 and proposing sdo:unset
which solves 3-2 (unset attribute) and 3-3 (empty many) as well.
Here describes 3-1 (qualified Path) in more details in the case to open a
spec issue:
The "delete" attribute v
Sebastien did a good job enumerating the rationale for why the
exists in the specifications. Perhaps your concern is over the name of the
binding, and not the specific reason for its existence? I could be
convinced that "default" is a bad name, but we'd need a suggestion for
an improvement.
d
WSDL2Java should set the correct annotation for the generated java interface
-
Key: TUSCANY-754
URL: http://issues.apache.org/jira/browse/TUSCANY-754
Project: Tuscany
Hi,
I checked the changes for the first part (references using inbound/
outbound pairs last Friday) as well as cleaned up the connector impl
slightly (it still needs more work, but this can wait). In looking at
wire service, I think we may be able to generalize a bit further and
remove mos
[ http://issues.apache.org/jira/browse/TUSCANY-753?page=all ]
Rajith Attapattu updated TUSCANY-753:
-
Attachment: jmsbinding_jira753_25sep06.patch
The basic design is as follows.
I have tried to follow the spec as much as possible eventhough it is sti
JMS Binding
---
Key: TUSCANY-753
URL: http://issues.apache.org/jira/browse/TUSCANY-753
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Core
Reporter: Rajith Attapattu
Hi All,
I have attached
Hi,
The databinding feature is ready for your test as-is and I'm moving it to
core by the end of the day (the package names have already been refactored).
I used helloworldwsclient and helloworldws samples.
Please let me know if you need more information.
Thanks,
Raymond
- Original Mess
Hi Raymond,
I'd like to proceed with testing async ws (including ws/Axis2 callbacks). Two
requests: can you let me know when you are done with databinding changes so I
can pick up the latest? Second, what are you using to test sync axis binding,
helloworldws*?
Do we implement a "standard" level of the spec, or is the spec
level tied to our implementation? If the former, then separate
archives would make sense; if the latter, I don't see the value.
Simon
kelvin goodson wrote:
I have posted an update of the RC1 release following Ron Gavlin's helpful
Yang,
First of all, this is a pretty rare corner case. Even if the global
namespace wasn't null (for example, assume it's just "http://global";),
your example is an SDO Type with two properties named "element1". The SDO
spec says that if you have more than one property with the same name, the
[ http://issues.apache.org/jira/browse/TUSCANY-494?page=all ]
Pete Robbins closed TUSCANY-494.
Fix Version/s: Cpp-current
Resolution: Fixed
This is fixed in the latest Tuscany code and has also been accepted by the spec
group (included in C++ C&I
Hi,
As discussed with Jeremy on the IRC, I have consolidated on the Wiki the
responses to Jeremy's recent mail on the status of the current release. The
page of this is...
http://wiki.apache.org/ws/Tuscany/TuscanyJava/M2Tasks?action=show
From here on, could we please use this page to further
[EMAIL PROTECTED] wrote:
[snip]
Author: robbinspg
Date: Mon Sep 25 03:00:59 2006
New Revision: 449629
URL: http://svn.apache.org/viewvc?view=rev&rev=449629
Log:
Remove generated Makefiles from svn
Sorry I didn't notice I had committed the generated makefiles too. I had
set the svn:ignore
Thank Frank for clarifying "element ref" mapping. I'm working on
ChangeSummary StAX writer,
there're many places Properties/elements need to be outputed as XML,
such as ChangeSummary.Setting.
Supposing we have such Properties definition:
) please?
Thanks.
--
Yang ZHONG
Hi Yang,
3-1 - SDO XPaths have this limitation.
3-2 and 3-3 - The SDO 2.0.1 ChangeSummary format has no way to distinguish
between an old value that is unset vs. set to default/empty.
This is why I've said that I don't think that it's currently possible to
implement a fully functional interoper
Hi Yang,
"Yang ZHONG" <[EMAIL PROTECTED]> wrote on 09/25/2006 11:50:18
AM:
> More question, is this
>
> mapped to open content please?
No.
> If not (my impression from the specs),
> how to tell local element from global element without NameSpace please?
I'm not sure exactly what you're ask
Thank Frank very much for helping.
More question, is this
mapped to open content please?
If not (my impression from the specs),
how to tell local element from global element without NameSpace please?
On 9/25/06, Frank Budinsky <[EMAIL PROTECTED]> wrote:
Global elements are called open con
Are there enough of you interested in discussing the mechanics and detail of
the process to closing of the Java M2 release on IRC today?
Here's a list of things I'd like to discuss either on IRC or the mailing
list. If they get discussed on IRC I'll post a summary of what gets
resolved later.
A
>From a fresh checkout and after nuking my repo I get:
[INFO] -
---
[INFO] Building Apache Tuscany Simple WebApp Sample
[INFO]task-segment: [clean]
[INFO] ---
[
http://issues.apache.org/jira/browse/TUSCANY-742?page=comments#action_12437576
]
Kelvin Goodson commented on TUSCANY-742:
I applied these file in a mass check-in for Tuscany-653 earlier today
> Release Documentation
>
Re tests... yes we should have a simple to run test suite ... scatest! The
existing scatest is justa MyValue sample with some extras thrown in. We
need more "unit test"s. Having said that I don't think this is essential for
a release. If our samples are documented and work then that is good enoug
I'm currently working on making the JSON-RPC binding a little more
Dojo friendly by making it expose a SMD url for bound services.
I also plan on looking further into a JSON-RPC reference binding. If
anyone has any other suggestions, I'm all ears.
-Bert
On 8/31/06, ant elder <[EMAIL PROTECTED]
Yang, I agree with you that this needs to be changed in the spec.
"If SDO Types and Properties were not originally defined by an XSD, or if
the original XSD declaration information is not available, the helper
methods *may* return null or false."
Thanks,
Frank.
"Yang ZHONG" <[EMAIL PROTECTED]
Global elements are called open content properties in SDO. The 2.0.1. spec
says that a property is from open content if it appears in
getInstanceProperties() but not in getType.getProperties(). One way to
check this: !d.getType.getProperties().contains(p). Another more efficient
way is !p.getCo
Support soapbinding element in binding.ws
-
Key: TUSCANY-752
URL: http://issues.apache.org/jira/browse/TUSCANY-752
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Axis Binding
Hi...
I am trying to build the RMI Binding project alone, for coverage report and
am using the following command..
'mvn cobertura:cobertura' in the RMI Binding project directory.
I end with the follwoing exception. This seems to be the case with any
project that I run.
For example when I run w
[ http://issues.apache.org/jira/browse/TUSCANY-638?page=all ]
ant elder updated TUSCANY-638:
--
Component/s: (was: Java SCA Axis Binding)
Removed JIRA from the axis binding component for now as we'll likely not have a
binding.axis in the near future
>
[ http://issues.apache.org/jira/browse/TUSCANY-721?page=all ]
ant elder closed TUSCANY-721.
-
Resolution: Fixed
Patch appied in revision 443381, see discussion thread:
http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200609.mbox/[EMAIL
PROTECTED]
[ http://issues.apache.org/jira/browse/TUSCANY-120?page=all ]
ant elder closed TUSCANY-120.
-
Resolution: Fixed
Not really clear what the status of this and all he attached patches is. I'm
going to assume all these patches are either in or now superseeded by
[ http://issues.apache.org/jira/browse/TUSCANY-70?page=all ]
ant elder closed TUSCANY-70.
Resolution: Fixed
I'm assuming this was for the old M1 code base and is no longer relevant.
> Update Tuscany SCA implementation to use SDO extension API
> -
I have posted an update of the RC1 release following Ron Gavlin's helpful
comments on tuscany-user
See http://people.apache.org/~kelvingoodson/sdo_java/RC1a/
I have now managed to produce detached .asc files (--detach-sig), and for
the moment I have experimented with creating a combined spec and
A few things:
- Python extension - could re-jig the core to allow Python components
to not require a .componentType side file. Not necessary, but nice to
have.
- PHP extension - if we want to include this we need to add reference
& property support to components and a client API (a locateService
Hi Jeremy, Raymond,
Hi Jeremy / Raymond,
- Here is what I propose to do w.r.t. Component Properties
1) I have added a new attribute called 'override' to capture the override
options and have defined three constants 'must', 'may', 'no' that can be set
to this attribute. I have done away with th
There have been significant changes since our last C++ release so I think we
should plan for an M2 release in the next couple of weeks. We have updated
to the latest assembly model, built a basic extension mechanism and now have
extensions for Ruby, Python, PHP. Functionally this seems like good c
Sounds good.
On 25/09/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Pete Robbins wrote:
> I've checked in a change to the linux automake for C++ SCA to allow
> building
> of the extensions to be optional.
>
> I've added --enable-XXX to configure where XXX is php, python, ruby.
> The ./b
Pete Robbins wrote:
I've checked in a change to the linux automake for C++ SCA to allow
building
of the extensions to be optional.
I've added --enable-XXX to configure where XXX is php, python, ruby.
The ./build.sh script in the sca root does not specify these so they will
NOT be built by defau
On Sep 24, 2006, at 10:45 PM, Luciano Resende wrote:
There was some discussion in IRC about using mvn export to generate
source
distribution for Tuscany. I was wondering if this could could be
integrated
in the build process, using maven assembly plugin ? or some other
plugin
that I might
43 matches
Mail list logo
