[
https://issues.apache.org/jira/browse/TUSCANY-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-3505.
--
Resolution: Fixed
Patch applied, thanks for the fix Ivan.
> @Destroy annotation not allowed on non-p
On Thu, Mar 18, 2010 at 10:42 AM, Simon Laws wrote:
>
> I'm seeing the same list as Luciano.
>
> I think we should follow Ant's suggestion and make local changes.I
> don't think we'll get OASIS changes before next week. Anything I can
> do to help?
>
> Simon
>
I'm half way trough all the OTests a
[
https://issues.apache.org/jira/browse/TUSCANY-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Krizsan updated TUSCANY-3505:
--
Attachment: testcase_patch
impl_patch
Patched DestroyProcessor to allow @Dest
[
https://issues.apache.org/jira/browse/TUSCANY-3505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Krizsan updated TUSCANY-3505:
--
Patch Info: [Patch Available]
> @Destroy annotation not allowed on non-public methods.
>
@Destroy annotation not allowed on non-public methods.
--
Key: TUSCANY-3505
URL: https://issues.apache.org/jira/browse/TUSCANY-3505
Project: Tuscany
Issue Type: Bug
Affects Versions: Ja
[
https://issues.apache.org/jira/browse/TUSCANY-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847202#action_12847202
]
Simon Nash commented on TUSCANY-3476:
-
This problem seems ot be caused by using imple
[
https://issues.apache.org/jira/browse/TUSCANY-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash reopened TUSCANY-3476:
-
I am reopening this issue because this change causes the fullapp distributed
scenario to fail. Th
[
https://issues.apache.org/jira/browse/TUSCANY-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash reassigned TUSCANY-3476:
---
Assignee: Simon Nash
> Travel sample fullapp and fullapp-domain launchers use different con
On Thu, Mar 18, 2010 at 6:07 PM, Raymond Feng wrote:
> Hi,
>
> It seems that the official otest suite has latency to fix some of the
> issues. Should we consider the following option to get Tuscany otest build
> stable?
>
> 1) Check out the latest otest from oasis svn
> 2) We maintain a patch with
On Thu, Mar 18, 2010 at 6:16 PM, Luciano Resende wrote:
> On Thu, Mar 18, 2010 at 10:15 AM, Raymond Feng wrote:
>> The following ones should have been fixed now:
>>
>>> Apache Tuscany SCA iTest Nodes binding.sca Using Hazelcast Registry
>>> Apache Tuscany SCA iTest Nodes binding.sca Using Tribes
[
https://issues.apache.org/jira/browse/TUSCANY-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-3498:
-
Assignee: Raymond Feng
> xmlHelper cannot save multi-byte character correctly
> --
On Thu, Mar 18, 2010 at 11:07 AM, Raymond Feng wrote:
> Hi,
>
> It seems that the official otest suite has latency to fix some of the
> issues. Should we consider the following option to get Tuscany otest build
> stable?
>
I'd rather have better turnaround from OASIS, but I think we should
fallba
On Thu, Mar 18, 2010 at 10:15 AM, Raymond Feng wrote:
> The following ones should have been fixed now:
>
>> Apache Tuscany SCA iTest Nodes binding.sca Using Hazelcast Registry
>> Apache Tuscany SCA iTest Nodes binding.sca Using Tribes Registry
>> Apache Tuscany SCA iTest Builder Recusive Multi-Lev
Hi,
It seems that the official otest suite has latency to fix some of the
issues. Should we consider the following option to get Tuscany otest build
stable?
1) Check out the latest otest from oasis svn
2) We maintain a patch with changes on the otest that are not handled by
OASIS yet
3) Hav
> I'm seeing the same list as Luciano.
>
> I think we should follow Ant's suggestion and make local changes.I
> don't think we'll get OASIS changes before next week. Anything I can
> do to help?
>
> Simon
>
The policy otest changes are pretty much the two below. Is there are
JIRA open I can attach
Binding JMS Response type definition should reference wireFormat instead of
defining a new element
--
Key: TUSCANY-3504
URL: https://issues.apache.org/jira/browse/TUSC
On Thu, Mar 18, 2010 at 5:15 PM, Raymond Feng wrote:
> The following ones should have been fixed now:
>
>> Apache Tuscany SCA iTest Nodes binding.sca Using Hazelcast Registry
>> Apache Tuscany SCA iTest Nodes binding.sca Using Tribes Registry
>> Apache Tuscany SCA iTest Builder Recusive Multi-Leve
The following ones should have been fixed now:
Apache Tuscany SCA iTest Nodes binding.sca Using Hazelcast Registry
Apache Tuscany SCA iTest Nodes binding.sca Using Tribes Registry
Apache Tuscany SCA iTest Builder Recusive Multi-Level
Thanks,
Raymond
---
On Thu, Mar 18, 2010 at 9:59 AM, Raymond Feng wrote:
> It seems now composite reference promotion requires the @multiplicity. I'll
> fix the last 3 itests from Luciano's list.
>
I'm looking into the two JMS test issues. And then I could look into
updating the OASIS Tests. BTW, I have raised a new
It seems now composite reference promotion requires the @multiplicity. I'll
fix the last 3 itests from Luciano's list.
Thanks,
Raymond
--
From: "Luciano Resende"
Sent: Thursday, March 18, 2010 9:11 AM
To: ;
Subject: Re: OASIS Schema Updates
On
On Thu, Mar 18, 2010 at 4:52 PM, Luciano Resende wrote:
> On Thu, Mar 18, 2010 at 9:38 AM, Luciano Resende wrote:
>> On Thu, Mar 18, 2010 at 9:18 AM, Simon Laws
>> wrote:
>>> Hi Luciano
>>>
>>> Were you running with the latest code from OASIS? I note that Mike has
>>> been making quite a few ch
On Thu, Mar 18, 2010 at 4:11 PM, Luciano Resende wrote:
> On Thu, Mar 18, 2010 at 2:03 AM, ant elder wrote:
>> Some regressions! There are 235 new fails in the otests and a whole
>> bunch of fails in the Tuscany samples and itest, so anyone with local
>> changes has no way of knowing if they're b
On Thu, Mar 18, 2010 at 9:38 AM, Luciano Resende wrote:
> On Thu, Mar 18, 2010 at 9:18 AM, Simon Laws wrote:
>> Hi Luciano
>>
>> Were you running with the latest code from OASIS? I note that Mike has
>> been making quite a few changes recently but don't know if they
>> address any of these issues
On Thu, Mar 18, 2010 at 9:18 AM, Simon Laws wrote:
> Hi Luciano
>
> Were you running with the latest code from OASIS? I note that Mike has
> been making quite a few changes recently but don't know if they
> address any of these issues.
>
> Simon
>
Running from oTests/newyout, and most of the issu
>
> The only Tuscany failures I'm seeing are :
> Apache Tuscany SCA iTest JMS Message Format jmstextxmlinjmsobjectout
> Apache Tuscany SCA iTest JMS Tests For Selectors
> Apache Tuscany SCA iTest Nodes binding.sca Using Hazelcast Registry
> Apache Tuscany SCA iTest Nodes binding.sca Using Tribes Re
On Thu, Mar 18, 2010 at 2:03 AM, ant elder wrote:
> Some regressions! There are 235 new fails in the otests and a whole
> bunch of fails in the Tuscany samples and itest, so anyone with local
> changes has no way of knowing if they're breaking anything now. What
> sort of time frame are you lookin
[
https://issues.apache.org/jira/browse/TUSCANY-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846945#action_12846945
]
Simon Laws edited comment on TUSCANY-3482 at 3/18/10 3:05 PM:
-
[
https://issues.apache.org/jira/browse/TUSCANY-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846945#action_12846945
]
Simon Laws commented on TUSCANY-3482:
-
Today I spotted that the rutime code to proces
>>
>
> AFAICT these tests aren't working correctly yet and the otests are
> just passing because they only check for a ServiceRuntimeException and
> not checking for any message about what the test is testing, thats in
> both the otests and trunk.
>
> ...ant
>
I'm seeing the same Ant. While the
Some regressions! There are 235 new fails in the otests and a whole
bunch of fails in the Tuscany samples and itest, so anyone with local
changes has no way of knowing if they're breaking anything now. What
sort of time frame are you looking at for fixing these?
...ant
On Wed, Mar 17, 2010 at
On Tue, Mar 16, 2010 at 5:32 PM, Luciano Resende wrote:
> On Tue, Mar 16, 2010 at 10:15 AM, ant elder wrote:
>> On Tue, Mar 16, 2010 at 4:20 PM, Luciano Resende
>> wrote:
>>> On Tue, Mar 16, 2010 at 2:50 AM, Simon Laws
>>> wrote:
I don't have any insight yet but running the otest/ne
I've seen that happen for several reasons - some other module the test
depends on has failed to build cleanly, or something has been renamed
or moved and Hudson remembers the old one. Checking the build summary
in the console log shows what actually happened. I've just deleted the
Hudson workspace
32 matches
Mail list logo
