Folks,
I tend to agree with Simon, that the package name would rightly be derived from the target namespace
of the wsdl:definitions/ containing the portType definition, since it's the port type that
defines the interface.
So +1 to the CXF interpretation.
On the other hand, there is a
Folks,
I think that SCA is a significant advance in application development technologies which is directed
to simplifying the building of agile and adaptable business systems.
Organisations are already reaping benefits from using SCA - IBM customers in particular have been
able to exploit an
Dalys,
Can you post the contents of the following files, please:
- composite file
- BPEL process file
- WSDL file
The WSDL file is especially important here - it defines the interface that the BPEL process is using
and also any policies that may apply.
It appears as if there is a failure at
Ashwini Kumar Jeksani wrote:
Hi,
I am having problems in invoking a webservice from the BPEL.
This line is printed in the console and nothing is happening beyond this :
[java] Invoking a partner operation: approveDataLoad
Could anyone tellme if there is any update done on the BPEL
Ashwini Kumar Jeksani wrote:
Hi,
I'm trying to create a BPEL for asynchronous web service call. A snippet of it
is shown below:
!-Receive request from client --
receive createInstance=yes operation=initiate partnerLink=ApprovalProcessClient
portType=ns1:approvalProcessPT
Abraham Washington wrote:
hi all, i have a service that has a reference to another service.� so,
in my impl class there's a setter method for the reference.�� when the
app is deployed, the wsdl generates the setter method operation, thus
making it available to be invoked (not a good thing).�
Luciano Resende wrote:
Now that we are making more progress with the SCA BPEL integration
and have figured out how to make References to work, let's discuss
what could be the next steps on this area. Below are couple examples
of what we could do next
- WS-BPEL Process Introspection : Currently
Ivan Dubrov wrote:
Hi,
Is that possible to refer to the CONVERSATION-scoped component from
COMPOSITE-scoped?
What I want to achieve, is to make singleton component
(COMPOSITE-scoped) retrieve some session data (which I want to model as
a CONVERSATION-scoped component) during the request
Raymond Feng wrote:
Hi,
Now the SDO 1.1-incubating has been released. Should we adjust the
pom.xml in SCA Java to reference this release?
ATM, we have SDO 1.0-incubating-SNAPSHOT in trunk. And SCA projects
either reference SDO 1.0-incubating or 1.0-incubating-SNAPSHOT. I think
it's better
Luciano Resende wrote:
Thanks for your interest Juergen.
I was very busy with SCA 1.2 release, so I haven't worked on this on
the last couple weeks. I have local changes that can make the
reference invocation, but looks like there are still some issues with
the ODE integration and I keep
Stanislaw Findeisen wrote:
What is the release schedule for Tuscany projects?
In particular, when do you plan to release the next SDO Java
implementation?
Thanks!
STF
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Joshua,
I'll take a look at this.
Yours, Mike.
Joshua Jackson wrote:
* ws-policy.xsd is now located at
http://schemas.xmlsoap.org/ws/2004/09/policy/ws-policy.xsd
* ws-addr.xsd is now located at http://www.w3.org/2005/08/addressing/ws-addr.xsd
On 3/18/08, Joshua Jackson [EMAIL PROTECTED]
Joshua Jackson wrote:
* ws-policy.xsd is now located at
http://schemas.xmlsoap.org/ws/2004/09/policy/ws-policy.xsd
* ws-addr.xsd is now located at http://www.w3.org/2005/08/addressing/ws-addr.xsd
On 3/18/08, Joshua Jackson [EMAIL PROTECTED] wrote:
Dear all,
When I refer
Folks,
Are users of the Spring Implementation ready for us to move up to use
the 2.5 version of the Spring Framework? Please let us know.
Yours, Mike.
Kapish Aggarwal wrote:
Just a quick general question, are there plans to move the core-spring
and implementation-spring modules to
Hmm, this looks like one of the those flaws in Java exceptions - there
is no way of having something like a number to uniquely identify an
exception beyond its class - using strings is a bad idea, for exactly
this issue with language conversions.
This has led to the message string being used
Kevin,
Comments inline
Kevin Williams wrote:
Does the current Spring support provide the basic capabilities
outlined in the specification? The basic function boils down to these
4 items:
1. Spring Applications Contexts may be used as implementations for SCA
composite components
Yes,
in advance
Yours, Mike Edwards
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Folks,
OASIS is organising a series of free webinars on SCA. Here is the
announcement from OASIS:
-
Open CSA hosts five webinars on the role of SCA in SOA
Beginning 10 Dec, the OASIS Open CSA Member Section will present
Barb,
(Speaking as one of the OSOA SCA Spec Authors)
The OSOA SCA spec terms do talk about compliant implementations - but
this is a piece of legalese that has no force, since the specifications
themselves nowhere define what compliance is.
The OSOA SCA specs in fact deliberately left
Folks,
It's fixed now - the online sca-core.xsd matches the XSD published in
the SCA Assembly 1.0 spec.
Yours, Mike.
Mike Edwards wrote:
Folks,
This is a screw-up in the online versions of the XSDs on www.osoa.org -
they don't match the spec declarations for the XSDs.
I'll go fix
Florian,
I'd point out that the recommended way of doing things is to add
things in your own namespace.
Adding stuff to the OSOA XSDs is not encouraged.
If using your own namespace does not work, then we have some work to do
to fix that...
Yours, Mike.
Jean-Sebastien Delfino wrote:
Florian,
This isn't quite the way that componentType is intended to work. Let me
try to explain.
A componentType file is something that is really associated with an
implementation, not with the component that uses the implementation. In
effect, componentType is really a description of the
haleh mahbod wrote:
great idea. It'll make it easier for everyone to find this information.
I'll add it if others agreeing.
+1 from me.
Yours, Mike.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Folks,
Sorry to cut across the discussion about Transaction support in DAS, but
are folks aware of the proposal for Transaction support in SCA?
which leads to the entertaining question of how the DAS transaction
support relates to the SCA transaction support.
The problem at the moment
Rob,
I'm having a bit of trouble understanding exactly what you are trying to
do. Could you post some of your code so that we get a better idea of
what is going on, please?
Yours, Mike.
Robert Young wrote:
Hi,
I am running Tuscany within a Tomcat web project and I am getting the
am ready to look at a
sample. For example,
1. 'sample name' demonstrates the following
a) create data object, update, retrieve
b) How to use change history
2. 'sample name' demonstrates the following
a)
b)
my 2 cents.. What do other users think?
Haleh
On 7/2/07, Mike Edwards
Jean,
Are you running with Java 6? We have had a report of this problem
previously when people were running Tuscany with Java 6.
Without having checked in detail, I suspect that this problem is caused
because we build and test Tuscany on Java 5. In Java 5, the XML stream
API is not part
Patrick,
One point to make here is that separate contributions are intended to
have different addresses, which in a simple file system equates to
different directories. If you want multiple composites in the same
directory, then you should make them part of one contribution, which is
Dan,
I'm working on this for the SCA materials.
We have just had an upgrade of the www.osoa.org server that will allow
us to serve files outside of the Confluence Wiki. This should allow us
to place files at the correct URLs implied by the specifications.
Previously, the server
information.
Forwarding your email to tuscany-user mailing list as well.
-- Forwarded message --
From: *Mike Edwards* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
Date: Oct 24, 2006 5:52 AM
Subject: Closer Involvement with the OSOA Specifications for Tuscany
Developers
To: tuscany-dev
30 matches
Mail list logo
