On 5/5/08, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Rajini Sivaram wrote:
At the moment, I am creating a single virtual 3rd party bundle. For the
longer term, if there are use-cases where different Tuscany extensions
require different versions of 3rd party libs, we may want to
I've just updated and built from scratch and, with a top level build got
INFO: Loading composite:
http://localhost:9990/composite-resolved/composite:stor
e-client;http://store;store-client
Unhandled exception
Type=Segmentation error vmState=0x
J9Generic_Signal_Number=0004
Hi,
I will try to summarize the modifications I've done on SCA to run on Android
so far.
As I aforementioned, most dynamic instantiations were being done on
host-embedded module. However, there was another modules which were also
using the dynamic instantiation and I had to modify too. For
Hi Luciano,
I've submitted CLA and now my full name (Wojciech Janiszewski) is
listed on Unlisted CLAs
Thanks,
Wojtek
2008/4/30 Luciano Resende [EMAIL PROTECTED]:
The ASF desires that all contributors of ideas, code, or documentation
to the Apache projects complete, sign, and submit (via postal
On Tue, May 6, 2008 at 11:45 AM, Adriano Crestani
[EMAIL PROTECTED] wrote:
Hi,
I will try to summarize the modifications I've done on SCA to run on
Android
so far.
As I aforementioned, most dynamic instantiations were being done on
host-embedded module. However, there was another modules
On Mon, May 5, 2008 at 5:54 PM, Hasan Muhammad [EMAIL PROTECTED] wrote:
So if plugins want to create their own monitor, what will happen in this
case? Now, the way plugins have control is, by looking at the messageID of
the problem, they can decide whether they want to change the behaviour
I've updated and its still working ok for me
...ant
On Tue, May 6, 2008 at 9:37 AM, Simon Laws [EMAIL PROTECTED]
wrote:
I've just updated and built from scratch and, with a top level build
got
INFO: Loading composite:
http://localhost:9990/composite-resolved/composite:stor
I updated this morning and also saw the Segmentation Fault. I've
since re-run and now only see the Exception. Further up on the build
there's also the following SQL Exception:
INFO: Starting node: http://localhost:9990/node-config/StoreClientNode
Connecting to database:
Vamsi,
Thanks for your contribution to the vtest bucket for @Init and
@Destroy annotations. Can you say why you do not use the SCADomain
APIs to configure the domain and locate services from the test client?
I would like to keep this pattern consistent throughout the entire
suite.
--
Kevin
Lou Amodeo wrote:
I am reading the WS Binding Specification and am trying to understand the
meaning of the wsdl.service form of the WSDL Element's URI and to what
extent and how it is supported in Tuscany? Thanks for your help.
Service:
39 WSDL-namespace-URI#wsdl.service(service-name)
40 In
Add support for data Collection interface to the implementation-data-xml
Key: TUSCANY-2297
URL: https://issues.apache.org/jira/browse/TUSCANY-2297
Project: Tuscany
[
https://issues.apache.org/jira/browse/TUSCANY-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Douglas Siqueira Leite updated TUSCANY-2297:
Attachment: tuscany2297_douglas_2008_05_06.patch
Add support for data
[
https://issues.apache.org/jira/browse/TUSCANY-2296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vamsavardhana Reddy updated TUSCANY-2296:
-
Attachment: TUSCANY-2296-recreate.patch
TUSCANY-2296-recreate.patch: Helps
Hi Kevin,
I have created a JIRA TUSCANY-2296 describing the problem. I have also
posted a patch file that will help understand the problem better.
++Vamsi
On Tue, May 6, 2008 at 8:42 PM, Kevin Williams [EMAIL PROTECTED]
wrote:
Vamsi,
Thanks for your contribution to the vtest bucket for
Here is a first version of the implementation proposed:
https://issues.apache.org/jira/browse/TUSCANY-2297
I've added the Collection interface support to the implementation-data-xml,
where the logic of the put, post, get, and delete methods are, basically,
the same of the update, insert, get,
Mike Edwards wrote:
Ashwini Kumar Jeksani wrote:
Hi,
Does Tuscany support SCA Extentions to WS-BPEL? If it doesn't then I
guess we could look into that one as well.
Thanks Regards
Ashwini Kumar Jeksani
Ashwini,
Which extensions are thinking about?
Currently I am working on code that
Vamsavardhana Reddy wrote:
I have created a JIRA TUSCANY-2296 describing the problem. I have also
posted a patch file that will help understand the problem better.
On Tue, May 6, 2008 at 8:42 PM, Kevin Williams [EMAIL PROTECTED]
wrote:
Thanks for your contribution to the vtest bucket for
Dan,
I think this error has got nothing to do with running with Java 2 security
on. See TUSCANY-2272 for a reference to the spec that says the lifecycle
methods must be public.
++Vamsi
On Wed, May 7, 2008 at 1:05 AM, Dan Becker [EMAIL PROTECTED] wrote:
Vamsavardhana Reddy wrote:
I have
Vamsavardhana Reddy wrote:
I think this error has got nothing to do with running with Java 2 security
on. See TUSCANY-2272 for a reference to the spec that says the lifecycle
methods must be public.
Cool. Our findings are the same. Thanks for the pointer to the spec
reference.
--
Thanks,
I have my AService with wsdl given below:
?xml version=1.0 encoding=UTF-8?
wsdl:definitions targetNamespace=
http://wsbinding.vtest.sca.tuscany.apache.org; xmlns:soap12=
http://schemas.xmlsoap.org/wsdl/soap12/; xmlns:ns0=
http://wsbinding.vtest.sca.tuscany.apache.org; xmlns:mime=
This is one of the areas I am having difficulty with. In SCA a service URI
is C1/S1 so a given service exposed over binding.ws would have that form.
So if a wsdl port is not another distinct service then how can multiple
ports refer to the same SCA service name name? It seems that this is
I thought Vamsi was illustrating a scenario and asking a question. I agree
with you as well, on the service side the spec does indicate some hosting
environments cannot support endpoints defined in wsdl. Still trying to nail
down the semantics of this attribute. The example above with the
Lou Amodeo wrote:
I thought Vamsi was illustrating a scenario and asking a question.
I thought so too, and I was doing my best to answer it :-)
It's my understanding that the port definitions in the WSDL should
be used in preference to the endpoint URI that SCA would compute
using its default
Vamsavardhana Reddy wrote:
Should the service be available on http://localhost:8080/AService,
http://localhost:8012/AService and http://localhost:8011/AService ? With
the current implementation, the service is available on
http://localhost:8080/AComponent.
Well, I thought this was referring to
Graham Charters wrote:
I updated this morning and also saw the Segmentation Fault. I've
since re-run and now only see the Exception. Further up on the build
there's also the following SQL Exception:
INFO: Starting node: http://localhost:9990/node-config/StoreClientNode
Connecting to database:
Another thought on how this might work and this may not be possible with the
current Axis2 engine but one can dream ;-)
Create a single SCA service from wsdl.service using 1 URI and 1 http port.
Create a single Axis2 service that the SCA service is mapped to.
Add 3 ports to that Axis2 service.
26 matches
Mail list logo
