[jira] Resolved: (TUSCANY-2267) Raise a warning if both reference target and binding URI are specified
[ https://issues.apache.org/jira/browse/TUSCANY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2267. - Resolution: Fixed committed at r667472, Thanks for the patch Ram. > Raise a warning if both reference target and binding URI are specified > -- > > Key: TUSCANY-2267 > URL: https://issues.apache.org/jira/browse/TUSCANY-2267 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: All >Reporter: Simon Laws >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2267.patch > > > The assembly spec says around line 1380 that " A reference must not mix the > use of endpoints specified via binding elements with target endpoints > specified via the target attribute". We should raise a warning if this is > detected in a composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2384) Message Conversion for Contribution Builders
[ https://issues.apache.org/jira/browse/TUSCANY-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2384. - Resolution: Fixed committed at r667472, Thanks for the patch Ram. > Message Conversion for Contribution Builders > > > Key: TUSCANY-2384 > URL: https://issues.apache.org/jira/browse/TUSCANY-2384 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Assembly Model >Affects Versions: Java-SCA-Next > Environment: Win XP SP2, JDK 1.5 >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2384-NEW.patch, TUSCANY-2384.patch > > > Message Conversion were required for the Contribution Builders, where few > instance of messages was found without using the messageID and > resourcebundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2267) Raise a warning if both reference target and binding URI are specified
[ https://issues.apache.org/jira/browse/TUSCANY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2267: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > Raise a warning if both reference target and binding URI are specified > -- > > Key: TUSCANY-2267 > URL: https://issues.apache.org/jira/browse/TUSCANY-2267 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: All >Reporter: Simon Laws >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2267.patch > > > The assembly spec says around line 1380 that " A reference must not mix the > use of endpoints specified via binding elements with target endpoints > specified via the target attribute". We should raise a warning if this is > detected in a composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2384) Message Conversion for Contribution Builders
[ https://issues.apache.org/jira/browse/TUSCANY-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2384: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > Message Conversion for Contribution Builders > > > Key: TUSCANY-2384 > URL: https://issues.apache.org/jira/browse/TUSCANY-2384 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Assembly Model >Affects Versions: Java-SCA-Next > Environment: Win XP SP2, JDK 1.5 >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2384-NEW.patch, TUSCANY-2384.patch > > > Message Conversion were required for the Contribution Builders, where few > instance of messages was found without using the messageID and > resourcebundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2379) CompositeProcessor.java is calling promotedService.getService() instead of promotedService.getName() when writing out a composite file.
[
https://issues.apache.org/jira/browse/TUSCANY-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-2379.
-
Resolution: Fixed
Committed at 667470. Thanks for the patch Ram
> CompositeProcessor.java is calling promotedService.getService() instead of
> promotedService.getName() when writing out a composite file.
> ---
>
> Key: TUSCANY-2379
> URL: https://issues.apache.org/jira/browse/TUSCANY-2379
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
>Affects Versions: Java-SCA-1.2
>Reporter: Richard Mah
>Assignee: Simon Laws
> Attachments: TUSCANY-2379.patch
>
>
> CompositeProcessor.java is calling promotedService.getService() instead of
> promotedService.getName() when writing out the promoted service to file.
> Here is the snippet of code starting from line 546 (Revision 665831):
> String promote;
> if (promotedService != null) {
> if (promotedService.getName() != null) {
> promote = promotedComponent.getName() + '/' +
> promotedService.getService();-Here is the
> promotedService.getService() call
> } else {
> promote = promotedComponent.getName();
> }
>
> promotedService.getService() looks like it should be
> promotedService.getName() instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2379) CompositeProcessor.java is calling promotedService.getService() instead of promotedService.getName() when writing out a composite file.
[
https://issues.apache.org/jira/browse/TUSCANY-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reassigned TUSCANY-2379:
---
Assignee: Simon Laws (was: Ramkumar Ramalingam)
> CompositeProcessor.java is calling promotedService.getService() instead of
> promotedService.getName() when writing out a composite file.
> ---
>
> Key: TUSCANY-2379
> URL: https://issues.apache.org/jira/browse/TUSCANY-2379
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
>Affects Versions: Java-SCA-1.2
>Reporter: Richard Mah
>Assignee: Simon Laws
> Attachments: TUSCANY-2379.patch
>
>
> CompositeProcessor.java is calling promotedService.getService() instead of
> promotedService.getName() when writing out the promoted service to file.
> Here is the snippet of code starting from line 546 (Revision 665831):
> String promote;
> if (promotedService != null) {
> if (promotedService.getName() != null) {
> promote = promotedComponent.getName() + '/' +
> promotedService.getService();-Here is the
> promotedService.getService() call
> } else {
> promote = promotedComponent.getName();
> }
>
> promotedService.getService() looks like it should be
> promotedService.getName() instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2347. - Resolution: Fixed Comitted at r667376. Looking through this very long series of patches I think there are still some exceptions that need tidying. I'll go ahead and look at 2384 where I think you have done some more. B.t.w your dev environment is still occasionally inserting tabs instead of spaces. > Removing the exception throws from the processors > - > > Key: TUSCANY-2347 > URL: https://issues.apache.org/jira/browse/TUSCANY-2347 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next > Environment: Windows XP, >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, > TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, > TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, > TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, > TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, > TUSCANY-2347-Part7.patch, TUSCANY-2347-Part8.patch, TUSCANY-2347-Part9.patch > > > After introducing the monitors in various part of the code (especially in the > processors), while the runtime reads and resolves the contribution. Now we > are trying to remove the exception that are being thrown from these modules. > As a first step we are removing the exceptions that are safe to remove, by > leaving the critical exceptions like > a) IOException > b) XMLStreamException > c) PriviledegedActionException > d) and ParseConfigurationExceptions > As a second step, we will also be dealing with the above said exception once > we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2347: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > Removing the exception throws from the processors > - > > Key: TUSCANY-2347 > URL: https://issues.apache.org/jira/browse/TUSCANY-2347 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next > Environment: Windows XP, >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2347-Part1.patch, TUSCANY-2347-Part2.patch, > TUSCANY-2347-Part3.patch, TUSCANY-2347-Part4-NEW.patch, > TUSCANY-2347-Part4.patch, TUSCANY-2347-Part5-NEW.patch, > TUSCANY-2347-Part5.patch, TUSCANY-2347-Part6-NEW.patch, > TUSCANY-2347-Part6.patch, TUSCANY-2347-Part7-NEW.patch, > TUSCANY-2347-Part7.patch, TUSCANY-2347-Part8.patch, TUSCANY-2347-Part9.patch > > > After introducing the monitors in various part of the code (especially in the > processors), while the runtime reads and resolves the contribution. Now we > are trying to remove the exception that are being thrown from these modules. > As a first step we are removing the exceptions that are safe to remove, by > leaving the critical exceptions like > a) IOException > b) XMLStreamException > c) PriviledegedActionException > d) and ParseConfigurationExceptions > As a second step, we will also be dealing with the above said exception once > we have a detailed discussion as how to handle them. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2347) Removing the exception throws from the processors
[ https://issues.apache.org/jira/browse/TUSCANY-2347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604433#action_12604433 ] Simon Laws commented on TUSCANY-2347: - I'm trying to apply these patches but I'm having some problems. With the latest code from svn and with these patches applied on top I get errors in the areas listed below. I'm going to start working through these shortly but if you could have a go with these patches yourself on the latest code and take a look that would be useful [INFO] [INFO] Error for project: Apache Tuscany SCA HelloWorld BPEL Sample (during inst all) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\samples\helloworld-bpel\target\s urefire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA XQuery Quote Implementation Sample (during install) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\samples\quote-xquery\target\sure fire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA HelloWorld BPEL iTest (during insta ll) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\itest\bpel\helloworld\target\sur efire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA HelloWorld BPEL iTest (during insta ll) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\itest\bpel\helloworld-ws\target\ surefire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA HelloWorld Reference BPEL iTest (du ring install) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\itest\bpel\helloworld-reference\ target\surefire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA Policy Framework Integration Tests (during install) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\itest\policy-security\target\sur efire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA Validation Integration Test (during install) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\itest\validation\target\surefire -reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA Java APIs and Annotations Verificat ion Tests - Annotations - @Init (during install) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\vtest\java-api\annotations\init\ target\surefire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA Java APIs and Annotations Verificat ion Tests - Annotations - @Destroy (during install) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\vtest\java-api\annotations\destr oy\target\surefire-reports for the individual test results. [INFO] [INFO] Error for project: Apache Tuscany SCA Java APIs and Annotations Verificat ion Tests - APIs - CallableReference (during install) [INFO] [INFO] There are test failures. Please refer to C:\simon\tuscany\java-trunk\sca\vtest\java-api\apis\callablerefe rence\target\surefire-reports for the individual test results. > Removing the exception throws from the processors > - > >
[jira] Commented: (TUSCANY-2324) InterfaceContract is not pushed down to an inner, promoted component reference only with Axis2 binding
[ https://issues.apache.org/jira/browse/TUSCANY-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604207#action_12604207 ] Simon Laws commented on TUSCANY-2324: - Is there a test case for this issue that shows the problem? I'm eyeballing the code and its interesting as the code that processes promotion on the reference side works differently to the code that processes promotion on the service side. On the reference side it only copies the bindings down. On the service side it does interface contracts also. > InterfaceContract is not pushed down to an inner, promoted component > reference only with Axis2 binding > --- > > Key: TUSCANY-2324 > URL: https://issues.apache.org/jira/browse/TUSCANY-2324 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Axis Binding Extension >Reporter: Scott Kurz >Priority: Minor > > If we take the following example where an inner component reference is > overridden in two ways by the outer component using the inner Composite as > impl: > 1) a is added > 2) a WSDL intf (compatible with the inner Java intf) is declared > > > > > interface="http://blah#wsdl.interface(HelloWorld)" /> > > > > > > > > interface="test.sca.w2j.ws.statc.exc.helloworld.HelloWorld"/> > > > promote="InnerComponent/helloWorldService"/> > > we have a problem. > The CompositeActivatorImpl is going to start an Axis2ReferenceBindingProvider > for the inner Composite ref. The WS binding is propagated down or > inwards, you could say.But this WS binding has a null IC, so we're going > to look at the component ref IC, but this will be the inner component ref IC, > which is a Java IC. This kicks off a Java2WSDL and the new WSDL IC > becomes the Axis2 ref binding IC. > So the generated WSDL may not match the actual WSDL, which is a problem. > Of course, if we had included a wsdlElement (e.g. wsdl.port ) on the outer > component's we would not have had a problem; it would have > been propagated inwards along with the binding itself. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2368) Seaprate the Policy calculation phase from the Wire build phase in the builders
[ https://issues.apache.org/jira/browse/TUSCANY-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2368. - Resolution: Fixed Change committed at r666037 > Seaprate the Policy calculation phase from the Wire build phase in the > builders > --- > > Key: TUSCANY-2368 > URL: https://issues.apache.org/jira/browse/TUSCANY-2368 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: All >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Currently the class BaseWireBuilderImpl.computePolicies() is private. Make > this protected so that a independent policy builder can be constructed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2267) Raise a warning if both reference target and binding URI are specified
[ https://issues.apache.org/jira/browse/TUSCANY-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603810#action_12603810 ] Simon Laws commented on TUSCANY-2267: - I think this should apply to all bindings. It's saying that you can't specify at the same time as > Raise a warning if both reference target and binding URI are specified > -- > > Key: TUSCANY-2267 > URL: https://issues.apache.org/jira/browse/TUSCANY-2267 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: All >Reporter: Simon Laws >Assignee: Ramkumar Ramalingam >Priority: Minor > Fix For: Java-SCA-Next > > > The assembly spec says around line 1380 that " A reference must not mix the > use of endpoints specified via binding elements with target endpoints > specified via the target attribute". We should raise a warning if this is > detected in a composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2368) Seaprate the Policy calculation phase from the Wire build phase in the builders
[ https://issues.apache.org/jira/browse/TUSCANY-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2368: --- Assignee: Simon Laws > Seaprate the Policy calculation phase from the Wire build phase in the > builders > --- > > Key: TUSCANY-2368 > URL: https://issues.apache.org/jira/browse/TUSCANY-2368 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: All >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Currently the class BaseWireBuilderImpl.computePolicies() is private. Make > this protected so that a independent policy builder can be constructed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2360) Autowiring in nested composites doesn't work in all cases
[ https://issues.apache.org/jira/browse/TUSCANY-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2360. - Resolution: Fixed Changes committed at r665992. Changed wire build so that autowire doesn't wire to self and so that composite references override promoted references. > Autowiring in nested composites doesn't work in all cases > - > > Key: TUSCANY-2360 > URL: https://issues.apache.org/jira/browse/TUSCANY-2360 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2, IBM JDK 5 >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: MultiLevelRecusion.zip > > > I had expect that autowire operated within the context of a composite even > when that composite is used as part of recursive composition. I've been > playing with a simple test (attached) that has up to 3 levels of composite > and in each level two component are autowired together. It seems that it's > not always the case that the autowiring works as I had expected. Sometimes a > component is autowired to a component at another level. I haven't determined > a pattern in this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2360) Autowiring in nested composites doesn't work in all cases
[ https://issues.apache.org/jira/browse/TUSCANY-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2360: --- Assignee: Simon Laws > Autowiring in nested composites doesn't work in all cases > - > > Key: TUSCANY-2360 > URL: https://issues.apache.org/jira/browse/TUSCANY-2360 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2, IBM JDK 5 >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: MultiLevelRecusion.zip > > > I had expect that autowire operated within the context of a composite even > when that composite is used as part of recursive composition. I've been > playing with a simple test (attached) that has up to 3 levels of composite > and in each level two component are autowired together. It seems that it's > not always the case that the autowiring works as I had expected. Sometimes a > component is autowired to a component at another level. I haven't determined > a pattern in this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2368) Seaprate the Policy calculation phase from the Wire build phase in the builders
Seaprate the Policy calculation phase from the Wire build phase in the builders --- Key: TUSCANY-2368 URL: https://issues.apache.org/jira/browse/TUSCANY-2368 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: All Reporter: Simon Laws Fix For: Java-SCA-Next Currently the class BaseWireBuilderImpl.computePolicies() is private. Make this protected so that a independent policy builder can be constructed -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2360) Autowiring in nested composites doesn't work in all cases
[ https://issues.apache.org/jira/browse/TUSCANY-2360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws updated TUSCANY-2360: Attachment: MultiLevelRecusion.zip We could turn this into an itest with some work I guess but for now this is just what I've been playing with. > Autowiring in nested composites doesn't work in all cases > - > > Key: TUSCANY-2360 > URL: https://issues.apache.org/jira/browse/TUSCANY-2360 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2, IBM JDK 5 >Reporter: Simon Laws > Fix For: Java-SCA-Next > > Attachments: MultiLevelRecusion.zip > > > I had expect that autowire operated within the context of a composite even > when that composite is used as part of recursive composition. I've been > playing with a simple test (attached) that has up to 3 levels of composite > and in each level two component are autowired together. It seems that it's > not always the case that the autowiring works as I had expected. Sometimes a > component is autowired to a component at another level. I haven't determined > a pattern in this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2360) Autowiring in nested composites doesn't work in all cases
Autowiring in nested composites doesn't work in all cases - Key: TUSCANY-2360 URL: https://issues.apache.org/jira/browse/TUSCANY-2360 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 5 Reporter: Simon Laws Fix For: Java-SCA-Next I had expect that autowire operated within the context of a composite even when that composite is used as part of recursive composition. I've been playing with a simple test (attached) that has up to 3 levels of composite and in each level two component are autowired together. It seems that it's not always the case that the autowiring works as I had expected. Sometimes a component is autowired to a component at another level. I haven't determined a pattern in this. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2338) Part 2 - itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2338. - Resolution: Fixed Committed at r661788. Thanks for the patches Ram. > Part 2 - itests for validation messages > --- > > Key: TUSCANY-2338 > URL: https://issues.apache.org/jira/browse/TUSCANY-2338 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Integration Tests >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2338-Part1.patch, TUSCANY-2338-Part2.patch, > TUSCANY-2338-Part3.patch, TUSCANY-2338-Part4.patch, TUSCANY-2338-Part5.patch > > > The remaining fixes on itest for validation messages. Part1 fixes are > available from TUSCANY-2329. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2338) Part 2 - itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2338: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > Part 2 - itests for validation messages > --- > > Key: TUSCANY-2338 > URL: https://issues.apache.org/jira/browse/TUSCANY-2338 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Integration Tests >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2338-Part1.patch, TUSCANY-2338-Part2.patch, > TUSCANY-2338-Part3.patch, TUSCANY-2338-Part4.patch, TUSCANY-2338-Part5.patch > > > The remaining fixes on itest for validation messages. Part1 fixes are > available from TUSCANY-2329. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2336) Option to turn Validation on/off
[ https://issues.apache.org/jira/browse/TUSCANY-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2336. - Resolution: Fixed Fix Version/s: Java-SCA-Next The majority of our validation code is an integral part of the code that reads, resolves and builds the assembly model. I.e. there is no one separate validation phase that can be turned of. The code that does XSD validation is written to turn itself off if there are no XSD to validate against so you could use this trick to turn that part off. Also if you are not interested in what happens to any validation messages, for example, in the case where you know that the contribution is alread valid, you could either provide a monitor that does nothing or simply, in you code, ignore the contents of the monitor once the build phase is complete. > Option to turn Validation on/off > > > Key: TUSCANY-2336 > URL: https://issues.apache.org/jira/browse/TUSCANY-2336 > Project: Tuscany > Issue Type: Improvement > Components: Java SCA Problem Determination > Environment: All >Reporter: Hasan Muhammad >Priority: Critical > Fix For: Java-SCA-Next > > > Tuscany should provide a flag or mechanism to turn validation on/off. Tools > developed on top of tuscany may perform validation using tuscany's validation > framework. In that case, any user may not want validation being done during > runtime as it was already done using external tools. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2319) binding.ws throws NullPointerException
[ https://issues.apache.org/jira/browse/TUSCANY-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2319. - Resolution: Fixed Committed at r6616651. Thanks for the patch Ram. > binding.ws throws NullPointerException > -- > > Key: TUSCANY-2319 > URL: https://issues.apache.org/jira/browse/TUSCANY-2319 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Misc Binding Extensions >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2319.patch > > > In helloworld-ws-reference-jms sample, when the helloworldwsjms.composite is > modified to look like this: > http://helloworld#wsdl.interface(HelloWorld2)" /> > wsdlElement="http://helloworld#wsdl.binding(HelloWorldSoapJmsBinding2)" > > uri="jms:/queue.sample?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61619"/> > Here the wsdl.interface HelloWorld is replace with HelloWorld2 and the > wsdl.binding HelloWorldSoapJmsBinding is replaced with > HelloWorldSoapJmsBinding2. > Here a NullPointerException is thrown while running the sample, instead of > showing a meaningful message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2319) binding.ws throws NullPointerException
[ https://issues.apache.org/jira/browse/TUSCANY-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2319: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > binding.ws throws NullPointerException > -- > > Key: TUSCANY-2319 > URL: https://issues.apache.org/jira/browse/TUSCANY-2319 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Misc Binding Extensions >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2319.patch > > > In helloworld-ws-reference-jms sample, when the helloworldwsjms.composite is > modified to look like this: > http://helloworld#wsdl.interface(HelloWorld2)" /> > wsdlElement="http://helloworld#wsdl.binding(HelloWorldSoapJmsBinding2)" > > uri="jms:/queue.sample?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61619"/> > Here the wsdl.interface HelloWorld is replace with HelloWorld2 and the > wsdl.binding HelloWorldSoapJmsBinding is replaced with > HelloWorldSoapJmsBinding2. > Here a NullPointerException is thrown while running the sample, instead of > showing a meaningful message. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2352) Recusive composition binding overiding not working corectly.
Recusive composition binding overiding not working corectly. - Key: TUSCANY-2352 URL: https://issues.apache.org/jira/browse/TUSCANY-2352 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2 IBM JDK 5.0 Reporter: Simon Laws Fix For: Java-SCA-Next The following recursive composition (dervied from that in itest/recursive-ws) does not work as the builder cannot match the reference binding to a service binding. http://localhost:8085/OuterTargetServiceComponent"/> And PolicyInnerComposite I also doesn't work if you move the binding down to the inner composite service (TargetService) It does work if you move the binding down to the inner component service There is is code in EndpointBuilderImpl which replaces the outer endpoint target with the inner endpoint target. This seems suspect and requires further investigation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2352) Recusive composition binding overiding not working corectly.
[ https://issues.apache.org/jira/browse/TUSCANY-2352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2352: --- Assignee: Simon Laws > Recusive composition binding overiding not working corectly. > - > > Key: TUSCANY-2352 > URL: https://issues.apache.org/jira/browse/TUSCANY-2352 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2 IBM JDK 5.0 >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > The following recursive composition (dervied from that in itest/recursive-ws) > does not work as the builder cannot match the reference binding to a service > binding. > > > > > > > > > > > > uri="http://localhost:8085/OuterTargetServiceComponent"/> > > > And PolicyInnerComposite > > > > > > > I also doesn't work if you move the binding down to the inner composite > service (TargetService) > It does work if you move the binding down to the inner component service > There is is code in EndpointBuilderImpl which replaces the outer endpoint > target with the inner endpoint target. This seems suspect and requires > further investigation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2335) binding.ws wsa:EndpointReference not honored
[
https://issues.apache.org/jira/browse/TUSCANY-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-2335.
-
Resolution: Fixed
Fix Version/s: Java-SCA-Next
Fix committed at r659574. The problem with the test for wsdl.binding was fixed
under TUSCANY-2241
> binding.ws wsa:EndpointReference not honored
> -
>
> Key: TUSCANY-2335
> URL: https://issues.apache.org/jira/browse/TUSCANY-2335
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Misc Binding Extensions
>Affects Versions: Java-SCA-1.1
>Reporter: Lou Amodeo
> Fix For: Java-SCA-Next
>
>
> I see some issues with using the wsa:EndpointReferecne with wsdl.binding.
> 1) EndpointReferecneHelper does not write out the Endpoint reference
> information to the SCDL.
> The writer passed into the method is not used to write the endpoint
> information.
> public static void writeEndPointReference(Element element,
> XMLStreamWriter writer) {
> try {
> Source domSource = new DOMSource(element);
> StreamResult result = new StreamResult(new StringWriter());
> javax.xml.transform.Transformer transformer =
> TransformerFactory.newInstance().newTransformer();
> transformer.transform(domSource , result);
>
> } catch (TransformerException e) {
> throw new RuntimeException(e);
> }
> }
>
> 2) Small issue with the test on whether the wsdl.binding was specified with
> wsa:EndpointReference. The code checks for presence of
> wsdl.binding then throws exception. This should thow an exception if
> wsdl.binding is NOT found.
>while (reader.hasNext()) {
> int event = reader.next();
> switch (event) {
> case START_ELEMENT: {
> if
> (END_POINT_REFERENCE.equals(reader.getName().getLocalPart())) {
> if (wsdlElementIsBinding != null &&
> wsdlElementIsBinding) {
> throw new ContributionReadException(
> wsdlElement +
> " must use wsdl.binding when using wsa:EndpointReference");
> }
>
> wsBinding.setEndPointReference(EndPointReferenceHelper.readEndPointReference(reader));
> } else if
> (Constants.OPERATION_QNAME.equals(reader.getName())) {
> confOp = configuredOperationProcessor.read(reader);
> if (confOp != null) {
>
> ((OperationsConfigurator)wsBinding).getConfiguredOperations().add(confOp);
> }
> }
> }
> break;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2311) Second equivalently typed callback field not injected
[ https://issues.apache.org/jira/browse/TUSCANY-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2311. - Resolution: Fixed Committed at r659359. Thanks for the pacht Vamsi. Looks OK to me. I could be optimized a little I guess but I can't imagine that this situation is going to arise that often. As you have made and tested the fix I've committed as is. > Second equivalently typed callback field not injected > - > > Key: TUSCANY-2311 > URL: https://issues.apache.org/jira/browse/TUSCANY-2311 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Simon Laws > Attachments: TUSCANY-2311.patch > > > The Java CAA specification states on lines 670-671: > 670 If a single callback has a type that is compatible with multiple declared > callback fields, then all of them will > 671 be set. > The test > org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statefulMultiBidirectional() > demonstrates that a second annotated field with the same type is not > injected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2311) Second equivalently typed callback field not injected
[ https://issues.apache.org/jira/browse/TUSCANY-2311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2311: --- Assignee: Simon Laws > Second equivalently typed callback field not injected > - > > Key: TUSCANY-2311 > URL: https://issues.apache.org/jira/browse/TUSCANY-2311 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Simon Laws > Attachments: TUSCANY-2311.patch > > > The Java CAA specification states on lines 670-671: > 670 If a single callback has a type that is compatible with multiple declared > callback fields, then all of them will > 671 be set. > The test > org.apache.tuscany.sca.vtest.javaapi.conversation.callback.CallbackTestCase.statefulMultiBidirectional() > demonstrates that a second annotated field with the same type is not > injected. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2248) SOAP intents not being honored
[ https://issues.apache.org/jira/browse/TUSCANY-2248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2248. - Resolution: Fixed Committed at r659257. Thanks for the patch Vamsi > SOAP intents not being honored > > > Key: TUSCANY-2248 > URL: https://issues.apache.org/jira/browse/TUSCANY-2248 > Project: Tuscany > Issue Type: Bug >Affects Versions: Java-SCA-1.0 >Reporter: Lou Amodeo > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2248-2.patch, TUSCANY-2248.patch > > > Hi, It looks like there are a couple issues with the handling of the SOAP > version intents with the Web Services binding. The first one is the literal > used to identify the SOAP version and the second is the alrogitym used to > apply the SOAP intent. > 1) Tuscany is currently using soap. soap11 and soap12 for the literals to > identify the soap version. I believe these should be soap, soap.1_1, > soap.1_2 according to section 2.3.1 of WS Binding specification. > 2) During WSDL generation the soap.1_1 intent is not being honored. It > appears that the algorithm to determine which soap version to use is > incorrect. I believe it should be as follows: > I think this is the algorithym: >no requires= specifying a soap version or requires="soap" > - generate soap.1_1 and soap.1_2 port and binding > >requires = "soap.1_1" > > - generate soap.1_1 port and binding only >requires = "soap.1_.2" > - generate soap.1_2. port and binding only > I also see that an http port/binding is generated by Axis2 by default. > Since he intetns are based on soap version I would > think the http:address should not be generated. > binding="ns:HelloWorldServiceHttpBinding"> >location="http://localhost:8080/axis2/services/HelloWorldService"/> > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2329) itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2329. - Resolution: Fixed Checked in at 658706. Thanks Ram for the patch. I had a few of the tests fail so I need you to take a look. The asserts are currently commented out. impl.spring.UnableToResolveComponentTypeTestCase impl.java.ContributionResolveExceptionTestCase interfacejava.xml.ContributionResolveExceptionTestCase > itests for validation messages > -- > > Key: TUSCANY-2329 > URL: https://issues.apache.org/jira/browse/TUSCANY-2329 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Integration Tests >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2329-Part1.patch > > > itests for validation messages introduced through monitors (with > TUSCANY-2277) for various processors during read and resolve phase of the > composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2329) itests for validation messages
[ https://issues.apache.org/jira/browse/TUSCANY-2329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2329: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > itests for validation messages > -- > > Key: TUSCANY-2329 > URL: https://issues.apache.org/jira/browse/TUSCANY-2329 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Integration Tests >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2329-Part1.patch > > > itests for validation messages introduced through monitors (with > TUSCANY-2277) for various processors during read and resolve phase of the > composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2283) Conversation should end due to non-business exception
[ https://issues.apache.org/jira/browse/TUSCANY-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2283. - Resolution: Fixed Fix committed at r658275. I've enabled the vtest also. > Conversation should end due to non-business exception > - > > Key: TUSCANY-2283 > URL: https://issues.apache.org/jira/browse/TUSCANY-2283 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > The Java APIs and Annotations spec states: > 487 A conversation ends, and any state associated with the conversation > is freed up, when: > ... > 492 • Any non-business exception is thrown by a conversational operation > This is not happening as illustrated by the vtest: > > org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.LifetimeTestCase.lifetime11 > It is currently @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2277. - Resolution: Fixed Checked in at r657881. Thanks Ram > Standardization of registering msg with monitor > --- > > Key: TUSCANY-2277 > URL: https://issues.apache.org/jira/browse/TUSCANY-2277 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Assembly Model >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2277-Part1-New.patch, TUSCANY-2277-Part1.patch, > TUSCANY-2277-Part2-New.patch, TUSCANY-2277-Part2.patch, > TUSCANY-2277-Part3-New.patch, TUSCANY-2277-Part3.patch > > > Lokking at the monitors that are being hooked up with different parts of the > code, found that we have some inconsistency interms of raising warning & > errors. In some places we throw exceptions and in other places we raise a > warning. > > Here are some examples for the inconsistency... > > BaseConfigurationBuilderImpl.java > Here we raise only a warning for URISyntaxException, should we not throw an > exception too? > > BaseWireBuilderImpl.java > Here we throw exceptions for IncompatibleInterfaceContractException, don't > you think we also need to register this message in our monitor? > In the same class, we raise a warning message for the PolicyRelated > Exceptions, should we also throw an exception here? > > CompositeProcessor.java > There are instances where we throw new ContributionReadException, i believe > registering this msg with a monitor is also required as this is caused by > incorrect user input. > From Simon's comments on how we can go ahead with handling such instance, we > will fix the issue as discussed > http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2283) Conversation should end due to non-business exception
[ https://issues.apache.org/jira/browse/TUSCANY-2283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2283: --- Assignee: Simon Laws > Conversation should end due to non-business exception > - > > Key: TUSCANY-2283 > URL: https://issues.apache.org/jira/browse/TUSCANY-2283 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > The Java APIs and Annotations spec states: > 487 A conversation ends, and any state associated with the conversation > is freed up, when: > ... > 492 • Any non-business exception is thrown by a conversational operation > This is not happening as illustrated by the vtest: > > org.apache.tuscany.sca.vtest.javaapi.conversation.lifetime.LifetimeTestCase.lifetime11 > It is currently @Ignore(d) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-2092. --- Resolution: Fixed Thanks for the patch Ram. Committed at 657093 > ConcurrentModificationException in ExtensibleContributionListener > - > > Key: TUSCANY-2092 > URL: https://issues.apache.org/jira/browse/TUSCANY-2092 > Project: Tuscany > Issue Type: Bug >Reporter: Greg Dritschler >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: JIRA-2092.patch, TUSCANY-2092.patch > > > java.util.ConcurrentModificationException > at java.util.AbstractList$SimpleListIterator.next(Unknown Source) > at > org.apache.tuscany.sca.contribution.service.ExtensibleContributionListener.contributionAdded(ExtensibleContributionListener.java:40) > at > org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:389) > at > org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:202) > The problem occurs if two threads try to add a contribution simultaneously. > DefaultContributionListenerExtensionPoint does not synchronize the list of > listeners. In particular loadListeners does not prevent multiple threads > from trying to load the list of listeners. One thread completes first while > the other is still loading. This leads to the exception shown above when a > thread tries to iterate the listener list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2092: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > ConcurrentModificationException in ExtensibleContributionListener > - > > Key: TUSCANY-2092 > URL: https://issues.apache.org/jira/browse/TUSCANY-2092 > Project: Tuscany > Issue Type: Bug >Reporter: Greg Dritschler >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: JIRA-2092.patch, TUSCANY-2092.patch > > > java.util.ConcurrentModificationException > at java.util.AbstractList$SimpleListIterator.next(Unknown Source) > at > org.apache.tuscany.sca.contribution.service.ExtensibleContributionListener.contributionAdded(ExtensibleContributionListener.java:40) > at > org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:389) > at > org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:202) > The problem occurs if two threads try to add a contribution simultaneously. > DefaultContributionListenerExtensionPoint does not synchronize the list of > listeners. In particular loadListeners does not prevent multiple threads > from trying to load the list of listeners. One thread completes first while > the other is still loading. This leads to the exception shown above when a > thread tries to iterate the listener list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2277) Standardization of registering msg with monitor
[
https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597473#action_12597473
]
Simon Laws commented on TUSCANY-2277:
-
Hi Ram
Was just trying to apply these patches and am having a few problems. What tool
did you use to generate them? I'm guessing Msftedit from the header. Can you
regenerate them using a diff tool. Let me know if you need some help.
The issues I'm having are
- has a strange Msft header (I can libe with this as I can remove it nmanually)
- the file dirs are absolute (I can live with this as I can go in and edit)
- there are some escaped charaters in there, e.g. \tab, \par, \{, \} which mess
it up. (I can't get round this as fixing manually messes up the formatting and
the patch tool can't then match the patch against the original code)
Thanks
Simon
> Standardization of registering msg with monitor
> ---
>
> Key: TUSCANY-2277
> URL: https://issues.apache.org/jira/browse/TUSCANY-2277
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Assembly Model
>Affects Versions: Java-SCA-Next
> Environment: Windows XP
>Reporter: Ramkumar Ramalingam
>Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
> Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch,
> TUSCANY-2277-Part3.patch
>
>
> Lokking at the monitors that are being hooked up with different parts of the
> code, found that we have some inconsistency interms of raising warning &
> errors. In some places we throw exceptions and in other places we raise a
> warning.
>
> Here are some examples for the inconsistency...
>
> BaseConfigurationBuilderImpl.java
> Here we raise only a warning for URISyntaxException, should we not throw an
> exception too?
>
> BaseWireBuilderImpl.java
> Here we throw exceptions for IncompatibleInterfaceContractException, don't
> you think we also need to register this message in our monitor?
> In the same class, we raise a warning message for the PolicyRelated
> Exceptions, should we also throw an exception here?
>
> CompositeProcessor.java
> There are instances where we throw new ContributionReadException, i believe
> registering this msg with a monitor is also required as this is caused by
> incorrect user input.
> From Simon's comments on how we can go ahead with handling such instance, we
> will fix the issue as discussed
> http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2277) Standardization of registering msg with monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2277: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > Standardization of registering msg with monitor > --- > > Key: TUSCANY-2277 > URL: https://issues.apache.org/jira/browse/TUSCANY-2277 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Assembly Model >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2277-Part1.patch, TUSCANY-2277-Part2.patch, > TUSCANY-2277-Part3.patch > > > Lokking at the monitors that are being hooked up with different parts of the > code, found that we have some inconsistency interms of raising warning & > errors. In some places we throw exceptions and in other places we raise a > warning. > > Here are some examples for the inconsistency... > > BaseConfigurationBuilderImpl.java > Here we raise only a warning for URISyntaxException, should we not throw an > exception too? > > BaseWireBuilderImpl.java > Here we throw exceptions for IncompatibleInterfaceContractException, don't > you think we also need to register this message in our monitor? > In the same class, we raise a warning message for the PolicyRelated > Exceptions, should we also throw an exception here? > > CompositeProcessor.java > There are instances where we throw new ContributionReadException, i believe > registering this msg with a monitor is also required as this is caused by > incorrect user input. > From Simon's comments on how we can go ahead with handling such instance, we > will fix the issue as discussed > http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30994.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-1534) Refactor wireable binding support to make it applicable to all bindings
[ https://issues.apache.org/jira/browse/TUSCANY-1534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-1534. --- Resolution: Fixed Done as part of the latest round of reference/binding/endpoint changes. > Refactor wireable binding support to make it applicable to all bindings > --- > > Key: TUSCANY-1534 > URL: https://issues.apache.org/jira/browse/TUSCANY-1534 > Project: Tuscany > Issue Type: Improvement > Components: Java SCA Core Runtime > Environment: All >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > Extracted from the now closed > https://issues.apache.org/jira/browse/TUSCANY-1526 > There is consensus that all bindings are potentially wireable and that the > current WireableBinding interface should either be removed or applied to all > bindings. Hence the following should be a valid configuration. > > > > > > > wsdlElement="http://calculator#wsdl.binding(MultiplySoapBinding)"/> > > > > > > > > wsdlElement="http://calculator#wsdl.binding(MultiplySoapBinding)"/> > > > There is further discussion in the mail thread associated with TUSCANY-1526 > (http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg21448.html) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2220) WSDL representations of binding.ws generated incorrectly.
[ https://issues.apache.org/jira/browse/TUSCANY-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws updated TUSCANY-2220: Fix Version/s: (was: Java-SCA-1.2) Java-SCA-Next Move fix to SCA Next > WSDL representations of binding.ws generated incorrectly. > - > > Key: TUSCANY-2220 > URL: https://issues.apache.org/jira/browse/TUSCANY-2220 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Embedded Runtime >Affects Versions: Java-SCA-1.2 > Environment: Websphere 6.1.0.14 on AIX, jdk150_10 > Jetty on Windows XP x86, jdk150_10 > Websphere on Windows XP x86, jdk150_10 > Tomcat on Windows XP x86. jdk150_10 >Reporter: Dave Sowerby > Fix For: Java-SCA-Next > > > WSDL representations of binding.ws generated incorrectly. > I'm currently facing issues when attmepting to utilise the wsdl > generated by a service exposed using binding.ws, when I use wsdl2java > with this wsdl I get the following exception: > IWAB0399E Error in generating Java from WSDL: java.io.IOException: > Emitter failure. Cannot find endpoint address in port > ServiceRequestPortType__SOAPHTTPPort in service > ServiceRequestPortType__ServiceLocator >java.io.IOException: Emitter failure. Cannot find endpoint > address in port ServiceRequestPortType__SOAPHTTPPort in service > ServiceRequestPortType__ServiceLocator >at > org.apache.axis.wsdl.toJava.JavaServiceImplWriter.writeFileBody(JavaServiceImplWriter.java:189) >at org.apache.axis.wsdl.toJava.JavaWriter.generate(JavaWriter.java:127) >at > org.apache.axis.wsdl.toJava.JavaServiceWriter.generate(JavaServiceWriter.java:112) >at > org.apache.axis.wsdl.toJava.JavaGeneratorFactory$Writers.generate(JavaGeneratorFactory.java:421) >at org.apache.axis.wsdl.gen.Parser.generate(Parser.java:476) >at org.apache.axis.wsdl.gen.Parser.access$000(Parser.java:45) >at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:362) >at java.lang.Thread.run(Unknown Source) > I've diffed a previously functioning wsdl against the currently (RC3a) > generated wsdl file, the difference causing this problem appears to be > the additional lines of: > > binding="ns2:ServiceRequestPortType__SOAPBinding"> > > > Which without an address is causing wsdl2java to fail. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2251) Problem with 1.2 RC4 with simple JavaBean
[ https://issues.apache.org/jira/browse/TUSCANY-2251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws updated TUSCANY-2251: Fix Version/s: (was: Java-SCA-1.2) Java-SCA-Next move fix to SCA Next > Problem with 1.2 RC4 with simple JavaBean > - > > Key: TUSCANY-2251 > URL: https://issues.apache.org/jira/browse/TUSCANY-2251 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Data Binding Runtime >Affects Versions: Java-SCA-1.2 > Environment: Eclipse 3.3, Tuscany SCA 1.2 - RC4 >Reporter: Nishant Joshi > Fix For: Java-SCA-Next > > Attachments: generatedClientCode.zip, SimpleBeanProblem.zip > > > Hi there, > I have one sample which was perfectly working with 1.0 incubating... when i > have tried same with 1.2 RC4 all the data come from client was null for all > the values for a simple bean. > Please note that I m creating Client on Eclipse 3.3... using WebService > client generation facility of eclipse... > I m attaching detail for more detail... > When tried same with SCA client it was giving me perfect result... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TUSCANY-2280) No data transformation for fault types
[ https://issues.apache.org/jira/browse/TUSCANY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws updated TUSCANY-2280: Fix Version/s: (was: Java-SCA-1.2) (was: Java-SCA-1.1) Java-SCA-Next Move fix to SCA Next > No data transformation for fault types > -- > > Key: TUSCANY-2280 > URL: https://issues.apache.org/jira/browse/TUSCANY-2280 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Data Binding Runtime >Affects Versions: Java-SCA-1.1, Java-SCA-1.2 >Reporter: Cezary Wisniewski > Fix For: Java-SCA-Next > > > DataTransformationInterceptor is not added to the InvocationChain when method > has no parameters and no return type e.g. > void someMethod() throws MyException > DataTransformationInterceptor should be added to the chain because the > exception has to be transformed. DataTransformationInterceptor is added to > the chain and exception is transformed when the method has at least one > parameter or return type e.g. > MyStruct someMethod() throws MyExcpetions > or > void someMethod(MyStruct param) throws MyException > The reason for such behavior is that DataBindingRuntimeWireProcessor only > takes care of parameters and return types and ignores fault types (see > DataBindingRuntimeWireProcessor.isTransformationRequired(Operation, Operation) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2272) @Init and @Destroy annotations on a non-public method
[ https://issues.apache.org/jira/browse/TUSCANY-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2272. - Resolution: Fixed Hi Vamsi, the patch looks ok to me. I got a clean build. I also temporarily modified one of the conversational tests to make sure I get the error under normal conditions. It worked. We could do with a test that does this so that the JavaClassIntrospector gets run also. I've checked the code in at r652566. Thanks > @Init and @Destroy annotations on a non-public method > -- > > Key: TUSCANY-2272 > URL: https://issues.apache.org/jira/browse/TUSCANY-2272 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Java Implementation Extension >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2272.patch > > > Java Common Annotations and APIs Specification v1.00 - Sec 1.2.4 - Lines 265 > to 269: > 265 An implementation type may allow component implementations to declare > lifecycle methods that are > 266 called when an implementation is instantiated or the scope is expired. > @Init denotes the method to be > 267 called upon first use of an instance during the lifetime of the scope > (except for composite scoped > 268 implementation marked to eagerly initialize, see Section XXX). @Destroy > specifies the method to be called > 269 when the scope ends. *Note that only public, no argument methods may be > annotated as lifecycle methods.* > Currently @Init and @Destroy annotations on a protected method do not result > in an error or a warning whereas these annotations on a private method result > in a warning. Should it result in an error in both cases? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2272) @Init and @Destroy annotations on a non-public method
[ https://issues.apache.org/jira/browse/TUSCANY-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2272: --- Assignee: Simon Laws (was: Vamsavardhana Reddy) > @Init and @Destroy annotations on a non-public method > -- > > Key: TUSCANY-2272 > URL: https://issues.apache.org/jira/browse/TUSCANY-2272 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Java Implementation Extension >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2272.patch > > > Java Common Annotations and APIs Specification v1.00 - Sec 1.2.4 - Lines 265 > to 269: > 265 An implementation type may allow component implementations to declare > lifecycle methods that are > 266 called when an implementation is instantiated or the scope is expired. > @Init denotes the method to be > 267 called upon first use of an instance during the lifetime of the scope > (except for composite scoped > 268 implementation marked to eagerly initialize, see Section XXX). @Destroy > specifies the method to be called > 269 when the scope ends. *Note that only public, no argument methods may be > annotated as lifecycle methods.* > Currently @Init and @Destroy annotations on a protected method do not result > in an error or a warning whereas these annotations on a private method result > in a warning. Should it result in an error in both cases? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2273) Return value of a method with @Init and @Destroy annotations must be a void
[ https://issues.apache.org/jira/browse/TUSCANY-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2273. - Resolution: Fixed Thanks for the patch Vamsi. Committed at r652543 > Return value of a method with @Init and @Destroy annotations must be a void > --- > > Key: TUSCANY-2273 > URL: https://issues.apache.org/jira/browse/TUSCANY-2273 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Java Implementation Extension, Java SCA > Verification Tests >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2273.patch > > > Java Common Annotations and APIs v1.00: > Sec 1.8.8 @Destroy - Lines 1226 and 1227: > 1226 The method must have a void return value and > 1227 no arguments. > Sec 1.8.11 @Init - Lines 1291 and 1292: > 1291 The method must have a void return value and no > 1292 arguments. > Currently the code checks only for no arguments but not the return type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2271) Java runtime should not inject property into an unannotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2271. - Resolution: Fixed Thanks for the patches Vamsi. Committed at r652542 > Java runtime should not inject property into an unannotated non-public field > > > Key: TUSCANY-2271 > URL: https://issues.apache.org/jira/browse/TUSCANY-2271 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime, Java SCA Verification Tests >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2271-vtest.patch, TUSCANY-2271.patch > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2273) Return value of a method with @Init and @Destroy annotations must be a void
[ https://issues.apache.org/jira/browse/TUSCANY-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2273: --- Assignee: Simon Laws (was: Vamsavardhana Reddy) > Return value of a method with @Init and @Destroy annotations must be a void > --- > > Key: TUSCANY-2273 > URL: https://issues.apache.org/jira/browse/TUSCANY-2273 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Java Implementation Extension, Java SCA > Verification Tests >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2273.patch > > > Java Common Annotations and APIs v1.00: > Sec 1.8.8 @Destroy - Lines 1226 and 1227: > 1226 The method must have a void return value and > 1227 no arguments. > Sec 1.8.11 @Init - Lines 1291 and 1292: > 1291 The method must have a void return value and no > 1292 arguments. > Currently the code checks only for no arguments but not the return type. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2271) Java runtime should not inject property into an unannotated non-public field
[ https://issues.apache.org/jira/browse/TUSCANY-2271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2271: --- Assignee: Simon Laws (was: Vamsavardhana Reddy) > Java runtime should not inject property into an unannotated non-public field > > > Key: TUSCANY-2271 > URL: https://issues.apache.org/jira/browse/TUSCANY-2271 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime, Java SCA Verification Tests >Affects Versions: Java-SCA-1.2 >Reporter: Vamsavardhana Reddy >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2271.patch > > > Java Common Annotations and APIs v1.0 - Sec 1.8.13: > 1349 Properties may also be injected via public setter methods even when the > @Property annotation is not > 1350 present. However, the @Property annotation must be used in order to > inject a property onto a non-public > 1351 field. In the case where there is no @Property annotation, the name of > the property is the same as the > 1352 name of the field or setter. > Currently the properties are injected into unannotated protected fields too. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2210) Java runtime should inject property to field with common name in absence of @Property
[ https://issues.apache.org/jira/browse/TUSCANY-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2210. - Resolution: Fixed Fix Version/s: Java-SCA-Next Committed at r652501 > Java runtime should inject property to field with common name in absence of > @Property > - > > Key: TUSCANY-2210 > URL: https://issues.apache.org/jira/browse/TUSCANY-2210 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Reporter: Gilbert Kwan >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2210.patch > > > The Java Annotations&APIs specification Lines 1349 to 1352: > Properties may also be injected via public setter methods even when the > "@Property" annotation is not present. However, the @Property annotation must > be used in order to inject a property onto a non-public field. In the case > where there is no "@Property" annotation, the name of the property is the > same as the name of the field or setter. > The vTest to demonstrate this issue will be posted later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2210) Java runtime should inject property to field with common name in absence of @Property
[ https://issues.apache.org/jira/browse/TUSCANY-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2210: --- Assignee: Simon Laws > Java runtime should inject property to field with common name in absence of > @Property > - > > Key: TUSCANY-2210 > URL: https://issues.apache.org/jira/browse/TUSCANY-2210 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Reporter: Gilbert Kwan >Assignee: Simon Laws >Priority: Minor > Attachments: TUSCANY-2210.patch > > > The Java Annotations&APIs specification Lines 1349 to 1352: > Properties may also be injected via public setter methods even when the > "@Property" annotation is not present. However, the @Property annotation must > be used in order to inject a property onto a non-public field. In the case > where there is no "@Property" annotation, the name of the property is the > same as the name of the field or setter. > The vTest to demonstrate this issue will be posted later. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2052) A Composite without a targetNamespace is not properly started in a contribution
[ https://issues.apache.org/jira/browse/TUSCANY-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2052: --- Assignee: Simon Laws (was: Luciano Resende) > A Composite without a targetNamespace is not properly started in a > contribution > --- > > Key: TUSCANY-2052 > URL: https://issues.apache.org/jira/browse/TUSCANY-2052 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.0 > Environment: All >Reporter: Hasan Muhammad >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > If the composite does not have a targetNamespace, then the composite QName in > the sca-contribution.xml file would just be the localname. In this case, when > we add the contribution and start the deployables, it seems they are not > properly being started, since none of the service can be found through > lookup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2262) Flow XSD schema validation errors through the monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2262. - Resolution: Fixed Checked in at r651657. Thanks for the patch Ram > Flow XSD schema validation errors through the monitor > - > > Key: TUSCANY-2262 > URL: https://issues.apache.org/jira/browse/TUSCANY-2262 > Project: Tuscany > Issue Type: New Feature > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2, JDK1.5 >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2262.txt > > > The Monitor to date is only integrated into the builders. There are other > places that raise validation warnings, i.e. warning to the user that there is > something wrong with the input that they have provided. The first one to look > at would be the XSD schema validation. This happens within the contribution > processing so we need to. > Make the monitor available to the part of the processing > Get warnings from the schema processor > Create a contribution resource bundle to hold any messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2052) A Composite without a targetNamespace is not properly started in a contribution
[ https://issues.apache.org/jira/browse/TUSCANY-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2052. - Resolution: Fixed Change checked in at r651657 > A Composite without a targetNamespace is not properly started in a > contribution > --- > > Key: TUSCANY-2052 > URL: https://issues.apache.org/jira/browse/TUSCANY-2052 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.0 > Environment: All >Reporter: Hasan Muhammad >Assignee: Simon Laws > Fix For: Java-SCA-Next > > > If the composite does not have a targetNamespace, then the composite QName in > the sca-contribution.xml file would just be the localname. In this case, when > we add the contribution and start the deployables, it seems they are not > properly being started, since none of the service can be found through > lookup. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2262) Flow XSD schema validation errors through the monitor
[ https://issues.apache.org/jira/browse/TUSCANY-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2262: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > Flow XSD schema validation errors through the monitor > - > > Key: TUSCANY-2262 > URL: https://issues.apache.org/jira/browse/TUSCANY-2262 > Project: Tuscany > Issue Type: New Feature > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2, JDK1.5 >Reporter: Simon Laws >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2262.txt > > > The Monitor to date is only integrated into the builders. There are other > places that raise validation warnings, i.e. warning to the user that there is > something wrong with the input that they have provided. The first one to look > at would be the XSD schema validation. This happens within the contribution > processing so we need to. > Make the monitor available to the part of the processing > Get warnings from the schema processor > Create a contribution resource bundle to hold any messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2145) SCADomain.getService () should throw exception when bogus component name is passed
[
https://issues.apache.org/jira/browse/TUSCANY-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-2145.
---
Resolution: Later
I'm going to close this a working as designed, i.e. to take account of
unresolved references. However new work is starting on a new spec compliant API
and I expect this subject will be revisited there.
> SCADomain.getService () should throw exception when bogus component name is
> passed
> --
>
> Key: TUSCANY-2145
> URL: https://issues.apache.org/jira/browse/TUSCANY-2145
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime
>Affects Versions: Java-SCA-Next
>Reporter: Kevin Williams
>Priority: Minor
>
> SCADomain.getService() currently returns a proxy even when the component name
> passed is not in the domain.
> I have created a test (currently "ignored") in the new vTest suite to
> demonstrate.
> @Test
> @Ignore
> public void bogusComponentName() throws Exception {
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2269) Import package could not be resolved in CalculateBindingURITestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2269. - Resolution: Fixed Checked in at r651490. Thanks for the patch Ram. > Import package could not be resolved in CalculateBindingURITestCase > --- > > Key: TUSCANY-2269 > URL: https://issues.apache.org/jira/browse/TUSCANY-2269 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2269.patch > > > The import com.sun.org.apache.xerces.internal.impl.xs.opti.DefaultNode could > not be resolved in > org.apache.tuscany.sca.implementation.node.builder.impl.CalculateBindingURITestCase. > Solution: Need to remove the import statement as this class is not used > anywhere in the code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2269) Import package could not be resolved in CalculateBindingURITestCase
[ https://issues.apache.org/jira/browse/TUSCANY-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2269: --- Assignee: Simon Laws (was: Ramkumar Ramalingam) > Import package could not be resolved in CalculateBindingURITestCase > --- > > Key: TUSCANY-2269 > URL: https://issues.apache.org/jira/browse/TUSCANY-2269 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Verification Tests >Affects Versions: Java-SCA-Next > Environment: Windows XP >Reporter: Ramkumar Ramalingam >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2269.patch > > > The import com.sun.org.apache.xerces.internal.impl.xs.opti.DefaultNode could > not be resolved in > org.apache.tuscany.sca.implementation.node.builder.impl.CalculateBindingURITestCase. > Solution: Need to remove the import statement as this class is not used > anywhere in the code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2267) Raise a warning if both reference target and binding URI are specified
Raise a warning if both reference target and binding URI are specified -- Key: TUSCANY-2267 URL: https://issues.apache.org/jira/browse/TUSCANY-2267 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: All Reporter: Simon Laws Priority: Minor Fix For: Java-SCA-Next The assembly spec says around line 1380 that " A reference must not mix the use of endpoints specified via binding elements with target endpoints specified via the target attribute". We should raise a warning if this is detected in a composite. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2262) Flow XSD schema validation errors through the monitor
Flow XSD schema validation errors through the monitor - Key: TUSCANY-2262 URL: https://issues.apache.org/jira/browse/TUSCANY-2262 Project: Tuscany Issue Type: New Feature Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, JDK1.5 Reporter: Simon Laws Fix For: Java-SCA-Next The Monitor to date is only integrated into the builders. There are other places that raise validation warnings, i.e. warning to the user that there is something wrong with the input that they have provided. The first one to look at would be the XSD schema validation. This happens within the contribution processing so we need to. Make the monitor available to the part of the processing Get warnings from the schema processor Create a contribution resource bundle to hold any messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2261) Default monitor failure if bundle for local not found
Default monitor failure if bundle for local not found - Key: TUSCANY-2261 URL: https://issues.apache.org/jira/browse/TUSCANY-2261 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Fix For: Java-SCA-Next Would like the default logging monitor to use a default resource bundle if it can't find the one it requires for the locale, i.e. it would be good if it didn't fail trying to write out a warning for people where we haven't translated the messages. This may be as easy as just providing a default bundle with no locale or may be a few code changes. haven't had chance to look at it yet. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2260) Validation Testcases Part -2
[ https://issues.apache.org/jira/browse/TUSCANY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2260. - Resolution: Fixed Fix Version/s: Java-SCA-Next Thanks for the patch Hasan. Committed at r650810 > Validation Testcases Part -2 > > > Key: TUSCANY-2260 > URL: https://issues.apache.org/jira/browse/TUSCANY-2260 > Project: Tuscany > Issue Type: Test > Components: Java SCA Integration Tests > Environment: All >Reporter: Hasan Muhammad >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: validation2.patch > > > Hi Simon, > I have attached a patch for a second set of validation test cases. With this, > there should be a total of 22 testcases running. Please review and commit. > Let me know if there is any problem with the patch > Hasan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2260) Validation Testcases Part -2
[ https://issues.apache.org/jira/browse/TUSCANY-2260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2260: --- Assignee: Simon Laws > Validation Testcases Part -2 > > > Key: TUSCANY-2260 > URL: https://issues.apache.org/jira/browse/TUSCANY-2260 > Project: Tuscany > Issue Type: Test > Components: Java SCA Integration Tests > Environment: All >Reporter: Hasan Muhammad >Assignee: Simon Laws >Priority: Minor > Attachments: validation2.patch > > > Hi Simon, > I have attached a patch for a second set of validation test cases. With this, > there should be a total of 22 testcases running. Please review and commit. > Let me know if there is any problem with the patch > Hasan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2255) Validation Testcases Part -1
[ https://issues.apache.org/jira/browse/TUSCANY-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2255. - Resolution: Fixed Thanks Hasan. I've commited the patch at r650505. I made a few changes to remove the unused code that got copied over from the original test. But apart from that looks good. > Validation Testcases Part -1 > > > Key: TUSCANY-2255 > URL: https://issues.apache.org/jira/browse/TUSCANY-2255 > Project: Tuscany > Issue Type: Test > Components: Java SCA Integration Tests > Environment: All >Reporter: Hasan Muhammad >Assignee: Simon Laws >Priority: Minor > Attachments: validation1.patch > > > Hi Simon, > Submitting the first round of validation Itest cases. Please review and > commit if the patch is ok. Otherwise let me know and i will just create a > patch for the diff files and create a zip for the new files. > Hasan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2255) Validation Testcases Part -1
[ https://issues.apache.org/jira/browse/TUSCANY-2255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2255: --- Assignee: Simon Laws > Validation Testcases Part -1 > > > Key: TUSCANY-2255 > URL: https://issues.apache.org/jira/browse/TUSCANY-2255 > Project: Tuscany > Issue Type: Test > Components: Java SCA Integration Tests > Environment: All >Reporter: Hasan Muhammad >Assignee: Simon Laws >Priority: Minor > Attachments: validation1.patch > > > Hi Simon, > Submitting the first round of validation Itest cases. Please review and > commit if the patch is ok. Otherwise let me know and i will just create a > patch for the diff files and create a zip for the new files. > Hasan -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TUSCANY-2254) Test failures in itest/osgi-tuscany (monitor missing)
[ https://issues.apache.org/jira/browse/TUSCANY-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2254. - Resolution: Fixed Thanks Graham for the patch. Applied at r650438 > Test failures in itest/osgi-tuscany (monitor missing) > - > > Key: TUSCANY-2254 > URL: https://issues.apache.org/jira/browse/TUSCANY-2254 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next > Environment: Found on Windows, but affects all. >Reporter: Graham Charters >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: osgi-tuscany-patch.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > The newly added monitor modules, tuscany-monitor and tuscany-monitor-logging > ,cause itest/osgi-tuscany to fail because they have not been added to the > dependencies for the tuscany osgi bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (TUSCANY-2254) Test failures in itest/osgi-tuscany (monitor missing)
[ https://issues.apache.org/jira/browse/TUSCANY-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2254: --- Assignee: Simon Laws > Test failures in itest/osgi-tuscany (monitor missing) > - > > Key: TUSCANY-2254 > URL: https://issues.apache.org/jira/browse/TUSCANY-2254 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next > Environment: Found on Windows, but affects all. >Reporter: Graham Charters >Assignee: Simon Laws >Priority: Minor > Fix For: Java-SCA-Next > > Attachments: osgi-tuscany-patch.patch > > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > The newly added monitor modules, tuscany-monitor and tuscany-monitor-logging > ,cause itest/osgi-tuscany to fail because they have not been added to the > dependencies for the tuscany osgi bundles. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2242) Incorrent port name in wsdlElement leads to NPE
Incorrent port name in wsdlElement leads to NPE --- Key: TUSCANY-2242 URL: https://issues.apache.org/jira/browse/TUSCANY-2242 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: WinXP SP2, IBM JDK 1.5 Reporter: Simon Laws Priority: Minor Fix For: Java-SCA-Next Can be reproduced by changing the SCDL in sample/helloworld-ws-reference to the following http://www.osoa.org/xmlns/sca/1.0"; targetNamespace="http://helloworld"; xmlns:hw="http://helloworld"; name="helloworldwsclient"> http://helloworld#wsdl.port(HelloWorldService/NonExistentPort)"/> http://helloworld#wsdl.port(HelloWorldService/HelloWorldSoapPort)"/> Notice the "NonExistentPort" port name. Running the nit test for ht sample leads to Caused by: java.lang.NullPointerException at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:292) at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProcessor.resolve(WebServiceBindingProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.DefaultStAXArtifactProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifactProcessorExtensionPoint.java:252) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.resolveContracts(BaseAssemblyProcessor.java:362) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:845) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolve(CompositeProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXArtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:139) at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcessor.resolve(CompositeDocumentProcessor.java:1) at org.apache.tuscany.sca.contribution.processor.ExtensibleURLArtifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processResolvePhase(ContributionServiceImpl.java:485) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:369) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:165) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:291) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:171) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:113) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:243) ... 22 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2109) Conflicts between component reference interface and promoted composite reference interface are not detected
[ https://issues.apache.org/jira/browse/TUSCANY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590031#action_12590031 ] Simon Laws commented on TUSCANY-2109: - I've commited Wang Feng's patch at r649093. Thanks Wang Feng. This is the first part of the fix for this JIRA and initiates the comparison of promoter and promoted interfaces. We need to add namespace compatibility testing to InterfaceContractMapperImpl.checkCompatibility() to complete this JIRA. There is discussion ongoing on the mail list. > Conflicts between component reference interface and promoted composite > reference interface are not detected > > > Key: TUSCANY-2109 > URL: https://issues.apache.org/jira/browse/TUSCANY-2109 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: All >Reporter: Simon Nash >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: jira2109.patch, jira2109.zip > > > See TUSCANY-2033 for the background to this problem. > When a component reference defined with (either explicitly > or implicitly by introspection) is promoted to a composite reference defined > with , and there is a namespace conflict between the > component reference's and the composite reference's > . this conflict should be diagnosed as an error because it > violates the spec rule that an interface specified on a composite reference > must be a compatible superset of the interface of the promoted component > reference. In this case, the composite interface is incompatible with the > component reference because it has a different namespace. > There is code in CompositeWireBuilderImpl.connectCompositeReferences() to > handle connections between composite references and promoted compoennt > references. The only interface processing performed in this method is to copy > the component reference's interface contract to the composite reference's > interface contract if the composite reference does not have an interface > contract. Code should be added here to check for conflicts between the > composite reference's interface and the component reference's interface if > both interfaces are specified. > Similar code should be added to > CompositeWireBuilderImpl.connectCompositeServices() to check that the > composite service interface is a compatible subset of the component service > interface as required by the spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-1937) Duplicate binding name not flagged as error
[ https://issues.apache.org/jira/browse/TUSCANY-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-1937. - Resolution: Fixed Fix Version/s: (was: Java-SCA-Next) Java-SCA-1.2 As part of the new URI calculation code in CompositeConfigurationBuildler there is code that raises a validation warning if two bindings appear with the same name. See CompositeConfigurationBuilderImpl.constructBindingName() > Duplicate binding name not flagged as error > --- > > Key: TUSCANY-1937 > URL: https://issues.apache.org/jira/browse/TUSCANY-1937 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.0.1 >Reporter: Simon Nash >Assignee: Simon Laws > Fix For: Java-SCA-1.2 > > > If multiple bindings on a service or reference have the same name (explicit > or defaulted), Tuscany should raise an error because this is illegal > according to the SCA Assembly specification. Both of the following > modifications of myapp.scdl in samples/callback-ws-client should be illegal, > but currently they are both accepted: > - - - - - - - - example 1 - - - - - - - - > http://www.osoa.org/xmlns/sca/1.0"; > targetNamespace="http://myapp"; > name="myapp"> > > > > callbackInterface="myserver.MyServiceCallback" /> > uri="http://localhost:8086/MyServiceComponent"; /> > > > > > > > > - - - - - - - - example 2 - - - - - - - - > http://www.osoa.org/xmlns/sca/1.0"; > targetNamespace="http://myapp"; > name="myapp"> > > > > callbackInterface="myserver.MyServiceCallback" /> > http://localhost:8086/MyServiceComponent"; /> > > > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589572#action_12589572 ] Simon Laws commented on TUSCANY-2230: - Hi Yee-Kang I'm looking at applying this patch but having a little trouble. It seems that the patch file includes duplicate entries which results with undesirable results at my end (some files are twice as long as they should be). For example, if you open the patch you see that "requestcontext/pom.xml" appears twice. Can you try regenerating to remove these duplications? This seems to be a feature for the patches for 2231, 2232, 2233 also. > Test Cases for RequestContext API > - > > Key: TUSCANY-2230 > URL: https://issues.apache.org/jira/browse/TUSCANY-2230 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Simon Laws > Attachments: RequestContextJIRA2230.patch > > > Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2230) Test Cases for RequestContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2230: --- Assignee: Simon Laws > Test Cases for RequestContext API > - > > Key: TUSCANY-2230 > URL: https://issues.apache.org/jira/browse/TUSCANY-2230 > Project: Tuscany > Issue Type: Test > Components: Java SCA Verification Tests >Reporter: Yee-Kang Chang >Assignee: Simon Laws > Attachments: RequestContextJIRA2230.patch > > > Test Cases for RequestContext's vtest. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-2197) Conversations with OSGi services expire immediately
[ https://issues.apache.org/jira/browse/TUSCANY-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2197. - Resolution: Fixed Hi Jurgen. I'm marking this as resolved as Rajini applied the patch. > Conversations with OSGi services expire immediately > --- > > Key: TUSCANY-2197 > URL: https://issues.apache.org/jira/browse/TUSCANY-2197 > Project: Tuscany > Issue Type: Bug > Components: Java SCA OSGi Integration >Affects Versions: Java-SCA-1.2 > Environment: Windows XP, Eclipse 3.3.2 >Reporter: Jürgen Schumacher > Attachments: tuscany-implosgi-osgiannotation.patch > > > This occurred with current revision from sca-java-1.2 branch. > I use the Tuscany OSGi bundles created by itests/osgi-tuscany in Eclipse > Equinox, the SCA domain is started in a BundleActivator of my test projects. > When I use implementation.osgi for a conversational service, the first method > call after the init method throws a org.osoa.sca.ConversationEndedException: > Conversation 44c36d6c-68af-4ba9-a9ba-354ccc5dd9d0 has expired. I debugged > this and it seems that is caused by > org.apache.tuscany.sca.implementation.osgi.context.OSGiAnnotations, which > uses Long.MAX_VALUE as the default values for maxAge and maxIdleTime which in > turn causes an overflow in the initializeConversationAttributes() of > org.apache.tuscany.sca.core.conversation.ExtendedConversationImpl. This > results in a negative expirationTime which is of course always smaller than > the current time. When I change the default values to -1 (as in > org.apache.tuscany.sca.implementation.java.impl.JavaImplementationImpl), it > works. See attached patch for modules/implementation-osgi. I'm not sure if > this is the best or correct solution, but it may be a hint to someone with > more knowledge about this code. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Resolved: (TUSCANY-2191) A @Service annotation with no attributes causes exception
[ https://issues.apache.org/jira/browse/TUSCANY-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws resolved TUSCANY-2191. - Resolution: Fixed Patch applied at revision 648192. Thanks Vamsi. > A @Service annotation with no attributes causes exception > - > > Key: TUSCANY-2191 > URL: https://issues.apache.org/jira/browse/TUSCANY-2191 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2191.patch > > > Line 1635 of the Java Annotations spec says: >A @Service annotation with no attributes is meaningless, it is the same as > not having the annotation there at all. > However, the presence of the the annotation without attributes results in the > following: > org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: > org.apache.tuscany.sca.contribution.service.ContributionResolveException: > org.apache.tuscany.sca.implementation.java.introspect.impl.IllegalServiceDefinitionException: > No interfaces specified > at > org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) > at > org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2191) A @Service annotation with no attributes causes exception
[ https://issues.apache.org/jira/browse/TUSCANY-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2191: --- Assignee: Simon Laws > A @Service annotation with no attributes causes exception > - > > Key: TUSCANY-2191 > URL: https://issues.apache.org/jira/browse/TUSCANY-2191 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-Next >Reporter: Kevin Williams >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: TUSCANY-2191.patch > > > Line 1635 of the Java Annotations spec says: >A @Service annotation with no attributes is meaningless, it is the same as > not having the annotation there at all. > However, the presence of the the annotation without attributes results in the > following: > org.osoa.sca.ServiceRuntimeException: org.osoa.sca.ServiceRuntimeException: > org.apache.tuscany.sca.contribution.service.ContributionResolveException: > org.apache.tuscany.sca.implementation.java.introspect.impl.IllegalServiceDefinitionException: > No interfaces specified > at > org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) > at > org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2109) Conflicts between component reference interface and promoted composite reference interface are not detected
[ https://issues.apache.org/jira/browse/TUSCANY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587574#action_12587574 ] Simon Laws commented on TUSCANY-2109: - I've also just checked in the test case that Simon Nash created see (http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/itest/promotion-interface-missmatch/). It's not part of the build at the moment by you can run it directly and it's successful. With namespace checks in place this test should fail. We then of course need to adjust the test to check for failure :-) > Conflicts between component reference interface and promoted composite > reference interface are not detected > > > Key: TUSCANY-2109 > URL: https://issues.apache.org/jira/browse/TUSCANY-2109 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: All >Reporter: Simon Nash >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: jira2109.patch, jira2109.zip > > > See TUSCANY-2033 for the background to this problem. > When a component reference defined with (either explicitly > or implicitly by introspection) is promoted to a composite reference defined > with , and there is a namespace conflict between the > component reference's and the composite reference's > . this conflict should be diagnosed as an error because it > violates the spec rule that an interface specified on a composite reference > must be a compatible superset of the interface of the promoted component > reference. In this case, the composite interface is incompatible with the > component reference because it has a different namespace. > There is code in CompositeWireBuilderImpl.connectCompositeReferences() to > handle connections between composite references and promoted compoennt > references. The only interface processing performed in this method is to copy > the component reference's interface contract to the composite reference's > interface contract if the composite reference does not have an interface > contract. Code should be added here to check for conflicts between the > composite reference's interface and the component reference's interface if > both interfaces are specified. > Similar code should be added to > CompositeWireBuilderImpl.connectCompositeServices() to check that the > composite service interface is a compatible subset of the component service > interface as required by the spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2109) Conflicts between component reference interface and promoted composite reference interface are not detected
[ https://issues.apache.org/jira/browse/TUSCANY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587556#action_12587556 ] Simon Laws commented on TUSCANY-2109: - Hi Yes. I think you are right. We need to ensure that the "package name of java interface must be consistent to the target namespace of wsdl interface". You are also correct that missmatched namespaces are not called out explicitly in the spec as a reason for marking interfaces as incompatible. However the underlying problem here is that the namespace of the interface is used to scope the SOAP request that is sent across the wire to the service. If the reference interface is not "namespace compatible" with the interface that the service is using to describe itself then it won't be able to understand the arriving message. So I think we need to extend the compatibility test to compare namesapces (namespace here would mean the namespace dervied from the java package name, or from the JAXWS annotations or from the WSDL). I'm not sure how namespace is recorded when the interface type is java so we need to look at that. Does that sounds right? Simon > Conflicts between component reference interface and promoted composite > reference interface are not detected > > > Key: TUSCANY-2109 > URL: https://issues.apache.org/jira/browse/TUSCANY-2109 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: All >Reporter: Simon Nash >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: jira2109.patch, jira2109.zip > > > See TUSCANY-2033 for the background to this problem. > When a component reference defined with (either explicitly > or implicitly by introspection) is promoted to a composite reference defined > with , and there is a namespace conflict between the > component reference's and the composite reference's > . this conflict should be diagnosed as an error because it > violates the spec rule that an interface specified on a composite reference > must be a compatible superset of the interface of the promoted component > reference. In this case, the composite interface is incompatible with the > component reference because it has a different namespace. > There is code in CompositeWireBuilderImpl.connectCompositeReferences() to > handle connections between composite references and promoted compoennt > references. The only interface processing performed in this method is to copy > the component reference's interface contract to the composite reference's > interface contract if the composite reference does not have an interface > contract. Code should be added here to check for conflicts between the > composite reference's interface and the component reference's interface if > both interfaces are specified. > Similar code should be added to > CompositeWireBuilderImpl.connectCompositeServices() to check that the > composite service interface is a compatible subset of the component service > interface as required by the spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2212) SCA Java builds are getting very large
[ https://issues.apache.org/jira/browse/TUSCANY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587242#action_12587242 ] Simon Laws commented on TUSCANY-2212: - Here is the list of dependencies from the latest trunk (http://people.apache.org/~slaws/deptotal.htm). Not as bad as it was but we do, for example, depend on 3 versions of xerces and jaxb. > SCA Java builds are getting very large > -- > > Key: TUSCANY-2212 > URL: https://issues.apache.org/jira/browse/TUSCANY-2212 > Project: Tuscany > Issue Type: Improvement > Components: Build System >Affects Versions: Java-SCA-Next >Reporter: ant elder > Fix For: Java-SCA-Next > > > As discussed on the ML SCA Java builds are getting very large. See > http://apache.markmail.org/message/u7ebawcoicyqi55a > Current size for me is 1.5GB so this jira is to track fixes to reduce that. > Looking at the build and repo there's here's some things OTTOMH to start with: > - the distribution build copies the distros to the target-last-successful > folder. this is only needed for the continuum build and adds 120MB > - where ever JMS is used the ActiveMQ default is persistence=true which adds > about 50MB for the dbs, changing to persistence=false avoids that > - a large amount of the mvn repository size is webapp samples but we don't > need these installed into the mvn repo, is there a way to prevent that > happening? > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2214) xml-bigbank demo relies on http://www.swanandmokashi.com which is not (currently) available
xml-bigbank demo relies on http://www.swanandmokashi.com which is not
(currently) available
Key: TUSCANY-2214
URL: https://issues.apache.org/jira/browse/TUSCANY-2214
Project: Tuscany
Issue Type: Bug
Components: Java SCA Demos
Affects Versions: Java-SCA-1.2
Environment: WinXP SP2, IBM JDK5
Reporter: Simon Laws
Priority: Minor
Fix For: Java-SCA-1.2
demo/xml-bingbank fails with the error below because the web site the demo is
trying to contact is not (currently) available to me. It may be temporary or
may be permanent. At a minimum we should note in the README that this can
happen and that the demo will not work it this is the case.
ant run
Buildfile: build.xml
run:
[java] 09-Apr-2008 13:06:11 org.apache.tuscany.sca.contribution.processor.E
xtensibleStAXArtifactProcessor read
[java] WARNING: Element {http://tuscany.apache.org/xmlns/sca/1.0}binding.rs
s cannot be processed. ([row,col {unknown-source}]: [34,13])
[java] [Fatal Error] StockQuotes.asmx?WSDL:1:133: The element type "META" m
ust be terminated by the matching end-tag "".
[java] Exception in thread "main" org.osoa.sca.ServiceRuntimeException: jav
a.lang.RuntimeException: org.apache.tuscany.sca.contribution.service.Contributio
nReadException: javax.wsdl.WSDLException: WSDLException (at /wsdl:definitions/ws
dl:import): faultCode=PARSER_ERROR: Problem parsing 'http://www.swanandmokashi.c
om/HomePage/WebServices/StockQuotes.asmx?WSDL'.: org.xml.sax.SAXParseException:
The element type "META" must be terminated by the matching end-tag "".
[java] at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta
nce(SCADomain.java:264)
[java] at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC
ADomain.java:69)
[java] at bigbank.BigBankClient.main(BigBankClient.java:30)
[java] Caused by: java.lang.RuntimeException: org.apache.tuscany.sca.contri
bution.service.ContributionReadException: javax.wsdl.WSDLException: WSDLExceptio
n (at /wsdl:definitions/wsdl:import): faultCode=PARSER_ERROR: Problem parsing 'h
ttp://www.swanandmokashi.com/HomePage/WebServices/StockQuotes.asmx?WSDL'.: org.x
ml.sax.SAXParseException: The element type "META" must be terminated by the matc
hing end-tag "".
[java] at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
r.loadOnDemand(WSDLModelResolver.java:290)
[java] at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
r.aggregate(WSDLModelResolver.java:223)
[java] at org.apache.tuscany.sca.interfacedef.wsdl.xml.WSDLModelResolve
r.resolveModel(WSDLModelResolver.java:256)
[java] at org.apache.tuscany.sca.contribution.resolver.ExtensibleModelR
esolver.resolveModel(ExtensibleModelResolver.java:150)
[java] at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
sor.resolve(WebServiceBindingProcessor.java:269)
[java] at org.apache.tuscany.sca.binding.ws.xml.WebServiceBindingProces
sor.resolve(WebServiceBindingProcessor.java:59)
[java] at org.apache.tuscany.sca.contribution.processor.DefaultStAXArti
factProcessorExtensionPoint$LazyStAXArtifactProcessor.resolve(DefaultStAXArtifac
tProcessorExtensionPoint.java:252)
[java] at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
[java] at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.res
olveContracts(BaseAssemblyProcessor.java:362)
[java] at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
e(CompositeProcessor.java:822)
[java] at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.resolv
e(CompositeProcessor.java:80)
[java] at org.apache.tuscany.sca.contribution.processor.ExtensibleStAXA
rtifactProcessor.resolve(ExtensibleStAXArtifactProcessor.java:109)
[java] at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
r.resolve(CompositeDocumentProcessor.java:138)
[java] at org.apache.tuscany.sca.assembly.xml.CompositeDocumentProcesso
r.resolve(CompositeDocumentProcessor.java:53)
[java] at org.apache.tuscany.sca.contribution.processor.ExtensibleURLAr
tifactProcessor.resolve(ExtensibleURLArtifactProcessor.java:86)
[java] at org.apache.tuscany.sca.contribution.service.impl.Contribution
ServiceImpl.processResolvePhase(ContributionServiceImpl.java:464)
[java] at org.apache.tuscany.sca.contribution.service.impl.Contribution
ServiceImpl.addContribution(ContributionServiceImpl.java:348)
[java] at org.apache.tuscany.sca.contribution.service.impl.Contribution
ServiceImpl.contribute(ContributionServiceImpl.java:161)
[java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.ad
dContribution(DefaultSCADomain.jav
[jira] Commented: (TUSCANY-2109) Conflicts between component reference interface and promoted composite reference interface are not detected
[ https://issues.apache.org/jira/browse/TUSCANY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587102#action_12587102 ] Simon Laws commented on TUSCANY-2109: - Hi wangfeng I've applied the patch locally and taken SimonN's test from here and created an itest. The changes you have made to the assembly builders to introduce interface compatibility tests look good (although, as an aside, we may need to revisit the exception throwing in light of the ongoing discussion on monitoring of builder faults) but currently the code in InterfaceContractMapper.checkCompatibility doesn't perform a namespace compatibility test so the change doesn't fix the problem reported. Do you have more changes to added to this? SimonL > Conflicts between component reference interface and promoted composite > reference interface are not detected > > > Key: TUSCANY-2109 > URL: https://issues.apache.org/jira/browse/TUSCANY-2109 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: All >Reporter: Simon Nash >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: jira2109.patch, jira2109.zip > > > See TUSCANY-2033 for the background to this problem. > When a component reference defined with (either explicitly > or implicitly by introspection) is promoted to a composite reference defined > with , and there is a namespace conflict between the > component reference's and the composite reference's > . this conflict should be diagnosed as an error because it > violates the spec rule that an interface specified on a composite reference > must be a compatible superset of the interface of the promoted component > reference. In this case, the composite interface is incompatible with the > component reference because it has a different namespace. > There is code in CompositeWireBuilderImpl.connectCompositeReferences() to > handle connections between composite references and promoted compoennt > references. The only interface processing performed in this method is to copy > the component reference's interface contract to the composite reference's > interface contract if the composite reference does not have an interface > contract. Code should be added here to check for conflicts between the > composite reference's interface and the component reference's interface if > both interfaces are specified. > Similar code should be added to > CompositeWireBuilderImpl.connectCompositeServices() to check that the > composite service interface is a compatible subset of the component service > interface as required by the spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1802) RMI Implementation Error Handling lost inner exception's detail information
[
https://issues.apache.org/jira/browse/TUSCANY-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587076#action_12587076
]
Simon Laws commented on TUSCANY-1802:
-
Great. Thanks Venkat. Sorry for the confusion.
> RMI Implementation Error Handling lost inner exception's detail information
> ---
>
> Key: TUSCANY-1802
> URL: https://issues.apache.org/jira/browse/TUSCANY-1802
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Java Implementation Extension
>Reporter: Yang Sun
>Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
> Attachments: 1802.patch
>
>
> Here is an email I sent to the tuscany user group. Raymond Feng confirms it
> may be a potential bug. Please have a look.
> /--
> Hi,
> I am a new user of Tuscany and I am very excited with this great software. I
> am trying to introduce it into my project and currently I am evaluate it with
> every possible situations.
> Currently, I met a small problem with the spring implementation. I am not
> sure if I understand the background and configure the composites right.
> Please correct me if I make anything wrong.
> The problem I met is that I cannot get the detailed original exception when
> the server-side throw any kinds of exceptions. After a rough looking at the
> src code and debugging, I see the following code in SpringInvoker.java :
> ---
> private Object doInvoke(Object payload) throws SpringInvocationException {
> if (theMethod == null)
> setupMethod();
> if (badInvoker)
> throw new SpringInvocationException("Spring invoker incorrectly
> configured");
> // Invoke the method on the Spring bean using the payload, returning
> the results
> try {
> Object ret;
> if (payload != null && !payload.getClass().isArray()) {
> ret = theMethod.invoke(bean, payload);
> } else {
> ret = theMethod.invoke(bean, (Object[])payload);
> }
> return ret;
> } catch (InvocationTargetException e) {
> throw new SpringInvocationException(e.getMessage());
> } catch (Exception e) {
> throw new SpringInvocationException(e.getMessage());
> }
> } // end method doInvoke
>
> When the invoked method throw an exception (checked or unchecked), the
> program flow will go to the InvocationTargetException exception handler. Then
> the program only put the message of the original message to the wrapper
> exception SpringInvocationException. The detailed information of the original
> exception is missing. I am thinking it is here that will lost the detailed
> information of the original exception detail.
> The reason for me to bring this question is that if we cannot get the
> detailed information of the original exception, how can we deal with the
> application exceptions (such as NotEnoughMoneyException)? The only thing I
> can get is the java.lang.reflect.InvocationTargetException wrapped in
> java.rmi.UnexpectedException. And with those information, I cannot get the
> right information to make the further decision in the program.
> I am not sure whether I got the right point or if I misunderstand anything.
> Please give me some suggestions on this problem.
> Best Regards,
> Yang Sun
> /
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2109) Conflicts between component reference interface and promoted composite reference interface are not detected
[ https://issues.apache.org/jira/browse/TUSCANY-2109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2109: --- Assignee: Simon Laws > Conflicts between component reference interface and promoted composite > reference interface are not detected > > > Key: TUSCANY-2109 > URL: https://issues.apache.org/jira/browse/TUSCANY-2109 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Core Runtime >Affects Versions: Java-SCA-1.1 > Environment: All >Reporter: Simon Nash >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: jira2109.patch, jira2109.zip > > > See TUSCANY-2033 for the background to this problem. > When a component reference defined with (either explicitly > or implicitly by introspection) is promoted to a composite reference defined > with , and there is a namespace conflict between the > component reference's and the composite reference's > . this conflict should be diagnosed as an error because it > violates the spec rule that an interface specified on a composite reference > must be a compatible superset of the interface of the promoted component > reference. In this case, the composite interface is incompatible with the > component reference because it has a different namespace. > There is code in CompositeWireBuilderImpl.connectCompositeReferences() to > handle connections between composite references and promoted compoennt > references. The only interface processing performed in this method is to copy > the component reference's interface contract to the composite reference's > interface contract if the composite reference does not have an interface > contract. Code should be added here to check for conflicts between the > composite reference's interface and the component reference's interface if > both interfaces are specified. > Similar code should be added to > CompositeWireBuilderImpl.connectCompositeServices() to check that the > composite service interface is a compatible subset of the component service > interface as required by the spec. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-1802) RMI Implementation Error Handling lost inner exception's detail information
[
https://issues.apache.org/jira/browse/TUSCANY-1802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reassigned TUSCANY-1802:
---
Assignee: Simon Laws (was: Venkatakrishnan)
> RMI Implementation Error Handling lost inner exception's detail information
> ---
>
> Key: TUSCANY-1802
> URL: https://issues.apache.org/jira/browse/TUSCANY-1802
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Java Implementation Extension
>Reporter: Yang Sun
>Assignee: Simon Laws
> Fix For: Java-SCA-Next
>
> Attachments: 1802.patch
>
>
> Here is an email I sent to the tuscany user group. Raymond Feng confirms it
> may be a potential bug. Please have a look.
> /--
> Hi,
> I am a new user of Tuscany and I am very excited with this great software. I
> am trying to introduce it into my project and currently I am evaluate it with
> every possible situations.
> Currently, I met a small problem with the spring implementation. I am not
> sure if I understand the background and configure the composites right.
> Please correct me if I make anything wrong.
> The problem I met is that I cannot get the detailed original exception when
> the server-side throw any kinds of exceptions. After a rough looking at the
> src code and debugging, I see the following code in SpringInvoker.java :
> ---
> private Object doInvoke(Object payload) throws SpringInvocationException {
> if (theMethod == null)
> setupMethod();
> if (badInvoker)
> throw new SpringInvocationException("Spring invoker incorrectly
> configured");
> // Invoke the method on the Spring bean using the payload, returning
> the results
> try {
> Object ret;
> if (payload != null && !payload.getClass().isArray()) {
> ret = theMethod.invoke(bean, payload);
> } else {
> ret = theMethod.invoke(bean, (Object[])payload);
> }
> return ret;
> } catch (InvocationTargetException e) {
> throw new SpringInvocationException(e.getMessage());
> } catch (Exception e) {
> throw new SpringInvocationException(e.getMessage());
> }
> } // end method doInvoke
>
> When the invoked method throw an exception (checked or unchecked), the
> program flow will go to the InvocationTargetException exception handler. Then
> the program only put the message of the original message to the wrapper
> exception SpringInvocationException. The detailed information of the original
> exception is missing. I am thinking it is here that will lost the detailed
> information of the original exception detail.
> The reason for me to bring this question is that if we cannot get the
> detailed information of the original exception, how can we deal with the
> application exceptions (such as NotEnoughMoneyException)? The only thing I
> can get is the java.lang.reflect.InvocationTargetException wrapped in
> java.rmi.UnexpectedException. And with those information, I cannot get the
> right information to make the further decision in the program.
> I am not sure whether I got the right point or if I misunderstand anything.
> Please give me some suggestions on this problem.
> Best Regards,
> Yang Sun
> /
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2149) samples/helloworld-service&reference-jms failure
[ https://issues.apache.org/jira/browse/TUSCANY-2149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws updated TUSCANY-2149: Attachment: tuscany-2149.patch These changes get the sample working in my Eclipse workspace. Unfortunately I've run out of time to get this working in the disitribution build as a few more changes are required and I don't want to half do them in a rush. Primarily the distribution needs to be updated to include ActiveMQ and the appropriate changes need to be made to LICENSE/NOTICE to take account of this. > samples/helloworld-service&reference-jms failure > - > > Key: TUSCANY-2149 > URL: https://issues.apache.org/jira/browse/TUSCANY-2149 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Samples >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2 IBM JDK 5 >Reporter: Simon Laws > Fix For: Java-SCA-1.2 > > Attachments: tuscany-2149.patch > > > Firstly you have to do "ant compile" before "ant run" which is not what the > README says > Secondly running helloworld-service-jms gives rise to > C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\samples\hellowo > rld-service-jms>ant run > Buildfile: build.xml > run: > [java] Exception in thread "main" org.osoa.sca.ServiceRuntimeException: > org > .apache.tuscany.sca.binding.jms.impl.JMSBindingException: Error starting > JMSServ > iceBinding > [java] at > org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta > nce(SCADomain.java:264) > [java] at > org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC > ADomain.java:69) > [java] at helloworld.HelloWorldServer.main(HelloWorldServer.java:34) > [java] Caused by: > org.apache.tuscany.sca.binding.jms.impl.JMSBindingExcepti > on: Error starting JMSServiceBinding > [java] at > org.apache.tuscany.sca.binding.jms.provider.JMSBindingService > BindingProvider.start(JMSBindingServiceBindingProvider.java:104) > [java] at > org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.s > tart(CompositeActivatorImpl.java:520) > [java] at > org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in > it(DefaultSCADomain.java:226) > [java] at > org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain. nit>(DefaultSCADomain.java:109) > [java] at > org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta > nce(SCADomain.java:230) > [java] ... 2 more > [java] Caused by: > org.apache.tuscany.sca.binding.jms.impl.JMSBindingExcepti > on: connection factory not found: ConnectionFactory > [java] at > org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactor > y.createConnection(JMSResourceFactory.java:108) > [java] at > org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactor > y.getConnection(JMSResourceFactory.java:68) > [java] at > org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactor > y.createSession(JMSResourceFactory.java:79) > [java] at > org.apache.tuscany.sca.binding.jms.provider.JMSBindingService > BindingProvider.registerListerner(JMSBindingServiceBindingProvider.java:120) > [java] at > org.apache.tuscany.sca.binding.jms.provider.JMSBindingService > BindingProvider.start(JMSBindingServiceBindingProvider.java:102) > [java] ... 6 more > [java] Java Result: 1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2147) samples/calculator-implementation-policies
[
https://issues.apache.org/jira/browse/TUSCANY-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-2147:
Fix Version/s: (was: Java-SCA-1.2)
Java-SCA-Next
OK, I'll move this to SCA Next. If there is a duplicate of this discussing this
spec question then we can close this one. I couldn't spot one.
> samples/calculator-implementation-policies
> --
>
> Key: TUSCANY-2147
> URL: https://issues.apache.org/jira/browse/TUSCANY-2147
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Samples
>Affects Versions: Java-SCA-1.2
> Environment: WinXP SP2, IBM JDK 5
>Reporter: Simon Laws
>Priority: Minor
> Fix For: Java-SCA-Next
>
>
> Running the calculator-implementation-policies report success at the end of
> the run but the first lines of logged output are...
> tor-implementation-policies>ant run
> Buildfile: build.xml
> run:
> [java] 27-Mar-2008 09:36:29
> org.apache.tuscany.sca.contribution.processor.V
> alidatingXMLStreamReader$1 error
> [java] WARNING: XMLSchema validation problem in: null, line: 22, column:
> 4
> [java] cvc-complex-type.2.4.a: Invalid content was found starting with
> elem
> ent 'operation'. One of '{WC[##other:"http://www.osoa.org/xmlns/sca/1.0"]}'
> is e
> xpected.
> [java] Calling CalculatorServiceComponent configured with 'logging'
> policy
> for subtract and divide operations...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2156) demos/xml-bigbank run failure
demos/xml-bigbank run failure - Key: TUSCANY-2156 URL: https://issues.apache.org/jira/browse/TUSCANY-2156 Project: Tuscany Issue Type: Bug Components: Java SCA Demos Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 5 Reporter: Simon Laws Fix For: Java-SCA-1.2 running demos/xml-bigbank give rise to C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\demos\xml-bigba nk>ant run Buildfile: build.xml run: [java] Exception in thread "main" javax.xml.stream.FactoryConfigurationErro r: Provider com.bea.xml.stream.MXParserFactory not found [java] at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java :72) [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:176) [java] at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92) [java] at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory. java:136) [java] at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntimeB uilder.createContributionService(ReallySmallRuntimeBuilder.java:176) [java] at org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime. start(ReallySmallRuntime.java:139) [java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in it(DefaultSCADomain.java:118) [java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta nce(SCADomain.java:230) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC ADomain.java:69) [java] at bigbank.BigBankClient.main(BigBankClient.java:30) [java] Java Result: 1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2155) demos/bigbank assembly warnings on start up
demos/bigbank assembly warnings on start up --- Key: TUSCANY-2155 URL: https://issues.apache.org/jira/browse/TUSCANY-2155 Project: Tuscany Issue Type: Bug Components: Java SCA Demos Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 5 Reporter: Simon Laws Priority: Minor Fix For: Java-SCA-1.2 demos/bigbank runs successfully but reports assembly warnings on startup as follows, which is a little disconcerting run: [java] Starting the Sample SCA BigBank server... [java] 27-Mar-2008 11:46:31 org.apache.tuscany.sca.assembly.builder.impl.Co mpositeBuilderImpl$1 problem [java] WARNING: Service not found for component service: SavingsAccountServ iceComponent/$promoted$.SavingsAccountService [java] 27-Mar-2008 11:46:31 org.apache.tuscany.sca.assembly.builder.impl.Co mpositeBuilderImpl$1 problem [java] WARNING: Service not found for component service: CheckingAccountSer viceComponent/$promoted$.CheckingsAccountService [java] 27-Mar-2008 11:46:31 org.apache.tuscany.sca.assembly.builder.impl.Co mpositeBuilderImpl$1 problem [java] WARNING: Service not found for component service: StockAccountServic eComponent/$promoted$.StockAccountService [java] 27-Mar-2008 11:46:31 org.apache.tuscany.sca.assembly.builder.impl.Co mpositeBuilderImpl$1 problem [java] WARNING: Service not found for component service: SavingsAccountServ iceComponent/$promoted$.SavingsAccountService [java] 27-Mar-2008 11:46:31 org.apache.tuscany.sca.assembly.builder.impl.Co mpositeBuilderImpl$1 problem [java] WARNING: Service not found for component service: CheckingAccountSer viceComponent/$promoted$.CheckingsAccountService [java] 27-Mar-2008 11:46:31 org.apache.tuscany.sca.assembly.builder.impl.Co mpositeBuilderImpl$1 problem [java] WARNING: Service not found for component service: StockAccountServic eComponent/$promoted$.StockAccountService -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2154) demos/alert-aggregator-webapp still uses package ant target and startup failure
demos/alert-aggregator-webapp still uses package ant target and startup failure --- Key: TUSCANY-2154 URL: https://issues.apache.org/jira/browse/TUSCANY-2154 Project: Tuscany Issue Type: Bug Components: Java SCA Demos Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK5, Tomcat 6.0.13 Reporter: Simon Laws Priority: Minor Fix For: Java-SCA-1.2 Firstly this demo still relies on the "package" ant target. We should replace this with "compile" which all other samples & demos use Secondly, on start up, the webapp fails and reports the following in the tomcat log (this looks to be the same problem as https://issues.apache.org/jira/browse/TUSCANY-2151) SEVERE: Exception starting filter tuscany org.osoa.sca.ServiceRuntimeException: java.lang.reflect.InvocationTargetException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:82) at org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:215) at org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:50) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4340) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:566) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:521) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:246) ... 30 more Caused by: java.lang.NoClassDefFoundError: javax.wsdl.extensions.ExtensionSerializer at java.lang.J9VMInternals.verifyImpl(Native Method) at java.lang.J9VMInternals.verify(J9VMInternals.java:66) at java.lang.J9VMInternals.initialize(J9VMInternals.java:127) at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:163) at org.apache.tuscany.sca.extensibility.ServiceDeclaration.loadClass(ServiceDeclaration.java:63) at org.apache.tuscany.sca.contribution.resolver.DefaultModelResolverExtensionPoint.getResolver(DefaultModelResolverExtensionPoint.java:65) at org.apache.tuscany.sca.contribution.resolver.ExtensibleModelResolver.getModelResolverInstance(ExtensibleModelResolver.java:107)
[jira] Created: (TUSCANY-2153) samples/implementation-pojo
samples/implementation-pojo --- Key: TUSCANY-2153 URL: https://issues.apache.org/jira/browse/TUSCANY-2153 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 5 Reporter: Simon Laws Fix For: Java-SCA-1.2 There is no "ant run" target. The README suggests there should be. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2152) samples/implementation-notification
samples/implementation-notification --- Key: TUSCANY-2152 URL: https://issues.apache.org/jira/browse/TUSCANY-2152 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 5 Reporter: Simon Laws Fix For: Java-SCA-1.2 implementation-notification README doesn't point out that you need to do ant compile ant run So we need to fix the README or fix the sample to work with just ant run -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2151) samples/helloworld-ws-sdo-webapp
samples/helloworld-ws-sdo-webapp Key: TUSCANY-2151 URL: https://issues.apache.org/jira/browse/TUSCANY-2151 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 5, Tomcat 6.0.13 Reporter: Simon Laws Fix For: Java-SCA-1.2 helloworld-ws-sdo-webapp fails to start up in Tomcat giving the following message in the Tomcat log SEVERE: Exception starting filter tuscany org.osoa.sca.ServiceRuntimeException: java.lang.reflect.InvocationTargetException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:82) at org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:215) at org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:50) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4340) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) at java.lang.Thread.run(Thread.java:801) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:521) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:246) ... 22 more Caused by: java.lang.NoClassDefFoundError: javax.wsdl.extensions.ExtensionSerializer at java.lang.J9VMInternals.verifyImpl(Native Method) at java.lang.J9VMInternals.verify(J9VMInternals.java:66) at java.lang.J9VMInternals.initialize(J9VMInternals.java:127) at java.lang.Class.forNameImpl(Native Method) at java.lang.Class.forName(Class.java:163) at org.apache.tuscany.sca.extensibility.ServiceDeclaration.loadClass(ServiceDeclaration.java:63) at org.apache.tuscany.sca.contribution.resolver.DefaultModelResolverExtensionPoint.getResolver(DefaultModelResolverExtensionPoint.java:65) at org.apache.tuscany.sca.contribution.resolver.ExtensibleModelResolver.getModelResolverInstance(ExtensibleModelResolver.java:107) at org.apache.tuscany.sca.contribution.resolver.ExtensibleModelResolver.addModel(ExtensibleModelResolver.java:130) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.processReadPhase(ContributionServiceImpl.java:407) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:339) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:161) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.addContribution(DefaultSCADomain.java:272) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:152) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109) at org.apache.tuscany.sc
tuscany-dev@ws.apache.org
samples/helloworld-ws-service&reference-jms --- Key: TUSCANY-2150 URL: https://issues.apache.org/jira/browse/TUSCANY-2150 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK 5 Reporter: Simon Laws Fix For: Java-SCA-1.2 Running helloworld-ws-service-jms gives rise to... C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\samples\hellowo rld-ws-service-jms>ant run Buildfile: build.xml run: [java] 27-Mar-2008 10:57:15 org.apache.tuscany.sca.binding.ws.axis2.Axis2Se rviceProvider start [java] INFO: Axis2 JMS URL=jms:/queue.sample?transport.jms.ConnectionFactor yJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq .jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:616 19 [java] Exception in thread "main" org.osoa.sca.ServiceRuntimeException: org .apache.axis2.transport.jms.AxisJMSException: Error connecting to JMS connection factory : QueueConnectionFactory [java] at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta nce(SCADomain.java:264) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC ADomain.java:69) [java] at helloworld.HelloWorldServer.main(HelloWorldServer.java:33) [java] Caused by: org.apache.axis2.transport.jms.AxisJMSException: Error co nnecting to JMS connection factory : QueueConnectionFactory [java] at org.apache.axis2.transport.jms.JMSListener.handleException(JM SListener.java:420) [java] at org.apache.axis2.transport.jms.JMSListener.initializeConnecti onFactories(JMSListener.java:256) [java] at org.apache.axis2.transport.jms.JMSListener.init(JMSListener.j ava:109) [java] at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider. start(Axis2ServiceProvider.java:285) [java] at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingPr ovider.start(Axis2ServiceBindingProvider.java:94) [java] at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.s tart(CompositeActivatorImpl.java:520) [java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in it(DefaultSCADomain.java:226) [java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta nce(SCADomain.java:230) [java] ... 2 more [java] Caused by: javax.naming.NoInitialContextException: Cannot instantiat e class: org.apache.activemq.jndi.ActiveMQInitialContextFactory [Root exception is java.lang.ClassNotFoundException: org.apache.activemq.jndi.ActiveMQInitialCon textFactory] [java] at javax.naming.spi.NamingManager.getInitialContext(NamingManage r.java:669) [java] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext. java:259) [java] at javax.naming.InitialContext.init(InitialContext.java:235) [java] at javax.naming.InitialContext.(InitialContext.java:209) [java] at org.apache.axis2.transport.jms.JMSConnectionFactory.createIni tialContext(JMSConnectionFactory.java:189) [java] at org.apache.axis2.transport.jms.JMSConnectionFactory.connect(J MSConnectionFactory.java:170) [java] at org.apache.axis2.transport.jms.JMSListener.initializeConnecti onFactories(JMSListener.java:253) [java] ... 9 more [java] Caused by: java.lang.ClassNotFoundException: org.apache.activemq.jnd i.ActiveMQInitialContextFactory [java] at java.lang.Class.forName(Class.java:163) [java] at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelp er12.java:57) [java] at javax.naming.spi.NamingManager.getInitialContext(NamingManage r.java:666) [java] ... 15 more [java] Java Result: 1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2148) samples/calculator-ws-webapp - failure on start
[ https://issues.apache.org/jira/browse/TUSCANY-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12582594#action_12582594 ] Simon Laws commented on TUSCANY-2148: - Looks like the same problem as https://issues.apache.org/jira/browse/TUSCANY-2107 > samples/calculator-ws-webapp - failure on start > --- > > Key: TUSCANY-2148 > URL: https://issues.apache.org/jira/browse/TUSCANY-2148 > Project: Tuscany > Issue Type: Bug > Components: Java SCA Samples >Affects Versions: Java-SCA-1.2 > Environment: WinXP SP2, IBM JDK5, Tomcat 6.0.13 >Reporter: Simon Laws > Fix For: Java-SCA-1.2 > > > Webapp startup fails. The tomcat log reports... > SEVERE: Exception starting filter tuscany > org.osoa.sca.ServiceRuntimeException: > java.lang.reflect.InvocationTargetException > at > org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) > at > org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:82) > at > org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:215) > at > org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:50) > at > org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) > at > org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) > at > org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:108) > at > org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693) > at > org.apache.catalina.core.StandardContext.start(StandardContext.java:4340) > at > org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) > at > org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) > at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) > at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) > at > org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) > at > org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) > at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206) > at > org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293) > at > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) > at > org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337) > at > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) > at > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) > at > org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) > at java.lang.Thread.run(Thread.java:801) > Caused by: java.lang.reflect.InvocationTargetException > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) > at > sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) > at java.lang.reflect.Constructor.newInstance(Constructor.java:521) > at > org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:246) > ... 22 more > Caused by: org.osoa.sca.ServiceRuntimeException: > org.apache.tuscany.sca.core.assembly.ActivationException: > java.lang.RuntimeException: org.apache.axis2.AxisFault: > org.apache.commons.fileupload.FileUploadException > at > org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:220) > at > org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109) > at > org.apache.tuscany.sca.host.webapp.WebSCADomain.(WebSCADomain.java:41) > ... 27 more > Caused by: org.apache.tuscany.sca.core.assembly.ActivationException: > java.lang.RuntimeException: org.apache.axis2.AxisFault: > org.apache.commons.fileupload.FileUploadException > at > org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:792) > at > org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:218) > ... 29 more > Caused by: java.lang.RuntimeException: org.apache.axis2.AxisFault: > org.apache.commons.fileupload.FileUploadException > at > org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.(Axis2ServiceProvider.java:159) > at > org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.(Ax
[jira] Created: (TUSCANY-2149) samples/helloworld-service&reference-jms failure
samples/helloworld-service&reference-jms failure - Key: TUSCANY-2149 URL: https://issues.apache.org/jira/browse/TUSCANY-2149 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Environment: WinXP SP2 IBM JDK 5 Reporter: Simon Laws Fix For: Java-SCA-1.2 Firstly you have to do "ant compile" before "ant run" which is not what the README says Secondly running helloworld-service-jms gives rise to C:\simon\tuscany\release\sca-r1.2-rc2\tuscany-sca-1.2-incubating\samples\hellowo rld-service-jms>ant run Buildfile: build.xml run: [java] Exception in thread "main" org.osoa.sca.ServiceRuntimeException: org .apache.tuscany.sca.binding.jms.impl.JMSBindingException: Error starting JMSServ iceBinding [java] at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta nce(SCADomain.java:264) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SC ADomain.java:69) [java] at helloworld.HelloWorldServer.main(HelloWorldServer.java:34) [java] Caused by: org.apache.tuscany.sca.binding.jms.impl.JMSBindingExcepti on: Error starting JMSServiceBinding [java] at org.apache.tuscany.sca.binding.jms.provider.JMSBindingService BindingProvider.start(JMSBindingServiceBindingProvider.java:104) [java] at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.s tart(CompositeActivatorImpl.java:520) [java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.in it(DefaultSCADomain.java:226) [java] at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109) [java] at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInsta nce(SCADomain.java:230) [java] ... 2 more [java] Caused by: org.apache.tuscany.sca.binding.jms.impl.JMSBindingExcepti on: connection factory not found: ConnectionFactory [java] at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactor y.createConnection(JMSResourceFactory.java:108) [java] at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactor y.getConnection(JMSResourceFactory.java:68) [java] at org.apache.tuscany.sca.binding.jms.provider.JMSResourceFactor y.createSession(JMSResourceFactory.java:79) [java] at org.apache.tuscany.sca.binding.jms.provider.JMSBindingService BindingProvider.registerListerner(JMSBindingServiceBindingProvider.java:120) [java] at org.apache.tuscany.sca.binding.jms.provider.JMSBindingService BindingProvider.start(JMSBindingServiceBindingProvider.java:102) [java] ... 6 more [java] Java Result: 1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2148) samples/calculator-ws-webapp - failure on start
samples/calculator-ws-webapp - failure on start --- Key: TUSCANY-2148 URL: https://issues.apache.org/jira/browse/TUSCANY-2148 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK5, Tomcat 6.0.13 Reporter: Simon Laws Fix For: Java-SCA-1.2 Webapp startup fails. The tomcat log reports... SEVERE: Exception starting filter tuscany org.osoa.sca.ServiceRuntimeException: java.lang.reflect.InvocationTargetException at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:82) at org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:215) at org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:50) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:397) at org.apache.catalina.core.ApplicationFilterConfig.(ApplicationFilterConfig.java:108) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3693) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4340) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1206) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:293) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117) at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1337) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1601) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1610) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1590) at java.lang.Thread.run(Thread.java:801) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:67) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:521) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:246) ... 22 more Caused by: org.osoa.sca.ServiceRuntimeException: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.RuntimeException: org.apache.axis2.AxisFault: org.apache.commons.fileupload.FileUploadException at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:220) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.(DefaultSCADomain.java:109) at org.apache.tuscany.sca.host.webapp.WebSCADomain.(WebSCADomain.java:41) ... 27 more Caused by: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.RuntimeException: org.apache.axis2.AxisFault: org.apache.commons.fileupload.FileUploadException at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:792) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:218) ... 29 more Caused by: java.lang.RuntimeException: org.apache.axis2.AxisFault: org.apache.commons.fileupload.FileUploadException at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.(Axis2ServiceProvider.java:159) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.(Axis2ServiceBindingProvider.java:90) at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createServiceBindingProvider(Axis2BindingProviderFactory.java:64) at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingProviderFactory.createServiceBindingProvider(Axis2BindingProviderFactory.java:45) at org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyBindingProviderFactory.cre
[jira] Created: (TUSCANY-2147) samples/calculator-implementation-policies
samples/calculator-implementation-policies
--
Key: TUSCANY-2147
URL: https://issues.apache.org/jira/browse/TUSCANY-2147
Project: Tuscany
Issue Type: Bug
Components: Java SCA Samples
Affects Versions: Java-SCA-1.2
Environment: WinXP SP2, IBM JDK 5
Reporter: Simon Laws
Priority: Minor
Fix For: Java-SCA-1.2
Running the calculator-implementation-policies report success at the end of the
run but the first lines of logged output are...
tor-implementation-policies>ant run
Buildfile: build.xml
run:
[java] 27-Mar-2008 09:36:29 org.apache.tuscany.sca.contribution.processor.V
alidatingXMLStreamReader$1 error
[java] WARNING: XMLSchema validation problem in: null, line: 22, column: 4
[java] cvc-complex-type.2.4.a: Invalid content was found starting with elem
ent 'operation'. One of '{WC[##other:"http://www.osoa.org/xmlns/sca/1.0"]}' is e
xpected.
[java] Calling CalculatorServiceComponent configured with 'logging' policy
for subtract and divide operations...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2146) Array index out of range in binding-notification sample
Array index out of range in binding-notification sample --- Key: TUSCANY-2146 URL: https://issues.apache.org/jira/browse/TUSCANY-2146 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.2 Environment: WinXP SP2, IBM JDK5 Reporter: Simon Laws Priority: Critical Fix For: Java-SCA-1.2 To reproduce run up binding-notification-broker binding-notification-producer binding-notification-consumer As per the associate README Enter some message into the broker, e.g ABC and hit enter. I see the following exception Then [java] java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 1 [java] at org.apache.tuscany.sca.core.databinding.wire.PassByValueInter ceptor.copy(PassByValueInterceptor.java:155) [java] at org.apache.tuscany.sca.core.databinding.wire.PassByValueInter ceptor.invoke(PassByValueInterceptor.java:106) [java] at org.apache.tuscany.sca.binding.notification.NotificationServi ceBindingProvider.invoke(NotificationServiceBindingProvider.java:263) [java] at org.apache.tuscany.sca.binding.notification.NotificationServi ceBindingProvider.handle(NotificationServiceBindingProvider.java:244) [java] at org.apache.tuscany.sca.binding.notification.util.Notification Servlet.doPost(NotificationServlet.java:76) [java] at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) [java] at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) [java] at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder. java:487) [java] at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandle r.java:362) [java] at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandle r.java:181) [java] at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandle r.java:726) [java] at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrappe r.java:139) [java] at org.mortbay.jetty.Server.handle(Server.java:324) [java] at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection .java:505) [java] at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpC onnection.java:842) [java] at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648) [java] at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:2 11) [java] at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:3 80) [java] at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEnd Point.java:395) [java] at org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.ja va:61) [java] at org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$Decora tingWork.run(ThreadPoolWorkManager.java:214) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Thread PoolExecutor.java:665) [java] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPool Executor.java:690) [java] at java.lang.Thread.run(Thread.java:801) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2112) Add conversational intents as described in the assembly spec
Add conversational intents as described in the assembly spec Key: TUSCANY-2112 URL: https://issues.apache.org/jira/browse/TUSCANY-2112 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Environment: All Reporter: Simon Laws Priority: Minor Fix For: Java-SCA-Next I've been looking at the parts for the assembly spec that deal with conversational semantics and there are a couple of gaps when compared with the current TUscany implementation. In particular Tuscany only supports annotations in Java interfaces when declaring conversational behaviour. Section 1.5.3 describes the use of policy intents for specifying conversational behaviour 819 interface type. Note that it is also possible for a service or a reference to set the conversational 820 intent when using an interface which is not marked with the conversational intent. This can be 821 useful when reusing an existing interface definition that does not contain SCA information. I assume this meansa service could have a "conversational" intent as could a reference It's not clear from the spec if there should be an EndsConversation intent for operations. These intents would drive the existing underlying conversational functionality by augmenting the interface model will appropriate conversation information. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2099) Porting Workpool-Distributed demo to current.
[ https://issues.apache.org/jira/browse/TUSCANY-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580743#action_12580743 ] Simon Laws commented on TUSCANY-2099: - Hi Girogio. I've committed the patch. It's difficult to comment in detail until we have the code working. What I was wondering though is whether new components really need to be installed dynamically, with all the code complexity involved, or whether the same effect can be produced by relying on separate, for example, conversational, instances of the same component for running jobs. What I'm not clear on is whether 1) all of the components you start are all of the same type and just run jobs or whether 2) the jobs them selves are components. Looking at the code it seems that 1) is the case. Anyhow I'm not suggesting you change the design on the fly but there may be some opportunities for simplification down the line. Simon > Porting Workpool-Distributed demo to current. > - > > Key: TUSCANY-2099 > URL: https://issues.apache.org/jira/browse/TUSCANY-2099 > Project: Tuscany > Issue Type: New Feature >Reporter: Giorgio Zoppi >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: firstpatch.diff > > > This is the first patch to adapt workpool demo to current. Still it doens't > compile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2099) Porting Workpool-Distributed demo to current.
[ https://issues.apache.org/jira/browse/TUSCANY-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580387#action_12580387 ] Simon Laws commented on TUSCANY-2099: - I'm just checking in the patch associated with TUSCANY-2099 and one of the changes is to fill some gaps in the CompositeActivator's arsenal of component activation and deactivation methods. I have previous experience of the existing CompositeActivator methods for deactivating and reactivating components and their references when implementing some domain/node features before Christmas. I found them to be somewhat unreliable and I think the feeling at the time was that they weren't used very much and that they weren't well maintained. Can I just check with you the mode of operation of the workpool demo and the way that it uses these methods to add new worker components. The question on my mind is is it important that new components are added to the composite to service new jobs in parallel or is it, instead, a matter of ensuring that sufficient instances of an existing component are available to service tasks? Simon > Porting Workpool-Distributed demo to current. > - > > Key: TUSCANY-2099 > URL: https://issues.apache.org/jira/browse/TUSCANY-2099 > Project: Tuscany > Issue Type: New Feature >Reporter: Giorgio Zoppi >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: firstpatch.diff > > > This is the first patch to adapt workpool demo to current. Still it doens't > compile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Assigned: (TUSCANY-2099) Porting Workpool-Distributed demo to current.
[ https://issues.apache.org/jira/browse/TUSCANY-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2099: --- Assignee: Simon Laws > Porting Workpool-Distributed demo to current. > - > > Key: TUSCANY-2099 > URL: https://issues.apache.org/jira/browse/TUSCANY-2099 > Project: Tuscany > Issue Type: New Feature >Reporter: Giorgio Zoppi >Assignee: Simon Laws > Fix For: Java-SCA-Next > > Attachments: firstpatch.diff > > > This is the first patch to adapt workpool demo to current. Still it doens't > compile. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
