Re: Tracking Tuscany extensions, was: Distribution zips and what they contain, was: SCA runtimes
On Fri, Jun 13, 2008 at 10:08 PM, Mike Edwards [EMAIL PROTECTED] wrote: snip b) A variety of functional components, that represent sets of coherent functions. Each consists of a series of the basic modules, aggregated together. Their function in life is to assist developers of applications that embed some level of Tuscany capability (including tools, Tuscany itself and so on) These are probably not agreed by folk today - we have work to do here to define these. You demonstrate the problem in your example above - you want Basic Web Services separate from Web Services Security - but for an end user, the step from using the first to using the second is a trivial addition of @required=integrity to the SCDL. Anyone care to have a go at defining these compoennts? Thats taking a different tack to the launcher appraoch but maybe we need both and this approach would be easier for embedders so ok to move things long I'll try an initial stab at it: 1) tuscany-scdl4j An aggregated jar containing _all_ the model and stax processor classes which can be used by tools etc for for reading/writing scdl without booting a runtime. It includes all the extension classes as they generally don't drag in any other dependencies so its not really any problem to incude them. The only required dependency would be on stax, maybe some optional dependencies like wsdl4j as the wsdl extension may need that. Not sure if any of the contribution modules should be included, would have to investigate that a bit. 2) tuscany-runtime An aggregated jar containing the minimum modules to start a runtime able to run something like the simple calculator sample. Has dependencies on tuscany-scdl4j and minimal other jars - geronimo-commonj_1.1_spec, cglib, jaxb etc. 3) tuscany-api An aggregated jar containing everything tuscany/sca applications might need to compile - sca-api, SCADomain class from host-embedded, node2-api, jsp taglib etc. Has no external dependencies. 4) Single jars for all the binding and implementation type extensions which add the capability to the minimal tuscany-runtime. We're already starting to get these with the way extensions are being structured nowadays - binding-jsonrpc-runtime, binding-ejb-runtime, implementation-widget-runtime etc. The above would make life for embedders much easier like the Tuscany-Geronimo integration code (or JBoss when they come along) less likely to break over releases as we add remove modules. ...ant
Re: Tuscany Board Report for June
Last call for any input on what i'll be submitting tomorrow: http://cwiki.apache.org/confluence/display/TUSCANYWIKI/June+2008 ...ant On Tue, Jun 10, 2008 at 9:59 AM, ant elder [EMAIL PROTECTED] wrote: I need to submit our ASF board report by next Monday. I've created a wiki page - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/June+2008 - please add anything you want mentioned. ...ant
Re: Tuscany Board Report for June
I modified the text a bit. It sounded negative although a lot of good work has been done. On 6/15/08, ant elder [EMAIL PROTECTED] wrote: Last call for any input on what i'll be submitting tomorrow: http://cwiki.apache.org/confluence/display/TUSCANYWIKI/June+2008 ...ant On Tue, Jun 10, 2008 at 9:59 AM, ant elder [EMAIL PROTECTED] wrote: I need to submit our ASF board report by next Monday. I've created a wiki page - http://cwiki.apache.org/confluence/display/TUSCANYWIKI/June+2008 - please add anything you want mentioned. ...ant
[jira] Assigned: (TUSCANY-2298) Incorrect service endpoint when wsdl.service is used with Service webservice binding
[
https://issues.apache.org/jira/browse/TUSCANY-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash reassigned TUSCANY-2298:
---
Assignee: Simon Nash
Incorrect service endpoint when wsdl.service is used with Service webservice
binding
Key: TUSCANY-2298
URL: https://issues.apache.org/jira/browse/TUSCANY-2298
Project: Tuscany
Issue Type: Bug
Components: Java SCA Axis Binding Extension, Java SCA Tomcat
Integration
Affects Versions: Java-SCA-1.2
Reporter: Vamsavardhana Reddy
Assignee: Simon Nash
Fix For: Java-SCA-Next
Web Service Binding Specification Spec v1.00 - Sec 2.1 - lines 38 to 41:
38 o Service:
39 WSDL-namespace-URI#wsdl.service(service-name)
40 In this case, all the endpoints in the WSDL Service that have equivalent
PortTypes with
41 the SCA service or reference must be available to the SCA service or
reference.
When wsdlElement is of 'Service' type, service must be available on all ports
corresponding to the service. The following is the wsdl I am using for
'AService':
{code}
?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=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:ns1=http://org.apache.axis2/xsd;
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
wsdl:types
xs:schema attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://wsbinding.vtest.sca.tuscany.apache.org;
xmlns:ns=http://wsbinding.vtest.sca.tuscany.apache.org;
xs:element name=getGreetings
xs:complexType
xs:sequence
xs:element minOccurs=0 name=param0
nillable=true type=xs:string/
/xs:sequence
/xs:complexType
/xs:element
xs:element name=getGreetingsResponse
xs:complexType
xs:sequence
xs:element minOccurs=0 name=return
nillable=true type=xs:string/
/xs:sequence
/xs:complexType
/xs:element
/xs:schema
/wsdl:types
wsdl:message name=getGreetingsRequest
wsdl:part name=parameters element=ns0:getGreetings
/wsdl:part
/wsdl:message
wsdl:message name=getGreetingsResponse
wsdl:part name=parameters element=ns0:getGreetingsResponse
/wsdl:part
/wsdl:message
wsdl:portType name=AServicePortType
wsdl:operation name=getGreetings
wsdl:input message=ns0:getGreetingsRequest
wsaw:Action=urn:getGreetings
/wsdl:input
wsdl:output message=ns0:getGreetingsResponse
wsaw:Action=urn:getGreetingsResponse
/wsdl:output
/wsdl:operation
/wsdl:portType
wsdl:binding name=AServiceSOAP12Binding type=ns0:AServicePortType
soap12:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getGreetings
soap12:operation soapAction=urn:getGreetings style=document/
wsdl:input
soap12:body use=literal/
/wsdl:input
wsdl:output
soap12:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:binding name=AServicePortTypeBinding type=ns0:AServicePortType
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getGreetings
soap:operation soapAction=/
wsdl:input
soap:body use=literal/
/wsdl:input
wsdl:output
soap:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:binding name=AServiceHttpBinding type=ns0:AServicePortType
http:binding verb=POST/
wsdl:operation name=getGreetings
http:operation location=AService/getGreetings/
wsdl:input
mime:content part=getGreetings type=text/xml/
/wsdl:input
wsdl:output
mime:content part=getGreetings type=text/xml/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:binding name=AServiceSOAP11Binding type=ns0:AServicePortType
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getGreetings
soap:operation soapAction=urn:getGreetings style=document/
wsdl:input
soap:body use=literal/
/wsdl:input
wsdl:output
soap:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
Re: Branching for Release 1.3 was: Re: Release 1.3?
Simon Laws wrote: On Sat, Jun 14, 2008 at 12:11 AM, Luciano Resende [EMAIL PROTECTED] wrote: I'm done with the JSR 250 issues, and got a clean build from latest svn revision. On Fri, Jun 13, 2008 at 1:34 PM, Simon Laws [EMAIL PROTECTED] wrote: On Fri, Jun 13, 2008 at 9:32 PM, Raymond Feng [EMAIL PROTECTED] wrote: I just checked in some improvements in the databinding area after a full clean build. Now I will stay away from the code :-). Thanks, Raymond -- From: Simon Laws [EMAIL PROTECTED] Sent: Friday, June 13, 2008 11:16 AM To: tuscany-dev@ws.apache.org Subject: Branching for Release 1.3 was: Re: Release 1.3? I'm just trying to finish up the changes required to unhook the old domain modules from the runtime, tests and samples. Then I'm pretty much done with things I want to do before cutting the R1.3 branch. I'm planning on doing this first thing tomorrow morning UK time. Can you let me know if there are changes you are working on that you want to finish before I cut the branch. Also if there are changes you have that don't need to go in the branch can you hold back for a little while as I get this done. Obviously I'd like to keep the trunk as stable as possible for the next 12 hours so if people have time to give the code a spin and do a build that would be great. Particularly after I've checked in the build changes related to domain. I'll post when I'm done. Regards Simon Great, thanks Raymond. I'll do an update and another build. Could you do the same to try the domain removal changes I checked in? Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ OK, thanks everyone. I've now taken the branch for 1.3 so feel free to do as you will with trunk. I'll start the process of tidying release, removing the dead modules etc. shortly. I've created a Java-SCA-1.3 category in JIRA so any new issues for the branch in there please. Thanks Simon I checked in a fix for TUSCANY-2298 as r668020. I did a full build before and after applying the patch, and everything was OK. Simon
[jira] Resolved: (TUSCANY-2298) Incorrect service endpoint when wsdl.service is used with Service webservice binding
[
https://issues.apache.org/jira/browse/TUSCANY-2298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash resolved TUSCANY-2298.
-
Resolution: Fixed
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.3
Fixed under r668025 in trunk, and r668020 in the 1.3 branch.
Incorrect service endpoint when wsdl.service is used with Service webservice
binding
Key: TUSCANY-2298
URL: https://issues.apache.org/jira/browse/TUSCANY-2298
Project: Tuscany
Issue Type: Bug
Components: Java SCA Axis Binding Extension, Java SCA Tomcat
Integration
Affects Versions: Java-SCA-1.2
Reporter: Vamsavardhana Reddy
Assignee: Simon Nash
Fix For: Java-SCA-1.3
Web Service Binding Specification Spec v1.00 - Sec 2.1 - lines 38 to 41:
38 o Service:
39 WSDL-namespace-URI#wsdl.service(service-name)
40 In this case, all the endpoints in the WSDL Service that have equivalent
PortTypes with
41 the SCA service or reference must be available to the SCA service or
reference.
When wsdlElement is of 'Service' type, service must be available on all ports
corresponding to the service. The following is the wsdl I am using for
'AService':
{code}
?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=http://schemas.xmlsoap.org/wsdl/mime/;
xmlns:http=http://schemas.xmlsoap.org/wsdl/http/;
xmlns:ns1=http://org.apache.axis2/xsd;
xmlns:wsaw=http://www.w3.org/2006/05/addressing/wsdl;
xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:soap=http://schemas.xmlsoap.org/wsdl/soap/;
xmlns:wsdl=http://schemas.xmlsoap.org/wsdl/;
wsdl:types
xs:schema attributeFormDefault=qualified
elementFormDefault=qualified
targetNamespace=http://wsbinding.vtest.sca.tuscany.apache.org;
xmlns:ns=http://wsbinding.vtest.sca.tuscany.apache.org;
xs:element name=getGreetings
xs:complexType
xs:sequence
xs:element minOccurs=0 name=param0
nillable=true type=xs:string/
/xs:sequence
/xs:complexType
/xs:element
xs:element name=getGreetingsResponse
xs:complexType
xs:sequence
xs:element minOccurs=0 name=return
nillable=true type=xs:string/
/xs:sequence
/xs:complexType
/xs:element
/xs:schema
/wsdl:types
wsdl:message name=getGreetingsRequest
wsdl:part name=parameters element=ns0:getGreetings
/wsdl:part
/wsdl:message
wsdl:message name=getGreetingsResponse
wsdl:part name=parameters element=ns0:getGreetingsResponse
/wsdl:part
/wsdl:message
wsdl:portType name=AServicePortType
wsdl:operation name=getGreetings
wsdl:input message=ns0:getGreetingsRequest
wsaw:Action=urn:getGreetings
/wsdl:input
wsdl:output message=ns0:getGreetingsResponse
wsaw:Action=urn:getGreetingsResponse
/wsdl:output
/wsdl:operation
/wsdl:portType
wsdl:binding name=AServiceSOAP12Binding type=ns0:AServicePortType
soap12:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getGreetings
soap12:operation soapAction=urn:getGreetings style=document/
wsdl:input
soap12:body use=literal/
/wsdl:input
wsdl:output
soap12:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:binding name=AServicePortTypeBinding type=ns0:AServicePortType
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getGreetings
soap:operation soapAction=/
wsdl:input
soap:body use=literal/
/wsdl:input
wsdl:output
soap:body use=literal/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:binding name=AServiceHttpBinding type=ns0:AServicePortType
http:binding verb=POST/
wsdl:operation name=getGreetings
http:operation location=AService/getGreetings/
wsdl:input
mime:content part=getGreetings type=text/xml/
/wsdl:input
wsdl:output
mime:content part=getGreetings type=text/xml/
/wsdl:output
/wsdl:operation
/wsdl:binding
wsdl:binding name=AServiceSOAP11Binding type=ns0:AServicePortType
soap:binding style=document
transport=http://schemas.xmlsoap.org/soap/http/
wsdl:operation name=getGreetings
soap:operation soapAction=urn:getGreetings style=document/
wsdl:input
soap:body
Re: Tracking Tuscany extensions, was: Distribution zips and what they contain, was: SCA runtimes
Thanks Mike for putting things in perspective. It always helps to think of these topics in terms of problem that we are trying to solve and who the audience is before we get into the details of how to solve it. Your idea of creating wiki pages for each of these topics will help clarify things further and keep the discussion focused. I created wiki pages based on my understanding of this thread for items a and c. It is a starting point and needs to be reviewed and fixed. a) Basic modules, as we have today. ß created under [1] b) A variety of functional components, that represent sets of coherent functions. ß created under [2] c) A small number of large packages aimed at supporting end users in a series of environments and with a specific set of functionality ß created under [3] d) Simple ways of starting Tuscany functionality - based on using the packages in c) [4] I also created wiki pages for items b and d, however I cannot articulate what problem we are trying to solve with b and d. Can you please expand on these two? What is the problem? Who is the audience? This email thread is 32 emails deep on gmail. It is extremely difficult to read and follow. Once there is agreement on the categories, can we start a separate thread per category and continue updating the wiki pages as the discussions solidify? This is like using the wiki pages as a white board for keeping discussions focused. I have created these pages under [5] and I hope that others find this approach useful. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Basic+Modules+Runtime+Bundles [2] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/functional+components+at+runtime [3] http://cwiki.apache.org/confluence/pages/viewpage.action?pageId=88325 [4 http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Simple+ways+of+starting+Tuscany [5]: http://cwiki.apache.org/confluence/display/TUSCANYWIKI/SCA+Java+White+Board+Index
Re: Tuscany_SCA_Chinese_Discussion_Forum_(Tuscany_SCA中文论坛)
It is a good news for chinese user.Thanks Raymond. Thanks, Feng Wang On 2008-06-14 06:28:01,Raymond Feng [EMAIL PROTECTED] wrote: Hi, I have created a Google group to provide a forum for Chinese-speaking developers and users to exchange ideas and practices in Chinese about Tuscany and SCA. The group home page is: http://groups.google.com/group/tuscany-sca-chinese. You are invited to join and contribute to the forum! Please note tuscany-dev and tuscany-user mailing lists are the official ways to interact within the Tuscany project. The group is more like a user group for the Chinese community who prefers to communicate in Chinese. Thanks, Raymond
