JIRA-4206 XSDModelResolver fails to initiate WSDL model resolution for inline schemas

2012-03-08 Thread Kaushik Mukherjee
I wanted to clarify the use case for JIRA-4206 a bit. The scenario I
am looking at involves a WSDL with an inline schema. This inline
schema is then referenced from another xsd through an import. The WSDL
is not referenced in any other way such as through interface.wsdl. It
is only indirectly referenced from the import of the inline schema
namespace. Should we expect to add a model of the inline schema to the
contribution in this scenario?

Thanks,
Kaushik


[jira] [Updated] (TUSCANY-4026) XSDModelResolver fails to initiate WSDL model resolution for inline schemas

2012-03-08 Thread Kaushik Mukherjee (Updated) (JIRA)

 [ 
https://issues.apache.org/jira/browse/TUSCANY-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kaushik Mukherjee updated TUSCANY-4026:
---

Attachment: JIRA-4206.patch

Updated XSDModelResolver to resolve inline schemas

> XSDModelResolver fails to initiate WSDL model resolution for inline schemas
> ---
>
> Key: TUSCANY-4026
> URL: https://issues.apache.org/jira/browse/TUSCANY-4026
> Project: Tuscany
>  Issue Type: Bug
>  Components: Java SCA Databinding-SDO
>Affects Versions: Java-SCA-2.x
>Reporter: Kaushik Mukherjee
> Attachments: JIRA-4206.patch
>
>
> XSDModelResolver fails to initiate WSDLModelResolver for inline schemas 
> during start so there is no inline schema document object model added to the 
> contribution. When we try to resolve the namespace and type associated with 
> the inline schema we fail to find the document since it was never built.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (TUSCANY-4026) XSDModelResolver fails to initiate WSDL model resolution for inline schemas

2012-03-08 Thread Kaushik Mukherjee (Created) (JIRA)
XSDModelResolver fails to initiate WSDL model resolution for inline schemas
---

 Key: TUSCANY-4026
 URL: https://issues.apache.org/jira/browse/TUSCANY-4026
 Project: Tuscany
  Issue Type: Bug
  Components: Java SCA Databinding-SDO
Affects Versions: Java-SCA-2.x
Reporter: Kaushik Mukherjee


XSDModelResolver fails to initiate WSDLModelResolver for inline schemas during 
start so there is no inline schema document object model added to the 
contribution. When we try to resolve the namespace and type associated with the 
inline schema we fail to find the document since it was never built.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Closed] (TUSCANY-4025) Give registry contribution listeners a chance to retireve the contribution info before removing it

2012-03-08 Thread Simon Laws (Closed) (JIRA)

 [ 
https://issues.apache.org/jira/browse/TUSCANY-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Laws closed TUSCANY-4025.
---

Resolution: Fixed

Fix committed at revision: 1298469

> Give registry contribution listeners a chance to retireve the contribution 
> info before removing it
> --
>
> Key: TUSCANY-4025
> URL: https://issues.apache.org/jira/browse/TUSCANY-4025
> Project: Tuscany
>  Issue Type: Bug
>  Components: SCA Java Runtime
>Affects Versions: Java-SCA-2.0-Beta3
> Environment: All 
>Reporter: Simon Laws
>Assignee: Simon Laws
> Fix For: Java-SCA-2.0
>
>
> In our DomainRegistryImpl class we have 
> public void uninstallContribution(String uri) {
> contributionDescriptions.remove(uri);
> for (ContributionListener listener : contributionlisteners) {
> listener.contributionRemoved(uri);
> }
> }
> It should wait until the listeners have been called before removing the 
> contribution description. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Assigned] (TUSCANY-4025) Give registry contribution listeners a chance to retireve the contribution info before removing it

2012-03-08 Thread Simon Laws (Assigned) (JIRA)

 [ 
https://issues.apache.org/jira/browse/TUSCANY-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Laws reassigned TUSCANY-4025:
---

Assignee: Simon Laws

> Give registry contribution listeners a chance to retireve the contribution 
> info before removing it
> --
>
> Key: TUSCANY-4025
> URL: https://issues.apache.org/jira/browse/TUSCANY-4025
> Project: Tuscany
>  Issue Type: Bug
>  Components: SCA Java Runtime
>Affects Versions: Java-SCA-2.0-Beta3
> Environment: All 
>Reporter: Simon Laws
>Assignee: Simon Laws
> Fix For: Java-SCA-2.0
>
>
> In our DomainRegistryImpl class we have 
> public void uninstallContribution(String uri) {
> contributionDescriptions.remove(uri);
> for (ContributionListener listener : contributionlisteners) {
> listener.contributionRemoved(uri);
> }
> }
> It should wait until the listeners have been called before removing the 
> contribution description. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] [Created] (TUSCANY-4025) Give registry contribution listeners a chance to retireve the contribution info before removing it

2012-03-08 Thread Simon Laws (Created) (JIRA)
Give registry contribution listeners a chance to retireve the contribution info 
before removing it
--

 Key: TUSCANY-4025
 URL: https://issues.apache.org/jira/browse/TUSCANY-4025
 Project: Tuscany
  Issue Type: Bug
  Components: SCA Java Runtime
Affects Versions: Java-SCA-2.0-Beta3
 Environment: All 
Reporter: Simon Laws
 Fix For: Java-SCA-2.0


In our DomainRegistryImpl class we have 

public void uninstallContribution(String uri) {
contributionDescriptions.remove(uri);
for (ContributionListener listener : contributionlisteners) {
listener.contributionRemoved(uri);
}
}

It should wait until the listeners have been called before removing the 
contribution description. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[VOTE] Release 2.0-Beta4 RC1

2012-03-08 Thread ant elder
Here's the release vote for RC1 of the 2.0-Beta4 artifacts, please
review and vote.

You can find the staged artifacts at:
http://people.apache.org/~antelder/tuscany/2.0-Beta4-RC1/

and the SVN tag for the release at:
https://svn.apache.org/repos/asf/tuscany/sca-java-2.x/tags/2.0-Beta4-RC1/

   ...ant