[
https://issues.apache.org/jira/browse/TUSCANY-1706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1706.
---
Resolution: Fixed
Patch applied under r576055. Thanks.
Change binding dispatch code to
[
https://issues.apache.org/jira/browse/TUSCANY-1705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1705.
---
Resolution: Fixed
Patch applied under r576055
Incorrect WS-Addressing header for
[
https://issues.apache.org/jira/browse/TUSCANY-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1536.
---
Resolution: Fixed
Patch applied under r576059. Vasil, thank you for the contribution.
It looks like Raymond has applied this patch to the trunk but not to
the 1.0 branch. Please can someone apply it to the 1.0 branch.
I have built and tested it with the branch.
Simon
Simon Nash wrote:
I have created a patch for TUSCANY-1705 that also resolves TUSCANY-1706.
(The code changes
Hey Ray
This seems something with surefire, not sure exactly what yet
I'll get back to this in the morning...
On 9/15/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I ran into an issue in the implementation-bpel module from the top-down
build. The error message is as follows. But if
Remove $callback$ prefix from services exposed by callback references
-
Key: TUSCANY-1712
URL: https://issues.apache.org/jira/browse/TUSCANY-1712
Project: Tuscany
Issue
[
https://issues.apache.org/jira/browse/TUSCANY-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash updated TUSCANY-1712:
Attachment: patch1712
Please apply this patch to the trunk and also to the 1.0 branch.
Remove
I have posted a patch for TUSCANY-1712. The change is small and all
the tests pass. Can someone please apply this patch to the trunk
and to the 1.0 branch. Thanks.
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
[
https://issues.apache.org/jira/browse/TUSCANY-1626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1626:
---
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
Deferring minor defects to
[
https://issues.apache.org/jira/browse/TUSCANY-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1646:
---
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
Deferring minor defects to
[
https://issues.apache.org/jira/browse/TUSCANY-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1347:
---
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
Deferring minor defects to
[
https://issues.apache.org/jira/browse/TUSCANY-1539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1539:
---
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
Deferring minor defects to
[
https://issues.apache.org/jira/browse/TUSCANY-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-1686.
--
Resolution: Fixed
Patches are applied so this can be closed now
Cannot throw business exceptions
The JIRA http://issues.apache.org/jira/browse/TUSCANY-1658 is marked as
critical and so is blocking the 1.0 release right now. Is anyone working on
it or know what its status is?
I'll be lowering the priority and deferring it unless someone says
something.
...ant
I'm get a similar build failure related to surefire in the 1.0 branch:
[INFO] Configured Artifact: org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apache\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.
1.zip into
[
https://issues.apache.org/jira/browse/TUSCANY-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1487:
---
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
No way this will make 1.0
[
https://issues.apache.org/jira/browse/TUSCANY-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-1558.
--
Resolution: Fixed
Tried the suggested recreate and the move up to Axis2 1.3 has fixed the problem
[
https://issues.apache.org/jira/browse/TUSCANY-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1702:
---
Fix Version/s: Java-SCA-Next
WSDL generated on Websphere contains an error at the end
[
https://issues.apache.org/jira/browse/TUSCANY-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1679:
---
Fix Version/s: Java-SCA-Next
PBVInvoker always uses service-side classloader to deserialize ...
[
https://issues.apache.org/jira/browse/TUSCANY-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1711:
---
Fix Version/s: Java-SCA-Next
Reference a ws with complex data type...
[
https://issues.apache.org/jira/browse/TUSCANY-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1680:
---
Fix Version/s: Java-SCA-Next
Need a way to detect that PBR can be used when building
[
https://issues.apache.org/jira/browse/TUSCANY-1678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1678:
---
Fix Version/s: Java-SCA-Next
Would like to improve performance by not doing a PBVInvoker.copy in
[
https://issues.apache.org/jira/browse/TUSCANY-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1681:
---
Fix Version/s: Java-SCA-Next
DataObject2XMLStreamReader can't handle a null (or could this be an
I am working on it (as well as TUSCANY-1653). I have fixed the
Tuscany java2wsdl module and verified that the output is correct.
I am now working on the runtime WSDL generation in binding-ws-axis2
and I expect to have a patch for both of these later today.
Simon
ant elder wrote:
The JIRA
Guys, there's a *lot* of development and code changes still going on in the
1.0 branch but hardly any sample and doc fixes happening . I know everyone
wants to get their last minute fixes in but there will be other releases
after 1.0 . If we don't review and fix the samples, build scripts and doc
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
Guys, there's a *lot* of development and code changes still going on in
the
1.0 branch but hardly any sample and doc fixes happening . I know everyone
wants to get their last minute fixes in but there will be other releases
after 1.0 . If we
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
A question though is should we flip the samples over to use NodeImpl instead
of SCAdomain?
To save digging around in the code / ML, what is the new way exactly?
Currently things do:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
I'm also still getting BPEL and OSGi failures in the branch build.
Could you paste in the log of the OSGi failures you get?
...ant
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
A question though is should we flip the samples over to use NodeImpl
instead
of SCAdomain?
To save digging around in the code / ML, what is the new way exactly?
Currently things do:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
I'm also still getting BPEL and OSGi failures in the branch build.
Could you paste in the log of the OSGi failures you get?
...ant
yep, will do. Just building again now
Simon
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
I'm also still getting BPEL and OSGi failures in the branch build.
Could you paste in the log of the OSGi failures you get?
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
I'm also still getting BPEL and OSGi failures in the branch build.
[
https://issues.apache.org/jira/browse/TUSCANY-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-1712:
-
Assignee: Raymond Feng (was: Simon Nash)
Remove $callback$ prefix from services
I have merged the changes into the branch locally. But I need some time to
commit it.
Thanks,
Raymond
- Original Message -
From: Simon Nash [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Sunday, September 16, 2007 1:15 AM
Subject: Please apply TUSCANY-1705 patch to the 1.0
[
https://issues.apache.org/jira/browse/TUSCANY-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1712.
---
Resolution: Fixed
Patch applied under r576320. I'll merge it into the 1.0 branch as well.
The WSDL-less feature doesn't honor the XSD type information in the SDO
parameter/return type
--
Key: TUSCANY-1713
URL:
Cleanup of Simple-BB and Simple-BB-Spring READMEs
-
Key: TUSCANY-1714
URL: https://issues.apache.org/jira/browse/TUSCANY-1714
Project: Tuscany
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/TUSCANY-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haleh mahbod reassigned TUSCANY-1714:
-
Assignee: haleh mahbod
Cleanup of Simple-BB and Simple-BB-Spring READMEs
[
https://issues.apache.org/jira/browse/TUSCANY-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haleh mahbod updated TUSCANY-1714:
--
Attachment: simple-bigbank.zip
Cleanup of Simple-BB and Simple-BB-Spring READMEs
[
https://issues.apache.org/jira/browse/TUSCANY-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
haleh mahbod updated TUSCANY-1714:
--
Attachment: simple-bigbank-spring.zip
attached two zips, one for simple-bb and one for
[
https://issues.apache.org/jira/browse/TUSCANY-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1702.
-
Resolution: Fixed
Fix Version/s: (was: Java-SCA-Next)
[
https://issues.apache.org/jira/browse/TUSCANY-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkatakrishnan reassigned TUSCANY-1714:
Assignee: Venkatakrishnan (was: haleh mahbod)
Cleanup of Simple-BB and
[
https://issues.apache.org/jira/browse/TUSCANY-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-1714:
Fix Version/s: Java-SCA-1.0
Cleanup of Simple-BB and Simple-BB-Spring
I'm getting a build error in implementation-osgi module in the 1.0
branch. Anybody else getting the same error?
testOSGiComponent(org.apache.tuscany.sca.implementation.osgi.invocation.OSGiPropertyTestCase)
Time elapsed: 0.152 sec FAILURE!
junit.framework.ComparisonFailure:
Following the README posted, I did the following in different command
windows:
1) ant runDomainNode
.. starts fine
2) ant runNodeB
... Fails with the following exception trace.
Buildfile: build.xml
runNodeB:
[java] Sep 16, 2007 10:40:30 AM
org.apache.tuscany.sca.node.impl.SCANodeImp
l
[
https://issues.apache.org/jira/browse/TUSCANY-1714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkatakrishnan resolved TUSCANY-1714.
--
Resolution: Fixed
Thanks for the patch. Applied to 1.0 branch and the trunk.
On 9/16/07, haleh mahbod [EMAIL PROTECTED] wrote:
Following the README posted, I did the following in different command
windows:
1) ant runDomainNode
.. starts fine
2) ant runNodeB
... Fails with the following exception trace.
Buildfile: build.xml
runNodeB:
[java] Sep 16, 2007
Incorrect tuscany namespace for implementation.spring
-
Key: TUSCANY-1715
URL: https://issues.apache.org/jira/browse/TUSCANY-1715
Project: Tuscany
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/TUSCANY-1715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1715.
-
Resolution: Fixed
Incorrect tuscany namespace for
If that helps, it is a random error. Happens every 3 or 4 build for me.
Jean-Sebastien Delfino wrote:
I'm getting a build error in implementation-osgi module in the 1.0
branch. Anybody else getting the same error?
Hi,
The axis2 ws binding has an itest that exercises the 'confidentialy policy
intent' which is realized by encrypting the parts of the soap xml. Though
we are just about using Rampart, WSS4J, under the covers there seems to be
bouncycastle's classes doing the work. In the past there had been
[
https://issues.apache.org/jira/browse/TUSCANY-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-1500.
--
Resolution: Fixed
As far as i can tell these patches have now been applied so closing this.
Thanks
On 9/16/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi,
The axis2 ws binding has an itest that exercises the 'confidentialy policy
intent' which is realized by encrypting the parts of the soap xml. Though
we are just about using Rampart, WSS4J, under the covers there seems to be
On 9/16/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi,
The axis2 ws binding has an itest that exercises the 'confidentialy policy
intent' which is realized by encrypting the parts of the soap xml. Though
we are just about using Rampart, WSS4J, under the covers there seems to be
ant elder wrote:
On 9/16/07, Venkata Krishnan [EMAIL PROTECTED] wrote:
Hi,
The axis2 ws binding has an itest that exercises the 'confidentialy policy
intent' which is realized by encrypting the parts of the soap xml. Though
we are just about using Rampart, WSS4J, under the covers there
[
https://issues.apache.org/jira/browse/TUSCANY-1276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1276.
-
Resolution: Fixed
This is now fixed, see the SVN commit history
[
https://issues.apache.org/jira/browse/TUSCANY-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-678.
Resolution: Fixed
This is now fixed, see TUSCANY-1276 for the resolution.
Simon Laws wrote:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
A question though is should we flip the samples over to use NodeImpl
instead
of SCAdomain?
To save digging around in the code / ML, what is the new way exactly?
Simon Laws wrote:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
A question though is should we flip the samples over to use NodeImpl
instead
of SCAdomain?
To save digging around in the code / ML, what is the new way
Simon Nash wrote:
Simon Laws wrote:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
A question though is should we flip the samples over to use NodeImpl
instead
of SCAdomain?
To save digging around in the code / ML, what is the new
[snip]
Raymond Feng wrote:
Hi,
I believe I have a fix now. First, in the
XQueryImplementationProvider, we should set the SAXON databinding for
the services/references of the componentType (implemention) instead of
the component. And then we need to make sure inline schema of the WSDL
Is the release branch really the place for something like this? How about a
sandbox?
...ant
On 9/16/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Author: jsdelfino
Date: Sun Sep 16 15:21:15 2007
New Revision: 576198
URL: http://svn.apache.org/viewvc?rev=576198view=rev
Log:
Strawman
Hi,
I'm almost ready to merge it in. Don't worry, I'll handle it as my next
thing.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Sunday, September 16, 2007 3:41 PM
Subject: Re: Including the XQuery sample in
Let me try to give a little background here. Initially I was having
the same issue as the one described in OPENJPA-256 [1] and to
workaround the issue, we started configuring surefire to use System
Class loader. Looks like this solves the problem building the module
itself, but building the
implementation.bpel build issue
---
Key: TUSCANY-1716
URL: https://issues.apache.org/jira/browse/TUSCANY-1716
Project: Tuscany
Issue Type: Bug
Components: Java SCA BPEL Implementation Extension
Hi,
I'm seeing the following test failure in the implementation-composite sample
with a top-down build but it's passing if I build the module alone.
Any clue?
Thanks,
Raymond
---
T E S T S
I see the same issue
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I'm seeing the following test failure in the implementation-composite sample
with a top-down build but it's passing if I build the module alone.
Any clue?
Thanks,
Raymond
On 9/17/07, Luciano Resende [EMAIL PROTECTED] wrote:
I see the same issue
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I'm seeing the following test failure in the implementation-composite
sample
with a top-down build but it's passing if I build the module alone.
Any
This is raised as a blocker so whats peoples feelings on it? I'd like bpel
to get in 1.0 as well but what should i do tomorrow morning if this is still
unresolved? Defer the JIRA or hold the RC vote till tomorrow evening in the
hope that will be time to find a resolution?
...ant
--
You're right, it's probably not the right place for this :)
I moved it to
http://svn.apache.org/repos/asf/incubator/tuscany/sandbox/sebastien/java/sca/node-api/smaller.
ant elder wrote:
Is the release branch really the place for something like this? How about a
sandbox?
...ant
On
Hi,
I found a fix for this problem: using surefire plugin version 2.3.1-SNAPSHOT
which fixes http://jira.codehaus.org/browse/SUREFIRE-322. It's not perfect
to reference SNAPSHOT versions but I think it's OK as a workaround to run
the test case.
I'll check in the fix if there is no
Jean-Sebastien Delfino wrote:
Simon Nash wrote:
Simon Laws wrote:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
A question though is should we flip the samples over to use NodeImpl
instead
of SCAdomain?
To save digging around in
On 9/17/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Jean-Sebastien Delfino wrote:
Simon Nash wrote:
Simon Laws wrote:
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
On 9/16/07, Simon Laws [EMAIL PROTECTED] wrote:
snip
A question though is should we flip the samples
Could you apply to trunk at least ? Then we could verify we are not
seeing the issue anymore, as it looks like your stackTrace and the one
from Ant and myself are different.
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I found a fix for this problem: using surefire plugin version
Luciano Resende wrote:
Could you apply to trunk at least ? Then we could verify we are not
seeing the issue anymore, as it looks like your stackTrace and the one
from Ant and myself are different.
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I found a fix for this problem: using
Jean-Sebastien Delfino wrote:
Luciano Resende wrote:
Could you apply to trunk at least ? Then we could verify we are not
seeing the issue anymore, as it looks like your stackTrace and the one
from Ant and myself are different.
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I found
[
https://issues.apache.org/jira/browse/TUSCANY-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino reassigned TUSCANY-1704:
---
Assignee: Jean-Sebastien Delfino
Message SPI and associated
Clean up EndpointReference and ReferenceParameters SPI
--
Key: TUSCANY-1717
URL: https://issues.apache.org/jira/browse/TUSCANY-1717
Project: Tuscany
Issue Type: Bug
Components:
[
https://issues.apache.org/jira/browse/TUSCANY-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527927
]
Jean-Sebastien Delfino commented on TUSCANY-1704:
-
Marking 1704 as resolved. Opened TUSCANY-1717
[
https://issues.apache.org/jira/browse/TUSCANY-1704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1704.
-
Resolution: Fixed
Message SPI and associated interfaces need cleanup
Hi,
I'm OK either way. Just want to point out that the scope of the SNAPSHOT
reference will be only for that module and it will be used for the build
time. There are usually SNAPSHOT versions of plugins involved in maven build
especially when the mvn prefix:goal command is used.
Thanks,
[
https://issues.apache.org/jira/browse/TUSCANY-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash updated TUSCANY-1658:
Attachment: patch1658
This is a patch for both TUSCANY-1658 and TUSCANY-1653. I'm not 100%
[
https://issues.apache.org/jira/browse/TUSCANY-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangfeng updated TUSCANY-1718:
--
Attachment: ContributionTestCase.zip
If you run the testcase,please modify the field's value in
[
https://issues.apache.org/jira/browse/TUSCANY-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1640.
-
Resolution: Fixed
Fixed. I merged ReferenceBindingProvider2 and
[
https://issues.apache.org/jira/browse/TUSCANY-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino resolved TUSCANY-1562.
-
Resolution: Fixed
The test case in jira1562 now works.
Service
85 matches
Mail list logo