[jira] Updated: (TUSCANY-76) Need a specifcation of how WSDL elements used in an SCA assembly get resolved
[ http://issues.apache.org/jira/browse/TUSCANY-76?page=all ] ant elder updated TUSCANY-76: - Fix Version/s: Java-M2 (was: Java-Mx) Affects Version/s: Java-M2 (was: Java-Mx) > Need a specifcation of how WSDL elements used in an SCA assembly get resolved > -- > > Key: TUSCANY-76 > URL: http://issues.apache.org/jira/browse/TUSCANY-76 > Project: Tuscany > Issue Type: New Feature > Components: Specification >Affects Versions: Java-M2 >Reporter: Jean-Sebastien Delfino > Assigned To: Michael John Edwards > Fix For: Java-M2 > > > The SCA 0.9 assembly spec references WSDL portTypes and ports by namespace + > local name. The specification does not make any statement about how an SCA > runtime or SCA tooling is supposed to resolve these WSDL elements. > I think we have a number of options here: > - define name mapping rules between WSDL namespaces and names and WSDL file > locations, allowing a runtime and tooling to derive the location of the WSDL > files from their namespaces for example (similar to the Java package -> > location mapping rules) > - introduce a way to associate a WSDL namespace to a particular file or > collection of files (similar to a WSDL ) > As a temporary solution until the spec resolves this issue, In Tuscany we > have introduced an SCDL extension for this. The app developer must add a > element to his sca.module, sca.fragment or sca.subsystem SCA > assembly file. The element makes the referenced WSDL available > within the scope of the particular SCA assembly. > The BigBank sample contains an example of this. > This Tuscany extension can be used to cover most scenarios for now but will > not address well scenarios where you want to share a .componentType that uses > a WSDL portType in two different modules. You'd have to repeat the same > in the two modules. > So we need the SCA assembly spec to address this issue and then adjust our > implementation to what the spec will define. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-76) Need a specifcation of how WSDL elements used in an SCA assembly get resolved
[ https://issues.apache.org/jira/browse/TUSCANY-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Sebastien Delfino updated TUSCANY-76: -- Fix Version/s: (was: Java-M2) Java-M3 > Need a specifcation of how WSDL elements used in an SCA assembly get resolved > -- > > Key: TUSCANY-76 > URL: https://issues.apache.org/jira/browse/TUSCANY-76 > Project: Tuscany > Issue Type: New Feature > Components: Specification >Affects Versions: Java-M2 >Reporter: Jean-Sebastien Delfino > Assigned To: Michael John Edwards > Fix For: Java-M3 > > > The SCA 0.9 assembly spec references WSDL portTypes and ports by namespace + > local name. The specification does not make any statement about how an SCA > runtime or SCA tooling is supposed to resolve these WSDL elements. > I think we have a number of options here: > - define name mapping rules between WSDL namespaces and names and WSDL file > locations, allowing a runtime and tooling to derive the location of the WSDL > files from their namespaces for example (similar to the Java package -> > location mapping rules) > - introduce a way to associate a WSDL namespace to a particular file or > collection of files (similar to a WSDL ) > As a temporary solution until the spec resolves this issue, In Tuscany we > have introduced an SCDL extension for this. The app developer must add a > element to his sca.module, sca.fragment or sca.subsystem SCA > assembly file. The element makes the referenced WSDL available > within the scope of the particular SCA assembly. > The BigBank sample contains an example of this. > This Tuscany extension can be used to cover most scenarios for now but will > not address well scenarios where you want to share a .componentType that uses > a WSDL portType in two different modules. You'd have to repeat the same > in the two modules. > So we need the SCA assembly spec to address this issue and then adjust our > implementation to what the spec will define. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-76) Need a specifcation of how WSDL elements used in an SCA assembly get resolved
[ http://issues.apache.org/jira/browse/TUSCANY-76?page=all ] Jean-Sebastien Delfino updated TUSCANY-76: -- Fix Version: 0.9x Version: 0.9x > Need a specifcation of how WSDL elements used in an SCA assembly get resolved > -- > > Key: TUSCANY-76 > URL: http://issues.apache.org/jira/browse/TUSCANY-76 > Project: Tuscany > Type: New Feature > Components: Specification > Versions: 0.9x > Reporter: Jean-Sebastien Delfino > Assignee: Michael John Edwards > Fix For: 0.9x > > The SCA 0.9 assembly spec references WSDL portTypes and ports by namespace + > local name. The specification does not make any statement about how an SCA > runtime or SCA tooling is supposed to resolve these WSDL elements. > I think we have a number of options here: > - define name mapping rules between WSDL namespaces and names and WSDL file > locations, allowing a runtime and tooling to derive the location of the WSDL > files from their namespaces for example (similar to the Java package -> > location mapping rules) > - introduce a way to associate a WSDL namespace to a particular file or > collection of files (similar to a WSDL ) > As a temporary solution until the spec resolves this issue, In Tuscany we > have introduced an SCDL extension for this. The app developer must add a > element to his sca.module, sca.fragment or sca.subsystem SCA > assembly file. The element makes the referenced WSDL available > within the scope of the particular SCA assembly. > The BigBank sample contains an example of this. > This Tuscany extension can be used to cover most scenarios for now but will > not address well scenarios where you want to share a .componentType that uses > a WSDL portType in two different modules. You'd have to repeat the same > in the two modules. > So we need the SCA assembly spec to address this issue and then adjust our > implementation to what the spec will define. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
