[jira] Resolved: (TUSCANY-198) Rename ComponentInfo to ComponentType
[ http://issues.apache.org/jira/browse/TUSCANY-198?page=all ] Jean-Sebastien Delfino resolved TUSCANY-198: Resolution: Fixed Fixed in revision r404728. Rename ComponentInfo to ComponentType - Key: TUSCANY-198 URL: http://issues.apache.org/jira/browse/TUSCANY-198 Project: Tuscany Type: Bug Components: Java SCA Model Versions: M1 Reporter: Jean-Sebastien Delfino Assignee: Jean-Sebastien Delfino Fix For: M1 At some point I renamed ComponentType to ComponentInfo in the assembly model. This is confusing and doesn't match the spec anymore. ComponentInfo should be renamed back to ComponentType. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-297) Various cleanups and enhancements to the website
[ http://issues.apache.org/jira/browse/TUSCANY-297?page=all ] Jean-Sebastien Delfino updated TUSCANY-297: --- Fix Version: M1 Various cleanups and enhancements to the website Key: TUSCANY-297 URL: http://issues.apache.org/jira/browse/TUSCANY-297 Project: Tuscany Type: Improvement Components: Website Versions: M1 Reporter: haleh mahbod Fix For: M1 Re-arranged the main page index to improve finding information. Added developer section and also added coding guidelines, JavaDocs. updated 'how to update website' instructions -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-313) Tuscany SCA and SDO plugins attempt to generate code on incorrect goals
[ http://issues.apache.org/jira/browse/TUSCANY-313?page=all ] Jean-Sebastien Delfino updated TUSCANY-313: --- Fix Version: M1 Version: M1 Tuscany SCA and SDO plugins attempt to generate code on incorrect goals --- Key: TUSCANY-313 URL: http://issues.apache.org/jira/browse/TUSCANY-313 Project: Tuscany Type: Bug Components: Java SCA Tools, Java SDO Tools Versions: M1 Reporter: Jean-Sebastien Delfino Priority: Minor Fix For: M1 The tuscany SCA and SDO plugins attempt to generate code on incorrect goals, for example the eclipse:eclipse goal. To reproduce the problem, from the tuscany/java directory do the following: mvn clean eclipse:eclipse The SCA and SDO maven plugins will generate Java interfaces for services and SDO classes. They shouldn't. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TUSCANY-315) Many updates to website to improve content
Many updates to website to improve content --- Key: TUSCANY-315 URL: http://issues.apache.org/jira/browse/TUSCANY-315 Project: Tuscany Type: Improvement Components: Website Versions: M1 Environment: All Reporter: haleh mahbod Fix For: M1 This defect encompasses many other ones that need to be linked to it. Including 290 and 160. Improvements with this fix: src/site.xml - modified to provide a more natural information flow navigation src/xdoc/codeguidelines.xml - added. this includes all coding guidelines. Including indentation, exception handling (input from Jim Marino), place holder for logging and package naming. src/xdoc/news - to include news on javaone release src/xdoc/howtobuildsite - enhanced to make the instructions clearer src/xdoc/javadocinfo - added as a place holder to point to java doc (to be provided by sebastien) src/xdoc/projectjava.xml - entry point to Java projects. It holds instructions for system setup, project checkout and build, java doc, code guidelines, etc. src/xdoc/projectC++ - place holder to contain the same info as projectjava.xml except for C++ src/xdoc/installjava.xml - cleaned up to have correct info src/xdoc/download.xml - cleaned up to have correct info src/xdoc/getinvolved.xml - modified to point to projectjava and projectC++. some of the info from here was relevant to projectjava and is moved. getinvolved.xml is now a generic getInvovled for Java and C++. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-315) Many updates to website to improve content
[ http://issues.apache.org/jira/browse/TUSCANY-315?page=all ] haleh mahbod updated TUSCANY-315: - Attachment: WebsiteFixes.zip Please let me know if the zip is not usable. I have 10 files that are changed. All mentioned in the defect comment. Many updates to website to improve content --- Key: TUSCANY-315 URL: http://issues.apache.org/jira/browse/TUSCANY-315 Project: Tuscany Type: Improvement Components: Website Versions: M1 Environment: All Reporter: haleh mahbod Assignee: haleh mahbod Fix For: M1 Attachments: WebsiteFixes.zip This defect encompasses many other ones that need to be linked to it. Including 290 and 160. Improvements with this fix: src/site.xml - modified to provide a more natural information flow navigation src/xdoc/codeguidelines.xml - added. this includes all coding guidelines. Including indentation, exception handling (input from Jim Marino), place holder for logging and package naming. src/xdoc/news - to include news on javaone release src/xdoc/howtobuildsite - enhanced to make the instructions clearer src/xdoc/javadocinfo - added as a place holder to point to java doc (to be provided by sebastien) src/xdoc/projectjava.xml - entry point to Java projects. It holds instructions for system setup, project checkout and build, java doc, code guidelines, etc. src/xdoc/projectC++ - place holder to contain the same info as projectjava.xml except for C++ src/xdoc/installjava.xml - cleaned up to have correct info src/xdoc/download.xml - cleaned up to have correct info src/xdoc/getinvolved.xml - modified to point to projectjava and projectC++. some of the info from here was relevant to projectjava and is moved. getinvolved.xml is now a generic getInvovled for Java and C++. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TUSCANY-316) ArrayIndexOutOfBounds exception running SOAP builders round 2 interop test case
ArrayIndexOutOfBounds exception running SOAP builders round 2 interop test case --- Key: TUSCANY-316 URL: http://issues.apache.org/jira/browse/TUSCANY-316 Project: Tuscany Type: Bug Components: Java SCA Axis Binding Versions: M1 Reporter: Jean-Sebastien Delfino Priority: Critical Fix For: M1 To reproduce the problem run the test case under java/testing/interop/webserviceSOAPRound2. You will get the following exception: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.apache.tuscany.binding.axis2.builder.ExternalWebServiceBuilder.createOperationInvokers(ExternalWebServiceBuilder.java:122) at org.apache.tuscany.binding.axis2.builder.ExternalWebServiceBuilder.createExternalServiceContextFactory(ExternalWebServiceBuilder.java:75) at org.apache.tuscany.core.extension.ExternalServiceBuilderSupport.build(ExternalServiceBuilderSupport.java:73) at org.apache.tuscany.core.builder.impl.AssemblyVisitorImpl.visit(AssemblyVisitorImpl.java:58) at org.apache.tuscany.model.assembly.impl.AssemblyObjectImpl.accept(AssemblyObjectImpl.java:39) at org.apache.tuscany.model.assembly.impl.ExtensibleImpl.accept(ExtensibleImpl.java:66) at org.apache.tuscany.model.assembly.impl.ExternalServiceImpl.accept(ExternalServiceImpl.java:102) at org.apache.tuscany.model.assembly.impl.AssemblyObjectImpl.accept(AssemblyObjectImpl.java:50) at org.apache.tuscany.model.assembly.impl.CompositeImpl.accept(CompositeImpl.java:336) at org.apache.tuscany.model.assembly.impl.ModuleImpl.accept(ModuleImpl.java:97) at org.apache.tuscany.model.assembly.impl.ComponentImpl.accept(ComponentImpl.java:206) at org.apache.tuscany.core.builder.impl.AssemblyVisitorImpl.start(AssemblyVisitorImpl.java:45) at org.apache.tuscany.core.runtime.RuntimeContextImpl.build(RuntimeContextImpl.java:161) at org.apache.tuscany.core.context.impl.AbstractCompositeContext.registerModelObject(AbstractCompositeContext.java:278) at org.apache.tuscany.core.client.BootstrapHelper.registerModule(BootstrapHelper.java:133) at org.apache.tuscany.core.client.TuscanyRuntime.init(TuscanyRuntime.java:104) at org.apache.tuscany.core.client.TuscanyRuntime.init(TuscanyRuntime.java:67) at org.apache.tuscany.test.interop.client.InteropTestDocLitTestCase.setUp(InteropTestDocLitTestCase.java:55) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-316) ArrayIndexOutOfBounds exception running SOAP builders round 2 interop test case
[ http://issues.apache.org/jira/browse/TUSCANY-316?page=all ] Jean-Sebastien Delfino updated TUSCANY-316: --- Attachment: org.apache.tuscany.test.interop.client.InteropTestDocLitTestCase.txt Attaching the surefire report. ArrayIndexOutOfBounds exception running SOAP builders round 2 interop test case --- Key: TUSCANY-316 URL: http://issues.apache.org/jira/browse/TUSCANY-316 Project: Tuscany Type: Bug Components: Java SCA Axis Binding Versions: M1 Reporter: Jean-Sebastien Delfino Priority: Critical Fix For: M1 Attachments: org.apache.tuscany.test.interop.client.InteropTestDocLitTestCase.txt To reproduce the problem run the test case under java/testing/interop/webserviceSOAPRound2. You will get the following exception: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at org.apache.tuscany.binding.axis2.builder.ExternalWebServiceBuilder.createOperationInvokers(ExternalWebServiceBuilder.java:122) at org.apache.tuscany.binding.axis2.builder.ExternalWebServiceBuilder.createExternalServiceContextFactory(ExternalWebServiceBuilder.java:75) at org.apache.tuscany.core.extension.ExternalServiceBuilderSupport.build(ExternalServiceBuilderSupport.java:73) at org.apache.tuscany.core.builder.impl.AssemblyVisitorImpl.visit(AssemblyVisitorImpl.java:58) at org.apache.tuscany.model.assembly.impl.AssemblyObjectImpl.accept(AssemblyObjectImpl.java:39) at org.apache.tuscany.model.assembly.impl.ExtensibleImpl.accept(ExtensibleImpl.java:66) at org.apache.tuscany.model.assembly.impl.ExternalServiceImpl.accept(ExternalServiceImpl.java:102) at org.apache.tuscany.model.assembly.impl.AssemblyObjectImpl.accept(AssemblyObjectImpl.java:50) at org.apache.tuscany.model.assembly.impl.CompositeImpl.accept(CompositeImpl.java:336) at org.apache.tuscany.model.assembly.impl.ModuleImpl.accept(ModuleImpl.java:97) at org.apache.tuscany.model.assembly.impl.ComponentImpl.accept(ComponentImpl.java:206) at org.apache.tuscany.core.builder.impl.AssemblyVisitorImpl.start(AssemblyVisitorImpl.java:45) at org.apache.tuscany.core.runtime.RuntimeContextImpl.build(RuntimeContextImpl.java:161) at org.apache.tuscany.core.context.impl.AbstractCompositeContext.registerModelObject(AbstractCompositeContext.java:278) at org.apache.tuscany.core.client.BootstrapHelper.registerModule(BootstrapHelper.java:133) at org.apache.tuscany.core.client.TuscanyRuntime.init(TuscanyRuntime.java:104) at org.apache.tuscany.core.client.TuscanyRuntime.init(TuscanyRuntime.java:67) at org.apache.tuscany.test.interop.client.InteropTestDocLitTestCase.setUp(InteropTestDocLitTestCase.java:55) at junit.framework.TestCase.runBare(TestCase.java:125) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TUSCANY-248) Create interop test suite for the Web Service binding
[ http://issues.apache.org/jira/browse/TUSCANY-248?page=all ] Jean-Sebastien Delfino resolved TUSCANY-248: Resolution: Fixed Structure of the test suite has been created we now have 3 interop test cases. We need to add more test cases later. Create interop test suite for the Web Service binding - Key: TUSCANY-248 URL: http://issues.apache.org/jira/browse/TUSCANY-248 Project: Tuscany Type: New Feature Components: Java SCA Axis Binding Versions: M1 Reporter: Jean-Sebastien Delfino Assignee: Jean-Sebastien Delfino Fix For: M1 For the details see discussion at http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200604.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (TUSCANY-63) Need an SPI for co-ordination between EntryPoints and the infrastructure that will invoke them
[ http://issues.apache.org/jira/browse/TUSCANY-63?page=all ] ant elder reassigned TUSCANY-63: Assign To: Jeremy Boynes (was: ant elder) Also, I'm now working on moving the Axis2 binding over so if the JSONRPC binding shows I'm going about this the wrong way knowing about it sooner rather that latter would be good :) Need an SPI for co-ordination between EntryPoints and the infrastructure that will invoke them -- Key: TUSCANY-63 URL: http://issues.apache.org/jira/browse/TUSCANY-63 Project: Tuscany Type: Bug Components: Java SCA Core Versions: M1 Reporter: Jeremy Boynes Assignee: Jeremy Boynes Priority: Blocker Fix For: M1 In order to get the Tomcat integration code to create servlets for web-services bound entry points it needed to know implementation details of the binding. This will not allow integrators to freely embed Tuscany in different environments or binding providers to contribute new bindings without knowing something about those environments. I would suggest that we define an SPI implemented by environment integrators that will allow entry point implementations to request creation of transport endpoints. So, taking the example of Axis2 and Tomcat, the Axis2 binding would request a transport binding from the environment and which would be activated when the EP started. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-282) Add to our build the production of a distribution for our release
[ http://issues.apache.org/jira/browse/TUSCANY-282?page=all ] ant elder updated TUSCANY-282: -- Priority: Critical (was: Major) Add to our build the production of a distribution for our release - Key: TUSCANY-282 URL: http://issues.apache.org/jira/browse/TUSCANY-282 Project: Tuscany Type: New Feature Components: Build System Versions: M1 Reporter: Jean-Sebastien Delfino Assignee: Jeremy Boynes Priority: Critical Fix For: M1 We need to add to our build the production of a distribution Zip for our release. The distribution should include a preconfigured Tomcat. See discussion on our wiki page at http://wiki.apache.org/ws/Tuscany/Tasks and a proposal on the dev list at http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200604.mbox/[EMAIL PROTECTED] Jeremy and Raymond are volunteering to work on this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (TUSCANY-189) The HelloWorldWS sample should reuse the Helloworld sample JAR
[ http://issues.apache.org/jira/browse/TUSCANY-189?page=all ] ant elder reopened TUSCANY-189: --- The helloworldws war now includes all the helloworld dependancy jars which doesn't seem right. The HelloWorldWS sample should reuse the Helloworld sample JAR -- Key: TUSCANY-189 URL: http://issues.apache.org/jira/browse/TUSCANY-189 Project: Tuscany Type: Improvement Components: Java SCA Samples Versions: Mx Reporter: Jean-Sebastien Delfino Assignee: Rick Rineholt Fix For: M1, Mx The HelloWorldWS sample currently re-implements the HelloWorld component, instead of reusing the component from the HelloWorld sample. It would be more interesting to show how the component from the HelloWorld sample can be reused and published by an entry point simply by reusing and packaging the Helloworld sample JAR in the HelloWorldWS WAR. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (TUSCANY-242) SCDL loader should trim the whitespaces when the element text is parsed
[ http://issues.apache.org/jira/browse/TUSCANY-242?page=all ] Rick Rineholt closed TUSCANY-242: - Fix Version: Mx Resolution: Won't Fix I understand that this would be a nice useablity feature. However it's not clear from what I could find in the specification if ignoring the white space and crl/lf is proper behavior. I would prefer to stay more conservative about what we accept in the SCDL than accept things we may later need to reject. I would like to see in the SCA specification make it clear that this ok before we do this. SCDL loader should trim the whitespaces when the element text is parsed --- Key: TUSCANY-242 URL: http://issues.apache.org/jira/browse/TUSCANY-242 Project: Tuscany Type: Bug Components: Java SCA Model Versions: M1 Reporter: Raymond Feng Assignee: Rick Rineholt Fix For: M1, Mx SCDL loader should trim the whitespaces when the element text is parsed. If I use the following SCDL section: entryPoint name=InteropDocService interface.wsdl interface=http://soapinterop.org/#DocTestPortType; / binding.ws port=http://soapinterop.org/#interopDocPort; / reference InteropDocServiceComponent/DocTestPortType /reference /entryPoint The \t, \n will show up as follows and the lookup will fail. targetURI= ServiceURIImpl (id=119) address= sca:\n\t\t\tInteropDocServiceComponent/DocTestPortType\n\t\t isParsed= true isSCAScheme= Boolean (id=124) moduleComponentName= partName= \n\t\t\tInteropDocServiceComponent serviceName= DocTestPortType\n\t\t Note: The following format works fine. referenceInteropDocServiceComponent/DocTestPortType/reference -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
NEW Tuscany user mailing list - tuscany-user@ws.apache.org
A Tuscany user mailing list has been created: [EMAIL PROTECTED] This list is for users of Tuscany to ask questions, share knowledge, and discuss issues related to using Tuscany. Please join us and subscribe to the list! To subscribe, send an empty message to [EMAIL PROTECTED] -- Jean-Sebastien
Groovy Container
Hi, I have written a Groovy container for Tuscany. Is it worth submitting? Kind regards Meeraj -- ___ Search for businesses by name, location, or phone number. -Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/default.asp?SRC=lycos10
Re: Groovy Container
Yes by all means. Could you post it to JIRA? Thanks! Jim On May 7, 2006, at 12:14 PM, meeraj kunnumpurath wrote: Hi, I have written a Groovy container for Tuscany. Is it worth submitting? Kind regards Meeraj -- ___ Search for businesses by name, location, or phone number. -Lycos Yellow Pages http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/ default.asp?SRC=lycos10
[jira] Created: (TUSCANY-317) Java SCA Groovy Container
Java SCA Groovy Container - Key: TUSCANY-317 URL: http://issues.apache.org/jira/browse/TUSCANY-317 Project: Tuscany Type: New Feature Reporter: Meeraj Kunnumpurath Priority: Minor SCA Container for running Groovy scripts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: java.lang.OutOfMemoryError: PermGen space
More specifically, you can set these options with the following at the top of the mvn.bat file: set MAVEN_OPTS=-XX:MaxPermSize=128m -XX:PermSize=64m Rick Rineholt wrote: I received the below error on builds ..added the following javac arguments to mvn.bat to resolve: -XX:MaxPermSize=128m -XX:PermSize=64m Don't ask me what, or why answer provided via Googling. YMMV [INFO] Compilation failure Failure executing javac, but could not parse the error: The system is out of resources. Consult the following stack trace for details. java.lang.OutOfMemoryError: PermGen space
[jira] Resolved: (TUSCANY-274) The Axis2 entryPoint servlet doesn't turn runtime exceptions into SOAP faults
[ http://issues.apache.org/jira/browse/TUSCANY-274?page=all ] Rick Rineholt resolved TUSCANY-274: --- Fix Version: Mx Resolution: Fixed http://svn.apache.org/viewcvs?rev=404869view=rev The Axis2 entryPoint servlet doesn't turn runtime exceptions into SOAP faults - Key: TUSCANY-274 URL: http://issues.apache.org/jira/browse/TUSCANY-274 Project: Tuscany Type: Bug Components: Java SCA Axis Binding Reporter: ant elder Assignee: Rick Rineholt Fix For: M1, Mx If a runtime exception is thrown while invoking a WS entrypoint then the servlet doesn't catch it so the default Tomcat servlet error page is returned. The WebServiceEntryPointServlet should catch the exception and return a proper SOAP fault. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (TUSCANY-242) SCDL loader should trim the whitespaces when the element text is parsed
[ http://issues.apache.org/jira/browse/TUSCANY-242?page=all ] Rick Rineholt resolved TUSCANY-242: --- Resolution: Fixed http://svn.apache.org/viewcvs?rev=404910view=rev SCDL loader should trim the whitespaces when the element text is parsed --- Key: TUSCANY-242 URL: http://issues.apache.org/jira/browse/TUSCANY-242 Project: Tuscany Type: Bug Components: Java SCA Model Versions: M1 Reporter: Raymond Feng Assignee: Rick Rineholt Fix For: M1, Mx SCDL loader should trim the whitespaces when the element text is parsed. If I use the following SCDL section: entryPoint name=InteropDocService interface.wsdl interface=http://soapinterop.org/#DocTestPortType; / binding.ws port=http://soapinterop.org/#interopDocPort; / reference InteropDocServiceComponent/DocTestPortType /reference /entryPoint The \t, \n will show up as follows and the lookup will fail. targetURI= ServiceURIImpl (id=119) address= sca:\n\t\t\tInteropDocServiceComponent/DocTestPortType\n\t\t isParsed= true isSCAScheme= Boolean (id=124) moduleComponentName= partName= \n\t\t\tInteropDocServiceComponent serviceName= DocTestPortType\n\t\t Note: The following format works fine. referenceInteropDocServiceComponent/DocTestPortType/reference -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-152) Java SDO generation from XML Schema needs schema validation.
[ http://issues.apache.org/jira/browse/TUSCANY-152?page=all ] Jean-Sebastien Delfino updated TUSCANY-152: --- Fix Version: Mx Version: Mx Java SDO generation from XML Schema needs schema validation. Key: TUSCANY-152 URL: http://issues.apache.org/jira/browse/TUSCANY-152 Project: Tuscany Type: New Feature Components: Java SDO Implementation Versions: Mx Environment: SVN HEAD java Reporter: Rick Rineholt Fix For: Mx Using the generation through the WSDL tool it appears the XML schema can have invalid schema and still the generator produces code. The particular case I had was the an element that had this case element name=foo type=tns:bar / element name='bar' .../element Note for it to be valid the bar should have been a complexType. The code generated seem to create a Foo that was java.lang.Object. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (TUSCANY-318) All the J2SE samples should call TuscanyRuntime.shutdown() instead of TuscanyRuntime.stop()
All the J2SE samples should call TuscanyRuntime.shutdown() instead of TuscanyRuntime.stop() --- Key: TUSCANY-318 URL: http://issues.apache.org/jira/browse/TUSCANY-318 Project: Tuscany Type: Bug Components: Java SCA Samples Versions: M1 Reporter: Jean-Sebastien Delfino Fix For: M1 The samples should show the correct use of the TuscanyRuntime API, and call TuscanyRuntime.shutdown() instead of TuscanyRuntime.stop(). Stop only disassociates the Tuscany runtime from the current thread and does not shutdown it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
