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
This has come up for discussion previously on the [EMAIL PROTECTED] list
(see [1]). The conclusion was that this clause in the OSOA license
should not be a concern for Tuscany's implementation of SCA 1.0.
Simon
[1]
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
1. Can we promote the same service using both ws rmi bindings?
2. I have a scenario where I am using a callback ws which has to be accessed
by two clients, one is callback client and other is just accessing some
methods. I had tried adding the operations in the same wsdl but it was not
working
ashjk wrote:
1. Can we promote the same service using both ws rmi bindings?
Yes, this should work.
2. I have a scenario where I am using a callback ws which has to be accessed
by two clients, one is callback client and other is just accessing some
methods. I had tried adding the
On Nov 27, 2007 3:35 PM, Simon Laws [EMAIL PROTECTED] wrote:
On Nov 27, 2007 3:32 PM, Jeff Davis [EMAIL PROTECTED] wrote:
I submitted the following JIRA:
https://issues.apache.org/jira/browse/TUSCANY-1920
I'm not certain I gave it the proper classification, so you might want
to
Hi Venkata,
I have tested helloworld-ws-reference-secure and
helloworld-ws-service-secure. I have some questions about it.Here i cant use
WSPasswordCallback.USERNAME_TOKEN but i m getting
WSPasswordCallback.USERNAME_TOKEN_UNKNOWN on service side. so is there any
problem in mine service and
