[jira] Commented: (TUSCANY-2253) TuscanyServletFilter cannot be initialized when no display-name is specified in web.xml
[ https://issues.apache.org/jira/browse/TUSCANY-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591263#action_12591263 ] wangfeng commented on TUSCANY-2253: --- In version 1.1,tuscany will use the display name to generate the domain uri.So if you use 1.1 and the display name is not be set ,it will throw an null pointer exception. But in version 1.2,the generating algorithm have been modified and the display name has not be used any more. What version are you using? can you try the latest version that can be downloaded from [1]. [1] http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/ TuscanyServletFilter cannot be initialized when no display-name is specified in web.xml --- Key: TUSCANY-2253 URL: https://issues.apache.org/jira/browse/TUSCANY-2253 Project: Tuscany Issue Type: Bug Components: Java SCA Web App Integration Affects Versions: Java-SCA-1.1 Reporter: Ilya Kanonirov When the display-name element is not specified in web.xml, TuscanyServletFilter fails to initialize with the following exception: 16:27:52,393 ERROR [[/]] Exception starting filter tuscany java.lang.NullPointerException at org.apache.tuscany.sca.host.webapp.WebAppServletHost.init(WebAppServletHost.java:209) at org.apache.tuscany.sca.host.webapp.TuscanyServletFilter.init(TuscanyServletFilter.java:51) at org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:225) at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:308) at org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:79) at org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3540) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4110) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) ... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TUSCANY-2245) A spelling mistake on the DomainModel class
A spelling mistake on the DomainModel class --- Key: TUSCANY-2245 URL: https://issues.apache.org/jira/browse/TUSCANY-2245 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.2 Reporter: wangfeng Fix For: Java-SCA-Next There is a spelling mistake on the DomainModel class. The method 'setDomainLeveComposite' should be 'setDomainLevelComposite'. -- 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-2245) A spelling mistake on the DomainModel class
[ https://issues.apache.org/jira/browse/TUSCANY-2245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-2245: -- Attachment: 2245.patch A spelling mistake on the DomainModel class --- Key: TUSCANY-2245 URL: https://issues.apache.org/jira/browse/TUSCANY-2245 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.2 Reporter: wangfeng Fix For: Java-SCA-Next Attachments: 2245.patch There is a spelling mistake on the DomainModel class. The method 'setDomainLeveComposite' should be 'setDomainLevelComposite'. -- 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-2227) Import export same composite namespace on different contribution,recursive resolve and stack overflow.
Import export same composite namespace on different contribution,recursive resolve and stack overflow. -- Key: TUSCANY-2227 URL: https://issues.apache.org/jira/browse/TUSCANY-2227 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.2 Environment: winxp ,tuscany 1.2 rc3,sun jdk 1.5.09 Reporter: wangfeng Fix For: Java-SCA-Next The related message on [1] When a contribution metadata contains a deployable composite but the composite is not exist and the metadata has exported and imported the same namespace, there will be recursive resolve the composite and will stack overflow. Run the testcase HelloWorldServerTestCase,it will throw stack overflow exception.Because it's contribution metadata has contains an not existed composite deployable composite=helloworld:notExit/ [1] http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30422.html -- 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-2227) Import export same composite namespace on different contribution,recursive resolve and stack overflow.
[ https://issues.apache.org/jira/browse/TUSCANY-2227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-2227: -- Attachment: contribution-import-export_testcase.zip The test case. Import export same composite namespace on different contribution,recursive resolve and stack overflow. -- Key: TUSCANY-2227 URL: https://issues.apache.org/jira/browse/TUSCANY-2227 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.2 Environment: winxp ,tuscany 1.2 rc3,sun jdk 1.5.09 Reporter: wangfeng Fix For: Java-SCA-Next Attachments: contribution-import-export_testcase.zip The related message on [1] When a contribution metadata contains a deployable composite but the composite is not exist and the metadata has exported and imported the same namespace, there will be recursive resolve the composite and will stack overflow. Run the testcase HelloWorldServerTestCase,it will throw stack overflow exception.Because it's contribution metadata has contains an not existed composite deployable composite=helloworld:notExit/ [1] http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg30422.html -- 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-tabpanelfocusedCommentId=12587460#action_12587460 ] wangfeng commented on TUSCANY-2109: --- Hi Simon According to the spec,line 1358 to 1360 define the reference interface restriction. 1358 If an interface is specified it must provide an interface which is the same or which is a 1359 compatible superset of the interface declared by the promoted component reference, i.e. provide 1360 a superset of the operations defined by the component for the reference. I think the interface only need to compare the operation is compatible or not. My understanding about 'namespace' is that if the interface is compatible ,the package name of java interface must be consistent to the target namespace of wsdl interface,is my understanding right? 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 interface.java (either explicitly or implicitly by introspection) is promoted to a composite reference defined with interface.wsdl, and there is a namespace conflict between the component reference's interface.java and the composite reference's interface.wsdl. 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] Updated: (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
]
wangfeng updated TUSCANY-1802:
--
Attachment: 1802.patch
This patch has provided the original exception when invoking the service.
Modifiy file
SpringBeanNotFoundException.java,SpringInvocationException.java,SpringOperationNotFoundException.java
and add the cause exception on the constructor method.
Modify file SpringInvoker.java and make the method 'setupMethod' throws an
SpringInvocationException.
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: Venkatakrishnan
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-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 ] wangfeng updated TUSCANY-2109: -- Attachment: jira2109.patch The patch can detect the reference and service InterfaceContract. If the reference or the service InterfaceContract of composite is not compatible with the promoted component refercnce or service,the runtime may throw an IncompatibleInterfaceContractException. 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 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 interface.java (either explicitly or implicitly by introspection) is promoted to a composite reference defined with interface.wsdl, and there is a namespace conflict between the component reference's interface.java and the composite reference's interface.wsdl. 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] Created: (TUSCANY-2164) binding.ws generate different endpoint URI according to the count services of implementation
binding.ws generate different endpoint URI according to the count services of implementation - Key: TUSCANY-2164 URL: https://issues.apache.org/jira/browse/TUSCANY-2164 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.2 Reporter: wangfeng Priority: Minor Fix For: Java-SCA-Next A component service bound by web service,the generated webservice endpoint URI has the rule like invoking service. If the implementation only supply one service,the webservice endpoint URI is '/componentname'. If the implementation supply multiple services,the endpoint URI is '/componentname/servicename'. But I have a scenario like this:I have a implementation only included one service and put it to web service and the web service endpoint URL has been used by customer.If I add another service on this implementation,I must notify my customer the endpoint URL has been changed,but this is not needed. Thus I think if the implementaion has only one service,the endpoint URI should be '/componentname/servicename' too. If do this,only need to modify the class CompositeConfigurationBuilderImpl and set the flag 'includeBindingName' always true.If do so,some samples will be modified too. -- 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-2074) Component Service not coming up.
[ https://issues.apache.org/jira/browse/TUSCANY-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582886#action_12582886 ] wangfeng commented on TUSCANY-2074: --- In your sample,there are three places to init the scadomain. If you use the TuscanyServletFilter,the filter will init the scadomain and not need to init too. You can get SCADomain instance through application.getAttribute(org.apache.tuscany.sca.SCADomain) in jsp or servletContext.setAttribute(org.apache.tuscany.sca.SCADomain) in servlet. There is a sample in tuscany sample dir calculator-ws-webapp. Component Service not coming up. Key: TUSCANY-2074 URL: https://issues.apache.org/jira/browse/TUSCANY-2074 Project: Tuscany Issue Type: Test Components: Java SCA Tomcat Integration Affects Versions: Java-SCA-1.1 Environment: Windows , Tomcat 5.5 , Apache tuscany 1.1 , Java 5.0 Reporter: Sandeep Raman Priority: Critical Fix For: Java-SCA-Next Attachments: src.zip, two-ws-reference.jar, TwoWS.war Original Estimate: 72h Remaining Estimate: 72h summary of the Issue: I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page contentType=text/html;charset=UTF-8 language=java % % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % and the Runtime.composite is as follows: component name=TwoWSService implementation.java class=eai.Compose / service name=Compose interface=http://eai#wsdl.interface(TwoWSService) / binding.ws uri=http://localhost:8080/TwoWSService; / /service /component Now I create a war of all my Java classes , wsdl , composite files and with the default.jsp as the default run target. This war gets deployed in tomcat and the jsp page comes up. It creates a new instance of Runtime.composite too , but it doesnt seem to be starting the component service which i have mentioned in the composite file : binding.ws uri=http://localhost:8080/TwoWSService; /. -- Following Mails explain the scenario:: I see everything in console, like INFO: initContextPath: /TwoWS INFO: Added Servlet mapping: /TwoWSService Even if i try to Run my low lying services which i am composing it Runs fine and can see the output in the console.. The issue is the wsdl url which i need to publish and not able to find it anywhere. As per the samples , in my case http://localhost:8080/TwoWS/TwoWSService?wsdl should point to my wsdl, but tht doesnt seem to exist Regards Sandeep ant elder [EMAIL PROTECTED] wrote on 03/11/2008 05:03:44 PM: A difference between this and the calculator sample is the way the jsp gets the SCADomain object, the Tuscany jsp samples do: % SCADomain scaDomain = (SCADomain) application.getAttribute( org.apache.tuscany.sca.SCADomain); CalculatorService calculatorService = (CalculatorService)scaDomain.getService(CalculatorService.class, CalculatorServiceComponent); % whereas this code does: % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % I've never tried that so i don't know if it will work. If Tuscany is activating the WS endpoint you should see the messages on the tomcat console about it, for example, with the calculator ws sample you see: INFO: ContextPath: /sample-calculator-ws-webapp and INFO: Added Servlet mapping: /AddServiceComponent so you can add those and you tomcat host and port to get http://localhost:8080//sample-calculator-ws-webapp/AddServiceComponent You can test thats working by appending ?wsdl to that and url and entering it in a browser which should return the wsdl document for the service. If you don't see the above messages then something is going wrong and the WS endpoint is not being registered correctly. ...ant On Tue, Mar 11, 2008 at 11:07 AM, Sandeep Raman [EMAIL PROTECTED] wrote: Hi, I have done pretty much in the same way as the sample. i need to see my wsdl , my component service which is running . I am not able to figure out the URL for the wsdl file. I am stuck up there, since all my external requests need this wsdl URL to process, any help or suggestion will be highly appreciated Regards Sandeep Raman ant elder
[jira] Created: (TUSCANY-2141) If the composite has a cyclic include,throw an OutOfMemory exception
If the composite has a cyclic include,throw an OutOfMemory exception Key: TUSCANY-2141 URL: https://issues.apache.org/jira/browse/TUSCANY-2141 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Reporter: wangfeng Fix For: Java-SCA-1.2 If the composite has a cyclic include,tuscany will throw an OutOfMemory exception when parsing the include. Demo1Composite.composite composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://sample; xmlns:sample=http://sample; name=Demo1Composite include name=sample:Demo2Composite/ /composite Demo2Composite.composite composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://sample; xmlns:sample=http://sample; name=Demo2Composite include name=sample:Demo1Composite/ /composite -- 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-2141) If the composite has a cyclic include,throw an OutOfMemory exception
[ https://issues.apache.org/jira/browse/TUSCANY-2141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-2141: -- Attachment: testcase.zip diff.txt The patch will detect the cyclic state. If found,logging an warning. If the composite has a cyclic include,throw an OutOfMemory exception Key: TUSCANY-2141 URL: https://issues.apache.org/jira/browse/TUSCANY-2141 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.2 Reporter: wangfeng Fix For: Java-SCA-1.2 Attachments: diff.txt, testcase.zip If the composite has a cyclic include,tuscany will throw an OutOfMemory exception when parsing the include. Demo1Composite.composite composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://sample; xmlns:sample=http://sample; name=Demo1Composite include name=sample:Demo2Composite/ /composite Demo2Composite.composite composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://sample; xmlns:sample=http://sample; name=Demo2Composite include name=sample:Demo1Composite/ /composite -- 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-2095) Change attribute element to type on wsdl part element,throws an error.
Change attribute element to type on wsdl part element,throws an error. -- Key: TUSCANY-2095 URL: https://issues.apache.org/jira/browse/TUSCANY-2095 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: sun jdk1.5.09 winxp Reporter: wangfeng Fix For: Java-SCA-1.2 I run the sample helloworld-ws-service and it works fine,but I modify the wsdl file changing the element attribute to type attribute on part element,throws an error. wsdl:message name=getGreetingsRequest wsdl:part name=parameters element=tns:getGreetings/ /wsdl:message wsdl:message name=getGreetingsResponse wsdl:part name=parameters element=tns:getGreetingsResponse/ /wsdl:message To wsdl:message name=getGreetingsRequest wsdl:part type=xsd:string name=parameters/ /wsdl:message wsdl:message name=getGreetingsResponse wsdl:part type=xsd:string name=parameters/ /wsdl:message Is this a bug or a axis's bug? Exception in thread main org.osoa.sca.ServiceRuntimeException: java.lang.RuntimeException: org.apache.axis2.AxisFault: No element type is defined for message getGreetingsRequest at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:264) at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.java:69) at helloworld.HelloWorldServer.main(HelloWorldServer.java:33) Caused by: java.lang.RuntimeException: org.apache.axis2.AxisFault: No element type is defined for message getGreetingsRequest at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.start(Axis2ServiceProvider.java:289) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.start(Axis2ServiceBindingProvider.java:94) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:520) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:226) at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.init(DefaultSCADomain.java:109) at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCADomain.java:231) ... 2 more Caused by: org.apache.axis2.AxisFault: No element type is defined for message getGreetingsRequest at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:291) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.createWSDLAxisService(Axis2ServiceProvider.java:512) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.createAxisService(Axis2ServiceProvider.java:427) at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.start(Axis2ServiceProvider.java:235) ... 7 more Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException: No element type is defined for message getGreetingsRequest at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameReference(WSDL11ToAxisServiceBuilder.java:1106) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameReference(WSDL11ToAxisServiceBuilder.java:1036) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBinding(WSDL11ToAxisServiceBuilder.java:536) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoint(WSDL11ToAxisServiceBuilder.java:422) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpoints(WSDL11ToAxisServiceBuilder.java:377) at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateService(WSDL11ToAxisServiceBuilder.java:281) ... 10 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] Updated: (TUSCANY-2066) Modify the sample 'ws-void-args-return',return a null javabean result,throw a NullPointerException
[
https://issues.apache.org/jira/browse/TUSCANY-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangfeng updated TUSCANY-2066:
--
Attachment: voidtest.zip
This is the modified test case.
Modify the sample 'ws-void-args-return',return a null javabean result,throw a
NullPointerException
--
Key: TUSCANY-2066
URL: https://issues.apache.org/jira/browse/TUSCANY-2066
Project: Tuscany
Issue Type: Bug
Components: Java SCA Axis Binding Extension
Affects Versions: Java-SCA-1.1
Environment: sun jdk1.5.09,windows xp
Reporter: wangfeng
Fix For: Java-SCA-Next
Attachments: voidtest.zip
I run the sample 'ws-void-args-return',it's ok.
But when I added a get javaBean method and return the null result,the example
throw a NullPointerException.
public Bean getNullBean(){
return null;
}
org.apache.tuscany.sca.databinding.TransformationException:
java.lang.NullPointerException
org.osoa.sca.ServiceRuntimeException:
org.apache.tuscany.sca.databinding.TransformationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:123)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:89)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:83)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:135)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:641)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:68)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:835)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:641)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
at org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.java:61)
at
org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:214)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.tuscany.sca.databinding.TransformationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.core.databinding.transformers.Output2OutputTransformer.transform(Output2OutputTransformer.java:199)
at
org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:73)
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:186)
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:169)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:114)
... 29 more
Caused by: java.lang.NullPointerException
at
org.apache.tuscany.sca.databinding.javabeans.JavaBean2XMLTransformer.transform(JavaBean2XMLTransformer.java:72)
at
[jira] Created: (TUSCANY-2066) Modify the sample 'ws-void-args-return',return a null javabean result,throw a NullPointerException
Modify the sample 'ws-void-args-return',return a null javabean result,throw a
NullPointerException
--
Key: TUSCANY-2066
URL: https://issues.apache.org/jira/browse/TUSCANY-2066
Project: Tuscany
Issue Type: Bug
Components: Java SCA Axis Binding Extension
Affects Versions: Java-SCA-1.1
Environment: sun jdk1.5.09,windows xp
Reporter: wangfeng
Fix For: Java-SCA-Next
I run the sample 'ws-void-args-return',it's ok.
But when I added a get javaBean method and return the null result,the example
throw a NullPointerException.
public Bean getNullBean(){
return null;
}
org.apache.tuscany.sca.databinding.TransformationException:
java.lang.NullPointerException
org.osoa.sca.ServiceRuntimeException:
org.apache.tuscany.sca.databinding.TransformationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:123)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:89)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:83)
at
org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:135)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:641)
at
org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:68)
at
org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
at
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:835)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:641)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:368)
at org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.java:61)
at
org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:214)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: org.apache.tuscany.sca.databinding.TransformationException:
java.lang.NullPointerException
at
org.apache.tuscany.sca.core.databinding.transformers.Output2OutputTransformer.transform(Output2OutputTransformer.java:199)
at
org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:73)
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:186)
at
org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:169)
at
org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:114)
... 29 more
Caused by: java.lang.NullPointerException
at
org.apache.tuscany.sca.databinding.javabeans.JavaBean2XMLTransformer.transform(JavaBean2XMLTransformer.java:72)
at
org.apache.tuscany.sca.databinding.axiom.Exception2OMElement.transform(Exception2OMElement.java:48)
at
org.apache.tuscany.sca.databinding.axiom.Exception2OMElement.transform(Exception2OMElement.java:1)
at
[jira] Created: (TUSCANY-1756) Using EmbeddedSCADomain to deploy two contribution error
Using EmbeddedSCADomain to deploy two contribution error
Key: TUSCANY-1756
URL: https://issues.apache.org/jira/browse/TUSCANY-1756
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-1.0
Environment: jdk 1.5.01,winxp
Reporter: wangfeng
Fix For: Java-SCA-1.0
I use EmbeddedSCADomain to deploy two contribution,one contribution
ready(build,activate,start) ,after that deploy the other contribution,get an
exception as below:
java.lang.IllegalStateException: Scope must be in UNINITIALIZED or STOPPED
state [4]
at
org.apache.tuscany.sca.core.scope.AbstractScopeContainer.start(AbstractScopeContainer.java:118)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:489)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:427)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:478)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:427)
at test.ContributionTestCase.setUp(ContributionTestCase.java:79)
at junit.framework.TestCase.runBare(TestCase.java:128)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:228)
at junit.framework.TestSuite.run(TestSuite.java:223)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
and also when the scopeContainer stop,get an similar exception too.
java.lang.IllegalStateException: Scope in wrong state [6]
at
org.apache.tuscany.sca.core.scope.AbstractScopeContainer.stop(AbstractScopeContainer.java:136)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:552)
at
org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:436)
at test.ContributionTestCase.tearDown(ContributionTestCase.java:106)
at junit.framework.TestCase.runBare(TestCase.java:136)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:120)
at junit.framework.TestSuite.runTest(TestSuite.java:228)
at junit.framework.TestSuite.run(TestSuite.java:223)
at
org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128)
at
org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
my java snippet:
ClassLoader cl = getClass().getClassLoader();
EmbeddedSCADomain domain = new EmbeddedSCADomain(cl, http://localhost;);
domain.start();
ContributionService contributionService = domain.getContributionService();
Contribution helloContribution =
contributionService.contribute(http://import-export/export-composite;,
helloContribution_URL, false);
for (Composite deployable : helloContribution.getDeployables()) {
domain.getDomainComposite().getIncludes().add(deployable);
domain.getCompositeBuilder().build(deployable);
}
for (Composite deployable : helloContribution.getDeployables()) {
domain.getCompositeActivator().activate(deployable);
domain.getCompositeActivator().start(deployable);
}
Contribution helloWorldContribution_one =
contributionService.contribute(http://import-export/helloworld_one;,
helloWorldContribution_one_URL, false);
for (Composite deployable : helloWorldContribution_one.getDeployables()) {
[jira] Updated: (TUSCANY-1756) Using EmbeddedSCADomain to deploy two contribution error
[ https://issues.apache.org/jira/browse/TUSCANY-1756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1756: -- Attachment: patch.diff testcase.zip The patch add the check of component's start flag. If the component already started,the method of start component return directly,and if the component not started,the method of stop component return directly too.when stop component,also check the stop flag of component's scopeContainer ,if the scopeContainer has stopped,return directly . To run the testcase,please modify the field value of contribution_Dir in ContributionTestCase.java to fit your contribution source dir. Using EmbeddedSCADomain to deploy two contribution error Key: TUSCANY-1756 URL: https://issues.apache.org/jira/browse/TUSCANY-1756 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-1.0 Environment: jdk 1.5.01,winxp Reporter: wangfeng Fix For: Java-SCA-1.0 Attachments: patch.diff, testcase.zip I use EmbeddedSCADomain to deploy two contribution,one contribution ready(build,activate,start) ,after that deploy the other contribution,get an exception as below: java.lang.IllegalStateException: Scope must be in UNINITIALIZED or STOPPED state [4] at org.apache.tuscany.sca.core.scope.AbstractScopeContainer.start(AbstractScopeContainer.java:118) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:489) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:427) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:478) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(CompositeActivatorImpl.java:427) at test.ContributionTestCase.setUp(ContributionTestCase.java:79) at junit.framework.TestCase.runBare(TestCase.java:128) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:228) at junit.framework.TestSuite.run(TestSuite.java:223) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) and also when the scopeContainer stop,get an similar exception too. java.lang.IllegalStateException: Scope in wrong state [6] at org.apache.tuscany.sca.core.scope.AbstractScopeContainer.stop(AbstractScopeContainer.java:136) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:552) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.stop(CompositeActivatorImpl.java:436) at test.ContributionTestCase.tearDown(ContributionTestCase.java:106) at junit.framework.TestCase.runBare(TestCase.java:136) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:228) at junit.framework.TestSuite.run(TestSuite.java:223) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) my java snippet: ClassLoader cl = getClass().getClassLoader(); EmbeddedSCADomain domain = new EmbeddedSCADomain(cl, http://localhost;); domain.start(); ContributionService contributionService =
[jira] Updated: (TUSCANY-1718) One contribution exported it's namespace and was imported by two contribution ,gets assembly error.
[ https://issues.apache.org/jira/browse/TUSCANY-1718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1718: -- Attachment: ContributionTestCase.zip If you run the testcase,please modify the field's value in ContributionTestCase.java to fit the contribution source dir. One contribution exported it's namespace and was imported by two contribution ,gets assembly error. --- Key: TUSCANY-1718 URL: https://issues.apache.org/jira/browse/TUSCANY-1718 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: winxp,eclipse,jdk1.5.09 Reporter: wangfeng Fix For: Java-SCA-1.0 Attachments: ContributionTestCase.zip My test case is that: 1.Contribution 'hello' export it's namespache 'http://hello'. 2.Contribution 'world_one' import the 'hello' contribution's namespache. 3.Contribution 'world_two' import the 'hello' contribution's namespache too. when run the testcase,get a fatal error as below: org.apache.tuscany.sca.core.assembly.ActivationException: java.lang.IllegalStateException: Reference interface not remoteable for component: HelloWorldServiceComponent_two and reference: helloServiceRef at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:739) at test.ContributionTestCase.setUp(ContributionTestCase.java:82) at junit.framework.TestCase.runBare(TestCase.java:128) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:228) at junit.framework.TestSuite.run(TestSuite.java:223) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:128) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:460) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:673) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:386) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) Caused by: java.lang.IllegalStateException: Reference interface not remoteable for component: HelloWorldServiceComponent_two and reference: helloServiceRef at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.isTargetRemote(RuntimeSCAReferenceBindingProvider.java:124) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCAReferenceBindingProvider.init(RuntimeSCAReferenceBindingProvider.java:85) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingProviderFactory.createReferenceBindingProvider(RuntimeSCABindingProviderFactory.java:59) at org.apache.tuscany.sca.binding.sca.impl.RuntimeSCABindingProviderFactory.createReferenceBindingProvider(RuntimeSCABindingProviderFactory.java:1) at org.apache.tuscany.sca.provider.DefaultProviderFactoryExtensionPoint$LazyBindingProviderFactory.createReferenceBindingProvider(DefaultProviderFactoryExtensionPoint.java:189) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.addReferenceBindingProvider(CompositeActivatorImpl.java:179) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:135) at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.activate(CompositeActivatorImpl.java:735) ... 14 more but when I remove the contribution 'world_one' or contribution 'world_two',the testcase works fine. -- 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-1671) Building two composite ,one implemented by the other, get a warning
Building two composite ,one implemented by the other, get a warning --- Key: TUSCANY-1671 URL: https://issues.apache.org/jira/browse/TUSCANY-1671 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Environment: WinXP,Eclipse 3.2 Reporter: wangfeng Fix For: Java-SCA-1.0 In my sca domain,there are two contributions which named Contribution_A and Contribution_B and the two contributions is deployable too. In Contribution_B,there is a component which implemented by a composite in Contribution_A.And the Contribution_A's composite build first,and then build the Contribution_B's composite. The conposite building processor will put a '$promoted$.' service on the component when the component service is promoted to a composite service.When building the Contribution_B's component which is implemented by the composite in Contribution_A, the component implementation services will not match the component type service,the component is implemented by the composite in Contribution_A,so print an warning as below: There is an warning message on the console: 2007-9-6 16:26:33 org.apache.tuscany.sca.assembly.builder.impl.CompositeBuilderImpl$1 problem Warn: [WARNING] Service not found for component service: HelloServiceComponent/$promoted$.HelloService null my composite on Contribution_A: ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://www.osoa.org/xmlns/sca/1.0; name=hello service name=HelloService promote=HelloServiceComponent/ component name=HelloServiceComponent implementation.java class=com.demo.HelloImpl / /component /composite my composite on Contribution_B: ?xml version=1.0 encoding=UTF-8? composite xmlns=http://www.osoa.org/xmlns/sca/1.0; targetNamespace=http://www.osoa.org/xmlns/sca/1.0; name=world service name=WorldService promote=WorldServiceComponent/ component name=WorldServiceComponent implementation.java class=com.demo.WorldImpl / reference name=hello target=WorldService_Hello/ /component component name=WorldService_Hello implementation.composite name=hello/ /component /composite -- 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-1492) Support implemental class not only interface when get a service
[ https://issues.apache.org/jira/browse/TUSCANY-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517421 ] wangfeng commented on TUSCANY-1492: --- Thank Raymond for applying the patch. Support implemental class not only interface when get a service --- Key: TUSCANY-1492 URL: https://issues.apache.org/jira/browse/TUSCANY-1492 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.91 Environment: JDK1.5.09,winXP Reporter: wangfeng Priority: Minor Fix For: Java-SCA-0.91 Attachments: patch.txt, TestCase_Calculator.zip when we get a service,we always generate a proxy on the service by using the jdk proxy class, so we must provide a interface to get a service. I provide a patch to remove the control. This patch not only support the interface,but also support the implemental class when getting a service.when the class isn't a interface,using the cglib to generate a proxy and using jdk proxy when the class is a interface. -- 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-1492) Support implemental class not only interface when get a service
Support implemental class not only interface when get a service --- Key: TUSCANY-1492 URL: https://issues.apache.org/jira/browse/TUSCANY-1492 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.91 Environment: JDK1.5.09,winXP Reporter: wangfeng Priority: Minor Fix For: Java-SCA-0.91 when we get a service,we always generate a proxy on the service by using the jdk proxy class, so we must provide a interface to get a service. I provide a patch to remove the control. This patch not only support the interface,but also support the implemental class when getting a service.when the class isn't a interface,using the cglib to generate a proxy and using jdk proxy when the class is a interface. -- 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-1492) Support implemental class not only interface when get a service
[ https://issues.apache.org/jira/browse/TUSCANY-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1492: -- Attachment: TestCase_Calculator.zip patch.txt This patch includes two new added files and two modified files. CglibProxyService.java -- generate the proxy with cglib ProxyServiceExtensionPoint.java -- dispatch the action to create a proxy,according to the class type JavaRuntimeModuleActivator.java -- modify the JDKProxyService type to it's interface type of ProxyFactory ReallySmallRuntimeBuilder.java -- modify the ProxyFactory definition to the class of ProxyServiceExtensionPoint The testcase includes the calculator sample,and remove all the interface's definition. Support implemental class not only interface when get a service --- Key: TUSCANY-1492 URL: https://issues.apache.org/jira/browse/TUSCANY-1492 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.91 Environment: JDK1.5.09,winXP Reporter: wangfeng Priority: Minor Fix For: Java-SCA-0.91 Attachments: patch.txt, TestCase_Calculator.zip when we get a service,we always generate a proxy on the service by using the jdk proxy class, so we must provide a interface to get a service. I provide a patch to remove the control. This patch not only support the interface,but also support the implemental class when getting a service.when the class isn't a interface,using the cglib to generate a proxy and using jdk proxy when the class is a interface. -- 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-1473) Define component's service with interface.wsdl ,throws 'No matching operation' error.
[ https://issues.apache.org/jira/browse/TUSCANY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514469 ] wangfeng commented on TUSCANY-1473: --- Thank Raymond for providing the patch. I think this resolution is not perfect. I read the code and found this getPhysical method always returned 'Object' class type.We called the isAssignableFrom method to match the input type,thus what ever type was inputed,this method always returned true. Maybe modifing the getPhysical method's return type which should be the type defined in the WSDL file would be better. Define component's service with interface.wsdl ,throws 'No matching operation' error. - Key: TUSCANY-1473 URL: https://issues.apache.org/jira/browse/TUSCANY-1473 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-0.91 Environment: Windows XP Reporter: wangfeng Assignee: Raymond Feng Fix For: Java-SCA-Next Attachments: testcase.zip I define the component's service with interface.java,the sample runs fine. but when I modify the component's service with interface.wsdl,the sample throws an exception. The throwable stack is : Exception in thread main java.lang.IllegalArgumentException: No matching operation is found: public abstract java.lang.String helloworld.HelloWorldService.getGreetings(java.lang.String) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:69) at $Proxy10.getGreetings(Unknown Source) at helloworld.HelloWorldClient.main(HelloWorldClient.java:33) I look into the code,found the invoke mothod's input type is 'String',but the method which name is operation.getInputType().getLogical().get(i).getPhysical() on the SourceOperation of the InvocationChain is always return 'Object' type,so can't find an operation to match. -- 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] Reopened: (TUSCANY-1473) Define component's service with interface.wsdl ,throws 'No matching operation' error.
[ https://issues.apache.org/jira/browse/TUSCANY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng reopened TUSCANY-1473: --- Thank Raymond for providing the patch. I think this resolution is not perfect. I read the code and found this getPhysical method always returned 'Object' class type.We called the isAssignableFrom method to match the input type,thus what ever type was inputed,this method always returned true. Maybe modifing the getPhysical method's return type which should be the type defined in the WSDL file would be better. Define component's service with interface.wsdl ,throws 'No matching operation' error. - Key: TUSCANY-1473 URL: https://issues.apache.org/jira/browse/TUSCANY-1473 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-0.91 Environment: Windows XP Reporter: wangfeng Assignee: Raymond Feng Fix For: Java-SCA-Next Attachments: testcase.zip I define the component's service with interface.java,the sample runs fine. but when I modify the component's service with interface.wsdl,the sample throws an exception. The throwable stack is : Exception in thread main java.lang.IllegalArgumentException: No matching operation is found: public abstract java.lang.String helloworld.HelloWorldService.getGreetings(java.lang.String) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:69) at $Proxy10.getGreetings(Unknown Source) at helloworld.HelloWorldClient.main(HelloWorldClient.java:33) I look into the code,found the invoke mothod's input type is 'String',but the method which name is operation.getInputType().getLogical().get(i).getPhysical() on the SourceOperation of the InvocationChain is always return 'Object' type,so can't find an operation to match. -- 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-1473) Define component's service with interface.wsdl ,throws 'No matching operation' error.
[ https://issues.apache.org/jira/browse/TUSCANY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1473: -- Comment: was deleted Define component's service with interface.wsdl ,throws 'No matching operation' error. - Key: TUSCANY-1473 URL: https://issues.apache.org/jira/browse/TUSCANY-1473 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-0.91 Environment: Windows XP Reporter: wangfeng Assignee: Raymond Feng Fix For: Java-SCA-Next Attachments: testcase.zip I define the component's service with interface.java,the sample runs fine. but when I modify the component's service with interface.wsdl,the sample throws an exception. The throwable stack is : Exception in thread main java.lang.IllegalArgumentException: No matching operation is found: public abstract java.lang.String helloworld.HelloWorldService.getGreetings(java.lang.String) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:69) at $Proxy10.getGreetings(Unknown Source) at helloworld.HelloWorldClient.main(HelloWorldClient.java:33) I look into the code,found the invoke mothod's input type is 'String',but the method which name is operation.getInputType().getLogical().get(i).getPhysical() on the SourceOperation of the InvocationChain is always return 'Object' type,so can't find an operation to match. -- 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-1473) Define component's service with interface.wsdl ,throws 'No matching operation' error.
Define component's service with interface.wsdl ,throws 'No matching operation' error. - Key: TUSCANY-1473 URL: https://issues.apache.org/jira/browse/TUSCANY-1473 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-0.91 Environment: Windows XP Reporter: wangfeng Fix For: Java-SCA-Next I define the component's service with interface.java,the sample runs fine. but when I modify the component's service with interface.wsdl,the sample throws an exception. The throwable stack is : Exception in thread main java.lang.IllegalArgumentException: No matching operation is found: public abstract java.lang.String helloworld.HelloWorldService.getGreetings(java.lang.String) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:69) at $Proxy10.getGreetings(Unknown Source) at helloworld.HelloWorldClient.main(HelloWorldClient.java:33) I look into the code,found the invoke mothod's input type is 'String',but the method which name is operation.getInputType().getLogical().get(i).getPhysical() on the SourceOperation of the InvocationChain is always return 'Object' type,so can't find an operation to match. -- 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-1473) Define component's service with interface.wsdl ,throws 'No matching operation' error.
[ https://issues.apache.org/jira/browse/TUSCANY-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1473: -- Attachment: testcase.zip The testcase attachment contains five files. HelloWorldService.java The interface of component HelloWorldImpl.java The implementation of component helloworldws.composite Composite define file helloworld.wsdl Define the HelloWorldService interface whith WSDL HelloWorldClient.javaThe client to test the case Define component's service with interface.wsdl ,throws 'No matching operation' error. - Key: TUSCANY-1473 URL: https://issues.apache.org/jira/browse/TUSCANY-1473 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-0.91 Environment: Windows XP Reporter: wangfeng Fix For: Java-SCA-Next Attachments: testcase.zip I define the component's service with interface.java,the sample runs fine. but when I modify the component's service with interface.wsdl,the sample throws an exception. The throwable stack is : Exception in thread main java.lang.IllegalArgumentException: No matching operation is found: public abstract java.lang.String helloworld.HelloWorldService.getGreetings(java.lang.String) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:69) at $Proxy10.getGreetings(Unknown Source) at helloworld.HelloWorldClient.main(HelloWorldClient.java:33) I look into the code,found the invoke mothod's input type is 'String',but the method which name is operation.getInputType().getLogical().get(i).getPhysical() on the SourceOperation of the InvocationChain is always return 'Object' type,so can't find an operation to match. -- 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-1405) when the component is implemented by a composite which has multi service,occur can't find service error.
[
https://issues.apache.org/jira/browse/TUSCANY-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514085
]
wangfeng commented on TUSCANY-1405:
---
I look into the code and found the crux of this problem.
when a component is implemented by a inner composite,the composite service only
generate a promoted service named by the prefix of '$promoted$.' on the
promoted component but not generate the reference such as self reference.
so when we locate a service which really locate the reference on this
component,occur this service not found error .
I think there are two ways to solve this problem.One is generate the self
reference for every promote service on the promoted component,the other way is
when locate a service ,we search the reference name not only loop the
component's reference,but also loop the component's service.
anyone has better ideas for this?
when the component is implemented by a composite which has multi
service,occur can't find service error.
Key: TUSCANY-1405
URL: https://issues.apache.org/jira/browse/TUSCANY-1405
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-0.90
Reporter: wangfeng
Assignee: Raymond Feng
Fix For: Java-SCA-0.91
Attachments: ConmpositeImplementation.jar
I create a simple SCA application,which test composite Implementation.I
defined two composite files,one is OuterComposite.composite,the other is
InnerComposite.composite and the Innercomposite file has defined two
composite services.
when I get a service (offer a service name to the getService method) from the
component which defined in the OuterComposite file ,occur an error as below.
Exception in thread main org.osoa.sca.ServiceRuntimeException: Service not
found: TargetComponent/Service_Two
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.getService(DefaultSCADomain.java:278)
at composite.CompositeClient.main(CompositeClient.java:31)
OuterComposite.composite
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://sample;
xmlns:sample=http://sample;
name=OuterComposite
component name=TargetComponent
implementation.composite name=sample:InnerComposite/
/component
/composite
InnerComposite.composite
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://sample;
xmlns:sample=http://sample;
name=InnerComposite
service name=Service_One promote=ComponentOne
interface.java interface=composite.Target/
/service
service name=Service_Two promote=ComponentTwo
interface.java interface=composite.Target/
/service
component name=ComponentOne
implementation.java class=composite.TargetOne/
/component
component name=ComponentTwo
implementation.java class=composite.TargetTwo/
/component
/composite
Target.java
package composite;
public interface Target {
String hello(String arg);
}
TargetOne.java
package composite;
import org.osoa.sca.annotations.Service;
@Service(Target.class)
public class TargetOne implements Target {
public String hello(String arg) {
return TargetOne: Hello + arg+ !;
}
}
TargetTwo.java
package composite;
import org.osoa.sca.annotations.Service;
@Service(Target.class)
public class TargetTwo implements Target {
public String hello(String arg) {
return TargetTwo: Hello + arg + !;
}
}
CompositeClient .java
package composite;
import org.apache.tuscany.sca.host.embedded.SCADomain;
public class CompositeClient {
public static void main(String[] args) throws Exception {
SCADomain scaDomain =
SCADomain.newInstance(OuterComposite.composite);
Target target = scaDomain.getService(Target.class,
TargetComponent/Service_Two);
String res = target.hello(Wang Feng);
System.out.println(res);
scaDomain.close();
}
}
--
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-1449) The annotation 'Service' processor occurs error.
The annotation 'Service' processor occurs error. Key: TUSCANY-1449 URL: https://issues.apache.org/jira/browse/TUSCANY-1449 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.91 Reporter: wangfeng Fix For: Java-SCA-Next 1.The SCA Java Component Implementation Spec (line 21 to 121) show the annotation 'Service' value may be three ways:Java Interface,Java class,WSDL portType.But in tuscany only support Java Interface. 21 1.2.1 Service 22A component implementation based on a Java class may provide one or more services. 23The services provided by a Java-based implementation may have an interface defined in one of the 24following ways: 25 A Java interface 26 A Java class 27 A Java interface generated from a Web Services Description Language[3] (WSDL) portType 2.The SCA Java AnnotationsAndAPIs Spec (line 1635) show the annotation 'Service' can has not attributes,but the 'Service' processor in tuscany don't support this. 1635 A @Service annotation with no attributes is meaningless, it is the same as not having the annotation there 1636 at all. -- 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-1449) The annotation 'Service' processor occurs error.
[ https://issues.apache.org/jira/browse/TUSCANY-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1449: -- Attachment: ServiceProcessor.java This is the patch for 'Service' processor. Please review and apply. The annotation 'Service' processor occurs error. Key: TUSCANY-1449 URL: https://issues.apache.org/jira/browse/TUSCANY-1449 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.91 Reporter: wangfeng Fix For: Java-SCA-Next Attachments: ServiceProcessor.java 1.The SCA Java Component Implementation Spec (line 21 to 121) show the annotation 'Service' value may be three ways:Java Interface,Java class,WSDL portType.But in tuscany only support Java Interface. 21 1.2.1 Service 22A component implementation based on a Java class may provide one or more services. 23The services provided by a Java-based implementation may have an interface defined in one of the 24following ways: 25 A Java interface 26 A Java class 27 A Java interface generated from a Web Services Description Language[3] (WSDL) portType 2.The SCA Java AnnotationsAndAPIs Spec (line 1635) show the annotation 'Service' can has not attributes,but the 'Service' processor in tuscany don't support this. 1635 A @Service annotation with no attributes is meaningless, it is the same as not having the annotation there 1636 at all. -- 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-1449) The annotation 'Service' processor occurs error.
[ https://issues.apache.org/jira/browse/TUSCANY-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1449: -- Attachment: 1449.patch I am sorry for this.I have make the patch using the patch format. The patch resolve the problem which is not support java class and must has attributes on the annotation of 'Service' . The annotation 'Service' processor occurs error. Key: TUSCANY-1449 URL: https://issues.apache.org/jira/browse/TUSCANY-1449 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.91 Reporter: wangfeng Fix For: Java-SCA-Next Attachments: 1449.patch, ServiceProcessor.java 1.The SCA Java Component Implementation Spec (line 21 to 121) show the annotation 'Service' value may be three ways:Java Interface,Java class,WSDL portType.But in tuscany only support Java Interface. 21 1.2.1 Service 22A component implementation based on a Java class may provide one or more services. 23The services provided by a Java-based implementation may have an interface defined in one of the 24following ways: 25 A Java interface 26 A Java class 27 A Java interface generated from a Web Services Description Language[3] (WSDL) portType 2.The SCA Java AnnotationsAndAPIs Spec (line 1635) show the annotation 'Service' can has not attributes,but the 'Service' processor in tuscany don't support this. 1635 A @Service annotation with no attributes is meaningless, it is the same as not having the annotation there 1636 at all. -- 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-1449) The annotation 'Service' processor occurs error.
[ https://issues.apache.org/jira/browse/TUSCANY-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wangfeng updated TUSCANY-1449: -- Attachment: (was: ServiceProcessor.java) The annotation 'Service' processor occurs error. Key: TUSCANY-1449 URL: https://issues.apache.org/jira/browse/TUSCANY-1449 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-0.91 Reporter: wangfeng Fix For: Java-SCA-Next Attachments: 1449.patch 1.The SCA Java Component Implementation Spec (line 21 to 121) show the annotation 'Service' value may be three ways:Java Interface,Java class,WSDL portType.But in tuscany only support Java Interface. 21 1.2.1 Service 22A component implementation based on a Java class may provide one or more services. 23The services provided by a Java-based implementation may have an interface defined in one of the 24following ways: 25 A Java interface 26 A Java class 27 A Java interface generated from a Web Services Description Language[3] (WSDL) portType 2.The SCA Java AnnotationsAndAPIs Spec (line 1635) show the annotation 'Service' can has not attributes,but the 'Service' processor in tuscany don't support this. 1635 A @Service annotation with no attributes is meaningless, it is the same as not having the annotation there 1636 at all. -- 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-1405) when the component is implemented by a composite which has multi service,occur can't find service error.
when the component is implemented by a composite which has multi service,occur
can't find service error.
Key: TUSCANY-1405
URL: https://issues.apache.org/jira/browse/TUSCANY-1405
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-0.90
Reporter: wangfeng
Fix For: Java-SCA-0.91
I create a simple SCA application,which test composite Implementation.I defined
two composite files,one is OuterComposite.composite,the other is
InnerComposite.composite and the Innercomposite file has defined two composite
services.
when I get a service (offer a service name to the getService method) from the
component which defined in the OuterComposite file ,occur an error as below.
Exception in thread main org.osoa.sca.ServiceRuntimeException: Service not
found: TargetComponent/Service_Two
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.getService(DefaultSCADomain.java:278)
at composite.CompositeClient.main(CompositeClient.java:31)
OuterComposite.composite
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://sample;
xmlns:sample=http://sample;
name=OuterComposite
component name=TargetComponent
implementation.composite name=sample:InnerComposite/
/component
/composite
InnerComposite.composite
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://sample;
xmlns:sample=http://sample;
name=InnerComposite
service name=Service_One promote=ComponentOne
interface.java interface=composite.Target/
/service
service name=Service_Two promote=ComponentTwo
interface.java interface=composite.Target/
/service
component name=ComponentOne
implementation.java class=composite.TargetOne/
/component
component name=ComponentTwo
implementation.java class=composite.TargetTwo/
/component
/composite
Target.java
package composite;
public interface Target {
String hello(String arg);
}
TargetOne.java
package composite;
import org.osoa.sca.annotations.Service;
@Service(Target.class)
public class TargetOne implements Target {
public String hello(String arg) {
return TargetOne: Hello + arg+ !;
}
}
TargetTwo.java
package composite;
import org.osoa.sca.annotations.Service;
@Service(Target.class)
public class TargetTwo implements Target {
public String hello(String arg) {
return TargetTwo: Hello + arg + !;
}
}
CompositeClient .java
package composite;
import org.apache.tuscany.sca.host.embedded.SCADomain;
public class CompositeClient {
public static void main(String[] args) throws Exception {
SCADomain scaDomain = SCADomain.newInstance(OuterComposite.composite);
Target target = scaDomain.getService(Target.class,
TargetComponent/Service_Two);
String res = target.hello(Wang Feng);
System.out.println(res);
scaDomain.close();
}
}
--
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-1405) when the component is implemented by a composite which has multi service,occur can't find service error.
[
https://issues.apache.org/jira/browse/TUSCANY-1405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wangfeng updated TUSCANY-1405:
--
Attachment: ConmpositeImplementation.jar
when the component is implemented by a composite which has multi
service,occur can't find service error.
Key: TUSCANY-1405
URL: https://issues.apache.org/jira/browse/TUSCANY-1405
Project: Tuscany
Issue Type: Bug
Components: Java SCA Assembly Model
Affects Versions: Java-SCA-0.90
Reporter: wangfeng
Fix For: Java-SCA-0.91
Attachments: ConmpositeImplementation.jar
I create a simple SCA application,which test composite Implementation.I
defined two composite files,one is OuterComposite.composite,the other is
InnerComposite.composite and the Innercomposite file has defined two
composite services.
when I get a service (offer a service name to the getService method) from the
component which defined in the OuterComposite file ,occur an error as below.
Exception in thread main org.osoa.sca.ServiceRuntimeException: Service not
found: TargetComponent/Service_Two
at
org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.getService(DefaultSCADomain.java:278)
at composite.CompositeClient.main(CompositeClient.java:31)
OuterComposite.composite
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://sample;
xmlns:sample=http://sample;
name=OuterComposite
component name=TargetComponent
implementation.composite name=sample:InnerComposite/
/component
/composite
InnerComposite.composite
composite xmlns=http://www.osoa.org/xmlns/sca/1.0;
targetNamespace=http://sample;
xmlns:sample=http://sample;
name=InnerComposite
service name=Service_One promote=ComponentOne
interface.java interface=composite.Target/
/service
service name=Service_Two promote=ComponentTwo
interface.java interface=composite.Target/
/service
component name=ComponentOne
implementation.java class=composite.TargetOne/
/component
component name=ComponentTwo
implementation.java class=composite.TargetTwo/
/component
/composite
Target.java
package composite;
public interface Target {
String hello(String arg);
}
TargetOne.java
package composite;
import org.osoa.sca.annotations.Service;
@Service(Target.class)
public class TargetOne implements Target {
public String hello(String arg) {
return TargetOne: Hello + arg+ !;
}
}
TargetTwo.java
package composite;
import org.osoa.sca.annotations.Service;
@Service(Target.class)
public class TargetTwo implements Target {
public String hello(String arg) {
return TargetTwo: Hello + arg + !;
}
}
CompositeClient .java
package composite;
import org.apache.tuscany.sca.host.embedded.SCADomain;
public class CompositeClient {
public static void main(String[] args) throws Exception {
SCADomain scaDomain =
SCADomain.newInstance(OuterComposite.composite);
Target target = scaDomain.getService(Target.class,
TargetComponent/Service_Two);
String res = target.hello(Wang Feng);
System.out.println(res);
scaDomain.close();
}
}
--
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]
