[
https://issues.apache.org/jira/browse/TUSCANY-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reassigned TUSCANY-1608:
---
Assignee: Simon Laws
Rationalize sample and demo ant build and run scripts
[
https://issues.apache.org/jira/browse/TUSCANY-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-1608.
-
Resolution: Fixed
For those sample and demos that require specific dependencies to be
For http://issues.apache.org/jira/browse/TUSCANY-1608 I've put in a change,
based on the ant generator plugin, to bring some automation to the process
of building the ant files for the samples and demos. For any sample or demo
that requires explicit dependencies, e.g. the webapp samples, I've
Firstly, should this be included in 1.1?
This new JMS host module can only be used once on any particular machine as
it uses a specific port (61616?). This causes problems in our demos and
samples unless we choose our dependencies carefully. If you use the
manifest/all approach then you always
-- Forwarded message --
From: Simon Laws [EMAIL PROTECTED]
Date: Dec 29, 2007 11:01 AM
Subject: Re: Release 1.1 - what will be ready for next week?
To: tuscany-dev@ws.apache.org
On Dec 28, 2007 4:00 PM, Luciano Resende [EMAIL PROTECTED] wrote:
Implementation-bpel was OK. I
On Jan 2, 2008 8:58 AM, Simon Laws [EMAIL PROTECTED] wrote:
For http://issues.apache.org/jira/browse/TUSCANY-1608 I've put in a
change,
based on the ant generator plugin, to bring some automation to the process
of building the ant files for the samples and demos. For any sample or
demo
that
On Jan 2, 2008 9:09 AM, Simon Laws [EMAIL PROTECTED] wrote:
Firstly, should this be included in 1.1?
This new JMS host module can only be used once on any particular machine
as
it uses a specific port (61616?). This causes problems in our demos and
samples unless we choose our dependencies
UpdateGenerator forms update statement with where clause like this -
iterate over all PKs and include them in where clause. Then iterate
over all changed fields and include them in where clause with values
set to old values from change summary. In case the PK itself is being
changed, this results
support update of PK
Key: TUSCANY-1944
URL: https://issues.apache.org/jira/browse/TUSCANY-1944
Project: Tuscany
Issue Type: Bug
Components: Java DAS RDB
Affects Versions: Java-DAS-Next
On Jan 2, 2008 10:53 AM, Mike Edwards [EMAIL PROTECTED]
wrote:
snip
We should be building:
a) runtimes of various kinds (SCA standalone, embedded within Tomcat, etc)
b) applications, containing only the code and other artifacts required
for the application itself
and then have some
On Jan 2, 2008 11:56 AM, Simon Nash [EMAIL PROTECTED] wrote:
I did a full checkout of Java SCA and tried to build it. I got the
following failure in samples/calculator-implementation-policies.
Looking at the messages, I see validation errors followed by a
problem with login configuration.
On Jan 2, 2008 12:00 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Jan 2, 2008 10:53 AM, Mike Edwards [EMAIL PROTECTED]
wrote:
Folks,
Some comments
Yours, Mike.
ant elder wrote:
On Jan 2, 2008 8:58 AM, Simon Laws [EMAIL PROTECTED] wrote:
For
[
https://issues.apache.org/jira/browse/TUSCANY-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1789:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
move to 1.1 as I expect
[
https://issues.apache.org/jira/browse/TUSCANY-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-1742.
---
Resolution: Fixed
module has now been removed
tuscany-interface-wsdl-runtime module version
[
https://issues.apache.org/jira/browse/TUSCANY-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1742:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
set as closed at 1.1
[
https://issues.apache.org/jira/browse/TUSCANY-1762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-1762.
---
Resolution: Fixed
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
[
https://issues.apache.org/jira/browse/TUSCANY-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1622:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
move to 1.1
bigbank
[
https://issues.apache.org/jira/browse/TUSCANY-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1710:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
move to 1.1
Get
[
https://issues.apache.org/jira/browse/TUSCANY-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1616:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
move to 1.1
[
https://issues.apache.org/jira/browse/TUSCANY-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1601:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
move to 1.1
README for
[
https://issues.apache.org/jira/browse/TUSCANY-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1595:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
move to 1.1
[
https://issues.apache.org/jira/browse/TUSCANY-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1594:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.1
move to 1.1
[
https://issues.apache.org/jira/browse/TUSCANY-1265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-1265.
---
Resolution: Fixed
Am closing this as I think it is a JDK issue. Cleaning before doing the
On Dec 20, 2007 10:07 PM, Simon Laws [EMAIL PROTECTED] wrote:
As an experiment I looked down the first page of the outstanding bug list
[1] allocating to release 1.1 those bugs that I believed should be fixed.
I was looking for the sort of thing which showed a failure of some feature
of
On Jan 2, 2008 2:11 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Dec 20, 2007 10:07 PM, Simon Laws [EMAIL PROTECTED] wrote:
As an experiment I looked down the first page of the outstanding bug
list
[1] allocating to release 1.1 those bugs that I believed should be
fixed.
I was looking for
On Jan 2, 2008 1:23 PM, ant elder [EMAIL PROTECTED] wrote:
On Jan 2, 2008 12:00 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Jan 2, 2008 10:53 AM, Mike Edwards [EMAIL PROTECTED]
wrote:
Folks,
Some comments
Yours, Mike.
ant elder wrote:
On Jan 2, 2008 8:58 AM,
Folks,
Looks like there are differences between the IBM JDK and Sun JDK on this
point. Certainly, the underlying security implementations within those
JDKs are very different. It is going to be necessary to double check
any security related code against both of those JDKs.
Yours, Mike.
Folks,
Perhaps this calls for something more general which will support other
use cases.
How about some form of management interfaces which will allow an
application to get information about entities inside the runtime in a
controlled fashion? So the idea would be to get some
I just committed r608125 which changes the serialization format of the
CallableReference and ServiceReference signature types from base64 binary
to XML strings (see TUSCANY-1943).
There are some method signatures that pass around service references
using the Externalizable type. I did not
[
https://issues.apache.org/jira/browse/TUSCANY-1943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash resolved TUSCANY-1943.
-
Resolution: Fixed
Committed as r608125.
Use XML serialization for CallableReference instead
I took Venkat's post as expressing a need for some kind of validation
that would be performed before the composite is allowed to be used by
the runtime. This seems to preclude a solution based on management
interfaces, as these would presumably not come into play until the
composite is actually
Apologies for the long delay in responding to this.
I am concerned about the number of significant JIRAs that are open
against the current trunk code. I have been working on two of these
that I consider to be must fix for 1.1. They are TUSCANY-1849 and
TUSCANY-1939. I have a fix for
I've also abandoned this approach for now as after many many hours I just
couldn't get the XML data binding to produce wrapped style XML even with
WSDL interfaces. So instead of using the XML databinding I'll use the Axiom
databinding and just convert the XML strings from/to OMElements myself.
On Jan 2, 2008 3:44 PM, Simon Nash [EMAIL PROTECTED] wrote:
I just committed r608125 which changes the serialization format of the
CallableReference and ServiceReference signature types from base64 binary
to XML strings (see TUSCANY-1943).
There are some method signatures that pass around
On Jan 2, 2008 4:06 PM, Simon Nash [EMAIL PROTECTED] wrote:
Apologies for the long delay in responding to this.
I am concerned about the number of significant JIRAs that are open
against the current trunk code. I have been working on two of these
that I consider to be must fix for 1.1.
On Jan 2, 2008 2:20 PM, ant elder [EMAIL PROTECTED] wrote:
On Jan 2, 2008 2:11 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Dec 20, 2007 10:07 PM, Simon Laws [EMAIL PROTECTED] wrote:
As an experiment I looked down the first page of the outstanding bug
list
[1] allocating to release
I just did an svn up and full build. All was OK until I got to the
itests and contribution-multiple. Here's the failure. It looks like
null was returned from domain.getCompositeBuilder(). Any ideas?
Simon
[INFO] -
---
Comments inline.
Simon
Simon Laws wrote:
On Jan 2, 2008 1:23 PM, ant elder [EMAIL PROTECTED] wrote:
On Jan 2, 2008 12:00 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Jan 2, 2008 10:53 AM, Mike Edwards [EMAIL PROTECTED]
wrote:
Folks,
Some comments
Yours, Mike.
ant elder wrote:
Simon Laws wrote:
I'm putting Sebastien's ant file generator into the build. The snag is that
it builds ant files based on dependencies it finds at the module level. We
ship a release excluding all but the latest level of dependencies. Hence the
ant file may be looking for dependencies that we
Simon Laws wrote:
On Dec 21, 2007 5:25 PM, Luciano Resende [EMAIL PROTECTED] wrote:
Does the ant file generator support projects that depend on wsdl
generation or sdo type generation? If not, some samples, that have
working ant scripts, might get broken...
On Dec 21, 2007 9:21 AM, Simon Laws
On Jan 2, 2008 5:04 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Jan 2, 2008 2:20 PM, ant elder [EMAIL PROTECTED] wrote:
On Jan 2, 2008 2:11 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Dec 20, 2007 10:07 PM, Simon Laws [EMAIL PROTECTED]
wrote:
As an experiment I looked down the
[snip]
Simon Laws wrote:
Looking at what we have at the moment the main issue I'm having is with
Saxon. implementation-bpel depends on 8.7 and other parts of Tuscany, e.g.
xml-bigbank, have a dependency on 9.0.0.2. I tried bringing
implementation-bpel up to 9.0.0.2 with no luck. Is there
[
https://issues.apache.org/jira/browse/TUSCANY-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash resolved TUSCANY-1939.
-
Resolution: Fixed
Fixed under r608213.
Can't pass business exceptions across Web services
It looks like my commit r608213 has broken the exceptions-cross-binding
itest. My apologies for this. I am looking into this now. My first
impression is that I need to refine the code for matching exception types
to data bindings in DefaultDataBindingExtensionPoint.introspectType() so
that the
Simon Laws wrote:
On Dec 20, 2007 10:07 PM, Simon Laws [EMAIL PROTECTED] wrote:
As an experiment I looked down the first page of the outstanding bug list
[1] allocating to release 1.1 those bugs that I believed should be fixed.
I was looking for the sort of thing which showed a failure of some
I ran the test again (standalone, not from the itest directory)
and it works OK now. I can't understand what changed since the
earlier failure. See below for the error message and stack trace
that I got earlier. Any insights into this?
Simon
Original Message
Subject:
Rajini Sivaram wrote:
Sebastien,
Sorry, ignore my previous note (the one below). Even with assets not in the
classpath, I can run launch.LaunchCloud as long as the assets contribution
is added first. The code in svn does:
currencyNode.addContribution(http://cloud;, cloudContribution);
Rajini Sivaram wrote:
Sebastien,
When I was implementing OSGi bundle contributions, I was very frustrated
about the fact that even though bundles can have cyclic dependencies,
bundles with cyclic dependencies could not be added to SCA, if the bundles
contained SCA artifacts
On Jan 2, 2008 7:04 PM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
Simon Laws wrote:
Looking at what we have at the moment the main issue I'm having is with
Saxon. implementation-bpel depends on 8.7 and other parts of Tuscany,
e.g.
xml-bigbank, have a dependency on 9.0.0.2.
49 matches
Mail list logo
