On Thu, Jan 20, 2011 at 9:36 PM, Scott Kurz wrote:
> I just committed what I hope is a fix in r1061531.
>
> It made the copyInput IndexOutOfBoundsException in
> sample-implementation-extension go away... (will give some more
> thought to whether this fix to interface-wsdl is the best solution).
>
Classification: UNCLASSIFIED
Caveats: NONE
Hi, Simon and others,
I converted by 1.6 policy extension to 2.0. I think/hope I did a
thorough job, but I can't get 2.0 runtime to match my newly defined
intent to the newly defined policy set. The ComponentPolicyBuilderImpl
keeps WARNING that the inten
I just committed what I hope is a fix in r1061531.
It made the copyInput IndexOutOfBoundsException in
sample-implementation-extension go away... (will give some more
thought to whether this fix to interface-wsdl is the best solution).
I can't run that async-services test yet.. I need to update my
On 20/01/2011 21:05, Scott Kurz wrote:
I see the problem in JavaInterfaceImpl.isAsyncServerOperation. The
output type will be an empty list in this case, so I can tweak the
check.
The issue with MediatorImpl concerns me more since I ran the same
tests and didn't notice that problem. One thing
On Thu, Jan 20, 2011 at 9:10 PM, Scott Kurz wrote:
> I recreated that MediatorImpl.copyInput failure now... Maybe the
> problem was that earlier I ran "offline" and had something stale in my
> mvn repo???
>
> Anyway..looking into both problems now..
>
> What was a module you used to notice the 2nd
I recreated that MediatorImpl.copyInput failure now... Maybe the
problem was that earlier I ran "offline" and had something stale in my
mvn repo???
Anyway..looking into both problems now..
What was a module you used to notice the 2nd problem with
JavaInterfaceImpl.isAsyncServerOperation?
I see the problem in JavaInterfaceImpl.isAsyncServerOperation. The
output type will be an empty list in this case, so I can tweak the
check.
The issue with MediatorImpl concerns me more since I ran the same
tests and didn't notice that problem. One thing I noticed during
various tests I ran was
On Thu, Jan 20, 2011 at 8:38 PM, Scott Kurz wrote:
> That's probably my change for TUSCANY-3819.
>
> What are you seeing ?
>
> I should say that there are 10 tests in
> itest/ws/holder-ws-service-multiple-outputs that I still expect to
> fail (am hoping to address that shortly).
>
> Scott
>
I thi
That's probably my change for TUSCANY-3819.
What are you seeing ?
I should say that there are 10 tests in
itest/ws/holder-ws-service-multiple-outputs that I still expect to
fail (am hoping to address that shortly).
Scott
I'm seeing some test fails in the latest svn code with an
IndexOutOfBoundsException in either
JavaInterfaceImpl.isAsyncServerOperation or MediatorImpl.copyInput.
Does anyone have some changes not completely checked in or know
anything that might be related?
...ant
Yang, Gang CTR US USA wrote:
Classification: UNCLASSIFIED
Caveats: NONE
Hi, Simon,
Thank you for the information. It's very helpful for me to better
understand the frameworks in both 1.6 and 2.0. I wish what you described
here be in the book you guys wrote. It doesn't have to be elaborate, but
[
https://issues.apache.org/jira/browse/TUSCANY-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984281#action_12984281
]
Mike Edwards commented on TUSCANY-3821:
---
Stage 1 (including fixup of callback handl
[
https://issues.apache.org/jira/browse/TUSCANY-3821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984277#action_12984277
]
Mike Edwards commented on TUSCANY-3821:
---
Perform this in 2 stages:
1) Enable Axis
Enable binding.ws (Axis2) to deal with Async service invocations
Key: TUSCANY-3821
URL: https://issues.apache.org/jira/browse/TUSCANY-3821
Project: Tuscany
Issue Type: Sub-task
Classification: UNCLASSIFIED
Caveats: NONE
Hi, Simon,
Thank you for the information. It's very helpful for me to better
understand the frameworks in both 1.6 and 2.0. I wish what you described
here be in the book you guys wrote. It doesn't have to be elaborate, but
some key phrases and high level
Classification: UNCLASSIFIED
Caveats: NONE
Thanks, Urso,
I think distribution for 2.0 is slightly different than 1.6. 1.6 has the
Tuscany-sca-all-1.6.jar that includes everything. That's why I was looking for
something at .composite level to specify which binding to use, i.e.
"binding.ws.jaxws
Classification: UNCLASSIFIED
Caveats: NONE
Hi, Simon,
Thanks for the history. It sounds like there is a chance that I could
use jaxws handlers if binding-ws-runtime-jaxws-ri simply relies on JVM
to handle the jaxws runtime. Of course normally the Tuscany user should
only use SCA APIs and not have
Classification: UNCLASSIFIED
Caveats: NONE
Hi, Mike,
The reason I'm asking about the jaxws handlers is that I need to plug in
a new WS-security. I had tried Tuscany Policy interceptor in 1.6 and it
does not seem to work out (I had another post under the title "How to
add new security extension to
[
https://issues.apache.org/jira/browse/TUSCANY-3819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984214#action_12984214
]
Scott Kurz commented on TUSCANY-3819:
-
Checked in patch at r1061329.Note the "bar
On Wed, Jan 19, 2011 at 10:37 PM, Urso Wieske wrote:
> Hi Gang
> I had problems with jax-ws ri. I switched to axis2. May be it's wise for you
> to consider using axis2. I discovered that my callbacks were not being
> injected by the SCA runtime.
> Kind regards
> Urso
>
> Sent from my iPhone
> On 1
On Tue, Jan 18, 2011 at 10:08 PM, Yang, Gang CTR US USA
wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Hi,
>
> I am trying to see how I can add a new WS-security implementation to the WS
> binding. I've got a policy extension hooked into Tuscany runtime using
> Tuscany 1.6. However, I s
21 matches
Mail list logo
