[jira] [Commented] (TUSCANY-4031) IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding
[ https://issues.apache.org/jira/browse/TUSCANY-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236484#comment-13236484 ] Simon Laws commented on TUSCANY-4031: - Hi Greg Are you happy to have this patch applied? If so can you check the box in the JIRA to confirm that. Thanks. IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding -- Key: TUSCANY-4031 URL: https://issues.apache.org/jira/browse/TUSCANY-4031 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Priority: Minor Attachments: TUSCANY-4031.patch ComponentPolicyBuilderImpl.checkIntentsResolved() checks when intents used by an Endpoint are provided by the binding. It should do the same for intents used by an EndpointReference. -- 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-4030) AccessControlException when trying to read schemas with Java 2 security enabled
[ https://issues.apache.org/jira/browse/TUSCANY-4030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-4030: --- Assignee: Simon Laws AccessControlException when trying to read schemas with Java 2 security enabled --- Key: TUSCANY-4030 URL: https://issues.apache.org/jira/browse/TUSCANY-4030 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee Assignee: Simon Laws Attachments: TUSCANY-4030v3.patch I believe we need to wrap line 183 in the XSDModelResolver with an AccessController.doPrivileged so we can read a schema when java 2 security is enabled. Working on a patch now. InputSource xsd = null; final XSDefinition finaldef = definition; try { try { xsd = (InputSource) AccessController.doPrivileged(new PrivilegedExceptionActionInputSource() { public InputSource run() throws IOException { return XMLDocumentHelper.getInputSource(finaldef.getLocation().toURL()); } }); } catch (PrivilegedActionException e) { throw (IOException) e.getException(); } } catch (IOException e) { throw new ContributionRuntimeException(e); } java.security.AccessControlException: Access denied (java.io.FilePermission C:\WAS\was85a\profiles\AppSrv01\installedAssets\sdoscope-shared-oasis.jar\BASE\sdoscope-shared-oasis.jar read) at java.security.AccessController.checkPermission(AccessController.java:132) at java.lang.SecurityManager.checkPermission(SecurityManager.java:544) at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java:208) at java.lang.SecurityManager.checkRead(SecurityManager.java:883) at java.util.zip.ZipFile.init(ZipFile.java:145) at java.util.jar.JarFile.init(JarFile.java:149) at java.util.jar.JarFile.init(JarFile.java:86) at sun.net.www.protocol.jar.URLJarFile.init(URLJarFile.java:84) at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:60) at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:92) at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:119) at sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:147) at org.apache.tuscany.sca.common.xml.XMLDocumentHelper.openStream(XMLDocumentHelper.java:139) at org.apache.tuscany.sca.common.xml.XMLDocumentHelper.getInputSource(XMLDocumentHelper.java:129) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:183) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:224) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:123) at org.apache.tuscany.sca.contribution.resolver.ExtensibleModelResolver.resolveModel(ExtensibleModelResolver.java:154) -- 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] [Commented] (TUSCANY-4035) Application could possibly fail to start if multiple threads are loading the same schema
[ https://issues.apache.org/jira/browse/TUSCANY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13236509#comment-13236509 ] Simon Laws commented on TUSCANY-4035: - Hi Kaushik Can you check the flag that says you're happy that this is a patch that Apache can use? Application could possibly fail to start if multiple threads are loading the same schema Key: TUSCANY-4035 URL: https://issues.apache.org/jira/browse/TUSCANY-4035 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee Attachments: TUSCANY-4035.patch This was an issue in Tuscany 1.x and is likely an issue in the 2.x code as well. The fix in 1.x was to synchronize schema loading across all XSDModelResolvers. Starting multiple applications simultaneously can lead to an exception such as: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: http://my.namespace at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:223) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:202) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:424) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:347) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:379) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:204) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:240) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:114) -- 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] [Updated] (TUSCANY-4035) Application could possibly fail to start if multiple threads are loading the same schema
[ https://issues.apache.org/jira/browse/TUSCANY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaushik Mukherjee updated TUSCANY-4035: --- Attachment: TUSCANY-4035.patch Grant license to ASF for inclusion in ASF works Application could possibly fail to start if multiple threads are loading the same schema Key: TUSCANY-4035 URL: https://issues.apache.org/jira/browse/TUSCANY-4035 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee Attachments: TUSCANY-4035.patch This was an issue in Tuscany 1.x and is likely an issue in the 2.x code as well. The fix in 1.x was to synchronize schema loading across all XSDModelResolvers. Starting multiple applications simultaneously can lead to an exception such as: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: http://my.namespace at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:223) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:202) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:424) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:347) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:379) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:204) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:240) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:114) -- 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] [Updated] (TUSCANY-4035) Application could possibly fail to start if multiple threads are loading the same schema
[ https://issues.apache.org/jira/browse/TUSCANY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaushik Mukherjee updated TUSCANY-4035: --- Attachment: (was: TUSCANY-4035.patch) Application could possibly fail to start if multiple threads are loading the same schema Key: TUSCANY-4035 URL: https://issues.apache.org/jira/browse/TUSCANY-4035 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee Attachments: TUSCANY-4035.patch This was an issue in Tuscany 1.x and is likely an issue in the 2.x code as well. The fix in 1.x was to synchronize schema loading across all XSDModelResolvers. Starting multiple applications simultaneously can lead to an exception such as: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: http://my.namespace at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:223) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:202) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:424) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:347) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:379) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:204) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:240) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:114) -- 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-4033) Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen
[ https://issues.apache.org/jira/browse/TUSCANY-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-4033. --- Resolution: Fixed Fix Version/s: Java-SCA-2.0 Fix applied at revision: 1304327 Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen Key: TUSCANY-4033 URL: https://issues.apache.org/jira/browse/TUSCANY-4033 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-2.0 Reporter: Vijai Kalathur Assignee: Simon Laws Fix For: Java-SCA-2.0 If I have a service interface which does not contain a no-arg default constructor and try to do a remote service invocation to that service, the invocation fails when the haveMatchingInterfaceContracts method in EndpointReferenceBinderImpl tries to generate a WSDL. Since the interface does not contain a no-arg constructor, the wsdl gen fails. We might have to update something in this check if (endpointReferenceContract.getClass() != endpointContract.getClass() || endpointReferenceContract.getNormalizedWSDLContract() != null || endpointContract.getNormalizedWSDLContract() != null) { endpointReferenceContract = ((RuntimeEndpointReference)endpointReference).getGeneratedWSDLContract(endpointReferenceContract); endpointContract = ((RuntimeEndpoint)endpoint).getGeneratedWSDLContract(endpointContract); } to not generate the wsdl in certain cases. -- 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-4033) Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen
[ https://issues.apache.org/jira/browse/TUSCANY-4033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-4033: --- Assignee: Simon Laws Interface matching code in EndpointReferenceBinderImpl fails doing a wsdlgen Key: TUSCANY-4033 URL: https://issues.apache.org/jira/browse/TUSCANY-4033 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-2.0 Reporter: Vijai Kalathur Assignee: Simon Laws Fix For: Java-SCA-2.0 If I have a service interface which does not contain a no-arg default constructor and try to do a remote service invocation to that service, the invocation fails when the haveMatchingInterfaceContracts method in EndpointReferenceBinderImpl tries to generate a WSDL. Since the interface does not contain a no-arg constructor, the wsdl gen fails. We might have to update something in this check if (endpointReferenceContract.getClass() != endpointContract.getClass() || endpointReferenceContract.getNormalizedWSDLContract() != null || endpointContract.getNormalizedWSDLContract() != null) { endpointReferenceContract = ((RuntimeEndpointReference)endpointReference).getGeneratedWSDLContract(endpointReferenceContract); endpointContract = ((RuntimeEndpoint)endpoint).getGeneratedWSDLContract(endpointContract); } to not generate the wsdl in certain cases. -- 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] [Updated] (TUSCANY-4035) Application could possibly fail to start if multiple threads are loading the same schema
[ https://issues.apache.org/jira/browse/TUSCANY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaushik Mukherjee updated TUSCANY-4035: --- Attachment: (was: TUSCANY-4035.patch) Application could possibly fail to start if multiple threads are loading the same schema Key: TUSCANY-4035 URL: https://issues.apache.org/jira/browse/TUSCANY-4035 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee This was an issue in Tuscany 1.x and is likely an issue in the 2.x code as well. The fix in 1.x was to synchronize schema loading across all XSDModelResolvers. Starting multiple applications simultaneously can lead to an exception such as: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: http://my.namespace at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:223) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:202) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:424) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:347) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:379) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:204) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:240) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:114) -- 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] [Updated] (TUSCANY-4035) Application could possibly fail to start if multiple threads are loading the same schema
[ https://issues.apache.org/jira/browse/TUSCANY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaushik Mukherjee updated TUSCANY-4035: --- Attachment: TUSCANY-4035v2.patch Updated patch on top of latest revision. Includes TUSCANY-4030. Application could possibly fail to start if multiple threads are loading the same schema Key: TUSCANY-4035 URL: https://issues.apache.org/jira/browse/TUSCANY-4035 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee Attachments: TUSCANY-4035v2.patch This was an issue in Tuscany 1.x and is likely an issue in the 2.x code as well. The fix in 1.x was to synchronize schema loading across all XSDModelResolvers. Starting multiple applications simultaneously can lead to an exception such as: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: http://my.namespace at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:223) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:202) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:424) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:347) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:379) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:204) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:240) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:114) -- 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] [Updated] (TUSCANY-4031) IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding
[ https://issues.apache.org/jira/browse/TUSCANY-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-4031: - Attachment: (was: TUSCANY-4031.patch) IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding -- Key: TUSCANY-4031 URL: https://issues.apache.org/jira/browse/TUSCANY-4031 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Priority: Minor Attachments: TUSCANY-4031.patch ComponentPolicyBuilderImpl.checkIntentsResolved() checks when intents used by an Endpoint are provided by the binding. It should do the same for intents used by an EndpointReference. -- 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] [Updated] (TUSCANY-4031) IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding
[ https://issues.apache.org/jira/browse/TUSCANY-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-4031: - Attachment: TUSCANY-4031.patch IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding -- Key: TUSCANY-4031 URL: https://issues.apache.org/jira/browse/TUSCANY-4031 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Priority: Minor Attachments: TUSCANY-4031.patch ComponentPolicyBuilderImpl.checkIntentsResolved() checks when intents used by an Endpoint are provided by the binding. It should do the same for intents used by an EndpointReference. -- 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-4031) IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding
[ https://issues.apache.org/jira/browse/TUSCANY-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-4031: --- Assignee: Simon Laws IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding -- Key: TUSCANY-4031 URL: https://issues.apache.org/jira/browse/TUSCANY-4031 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Assignee: Simon Laws Priority: Minor Fix For: Java-SCA-2.0 Attachments: TUSCANY-4031.patch ComponentPolicyBuilderImpl.checkIntentsResolved() checks when intents used by an Endpoint are provided by the binding. It should do the same for intents used by an EndpointReference. -- 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-4031) IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding
[ https://issues.apache.org/jira/browse/TUSCANY-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-4031. --- Resolution: Fixed Fix Version/s: Java-SCA-2.0 Applied at revision: 1304507. Thanks for the patch Greg. IntentNotSatisfiedAtBuild warning occurs when reference uses an intent provided by binding -- Key: TUSCANY-4031 URL: https://issues.apache.org/jira/browse/TUSCANY-4031 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Assignee: Simon Laws Priority: Minor Fix For: Java-SCA-2.0 Attachments: TUSCANY-4031.patch ComponentPolicyBuilderImpl.checkIntentsResolved() checks when intents used by an Endpoint are provided by the binding. It should do the same for intents used by an EndpointReference. -- 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-4032) Remote getService() lookup with only component name fails when target has a callback
[ https://issues.apache.org/jira/browse/TUSCANY-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-4032: --- Assignee: Simon Laws Remote getService() lookup with only component name fails when target has a callback Key: TUSCANY-4032 URL: https://issues.apache.org/jira/browse/TUSCANY-4032 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-2.0 Environment: All OS Reporter: Vijai Kalathur Assignee: Simon Laws If I deploy a composite with the following component component name=SCAJFrontendComponent implementation.java class=test.bindings.sca.FrontendImpl/ service name=FrontendService interface.java interface=test.bindings.sca.intf.FrontendService/ binding.sca / /service reference name=backendService target=SerializationBackendComponent interface.java interface=test.bindings.sca.intf.SerializeBackendService callbackInterface=test.bindings.sca.intf.SerializeCallback/ callback binding.sca / /callback /reference /component and try to do a getService lookup using just the component name on a different JVM, the lookup fails saying there are multiple services in the component and I need to specify a service name. The check in DefaultEndpointFinder to check if the endpoint service is a callback service doesn't seem to be working in the remote case. I think the code in the EndpointProcessor needs to be updated to include some attribute to indicate that the service is a callback service when it's getting serialized. -- 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-4032) Remote getService() lookup with only component name fails when target has a callback
[ https://issues.apache.org/jira/browse/TUSCANY-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-4032. --- Resolution: Fixed Fix Version/s: Java-SCA-2.0 Fix applied at revision: 1304510 Remote getService() lookup with only component name fails when target has a callback Key: TUSCANY-4032 URL: https://issues.apache.org/jira/browse/TUSCANY-4032 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-2.0 Environment: All OS Reporter: Vijai Kalathur Assignee: Simon Laws Fix For: Java-SCA-2.0 If I deploy a composite with the following component component name=SCAJFrontendComponent implementation.java class=test.bindings.sca.FrontendImpl/ service name=FrontendService interface.java interface=test.bindings.sca.intf.FrontendService/ binding.sca / /service reference name=backendService target=SerializationBackendComponent interface.java interface=test.bindings.sca.intf.SerializeBackendService callbackInterface=test.bindings.sca.intf.SerializeCallback/ callback binding.sca / /callback /reference /component and try to do a getService lookup using just the component name on a different JVM, the lookup fails saying there are multiple services in the component and I need to specify a service name. The check in DefaultEndpointFinder to check if the endpoint service is a callback service doesn't seem to be working in the remote case. I think the code in the EndpointProcessor needs to be updated to include some attribute to indicate that the service is a callback service when it's getting serialized. -- 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-4035) Application could possibly fail to start if multiple threads are loading the same schema
[ https://issues.apache.org/jira/browse/TUSCANY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-4035: --- Assignee: Simon Laws Application could possibly fail to start if multiple threads are loading the same schema Key: TUSCANY-4035 URL: https://issues.apache.org/jira/browse/TUSCANY-4035 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee Assignee: Simon Laws Attachments: TUSCANY-4035v2.patch This was an issue in Tuscany 1.x and is likely an issue in the 2.x code as well. The fix in 1.x was to synchronize schema loading across all XSDModelResolvers. Starting multiple applications simultaneously can lead to an exception such as: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: http://my.namespace at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:223) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:202) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:424) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:347) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:379) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:204) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:240) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:114) -- 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-4035) Application could possibly fail to start if multiple threads are loading the same schema
[ https://issues.apache.org/jira/browse/TUSCANY-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-4035. --- Resolution: Fixed Fix Version/s: Java-SCA-2.0 Applied at revision: 1304516. Thanks for the patch Kaushik. Application could possibly fail to start if multiple threads are loading the same schema Key: TUSCANY-4035 URL: https://issues.apache.org/jira/browse/TUSCANY-4035 Project: Tuscany Issue Type: Bug Reporter: Kaushik Mukherjee Assignee: Simon Laws Fix For: Java-SCA-2.0 Attachments: TUSCANY-4035v2.patch This was an issue in Tuscany 1.x and is likely an issue in the 2.x code as well. The fix in 1.x was to synchronize schema loading across all XSDModelResolvers. Starting multiple applications simultaneously can lead to an exception such as: org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in collection. Namespace: http://my.namespace at org.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(SchemaBuilder.java:223) at org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:202) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:424) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:347) at org.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollection.java:379) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.loadOnDemand(XSDModelResolver.java:204) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.aggregate(XSDModelResolver.java:240) at org.apache.tuscany.sca.xsd.xml.XSDModelResolver.resolveModel(XSDModelResolver.java:114) -- 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-4036) WSDL service names are duplicated when user does not provide WSDL
WSDL service names are duplicated when user does not provide WSDL - Key: TUSCANY-4036 URL: https://issues.apache.org/jira/browse/TUSCANY-4036 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Priority: Minor Attachments: TUSCANY-4036.patch Scenario: An SCA composite has multiple components which * use binding.ws * do not provide a WSDL document via the wsdlElement attribute * implement the same Java interface In this case, for each web service binding, WSDLServiceGenerator takes the WSDL Definition that is generated by Interface2WSDLGenerator and adds a WSDL service and port to it. In this scenario where multiple components implement the same interface, the resulting WSDL services have the same definition namespace (which is derived from the Java package name) and the same local name (which is derived from the Java class name). This may make it difficult for the runtime to tailor the WSDL to support component-specific policy. This problem does not exist when the user does provide WSDL (either via wsdlElement or interface.wsdl). In that case WSDLServiceGenerator creates a new WSDL Definition with a modified namespace that includes the component name. This is possible because the generated WSDL can import the user's WSDL document. It is more difficult to do this in the problem scenario because WSDLServiceGenerator is already working with a generated document that has no physical location for the import to refer to. An alternate solution is for WSDLServiceGenerator to include the component name in the WSDL service name. -- 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] [Updated] (TUSCANY-4036) WSDL service names are duplicated when user does not provide WSDL
[ https://issues.apache.org/jira/browse/TUSCANY-4036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Dritschler updated TUSCANY-4036: - Attachment: TUSCANY-4036.patch WSDL service names are duplicated when user does not provide WSDL - Key: TUSCANY-4036 URL: https://issues.apache.org/jira/browse/TUSCANY-4036 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-2.0 Reporter: Greg Dritschler Priority: Minor Attachments: TUSCANY-4036.patch Scenario: An SCA composite has multiple components which * use binding.ws * do not provide a WSDL document via the wsdlElement attribute * implement the same Java interface In this case, for each web service binding, WSDLServiceGenerator takes the WSDL Definition that is generated by Interface2WSDLGenerator and adds a WSDL service and port to it. In this scenario where multiple components implement the same interface, the resulting WSDL services have the same definition namespace (which is derived from the Java package name) and the same local name (which is derived from the Java class name). This may make it difficult for the runtime to tailor the WSDL to support component-specific policy. This problem does not exist when the user does provide WSDL (either via wsdlElement or interface.wsdl). In that case WSDLServiceGenerator creates a new WSDL Definition with a modified namespace that includes the component name. This is possible because the generated WSDL can import the user's WSDL document. It is more difficult to do this in the problem scenario because WSDLServiceGenerator is already working with a generated document that has no physical location for the import to refer to. An alternate solution is for WSDLServiceGenerator to include the component name in the WSDL service name. -- 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