[jira] Created: (TUSCANY-659) Position of not consistent between composite, component and componentType

Position of not consistent between composite, component and componentType Key: TUSCANY-659 URL: http://issues.apache.org/jira/browse/TUSCANY-659 Project: Tuscany

RE: OSGi host

Hi Joel, I'm new to SCA, so don't believe everything I say :) OSGi is IMO an infrastructure technology suitable for building container technologies such as SCA. Spring is a Java component wiring technology, so inevitably overlaps with some of what SCA is trying to achieve (and EJB3 for examp

Re: svn commit: r432722 [1/2] - in /incubator/tuscany/java/sca/containers/container.spring/src: main/java/org/apache/tuscany/container/spring/config/ main/java/org/apache/tuscany/container/spring/i

I spoke to Rod today, he seems happy to do the appropriate software grant to Apache as per the apache licensing conventions. NOTICES.txt would then need to contain an appropriate attribution. I think this would probably only need to be a temporary measure, but who knows. Thanks andy At 12:05

Re: [C++] Creating an SDO DataObject for the properties of a component

Sebastien, I'm fixing this. It shouldn't take long. Cheers, On 22/08/06, Pete Robbins <[EMAIL PROTECTED]> wrote: ah! On 22/08/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > It doesn't work at all now. With SCDL 0.9 a component declaration looked > like that: > > > abc >

Re: REST bindings for Tuscany SCA runtime

In the client: customers.get("http://my.customer.database.com/customers/1234";); returns an instance of the Customer XSD complex type customers.put("http://my.customer.database.com/customers/1234";, customerDataObject) updates customer 1234 with a Customer instance. customers.get("http://my.c

RE: Celtix binding

One thing you can try is same as what is done by axis2's WebServiceBindingLoader, i.e., using wsdlLocation to parse wsdl Definition by yourself. This way wsdl Definition is not cached but it works. I can not remember if we had a discussion on this before. Do we still need a wsdl cache (e.g. WSD

[jira] Closed: (TUSCANY-655) Updates to NOTICE.txt headers for DAS and SDO components

ava DAS RDB >Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Critical > Fix For: Java-Mx > > Attachments: lresende.notice.updates.20060822.txt > > > Need to update the

RE: Celtix binding

Hi Jim, Celtix binding currently is not working yet. I got the helloworldwsclient working with the Celtix binding with some hacks and without using SDO. At the same time, for the helloworldws-celtix sample, I am able to get the reference part working, and still struggling on the service part. th

Debugging Maven with remote debug session --- fails

I had a case where the Junit test worked in eclipse but failed with maven command line build. Typically this was just as easy to debug by just setting the MAVEN_OPTS environment variable to the java debug agent (Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8008,server=y,suspend=y) A

Re: Auto discovering WSDL

On Aug 22, 2006, at 4:53 PM, Jean-Sebastien Delfino wrote: ant elder wrote: On 8/22/06, Jim Marino <[EMAIL PROTECTED]> wrote: I really like the suggestion that WSDL be automatically discovered > anywhere > within the application directory structure. I pretty much have the same concerns as m

Re: REST bindings for Tuscany SCA runtime

Apologies for addressing the emails in this thread out of order :) I was on a similar track, thinking about implementing a REST binding for Tuscany C++. I agree with you that the REST pattern is about resources, so we need to go further than just sending XML service requests over HTTP, and

Re: REST bindings for Tuscany SCA runtime

bl says: Jean-Sebastien's approach seems to be a step in this direction. +1 --oh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: REST bindings for Tuscany SCA runtime

I think anything that is sent to/from a SCA REST binding needs to either be Plain Old XML or JSON and not SOAP. SOAP is generally what makes most RESTifarians shudder :) It's the encoding of the method in the XML body that is the anathema :) --oh -

Re: Auto discovering WSDL

On Aug 22, 2006, at 4:31 PM, ant elder wrote: On 8/22/06, Jim Marino <[EMAIL PROTECTED]> wrote: I really like the suggestion that WSDL be automatically discovered > anywhere > within the application directory structure. I pretty much have the same concerns as mentioned by Raymond on this.

Re: possible bug: IllegalArgumentException, XSDHelperImpl.define : 204 ?

Some bugs have been fixed since M1, do you want to try the latest build(s)? Some build instructions can be found at http://incubator.apache.org/tuscany/java_sdo_overview.html If any steps are unclear to you, welcome to raise question(s) even contribute to improve the documentation :-) On 8/22

Re: Auto discovering WSDL

Keying can be done by WeakReference or SoftReference, as long as no strong reference from value to key (value sure can have weak/soft reference to key). The registry I worked on, Eclipse Modeling Framework, and many other Java caches, use Java Reference. On 8/22/06, Jim Marino <[EMAIL PROTECTED]

Re: Auto discovering WSDL

ant elder wrote: On 8/22/06, Jim Marino <[EMAIL PROTECTED]> wrote: I really like the suggestion that WSDL be automatically discovered > anywhere > within the application directory structure. I pretty much have the same concerns as mentioned by Raymond on this. I'm confused by this thread, y

Re: SCDL extensions to define data types for parameters and return value

Hi, I think we have several use cases here: Case 1: Invoking a web service using a SCA reference with Axis2 binding ... Source DataType is controlled by the application (it can be either decorated by SCDL extensions or introspected from the value. For example, the Customer ca

Re: Auto discovering WSDL

On 8/22/06, Jim Marino <[EMAIL PROTECTED]> wrote: I really like the suggestion that WSDL be automatically discovered > anywhere > within the application directory structure. I pretty much have the same concerns as mentioned by Raymond on this. I'm confused by this thread, you're concerns are

Re: Unregister Method Design

On Aug 22, 2006, at 3:14 PM, Kapish Aggarwal wrote: Hey Jim, I'm still a bit unclear on your response to my post. I agree with the idea of not allowing Atomic Components to be unregistered from a Composite. But I'm looking at completely undeploying the top-level composite from the Tuscany

Re: Auto discovering WSDL

On Aug 22, 2006, at 2:46 PM, Yang ZHONG wrote: Ant has just mentioned two important aspects of a decent registry: multi-dimension scoping and NameSpace aggregation. I forgot to mention the registry I previously worked on supports them too, thank Ant. Specifically, "keyed by application and

Re: Auto discovering WSDL

On Aug 22, 2006, at 1:39 PM, ant elder wrote: I agree a registry would be good, we need some sort of cache or registry otherwise you need to specify the wsdlLocation on every interface.wsdl and binding.ws which is quite ugly. But we had a simple registry in M1 and that caused problems wit

Re: [C++] Creating an SDO DataObject for the properties of a component

ah! On 22/08/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: It doesn't work at all now. With SCDL 0.9 a component declaration looked like that: abc xyz tuv The DataObject loaded from that looked exactly like what the client Cpp code expected, allowing you to code Comp

Re: [C++] Creating an SDO DataObject for the properties of a component

Pete Robbins wrote: I thought this worked already in a very basic way! The code in the runtime/core/test did pretty much what you want I think. ComponentContext myContext = ComponentContext::getCurrent(); DataObjectInstance properties = myContext.getProperties(); if (properties) {

Re: Unregister Method Design

Hey Jim, I'm still a bit unclear on your response to my post. I agree with the idea of not allowing Atomic Components to be unregistered from a Composite. But I'm looking at completely undeploying the top-level composite from the Tuscany runtime, not just redeploying. The composite is ultimately

[jira] Closed: (TUSCANY-658) Remove parameter name from config model

[ http://issues.apache.org/jira/browse/TUSCANY-658?page=all ] Kevin Williams closed TUSCANY-658. -- Fix Version/s: Java-Mx Resolution: Fixed Verified with revision: 432058 > Remove parameter name from config model > ---

[jira] Closed: (TUSCANY-652) Create implied relationships when possible

[ http://issues.apache.org/jira/browse/TUSCANY-652?page=all ] Kevin Williams closed TUSCANY-652. -- Fix Version/s: Java-Mx Resolution: Fixed Verified with revision: 432058 > Create implied relationships when possible >

possible bug: IllegalArgumentException, XSDHelperImpl.define : 204 ?

does anyone know what causes this: 14:11:19,784 ERROR [STDERR] java.lang.IllegalArgumentException: org.eclipse.emf.ecore.impl.EDataTypeImpl 14:11:19,786 ERROR [STDERR] at org.apache.tuscany.sdo.helper.XSDHelperImpl.define(XSDHelperImpl.java:204) 14:11:19,786 ERROR [STDERR] at org.apache.

Re: Auto discovering WSDL

Ant has just mentioned two important aspects of a decent registry: multi-dimension scoping and NameSpace aggregation. I forgot to mention the registry I previously worked on supports them too, thank Ant. Specifically, "keyed by application and the WSDL location" mentions scoping by application/Cl

[jira] Updated: (TUSCANY-655) Updates to NOTICE.txt headers for DAS and SDO components

Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Critical > Fix For: Java-M2 > > Attachments: lresende.notice.updates.20060822.txt > > > Need to update the NOTICE.txt header

Re: Tuscany feature wish list

I think this would be great. I'm new (a couple weeks) to Tuscany and at some point would like to contribute (once the deer in headlights syndrome passes). The problem is, it's tough to know who's working on what and at the same time which features are at a priority and which have dependencies.

Re: Auto discovering WSDL

I prefer not to blindly discover WSDLs in the application archive without any control expressed by the application developer. By my experience, this is a big trap and Sebastien has pointed out a bunch of issues with that proposal. I do agree in some cases, it should be possible to omit the "wsd

Re: Auto discovering WSDL

I agree a registry would be good, we need some sort of cache or registry otherwise you need to specify the wsdlLocation on every interface.wsdl and binding.ws which is quite ugly. But we had a simple registry in M1 and that caused problems with namespace reuse. We definitely need to handle the re

Re: [C++] Creating an SDO DataObject for the properties of a component

I thought this worked already in a very basic way! The code in the runtime/core/test did pretty much what you want I think. ComponentContext myContext = ComponentContext::getCurrent(); DataObjectInstance properties = myContext.getProperties(); if (properties) { const char* f

[C++] Creating an SDO DataObject for the properties of a component

I'd like to get some basic property support in place to be able to configure component properties in the SupplyChain scenario that I'm working on. In an SCDL componentType file I have this for example: defining property names and types. In my SCDL component declaration I have this: U

[jira] Updated: (TUSCANY-658) Remove parameter name from config model

[ http://issues.apache.org/jira/browse/TUSCANY-658?page=all ] Brent Daniel updated TUSCANY-658: - Attachment: tuscany658.txt The attached patch removes the name element from the config and updates associated tests. > Remove parameter name from config m

[jira] Assigned: (TUSCANY-658) Remove parameter name from config model

[ http://issues.apache.org/jira/browse/TUSCANY-658?page=all ] Brent Daniel reassigned TUSCANY-658: Assignee: Brent Daniel > Remove parameter name from config model > --- > > Key: TUSCANY-658 >

[jira] Created: (TUSCANY-658) Remove parameter name from config model

Remove parameter name from config model --- Key: TUSCANY-658 URL: http://issues.apache.org/jira/browse/TUSCANY-658 Project: Tuscany Issue Type: Bug Components: Java DAS RDB Reporter:

[jira] Resolved: (TUSCANY-645) NullPointerException thrown in XMLHelper.define() method was called with an XSD file without specifying a target namespace

[ http://issues.apache.org/jira/browse/TUSCANY-645?page=all ] Frank Budinsky resolved TUSCANY-645. Resolution: Fixed Fixed in revision 433729. > NullPointerException thrown in XMLHelper.define() method was called with an > XSD file without specify

RE: Composite Reference Example

Jim, TUSCANY-657. Thanks for looking at this. Cheers, Joel -Original Message- From: Hawkins, Joel [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 22, 2006 11:04 AM To: tuscany-dev@ws.apache.org Subject: Composite Reference Example Can anyone point me to an example that uses a Composit

[jira] Created: (TUSCANY-657) Problem resolving references with external targets

Problem resolving references with external targets -- Key: TUSCANY-657 URL: http://issues.apache.org/jira/browse/TUSCANY-657 Project: Tuscany Issue Type: Bug Components: Java SCA Core

Re: DAS Article

Good article. Thanks for getting the word out on Tuscany and DAS. On 8/21/06, Jim Lynch <[EMAIL PROTECTED]> wrote: kudos to Kevin and Brent. I read this article over the weekend and it's great. Explains concepts well and make good use of an example and figures. great job!!...jim On 8/21/0

Re: Composite Reference Example

On Aug 22, 2006, at 8:59 AM, Hawkins, Joel wrote: Jim wrote: In the case above, I thought ShipperReference was wiring out over the binding and having the binding resolve the target through OSGi? If that is the case, what may be happening is a bug I ran into last night. Basically, the referenc

Re: Unregister Method Design

Hi Kappish, Comments inline On Aug 22, 2006, at 11:56 AM, Kapish Aggarwal wrote: Refering back to a previous posting about the removing an existing SCA composite from the Tuscany runtime, I was try to determine what is required in the process of removing a composite from the runtime. Looking

Re: Service, Reference and Binding models

On Aug 22, 2006, at 10:10 AM, Raymond Feng wrote: More comments in line. Thanks, Raymond - Original Message - From: "Ignacio Silva-Lepe" <[EMAIL PROTECTED]> To: Sent: Tuesday, August 22, 2006 6:37 AM Subject: Re: Service, Reference and Binding models Hi Raymond, Jim, Comments

Unregister Method Design

Refering back to a previous posting about the removing an existing SCA composite from the Tuscany runtime, I was try to determine what is required in the process of removing a composite from the runtime. Looking through the code, it seems that a couple things need to be done: 1) Add a method that

Re: Auto discovering WSDL

I like Raymond's and Yang's approach and perhaps someone is willing to propose the standardized way to the spec group? Sebastien, since you had a bunch of other issues raised against the spec group, do you want to do that? Jim On Aug 22, 2006, at 10:36 AM, Raymond Feng wrote: I'm leaning

Re: Auto discovering WSDL

I'm leaning the following: 1) Have a well-defined default scheme. I agree with Sebastien that the SCA spec should spell it out. 2) Allow extensibility to plug in new schemes (for example, "my:path") if the host platform desires. Thanks, Raymond - Original Message - From: "Jean-Sebas

Re: Auto discovering WSDL

Raymond Feng wrote: Hi, I would suggest that we define a system service to provide the artifact resolving strategy. Then we can supply a default implementation, for example, resolve the wsdlLocation based on classpath. The embedded can choose to replace it with its own more sophisticated res

Re: Service, Reference and Binding models

More comments in line. Thanks, Raymond - Original Message - From: "Ignacio Silva-Lepe" <[EMAIL PROTECTED]> To: Sent: Tuesday, August 22, 2006 6:37 AM Subject: Re: Service, Reference and Binding models Hi Raymond, Jim, Comments in line. Ignacio - Original Message - From:

Re: Auto discovering WSDL

Some product I previously worked on has such registry, furthermore, it loads resources on demand instead of loading everything at beginning to improve performance, not every execution path needs *all* resources after all. The way it works is 1. client queries the registry with some criterias such

Re: Auto discovering WSDL

Hi, I would suggest that we define a system service to provide the artifact resolving strategy. Then we can supply a default implementation, for example, resolve the wsdlLocation based on classpath. The embedded can choose to replace it with its own more sophisticated resolver (for exmaple, u

Sdo samples javadoc

In original drop of samples I removed overview.html from the javadoc due to some issues in maven javadoc plugin. Found that there was a bug in the 2.0beta 3 javadoc plugin. I have opened JIRA *TUSCANY-656 *and attached a patch to add the overvi

RE: Composite Reference Example

Jim wrote: >In the case above, I thought ShipperReference was wiring out over the >binding and having the binding resolve the target through OSGi? If >that is the case, what may be happening is a bug I ran into last >night. Basically, the reference builder need to set a URI on the >Referen

[jira] Updated: (TUSCANY-656) Maven javadoc plugin bug fixed allowing overview.html for javadoc to be created in a relative directory

[ http://issues.apache.org/jira/browse/TUSCANY-656?page=all ] Robbie Minshall updated TUSCANY-656: Attachment: TUSCANY-656a.patch Adds overview to the pom.xml > Maven javadoc plugin bug fixed allowing overview.html for javadoc to be > created in a

[jira] Created: (TUSCANY-656) Maven javadoc plugin bug fixed allowing overview.html for javadoc to be created in a relative directory

Maven javadoc plugin bug fixed allowing overview.html for javadoc to be created in a relative directory --- Key: TUSCANY-656 URL: http://issues.apache.org/jira/bro

Re: Sample framework

I'm back from a long-ish vacation and I'm catching up with all the postings to the list while I've been gone. I'm starting with this topic as it is a subject of particular interest to me. I think we need samples to address the following types of users: 1. Technology evaluators and prospective us

Re: svn commit: r433649

} // FIXME need to find out how to get wsdl and what context to use --- terrible hack attack! // URL wsdlurl = Thread.currentThread ().getContextClassLoader().getResource(wsdlLocation); +if(null == wsdlLocation) throw new RuntimeException ("Fa

Re: svn commit: r433593

On Aug 22, 2006, at 4:01 AM, [EMAIL PROTECTED] wrote: == --- incubator/tuscany/java/sca/databinding/databinding-sdo/src/main/ java/org/apache/tuscany/databinding/sdo/ImportSDOLoader.java (original) +++ incubator/tus

Re: Composite Reference Example

On Aug 22, 2006, at 8:03 AM, Hawkins, Joel wrote: Can anyone point me to an example that uses a Composite Reference? I noticed that the one in BigBank is commented out. I'm having trouble testing OSGi support against the latest code. I've got a sample that looks like this: http://www.osoa.org

[jira] Commented: (TUSCANY-655) Updates to NOTICE.txt headers for DAS and SDO components

gt;Affects Versions: Java-M2 >Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Critical > Fix For: Java-M2 > > Attachments: lresende.notice.updates.20060822.txt > > > Need to update the NOTICE.txt headers

Re: NOTICE file

I've already done the SDO one in 653. On 8/22/06, Luciano Resende <[EMAIL PROTECTED]> wrote: Previous post by Jeremy is available here : http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg05128.html So, looks like we need to change the Notice.txt headers to : Apache Tuscany Copyright

Re: REST bindings for Tuscany SCA runtime

This sounds like a very good place to start to be able to expose SCA resources in a REST way, but I think the more interesting and more difficult challenge will be to figure out how to get SCA to consume some of the growing number of REST resources that are being exposed on the net now. Jean-Seba

Re: REST bindings for Tuscany SCA runtime

I think anything that is sent to/from a SCA REST binding needs to either be Plain Old XML or JSON and not SOAP. SOAP is generally what makes most RESTifarians shudder :) -Bert On 8/18/06, Luciano Resende <[EMAIL PROTECTED]> wrote: Also, SOAP 1.2 now supports GET as a message response exchange

Re: Auto discovering WSDL

On 8/22/06, ant elder <[EMAIL PROTECTED]> wrote: In a C++ thread [1] Jean-Sebastien talked about having WSDL files automatically picked up by the C++ runtime instead of having to specify a wsdlLocation attribute somewhere in the SCDL. I'd really like the Java SCA runtime to also do this, do peop

Composite Reference Example

Can anyone point me to an example that uses a Composite Reference? I noticed that the one in BigBank is commented out. I'm having trouble testing OSGi support against the latest code. I've got a sample that looks like this: http://www.osoa.org/xmlns/sca/1.0"; xmlns:osgi="http://tuscan

Re: Auto discovering WSDL

ant elder wrote: In a C++ thread [1] Jean-Sebastien talked about having WSDL files automatically picked up by the C++ runtime instead of having to specify a wsdlLocation attribute somewhere in the SCDL. I'd really like the Java SCA runtime to also do this, do people agree or anyone have any con

Re: Tuscany feature wish list

On Aug 22, 2006, at 7:50 AM, ant elder wrote: I'm regularly asked be people new to Tuscany about what is something they could look at or help to develop, we don't give any help with this on the website or wiki so to help I've created a "Wish list" category in JIRA: http://issues.apache.o

Re: Auto discovering WSDL

On Aug 22, 2006, at 7:34 AM, ant elder wrote: In a C++ thread [1] Jean-Sebastien talked about having WSDL files automatically picked up by the C++ runtime instead of having to specify a wsdlLocation attribute somewhere in the SCDL. I'd really like the Java SCA runtime to also do this, do pe

Tuscany feature wish list

I'm regularly asked be people new to Tuscany about what is something they could look at or help to develop, we don't give any help with this on the website or wiki so to help I've created a "Wish list" category in JIRA: http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide

Re: [jira] Created: (TUSCANY-651) Port WSDL2Java and Java2WSDL from M1

Hey Jojo. I ran into this last week. I added stax-1.2.0.jar to the classpath/classloader. On 8/22/06, Jojo <[EMAIL PROTECTED]> wrote: Hi, I was trying to get some java2wsdl test case running, but got stuck with the following error : javax.xml.stream.FactoryConfigurationError: Provider com.

Re: [C++] Requirements for a pluggable C++ Tuscany implementation

On 8/22/06, Oisin Hurley <[EMAIL PROTECTED]> wrote: Hi Simon, > Had a long weekend so just picking up this thread. Looks like a really > useful discussion and I too like the requirement driven approach. I > have a > few to add/comment on. It seems that a plugin resolves to a > component type >

Auto discovering WSDL

In a C++ thread [1] Jean-Sebastien talked about having WSDL files automatically picked up by the C++ runtime instead of having to specify a wsdlLocation attribute somewhere in the SCDL. I'd really like the Java SCA runtime to also do this, do people agree or anyone have any concerns with that? So

Re: REST bindings for Tuscany SCA runtime

Luciano Resende wrote: [snip] Sebastien When you say this should tie with DAS, are you assuming that the REST services would emit XML (and not JSON or any other format) and then DAS would be able to consume the xml and bind to a data object ? - Luciano Luciano, I am assuming that REST "ser

[jira] Assigned: (TUSCANY-655) Updates to NOTICE.txt headers for DAS and SDO components

Reporter: Luciano Resende > Assigned To: Luciano Resende >Priority: Critical > Fix For: Java-M2 > > Attachments: lresende.notice.updates.20060822.txt > > > Need to update the NOTICE.txt headers as described on ASF website: > http

[jira] Updated: (TUSCANY-655) Updates to NOTICE.txt headers for DAS and SDO components

[ http://issues.apache.org/jira/browse/TUSCANY-655?page=all ] Luciano Resende updated TUSCANY-655: Attachment: lresende.notice.updates.20060822.txt Updates on the NOTICE.txt files based on http://www.apache.org/legal/src-headers.html#notice

Re: [jira] Created: (TUSCANY-651) Port WSDL2Java and Java2WSDL from M1

Hi, I was trying to get some java2wsdl test case running, but got stuck with the following error : javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory not found at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72) at javax.xml.str

[jira] Created: (TUSCANY-655) Updates to NOTICE.txt headers for DAS and SDO components

Updates to NOTICE.txt headers for DAS and SDO components Key: TUSCANY-655 URL: http://issues.apache.org/jira/browse/TUSCANY-655 Project: Tuscany Issue Type: Bug Components: J

Re: NOTICE file

Previous post by Jeremy is available here : http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg05128.html So, looks like we need to change the Notice.txt headers to : Apache Tuscany Copyright 2006 The Apache Software Foundation This product includes software developed at The Apache Soft

[jira] Created: (TUSCANY-654) Java SCA: Python container

Java SCA: Python container -- Key: TUSCANY-654 URL: http://issues.apache.org/jira/browse/TUSCANY-654 Project: Tuscany Issue Type: New Feature Affects Versions: Wish list Reporter: ant elder

Re: SCDL extensions to define data types for parameters and return value

Could you give a bit more detail and a few more complete examples, I'm not sure I understand all this? It seems a lot of XML, you're not likely to use different databinding technologies on the same interface are you, and would a lot of this have defaults so you don't have to specify all this for e

Re: REST bindings for Tuscany SCA runtime

Axis2 also has some built in REST support, and as we already have an Axis2 binding it would be relatively easy to get a Tuscany REST binding going using Axis2. All that you need to do is change the Tuscany code to use the Axis2 REST servlet instead of the SOAP one, and change the code where we set

Re: REST bindings for Tuscany SCA runtime

Just as a precaution reminder about PUT and DELETE, although they are probably the right way of doing some kind of actions, in reality, firewalls and deployment environments usually block those kind of operations. - Luciano On 8/22/06, Oisin Hurley <[EMAIL PROTECTED]> wrote: > REST is a very g

Re: REST bindings for Tuscany SCA runtime

REST is a very generic term, and I think it's more like a resource/ service naming pattern (URL/URI). When we say REST bindings, what are we expecting as the REST Service ? The resource part is really important, but the small interface part is important too, as are the expected behaviours of

Re: Service, Reference and Binding models

Hi Raymond, Jim, Comments in line. Ignacio - Original Message - From: "Jim Marino" <[EMAIL PROTECTED]> To: Sent: Monday, August 21, 2006 8:22 PM Subject: Re: Service, Reference and Binding models On Aug 21, 2006, at 4:21 PM, Raymond Feng wrote: Hi, I think the SPI models for SC

Re: [C++] Requirements for a pluggable C++ Tuscany implementation

Hi Simon, Had a long weekend so just picking up this thread. Looks like a really useful discussion and I too like the requirement driven approach. I have a few to add/comment on. It seems that a plugin resolves to a component type or binding, i.e. what the assembly model refers to as extensi

Re: New site sample

Good point Robbie, but if we go that way, we should make sure we explicitly say that we only have the RDB implementation as of now, not to mislead people that goes to the website. - Luciano On 8/21/06, Robbie Minshall <[EMAIL PROTECTED]> wrote: In the diagram DAS is represented as a single com

Re: REST bindings for Tuscany SCA runtime

Sebastien When you say this should tie with DAS, are you assuming that the REST services would emit XML (and not JSON or any other format) and then DAS would be able to consume the xml and bind to a data object ? - Luciano On 8/21/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: Oisin

Re: [C++] Requirements for a pluggable C++ Tuscany implementation

On 8/22/06, Oisin Hurley <[EMAIL PROTECTED]> wrote: [deletia] js-d says: >> > I've been thinking about this and wondering what the architecture >> > of the runtime will be with many different plugins? Are you guys >> > envisioning one big process with different (maybe incompatible?) >> > librari

Re: [C++] Requirements for a pluggable C++ Tuscany implementation

On 22/08/06, Oisin Hurley <[EMAIL PROTECTED]> wrote: . I've seen lots of +1s on this thread, which is nice, and I've just found out that I can edit the Tuscany wiki, so I'll summarize to there -- the page will be http://wiki.apache.org/ws/Tuscany/TuscanyCpp/ PluggableCppRuntime it'll be later t

[jira] Updated: (TUSCANY-419) Template XML for JavaScript components

[ http://issues.apache.org/jira/browse/TUSCANY-419?page=all ] ant elder updated TUSCANY-419: -- Priority: Major (was: Critical) > Template XML for JavaScript components > -- > > Key: TUSCANY-419 >

Re: [C++] Requirements for a pluggable C++ Tuscany implementation

[deletia] js-d says: > I've been thinking about this and wondering what the architecture > of the runtime will be with many different plugins? Are you guys > envisioning one big process with different (maybe incompatible?) > libraries loaded in it? or a more distributed architecture with > multip

[jira] Updated: (TUSCANY-435) Spaces binding for SCA

[ http://issues.apache.org/jira/browse/TUSCANY-435?page=all ] ant elder updated TUSCANY-435: -- Fix Version/s: Java-Mx Affects Version/s: Java-Mx > Spaces binding for SCA > -- > > Key: TUSCANY-435 >

[jira] Updated: (TUSCANY-650) End-to-end sample application

[ http://issues.apache.org/jira/browse/TUSCANY-650?page=all ] ant elder updated TUSCANY-650: -- Fix Version/s: Java-Mx > End-to-end sample application > - > > Key: TUSCANY-650 > URL: http://issues.ap

[jira] Updated: (TUSCANY-621) Create distribution for bindings, or how to switch binding implementations

[ http://issues.apache.org/jira/browse/TUSCANY-621?page=all ] ant elder updated TUSCANY-621: -- Fix Version/s: Java-Mx Affects Version/s: Java-Mx > Create distribution for bindings, or how to switch binding implementations > --

[jira] Updated: (TUSCANY-619) Fix classloader hierarchy for extensions

[ http://issues.apache.org/jira/browse/TUSCANY-619?page=all ] ant elder updated TUSCANY-619: -- Fix Version/s: Java-M2 Affects Version/s: Java-M2 > Fix classloader hierarchy for extensions > > >

[jira] Updated: (TUSCANY-616) JavaServiceContract introspection should use the ImplementationProcessor mechanism

[ http://issues.apache.org/jira/browse/TUSCANY-616?page=all ] ant elder updated TUSCANY-616: -- Fix Version/s: Java-Mx Affects Version/s: Java-Mx > JavaServiceContract introspection should use the ImplementationProcessor > mechanism > ---

[jira] Closed: (TUSCANY-593) Need a extendable way to register SCDL loaders

[ http://issues.apache.org/jira/browse/TUSCANY-593?page=all ] ant elder closed TUSCANY-593. - Resolution: Invalid Not applicable to new code base > Need a extendable way to register SCDL loaders > -- > >

[jira] Updated: (TUSCANY-541) support pluggable databinding and data transformation

[ http://issues.apache.org/jira/browse/TUSCANY-541?page=all ] ant elder updated TUSCANY-541: -- Fix Version/s: Java-M2 Affects Version/s: Java-M2 > support pluggable databinding and data transformation > ---

[jira] Closed: (TUSCANY-295) Document the architecture of the WS Axis2 binding

[ http://issues.apache.org/jira/browse/TUSCANY-295?page=all ] ant elder closed TUSCANY-295. - Resolution: Fixed > Document the architecture of the WS Axis2 binding > - > > Key: TUSCANY-295 >

  1   2   >