[
https://issues.apache.org/jira/browse/TUSCANY-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525027
]
ant elder commented on TUSCANY-1654:
Ok i've got the geronimo-tuscany integration up and running and have been
[
https://issues.apache.org/jira/browse/TUSCANY-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525030
]
Kelvin Goodson commented on TUSCANY-1527:
-
I had a play with this and have enabled notifications in our
[
https://issues.apache.org/jira/browse/TUSCANY-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-1657.
--
Resolution: Fixed
This should be fixed now as of yesterday
Dynamically generated WSDL using
I've updated the JIRA for this after debugging through the Geronimo-Tuscany
integration: https://issues.apache.org/jira/browse/TUSCANY-1654.
Its an issue with the way the context path is calculated currently in the
Geronimo-Tuscany code. I think there will need to be a fixed context path
used
We've 54 open JIRAs targeted for the SCA 1.0 release and just over one week
left before the first 1.0 RC, and there's 56 JIRAs in SCA-Next which likely
some of them may need to moved to 1.0. It may be time to start focusing on
JIRAs instead of new function if we're to get most of those resolved.
[
https://issues.apache.org/jira/browse/TUSCANY-1282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1282:
---
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
The webapp host uses a
On 9/2/07, Simon Laws [EMAIL PROTECTED] wrote:
On 8/31/07, Simon Laws [EMAIL PROTECTED] wrote:
On 8/31/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
The operation.getInput() cannot be null to qualify for the wrapper
style.
There must be a part in the input message
[
https://issues.apache.org/jira/browse/TUSCANY-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1337:
---
Fix Version/s: (was: Java-SCA-1.0)
Java-SCA-Next
Difering this as it
[
https://issues.apache.org/jira/browse/TUSCANY-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1559:
---
Summary: Pass-by-value interceptor not necessary with the Axis2 WS binding
(was: Exception
[
https://issues.apache.org/jira/browse/TUSCANY-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525053
]
Vamsavardhana Reddy commented on TUSCANY-1654:
--
Even if I decide to use a fixed context path (say
I'm looking at what we could do for TUSCANY-1559 which is about unnecessary
pass-by-value copies causing failures when arguments aren't serializable.
The problem is on line 260 of JavaComponentContextProvider where it tries to
determine if the pass-by-value invoker is required, but it doesn't take
[
https://issues.apache.org/jira/browse/TUSCANY-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525058
]
ant elder commented on TUSCANY-1654:
Thats a good point, but the problem with just using the last part of the
[
https://issues.apache.org/jira/browse/TUSCANY-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525060
]
ant elder commented on TUSCANY-1654:
I'm thinking we'll have to go with adding a getContextPath method to the
On 9/5/07, ant elder [EMAIL PROTECTED] wrote:
On 9/2/07, Simon Laws [EMAIL PROTECTED] wrote:
On 8/31/07, Simon Laws [EMAIL PROTECTED] wrote:
On 8/31/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
The operation.getInput() cannot be null to qualify for the wrapper
Ant,
ant elder wrote:
I'm looking at what we could do for TUSCANY-1559 which is about unnecessary
pass-by-value copies causing failures when arguments aren't serializable.
The problem is on line 260 of JavaComponentContextProvider where it tries to
determine if the pass-by-value invoker is
[
https://issues.apache.org/jira/browse/TUSCANY-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525075
]
Kelvin Goodson commented on TUSCANY-1638:
-
Could you please say how you re invoking the generator and what
Comments inline.
On 9/4/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Ignacio Silva-Lepe wrote:
Part of the design of binding-notification is that
NotificationReferenceBindingProvider
serves as a producer service to handle subscription requests from
consumers.
Because of this,
Get error: faultCode=UNBOUND_PREFIX: Unable to determine namespace of
'ax21:MyException'
Key: TUSCANY-1664
URL: https://issues.apache.org/jira/browse/TUSCANY-1664
[
https://issues.apache.org/jira/browse/TUSCANY-1664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nishant Joshi updated TUSCANY-1664:
---
Attachment: ExampleService.java
MyException.java
I have concerns about making the Tuscany code wrong to compensate for
the generated WSDL being wrong. This feels like a step in the wrong
direction, and it won't allow non-Tuscany Web service clients to call
Tuscany services that use generated WSDL.
Instead, I'd prefer to have Tuscany
[
https://issues.apache.org/jira/browse/TUSCANY-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Goodson closed TUSCANY-1540.
---
Resolution: Fixed
tests from patch added to the new toolsTest project
Abstract Static
Sample to demo DAS with external Transaction Manager
Key: TUSCANY-1665
URL: https://issues.apache.org/jira/browse/TUSCANY-1665
Project: Tuscany
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/TUSCANY-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kelvin Goodson updated TUSCANY-1359:
Patch Info: (was: [Patch Available])
patch available flag was set in error
New
Thank you Raymond. I am checking it out.
JOTM seems working well with JDK5 when used without Tomcat.
So, I am trying to create a simple quick non-web sample using JOTM. In this
MoneyTransfer example, user entered amount will be withdrawn from one of his
bankaccount using one call to
On 9/5/07, Simon Nash [EMAIL PROTECTED] wrote:
I have concerns about making the Tuscany code wrong to compensate for
the generated WSDL being wrong. This feels like a step in the wrong
direction, and it won't allow non-Tuscany Web service clients to call
Tuscany services that use generated
[
https://issues.apache.org/jira/browse/TUSCANY-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amita Vadhavkar updated TUSCANY-1665:
-
Attachment: 1665.patch
please see all details from
[
https://issues.apache.org/jira/browse/TUSCANY-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525098
]
Amita Vadhavkar commented on TUSCANY-1665:
--
Please see that the original copyright was preserved in the 2
[
https://issues.apache.org/jira/browse/TUSCANY-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525099
]
Kelvin Goodson commented on TUSCANY-1659:
-
could you please attach the report file from the
On 9/5/07, Mike Edwards [EMAIL PROTECTED] wrote:
Ant,
ant elder wrote:
I'm looking at what we could do for TUSCANY-1559 which is about
unnecessary
pass-by-value copies causing failures when arguments aren't
serializable.
The problem is on line 260 of JavaComponentContextProvider where
+1 to doing the fixup in one place, and rationalizing all the
places where we generate WSDL. I'd appreciate some pointers to
where these are as I don't think I've found them all yet :-)
Simon
Simon Laws wrote:
On 9/5/07, Simon Nash [EMAIL PROTECTED] wrote:
I have concerns about making
But doesn't that mean we're not going to work with wsdl generated by Axis2
tooling (and likely others) and all the existing services using that wsdl
and returning it with ?wsdl.
Its even debatable the wsdl is wrong as wrapped style has been used long
before jaxws came along but never precisely
On 9/5/07, Simon Nash [EMAIL PROTECTED] wrote:
+1 to doing the fixup in one place, and rationalizing all the
places where we generate WSDL. I'd appreciate some pointers to
where these are as I don't think I've found them all yet :-)
Simon
Simon Laws wrote:
On 9/5/07, Simon Nash
[
https://issues.apache.org/jira/browse/TUSCANY-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525115
]
Kelvin Goodson commented on TUSCANY-1659:
-
I get no errors on my pendrivelinux env (a debian derivative)
FYI...
In running through the following code path with multiple threads I noticed
the following, and opened a JIRA on AXIOM:
Caused by: java.util.ConcurrentModificationException: concurrent access to
HashMap attempted by Thread
at java.util.HashMap.onEntry(HashMap.java:213)
at
We could fix this issue by allowing some headers on the Message. The
DataBinding interceptor can then use one header to pass a flag down so that
the Pass-By-Value invoker can skip the copy.
Thanks,
Raymond
- Original Message -
From: ant elder [EMAIL PROTECTED]
To: tuscany-dev
At this moment, the code works as Ignacio described. We defer the activation
of a reference to the first time it's used for invocation. If we decide that
we need to agressively start the reference bindings, we can add the part
back to CompositeActivatorImpl.
Thanks,
Raymond
- Original
Sure, thats just making the source and target interfaces use different
databindings caused a databinding transformation explicit on the message.
So if you want it explicit like that that sounds ok to me as well.
Still seems like the pass-by-value code should be out of the Java
implementation and
[snip]
Simon Laws wrote:
I've done a bit more investigation now. For the signature
String foo()
Axis2 Java2WSDL generates
wsdl:types
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
attributeFormDefault=qualified elementFormDefault=qualified
[snip]
Raymond Feng wrote:
At this moment, the code works as Ignacio described. We defer the
activation of a reference to the first time it's used for invocation.
If we decide that we need to agressively start the reference bindings,
we can add the part back to CompositeActivatorImpl.
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
snip
I'm trying to understand the overall picture before choosing a side:
- tolerate what Axis2 generates in our isWrapped() algorithm?
Is it really just the wsdl that Axis2 (1.2) generates? What about anyone
using an existing wsdl
ant elder wrote:
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
snip
I'm trying to understand the overall picture before choosing a side:
- tolerate what Axis2 generates in our isWrapped() algorithm?
Is it really just the wsdl that Axis2 (1.2) generates? What about
On 8/30/07, ant elder [EMAIL PROTECTED] wrote:
This thread has gone quiet but there's been more discussion on this in
TUSCANY-1654 (in case people aren't reading all the jira comments).
How about we just have a ServletHost getContextPath() modeled after the
Servlet APIs getContextPath method?
Rajini,
If this goes into 1.0, can you please update Java user doc[1]?
Thanks,
Haleh
[1]:http://incubator.apache.org/tuscany/sca-java-user-guide.html
On 8/30/07, Rajini Sivaram [EMAIL PROTECTED] wrote:
Raymond,
The classes annotated in the bundle should be the classes used to
implement
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
ant elder wrote:
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
snip
I'm trying to understand the overall picture before choosing a side:
- tolerate what Axis2 generates in our isWrapped() algorithm?
Is it
Jean-Sebastien Delfino wrote:
[snip]
Simon Laws wrote:
I've done a bit more investigation now. For the signature
String foo()
Axis2 Java2WSDL generates
wsdl:types
xs:schema xmlns:xs=http://www.w3.org/2001/XMLSchema;
attributeFormDefault=qualified
Note that we have a similar issue that I'm looking at under the
wsdl2java tooling, described in this post [1]
[1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg22726.html
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Jean-Sebastien Delfino wrote:
[snip]
Simon Laws
Comments inline.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, September 05, 2007 9:03 AM
Subject: Re: Issue with dynamic creation of
NotificationReferenceBindingProvider
[snip]
Raymond Feng
On 9/5/07, Luciano Resende [EMAIL PROTECTED] wrote:
Note that we have a similar issue that I'm looking at under the
wsdl2java tooling, described in this post [1]
[1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg22726.html
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED]
In the case I'm investigating, the issue is around checking if the
wrapper style is in use for the wsdl, but the problem is that
wsdl2java generates wrong interfaces for the wsdl in question.
On 9/5/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/5/07, Luciano Resende [EMAIL PROTECTED] wrote:
Simon,
Thanks for the pointers. I will modify web services binding locally to try
out axis2 based SOAP/JMS as suggested.
In particular, I am looking to support JMS features such as client
acknowledgements, application properties, and publications of XML as well as
SOAP messages. I will try it
On 9/5/07, Dinesh Shahane [EMAIL PROTECTED] wrote:
Simon,
Thanks for the pointers. I will modify web services binding locally to try
out axis2 based SOAP/JMS as suggested.
In particular, I am looking to support JMS features such as client
acknowledgements, application properties, and
[
https://issues.apache.org/jira/browse/TUSCANY-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1521.
---
Resolution: Invalid
The stacktrace points to very old code. Please reopen it with the
I agree that interoperability is important, not just with Axis2 but
also with other Web Service stacks out there.
The best guide to industry standard Web Service interoperability
that I am aware of is the WS-I Basic Profile.
If we send an empty body in the case of a no-argument Java method
(as
[
https://issues.apache.org/jira/browse/TUSCANY-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1520.
---
Resolution: Invalid
The stacktrace points to old code which is not in trunk any more.
ant elder wrote:
On 8/30/07, ant elder [EMAIL PROTECTED] wrote:
This thread has gone quiet but there's been more discussion on this in
TUSCANY-1654 (in case people aren't reading all the jira comments).
How about we just have a ServletHost getContextPath() modeled after the
Servlet APIs
Done under revision #573040
On 9/3/07, Luciano Resende [EMAIL PROTECTED] wrote:
Contribution modules have couple of @deprecated artifacts today, such
as ContributionPostProcessor and ContributionMetadataDocumentProcessor
interfaces. As preparation for SCA 1.0 release, I'd like to remove
these
Security policy- participation in existing security context
---
Key: TUSCANY-1666
URL: https://issues.apache.org/jira/browse/TUSCANY-1666
Project: Tuscany
Issue Type: New Feature
Raymond Feng wrote:
Comments inline.
Thanks,
Raymond
- Original Message - From: Jean-Sebastien Delfino
[EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, September 05, 2007 9:03 AM
Subject: Re: Issue with dynamic creation of
NotificationReferenceBindingProvider
Support for transaction/compensation
Key: TUSCANY-1667
URL: https://issues.apache.org/jira/browse/TUSCANY-1667
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Core Runtime
Tuscany User request for BPEL integration with Tuscany
--
Key: TUSCANY-1668
URL: https://issues.apache.org/jira/browse/TUSCANY-1668
Project: Tuscany
Issue Type: New Feature
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
ant elder wrote:
On 8/30/07, ant elder [EMAIL PROTECTED] wrote:
This thread has gone quiet but there's been more discussion on this in
TUSCANY-1654 (in case people aren't reading all the jira comments).
How about we just have a
Tuscany User request: service lifecycle mechanism upporting both POJO/local
method invocation as well as remote WSI basic interoperable mechanisms.
---
Hi,
Comments inline.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, September 05, 2007 1:31 PM
Subject: Re: Issue with dynamic creation of
NotificationReferenceBindingProvider
Raymond Feng wrote:
ant elder wrote:
On 9/5/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
ant elder wrote:
On 8/30/07, ant elder [EMAIL PROTECTED] wrote:
This thread has gone quiet but there's been more discussion on this in
TUSCANY-1654 (in case people aren't reading all the jira comments).
How
Good, looks like we have most (if not all) the updates necessary to
support SDO 2.1 specification and to be compatible with SDO 1.0
release. I'd like to start to work on a new release in the next couple
days, and if we make it on time, we could still have a chance to
include DAS in the SCA 1.0
[
https://issues.apache.org/jira/browse/TUSCANY-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1517.
---
Resolution: Fixed
Fixed under r573085
If serviceImpl is pointing to wrong service in
[
https://issues.apache.org/jira/browse/TUSCANY-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1662.
---
Resolution: Fixed
Fixed under r573086
NullpointerException if reference name in
[
https://issues.apache.org/jira/browse/TUSCANY-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-1663:
-
Assignee: Raymond Feng
Unhelpful exception when user forgets to put @Remotable on
[
https://issues.apache.org/jira/browse/TUSCANY-1662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-1662:
-
Assignee: Raymond Feng
NullpointerException if reference name in composite file needs
[
https://issues.apache.org/jira/browse/TUSCANY-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-1517:
-
Assignee: Raymond Feng
If serviceImpl is pointing to wrong service in @Service
[
https://issues.apache.org/jira/browse/TUSCANY-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1663.
---
Resolution: Fixed
I believe it's fixed under r572846. Please verify.
Unhelpful exception
[
https://issues.apache.org/jira/browse/TUSCANY-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fuhwei Lwo updated TUSCANY-1645:
Attachment: 1645.patch
This patch should handle null namespace now. If xsd:schema doesn't have
ServiceReference.getConversationID always returns null
--
Key: TUSCANY-1670
URL: https://issues.apache.org/jira/browse/TUSCANY-1670
Project: Tuscany
Issue Type: Bug
Components:
Simon Nash wrote:
See inline.
Simon
Raymond Feng wrote:
Hi,
There are a set of states associated with
CallableReference/ServiceReference such as the callbackID,
conversationID and callbackObject. We need to flow them in the
Message so that the target service can have the correct
+1 on the proposal. I'll give a try to refactor the Message code.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, September 05, 2007 5:43 PM
Subject: Re: What is Message.set/getCallableReference used
[
https://issues.apache.org/jira/browse/TUSCANY-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1519.
---
Resolution: Fixed
we already print out warnings to report this problem in
sounds good to me.
On 9/6/07, Luciano Resende [EMAIL PROTECTED] wrote:
Good, looks like we have most (if not all) the updates necessary to
support SDO 2.1 specification and to be compatible with SDO 1.0
release. I'd like to start to work on a new release in the next couple
days, and if we
77 matches
Mail list logo
