Hi,
I have an component service (wsdl) created with the operation name
start. Once i run the tuscany runtime , i get an error saying
org.osoa.sca.ServiceRuntimeException: No matching operation for start is
found in service TwoWSService#Compose
what may be the possible reason for this error.
[
https://issues.apache.org/jira/browse/TUSCANY-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reassigned TUSCANY-1937:
---
Assignee: Simon Laws
Duplicate binding name not flagged as error
On Wed, Mar 5, 2008 at 6:22 PM, ant elder [EMAIL PROTECTED] wrote:
The main thing I'd like to do for 1.2 is to try to finish off the JMS
binding so that it as much as possible fully implements the spec but that
wont be done by middle of next week. Guess i don't mind too much just
committing
Hi Sandeep
Are you able to provide the test case which is giving the error? If so the
best thing to do is open a JIRA and attach it there so someone can run it
and track down the problem.
Just taking a wild stab in the dark it would appear that the runtime is not
able to find the appropriate
Hi Raymond,
I did start with the write option but ended up with trouble trying to access
the write methods from the Builders where the PolicySets get matched. I
brought this up for discussion in
http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg27768.html where
Sebastien suggested that
[
https://issues.apache.org/jira/browse/TUSCANY-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangfeng updated TUSCANY-2066:
--
Attachment: voidtest.zip
This is the modified test case.
Modify the sample
Modify the sample 'ws-void-args-return',return a null javabean result,throw a
NullPointerException
--
Key: TUSCANY-2066
URL:
Hi all,
I'm facing build error of Tuscany plugin for Geronimo.
I checked out sources from
https://svn.apache.org/repos/asf/geronimo/plugins/tuscany/trunk
Specifically, while building tuscany-tomcat module.
--
Downloading:
TUSCANY-2055 has raised an issue where we need some spec clarity. Namely, in
relation to the function ServiceReference.getConversationID(), the Java
Annotations and API V1 spec says a few things.
521 1.6.6.2. Accessing Conversation IDs from Clients
522 Whether the conversation ID is chosen by the
On Wed, Mar 5, 2008 at 9:46 AM, ant elder [EMAIL PROTECTED] wrote:
On Tue, Mar 4, 2008 at 6:19 PM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
ant elder wrote:
Ok thanks. The binding.ws element is also extensible so this axis2
config
could be added as extra attributes or
Hi, simon
Axis2's JAVA2WSDL can handle the JAX-WS annnotations by default.
Since it's org.apache.axis2.description.java2wsdl.DefaultSchemaGeneratorcontains
following lines:
JAnnotation annotation = jclass.getAnnotation(
AnnotationConstants.WEB_SERVICE);
if (annotation != null) {
Hi,
It should be fairly simple to make StAXArtifactProcessorExtensionPoint
available to CompositeBuilderImpl. With that, we can find the corresponding
StAXArtifactProcessor for a given PolicySetAttachPoint. For example, if you
try to match a component service with an XPath, you can do:
On 05/03/2008, Scott Kurz [EMAIL PROTECTED] wrote:
I didn't follow all of the discussion about removing SDO from the Tuscany
charter... but if SDO is no
longer a special part of the Tuscany project then what would happen to the
W2J/J2W tools built around
SDO support?
The WSDL/WSDL tools
Venkat,
I was trying some stuff with policy sets and noticed the QName resolution
wasn't working as I expected. Specifically the targetNameSpace attribute of
the definitions.xml document doesn't appear to be used to form the QName of
the policy sets within. I recalled we had discussed this in
One possibility in the SDO domain that I have heard a request for recently
from more than one source is an ECMAScript/JavaScript implementation of
SDO. This could be started by a GSoC activity. I opened a Wish List item
for it a few days ago as TUSCANY-2065. I don't have deep skills in this
On Thu, Mar 6, 2008 at 3:49 PM, Simon Laws [EMAIL PROTECTED]
wrote:
TUSCANY-2055 has raised an issue where we need some spec clarity. Namely,
in relation to the function ServiceReference.getConversationID(), the Java
Annotations and API V1 spec says a few things.
521 1.6.6.2. Accessing
Improving the XQuery component implementation type could be a good
candidate.
Thanks,
Raymond
--
From: Luciano Resende [EMAIL PROTECTED]
Sent: Friday, February 29, 2008 5:52 PM
To: tuscany-dev tuscany-dev@ws.apache.org
Subject: Tuscany
On Fri, Feb 29, 2008 at 5:37 PM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
Comments inline.
A) Contribution workspace (containing installed contributions):
- Contribution model representing a contribution
- Reader for the contribution model
- Workspace model representing a
On Thu, Mar 6, 2008 at 5:40 PM, Raymond Feng [EMAIL PROTECTED] wrote:
Improving the XQuery component implementation type could be a good
candidate.
Thanks,
Raymond
--
From: Luciano Resende [EMAIL PROTECTED]
Sent: Friday, February 29, 2008
On Wed, Mar 5, 2008 at 12:52 PM, Simon Laws [EMAIL PROTECTED]
wrote:
On Wed, Mar 5, 2008 at 6:01 AM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
Simon Laws wrote:
Thanks Sebastien, Hopefully some insight on the puzzle in line...
Simon
On Mon, Mar 3, 2008 at 9:57 PM,
Ok. Please be aware there is an errata associated with the authorization
elements.
http://www.osoa.org/jira/browse/POLICY-26
On Wed, Mar 5, 2008 at 1:51 AM, Venkata Krishnan [EMAIL PROTECTED]
wrote:
+1. I will start looking into this after I am done with some
half-finished
things on my
[
https://issues.apache.org/jira/browse/TUSCANY-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-2066:
Patch Info: [Patch Available]
Thanks for the patch! I just marked it as
[
https://issues.apache.org/jira/browse/TUSCANY-1910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1910.
---
Resolution: Fixed
Patch applied under r634464. Thanks for the contribution.
XStream
ant elder wrote:
On Wed, Mar 5, 2008 at 9:46 AM, ant elder [EMAIL PROTECTED] wrote:
On Tue, Mar 4, 2008 at 6:19 PM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
ant elder wrote:
Ok thanks. The binding.ws element is also extensible so this axis2
config
could be added as extra
On Fri, Mar 7, 2008 at 12:01 AM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
ant elder wrote:
On Wed, Mar 5, 2008 at 9:46 AM, ant elder [EMAIL PROTECTED] wrote:
On Tue, Mar 4, 2008 at 6:19 PM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
ant elder wrote:
Ok thanks. The
Hi, Zal.
Thank you for contributing documents to Tuscany. It's really great to see you
share ideas/practices in the community. Here are a few things that I suggest:
1) Start to contribute your content to our wiki site. I have created a blank
page as the starting point at
Simon Laws wrote:
I've been running the workspace code today with a view to integrating the
new code in assembly which calculates service endpoints i.e. point4 above.
I think we need to amend point 4 to make this work properly..
4. Point my Web browser to the various ATOM collections to get:
Simon Laws wrote:
On Wed, Mar 5, 2008 at 6:01 AM, Jean-Sebastien Delfino [EMAIL PROTECTED]
wrote:
Simon Laws wrote:
Thanks Sebastien, Hopefully some insight on the puzzle in line...
Simon
On Mon, Mar 3, 2008 at 9:57 PM, Jean-Sebastien Delfino
[EMAIL PROTECTED]
wrote:
I apologize in
Simon Laws wrote:
On Wed, Mar 5, 2008 at 12:52 PM, Simon Laws [EMAIL PROTECTED]
wrote:
On Wed, Mar 5, 2008 at 6:01 AM, Jean-Sebastien Delfino
[EMAIL PROTECTED] wrote:
Simon Laws wrote:
Thanks Sebastien, Hopefully some insight on the puzzle in line...
Simon
On Mon, Mar 3, 2008 at 9:57
Hi,
Right but this brings in a circular dependency isn't it ?
Thanks.
- Venkat
On Thu, Mar 6, 2008 at 10:27 PM, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
It should be fairly simple to make StAXArtifactProcessorExtensionPoint
available to CompositeBuilderImpl. With that, we can find the
Hi Greg,
Yes, it seems that when the PolicySet name is a NCName it does not assume
the targetNamespace as its namespace. I shall fix this rightaway.
But then, I suppose its ok for a PolicySet name to be a QName when it is
desired to have the PolicySet take a namespace other than the
Hi,
I'm adding the following SPIs to provide pluggable implementations to
various policies in Tuscany. See [1].
1) Define a PolicyProviderFactory that can be contributed to the
ProviderFactoryExtensionPoint by policy extensions. This is similar to our
BindingProviderFactory and
[
https://issues.apache.org/jira/browse/TUSCANY-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reassigned TUSCANY-2010:
---
Assignee: Simon Laws (was: Simon Nash)
Default binding URI for service from Composite
33 matches
Mail list logo
