Hi,
I have checked in the first cut of the Maven services for resolving
runtime artifacts transitively.
Jeremy, if you could please have a quick look, we can start looking into
integrating with the host environments.
TA
Meeraj
-Original Message-
From: Meeraj Kunnumpurath
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
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 ./build.sh
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
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
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
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
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
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
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]
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 tests. Having said that I don't think this is essential for
a release. If our samples are documented and work then that is good enough
[
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
Hi Yang,
Yang ZHONG [EMAIL PROTECTED] wrote on 09/25/2006 11:50:18
AM:
More question, is this
element ref=global:element1/
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
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
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
[ 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
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
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
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
element xmlns:global= ref=global:element1/
the XML should
19 matches
Mail list logo
