Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I think thats: http://issues.apache.org/jira/browse/TUSCANY-1268. If you ignore the unsightly error on the tomcat console the sample should still actually be working fine. I have started fixing this in the trunk code, will try to get it committed shortly. ...ant On 5/26/07, Simon Nash [EMAIL PROTECTED] wrote: I am trying out the samples for RC2. All went well until I came to helloworld-jsonrpc. The pre-built war file deployed and ran fine. I then used ant package to rebuild the war, and the war that was built did not deploy successfully. Here is the error that I got. INFO: Server startup in 1813 ms 26-May-2007 19:38:37 org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive sample-helloworldjsonrpc.war 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridgeregisterLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpServletRequestArgResolver for local class javax.servlet.http.HttpServletRequest with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridgeregisterLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpSessionArgResolver for local class javax.servlet.http.HttpSession with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridgeregisterLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.JSONRPCBridgeServletArgResolver for local class com.metaparadigm.jsonrpc.JSONRPCBridge with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 org.apache.catalina.session.StandardManager doLoad SEVERE: IOException while loading persisted sessions: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler java.io.WriteAbortedException : writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler at java.io.ObjectInputStream.readObject0(ObjectInputStream.java :1309) at java.io.ObjectInputStream.defaultReadFields ( ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java :1832) at java.io.ObjectInputStream.readOrdinaryObject( ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0 (ObjectInputStream.java :1305) at java.io.ObjectInputStream.defaultReadFields( ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java :1832) at java.io.ObjectInputStream.readOrdinaryObject ( ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java :1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java :348) at java.util.HashMap.readObject (HashMap.java:1067) 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) at java.io.ObjectStreamClass.invokeReadObject( ObjectStreamClass.java:946) at java.io.ObjectInputStream.readSerialData ( ObjectInputStream.java:1809) at java.io.ObjectInputStream.readOrdinaryObject( ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java :1305) at java.io.ObjectInputStream.defaultReadFields ( ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java :1832) at java.io.ObjectInputStream.readOrdinaryObject( ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0 (ObjectInputStream.java :1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java :348) at org.apache.catalina.session.StandardSession.readObject( StandardSession.java:1386) at org.apache.catalina.session.StandardSession.readObjectData ( StandardSession.java:921) at org.apache.catalina.session.StandardManager.doLoad( StandardManager.java:393) at org.apache.catalina.session.StandardManager.load( StandardManager.java:320) at org.apache.catalina.session.StandardManager.start( StandardManager.java:636) at org.apache.catalina.core.ContainerBase.setManager( ContainerBase.java:431) at org.apache.catalina.core.StandardContext.start ( StandardContext.java:4131) 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 org.apache.catalina.startup.HostConfig.deployWAR( HostConfig.java:809) at org.apache.catalina.startup.HostConfig.deployWARs( HostConfig.java :698)
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I confirmed that the sample runs OK after producing the error messages. The unexplained part of this (to me) is why the war that I built with ant consistently gave an error but the pre-built war in the binary distro was consistently OK. And even more bizarrely, I rebuilt the war again with ant today and it deploys without errors! Any ideas? Simon ant elder wrote: I think thats: http://issues.apache.org/jira/browse/TUSCANY-1268. If you ignore the unsightly error on the tomcat console the sample should still actually be working fine. I have started fixing this in the trunk code, will try to get it committed shortly. ...ant On 5/26/07, Simon Nash [EMAIL PROTECTED] wrote: I am trying out the samples for RC2. All went well until I came to helloworld-jsonrpc. The pre-built war file deployed and ran fine. I then used ant package to rebuild the war, and the war that was built did not deploy successfully. Here is the error that I got. INFO: Server startup in 1813 ms 26-May-2007 19:38:37 org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive sample-helloworldjsonrpc.war 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridgeregisterLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpServletRequestArgResolver for local class javax.servlet.http.HttpServletRequest with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridgeregisterLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpSessionArgResolver for local class javax.servlet.http.HttpSession with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridgeregisterLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.JSONRPCBridgeServletArgResolver for local class com.metaparadigm.jsonrpc.JSONRPCBridge with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 org.apache.catalina.session.StandardManager doLoad SEVERE: IOException while loading persisted sessions: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler java.io.WriteAbortedException : writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309) at java.io.ObjectInputStream.defaultReadFields (ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) (cut) I'm going out now so I will have to leave this until later. I will investigate further and try to identify the difference between the war that works and the one that doesn't. Does anyone else see the same problem after rebuilding this war using ant? Simon ant elder wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/http://people.apache.org/%7Eantelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I successfully built the source distribution (including the distribution module). I reviewed the contents of the binary distribution and I ran and built all the samples using the instructions in the READMEs. I have a few minor comments but nothing too serious, so here's my +1 (non-binding). Minor comments: 1. Can't build the distribution module unless you are either connected to the internet or explicitly use the -o option. I'll start a separate thread to discuss this. 2. Many of the sample README files contain typos. Most are obvious, but one in samples/README has now for not and is potentially confusing. 3. samples/calculator/README does not list all the sample files and has a typo in one of the file names. This filename typo is propagated to the other calculator samples as well. 4. samples/simple-bigbank/README has an incorrect directory hierarchy. 5. The output from the calculator-script sample included a jython warning message about a cache directory. This wasn't mentioned in the README. 6. The filenames listed in the READMEs for calculator-rmi-service and calculator-rmi-reference don't match what's in the samples. 7. The CalculatorClient class in calculator-rmi-service doesn't seem to be used. 8. samples/helloworld-jsonrpc/README has an incomplete list of file names, with typos in one of them. 9. I think it would be better the reverse the order of simple-callback and implementation-composite in the samples/README file. These samples are supposed to be in order of complexity, but implementation-composite introduces two new concepts (composite implementations and callbacks). It would be better to introduce the callback concept in simple-callback before using it as part of implementation-composite. 10. samples/simple-callback/README has typos in file names. 11. samples/databinding-echo/README has an outstanding TODO note. 12. samples/implementation-crud/README has incorrect file list under src/main (includes crud.composite which has moved to src/test). 13. samples/implementation-crud-client/README has incorrect package names under src/main and src/test. 14. samples/implementation-crud-client/README refers to a .png file name that does not match the .png file actually included in this sample. 15. CRUDTestCase in implementation-crud-client is testing the server code not the client code. 16. Sample test output in samples/implementation-crud-client/README does not match what is actually produced at runtime (a consequence of 15 above). 17. samples/binding-echo/README has incorrect file list under src/main (includes EchoBinding.composite which has moved to src/test). 18. samples/binding-echo-appl/README has incorrect composite file name under src/main/resources. 19. samples/binding-echo-appl/README refers to a .png file name that does not match the .png file actually included in this sample. 20. Sample application output and sample test output in samples/binding-echo-appl/README do not match what is actually produced at runtime. 21. The INSTALL file doesn't mention the README and RELEASE_NOTES files. I'll write JIRAs for the samples and README problems that I found (to be fixed in the next release), and I'll create and attach patches for these. Simon ant elder wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
{RESULT] was Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Release vote has passed with 6 binding +1s, 1 non-binding +1 and no -1s. Votes from: Ant Elder Luciano Resende Raymond Feng Venkata Krishnan Jean-Sebastien Delfino Simon Laws Simon Nash (non-binidng) ...ant On 5/24/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/ http://people.apache.org/%7Eantelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I am trying out the samples for RC2. All went well until I came to helloworld-jsonrpc. The pre-built war file deployed and ran fine. I then used ant package to rebuild the war, and the war that was built did not deploy successfully. Here is the error that I got. INFO: Server startup in 1813 ms 26-May-2007 19:38:37 org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive sample-helloworldjsonrpc.war 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridge registerLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpServletRequestArgResolver for local class javax.servlet.http.HttpServletRequest with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridge registerLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpSessionArgResolver for local class javax.servlet.http.HttpSession with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridge registerLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.JSONRPCBridgeServletArgResolver for local class com.metaparadigm.jsonrpc.JSONRPCBridge with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 org.apache.catalina.session.StandardManager doLoad SEVERE: IOException while loading persisted sessions: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at java.util.HashMap.readObject(HashMap.java:1067) 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) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at org.apache.catalina.session.StandardSession.readObject(StandardSession.java:1386) at org.apache.catalina.session.StandardSession.readObjectData(StandardSession.java:921) at org.apache.catalina.session.StandardManager.doLoad(StandardManager.java:393) at org.apache.catalina.session.StandardManager.load(StandardManager.java:320) at org.apache.catalina.session.StandardManager.start(StandardManager.java:636) at org.apache.catalina.core.ContainerBase.setManager(ContainerBase.java:431) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4131) 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 org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:809) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:698) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:472) at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1190) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:292) at
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I compared the distro war file with one produced by the ant script and they appear to have identical contents except for 2 additional pom files in the distro version. The failure only occurs when hot-deploying the war into a Tomcat server that is already started and running. If I do a cold start of the Tomcat server with the war file already in the webapps directory, it deploys OK and the test runs. I'll open a JIRA and attach both war files in the hope that someone else can confirm the problem symptoms I am seeing, and maybe spot the vital difference between these two war files! Simon Simon Nash wrote: I am trying out the samples for RC2. All went well until I came to helloworld-jsonrpc. The pre-built war file deployed and ran fine. I then used ant package to rebuild the war, and the war that was built did not deploy successfully. Here is the error that I got. INFO: Server startup in 1813 ms 26-May-2007 19:38:37 org.apache.catalina.startup.HostConfig deployWAR INFO: Deploying web application archive sample-helloworldjsonrpc.war 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridge registerLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpServletRequestArgResolver for local class javax.servlet.http.HttpServletRequest with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridge registerLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.HttpSessionArgResolver for local class javax.servlet.http.HttpSession with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 com.metaparadigm.jsonrpc.JSONRPCBridge registerLocalArgResolver INFO: registered local arg resolver com.metaparadigm.jsonrpc.JSONRPCBridgeServletArgResolver for local class com.metaparadigm.jsonrpc.JSONRPCBridge with context javax.servlet.http.HttpServletRequest 26-May-2007 19:38:42 org.apache.catalina.session.StandardManager doLoad SEVERE: IOException while loading persisted sessions: java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler java.io.WriteAbortedException: writing aborted; java.io.NotSerializableException: org.apache.tuscany.sca.core.invocation.JDKInvocationHandler at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1309) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832) (cut) I'm going out now so I will have to leave this until later. I will investigate further and try to identify the difference between the war that works and the one that doesn't. Does anyone else see the same problem after rebuilding this war using ant? Simon ant elder wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I tried again (empty maven repo, rc2 source distro). This time I was using a different network connection. I got a similar but slightly different error while building the SDO data binding: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven:maven-plugin-descriptor Reason: Error getting POM for 'org.apache.maven:maven-plugin-descriptor' from the repository: Error transferring file org.apache.maven:maven-plugin-descriptor:pom:2.0.4 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.incubator (http://people.apache.org/repo/m2-incubating-repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshot (http://snapshots.repository.codehaus.org), indiana (http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2/) Any clues here? Simon ant elder wrote: I'd guess that this is one of those intermittent maven repository problems, could you just try again? ...ant On 5/24/07, Simon Nash [EMAIL PROTECTED] wrote: I tried building the source distro from an empty local maven repo. The build failed in the Axis2 binding with the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: commons-fileupload:commons-fileupload Reason: Error getting POM for 'commons-fileupload:commons-fileupload' from the repository: Error transferring file commons-fileupload:commons-fileupload:pom:1.1.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.incubator ( http://people.apache.org/repo/m2-incubating-repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), apache.ws (http://ws.zones.apache.org/repository/) Simon ant elder wrote: I've just tried running it lots of times, the individual test, all the itests, and the full build and it always is working for me. ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
From a clean install of RC2 and an empty local repo... I tried a selection of the samples in the binary distro using ant scripts. All OK I built the source distiribution. It took a lng time (3 hours!) to get through it all told. In my case this seemed to be primarily that the repo hosting EMF resources was on a go slow and the build failed and I stopped the build thinking it had frozen a couple of times. Finaly got it to go right through and it was clean. Not a great experience for the user but nothing to do with RC2. +1 for releasing it Earlier in this thread problems were reported running the ant scripts in the source distribtion. This is working as designed. The ant scripts will not work in the source disitribution as the manifest jar that they depend on is not available. It is assumed that the use who downloads the source distribution will do a maven build (in fact they have to do a maven build). We could consider adding ant build capability to the samples in the src distro but I think this can wait for future releases. Simon
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I restarted the build without clearing out my local repo, and it ran to completion. So it does look like an intermittent maven problem and not a problem with the rc. It's strange that I seem consistently unable to build the whole distro from a clean repo, though. Simon Simon Nash wrote: I tried again (empty maven repo, rc2 source distro). This time I was using a different network connection. I got a similar but slightly different error while building the SDO data binding: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.apache.maven:maven-plugin-descriptor Reason: Error getting POM for 'org.apache.maven:maven-plugin-descriptor' from the repository: Error transferring file org.apache.maven:maven-plugin-descriptor:pom:2.0.4 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.incubator (http://people.apache.org/repo/m2-incubating-repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus-snapshot (http://snapshots.repository.codehaus.org), indiana (http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2/) Any clues here? Simon ant elder wrote: I'd guess that this is one of those intermittent maven repository problems, could you just try again? ...ant On 5/24/07, Simon Nash [EMAIL PROTECTED] wrote: I tried building the source distro from an empty local maven repo. The build failed in the Axis2 binding with the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: commons-fileupload:commons-fileupload Reason: Error getting POM for 'commons-fileupload:commons-fileupload' from the repository: Error transferring file commons-fileupload:commons-fileupload:pom:1.1.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.incubator ( http://people.apache.org/repo/m2-incubating-repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), apache.ws (http://ws.zones.apache.org/repository/) Simon ant elder wrote: I've just tried running it lots of times, the individual test, all the itests, and the full build and it always is working for me. ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Simon Laws wrote: From a clean install of RC2 and an empty local repo... I tried a selection of the samples in the binary distro using ant scripts. All OK I built the source distiribution. It took a lng time (3 hours!) to get through it all told. In my case this seemed to be primarily that the repo hosting EMF resources was on a go slow and the build failed and I stopped the build thinking it had frozen a couple of times. Finaly got it to go right through and it was clean. Not a great experience for the user but nothing to do with RC2. +1 for releasing it Earlier in this thread problems were reported running the ant scripts in the source distribtion. This is working as designed. The ant scripts will not work in the source disitribution as the manifest jar that they depend on is not available. It is assumed that the use who downloads the source distribution will do a maven build (in fact they have to do a maven build). We could consider adding ant build capability to the samples in the src distro but I think this can wait for future releases. I am not sure that we could do this without making the ant scripts more complicated. At the moment they serve as simple tutorial instructions for building and running Tuscany applications using the binary distro. I don't think we should add more sophisticated capabilities to these scripts if this means losing the simplicity and clarity that they currently have. Perhaps a reasonable comporomise for a future release would be for the ant scripts to detect that they are running from a source distro and produce a nice errror message. I don't know how hard it would be to do this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Thanks for the patch Simon, I have applied it on the 0.90 branch and in trunk as well and have resolved the JIRA. On 5/23/07, Simon Nash [EMAIL PROTECTED] wrote: I found a serious problem in the calculator-web sample in the 0.90 release candidate. The ant script for this sample builds a war that is not deployable because of two missing files. The pre-built war file that is shipped as part of the binary distro is fine. I discovered this as a last-minute glitch with my demo for the Tuscany presentation that I gave today at the IBM Impact conference. I'll write a JIRA for this now and post a patch asap (later today EDT). Simon Simon Nash wrote: I think the shop window factor is an important consideration. The cumulative effect of the issues that people have reported seems to be significant enough from this perspective that a respin is desirable. In particular, the build and sample README problems could be quite off-putting to a novice user. Simon Simon Laws wrote: I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
OK, below is an errata based on the points that people have highlighted as important in this thread. Anything else need to be added? Anyone have any better words for installing samples from the binary distro in Eclipse or any words at all for IDEA. Now we have most people's comments in, this is quite a long list! Simon Samples === * Some sample READMEs don't match the code as it stands calculator-rmi-reference The README describes how to start client and server processes from this project. This is now not the case. This project now only supports the client process. Use the calculator-rmi-service sample to start the server using ant-f build-server.xml run first and then run the client here. calculator-rmi-service The README describes how to start client and server processes from this project. This is now not the case. This project now only supports the server process. Run the server here first and then use the calculator-rmi-reference sample to start the client using ant -f build-client.xml run. * The implementation-crud-client sample has the wrong package name for the test client In both README and build.xml crud.CRUDClient should read crud.client.CRUDClient * The calculator-web and helloworld-jsonrpc build.xml produces a war that is not deployable. To fix the build.xml file. Move the line include name=sca-api-0.90-incubating-SNAPSHOT.jar/ From the lib section to the zipfileset section. * At the top of the web page provided by the helloworld-jsonrpc sample there is the text. ... to make JSON-RPC requests to the service located at services/HelloWorldService Selecting the link service/HelloWorldService causes and error. * There is no sample for how to use the META_INF/sca-deployables feature in this release. Build = * There is a problem building the source distribution on linux with the IBM JDK 1.5.0. The problem manifests itself with a problem building the databinding-jaxb module. Maven reports that it is unable to process the maven-jaxb-plugin pom. This occurs because this pom has non-UTF8 characters. The manual fix is to remove the offending characters manually from the pom in your local repo and restart the build: .m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven- jaxb-plugin-1.1.pom remove the non-UTF8 characters from this block. developer idMÆlfweald/id nameMalachi de Ælfweald/name email[EMAIL PROTECTED]/email roles roleDeveloper/role /roles /developer Documentation = * Java doc for some of the SPI packages listed in the the CHANGES file are missing from the docs directory * Java doc for org.osoa.sca.* packages is provided but not included on the index page * Java doc to the Tuscany Java SCA APIs is not provided with this release * Instructions for loading the binary distribution samples into an IDE without using maven to generate suitable project files are missing. For Eclipse - in a new or existing workspace Create a new java project to represent the sample you want to work on, e.g. calculator Import all of the sample code and resources into this project, e.g. File, Import and then select tuscany-sca-0.90-incubating\samples\calculator from the filesystem Configure the source path to include src/main/java src/main/resources Configure the output folder to be calculator/target Configure the build path to include all of the jars provided in lib modules If you select calculator.CalculatorClient.java and run as Java Application you should see 3 + 2=5.0 3 - 2=1.0 3 * 2=6.0 3 / 2=1.5 Other = * Some non-working modules have been included in the distribution and should be ignored modules/binding-jms modules/discovery-jms modules/implementation-spring modules/jmx
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I was looking for the javadoc issue, and the issue is that maven-dependency-plugin:unpack-javadoc just copy and unpack each module javadoc files, overriding files with same name from previous modules javadoc, this is why we only see the index.html from the last module processed, instead of having a aggregated index.html. I have tried various options to aggregate these javadocs from multiple modules, without any success. Does anybody know about some maven hacks to accomplish this ? On 5/24/07, Simon Laws [EMAIL PROTECTED] wrote: OK, below is an errata based on the points that people have highlighted as important in this thread. Anything else need to be added? Anyone have any better words for installing samples from the binary distro in Eclipse or any words at all for IDEA. Now we have most people's comments in, this is quite a long list! Simon Samples === * Some sample READMEs don't match the code as it stands calculator-rmi-reference The README describes how to start client and server processes from this project. This is now not the case. This project now only supports the client process. Use the calculator-rmi-service sample to start the server using ant-f build-server.xml run first and then run the client here. calculator-rmi-service The README describes how to start client and server processes from this project. This is now not the case. This project now only supports the server process. Run the server here first and then use the calculator-rmi-reference sample to start the client using ant -f build-client.xml run. * The implementation-crud-client sample has the wrong package name for the test client In both README and build.xml crud.CRUDClient should read crud.client.CRUDClient * The calculator-web and helloworld-jsonrpc build.xml produces a war that is not deployable. To fix the build.xml file. Move the line include name=sca-api-0.90-incubating-SNAPSHOT.jar/ From the lib section to the zipfileset section. * At the top of the web page provided by the helloworld-jsonrpc sample there is the text. ... to make JSON-RPC requests to the service located at services/HelloWorldService Selecting the link service/HelloWorldService causes and error. * There is no sample for how to use the META_INF/sca-deployables feature in this release. Build = * There is a problem building the source distribution on linux with the IBM JDK 1.5.0. The problem manifests itself with a problem building the databinding-jaxb module. Maven reports that it is unable to process the maven-jaxb-plugin pom. This occurs because this pom has non-UTF8 characters. The manual fix is to remove the offending characters manually from the pom in your local repo and restart the build: .m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven- jaxb-plugin-1.1.pom remove the non-UTF8 characters from this block. developer idMÆlfweald/id nameMalachi de Ælfweald/name email[EMAIL PROTECTED]/email roles roleDeveloper/role /roles /developer Documentation = * Java doc for some of the SPI packages listed in the the CHANGES file are missing from the docs directory * Java doc for org.osoa.sca.* packages is provided but not included on the index page * Java doc to the Tuscany Java SCA APIs is not provided with this release * Instructions for loading the binary distribution samples into an IDE without using maven to generate suitable project files are missing. For Eclipse - in a new or existing workspace Create a new java project to represent the sample you want to work on, e.g. calculator Import all of the sample code and resources into this project, e.g. File, Import and then select tuscany-sca-0.90-incubating\samples\calculator from the filesystem Configure the source path to include src/main/java src/main/resources Configure the output folder to be calculator/target Configure the build path to include all of the jars provided in lib modules If you select calculator.CalculatorClient.java and run as Java Application you should see 3 + 2=5.0 3 - 2=1.0 3 * 2=6.0 3 / 2=1.5 Other = * Some non-working modules have been included in the distribution and should be ignored modules/binding-jms modules/discovery-jms modules/implementation-spring modules/jmx -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
On 5/24/07, Simon Laws [EMAIL PROTECTED] wrote: OK, below is an errata based on the points that people have highlighted as important in this thread. Anything else need to be added? Anyone have any better words for installing samples from the binary distro in Eclipse or any words at all for IDEA. Now we have most people's comments in, this is quite a long list! Simon Samples === * Some sample READMEs don't match the code as it stands calculator-rmi-reference The README describes how to start client and server processes from this project. This is now not the case. This project now only supports the client process. Use the calculator-rmi-service sample to start the server using ant-f build-server.xml run first and then run the client here. calculator-rmi-service The README describes how to start client and server processes from this project. This is now not the case. This project now only supports the server process. Run the server here first and then use the calculator-rmi-reference sample to start the client using ant -f build-client.xml run. * The implementation-crud-client sample has the wrong package name for the test client In both README and build.xml crud.CRUDClient should read crud.client.CRUDClient * The calculator-web and helloworld-jsonrpc build.xml produces a war that is not deployable. To fix the build.xml file. Move the line include name=sca-api-0.90-incubating-SNAPSHOT.jar/ From the lib section to the zipfileset section. * At the top of the web page provided by the helloworld-jsonrpc sample there is the text. ... to make JSON-RPC requests to the service located at services/HelloWorldService Selecting the link service/HelloWorldService causes and error. * There is no sample for how to use the META_INF/sca-deployables feature in this release. Build = * There is a problem building the source distribution on linux with the IBM JDK 1.5.0. The problem manifests itself with a problem building the databinding-jaxb module. Maven reports that it is unable to process the maven-jaxb-plugin pom. This occurs because this pom has non-UTF8 characters. The manual fix is to remove the offending characters manually from the pom in your local repo and restart the build: .m2/repository/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven- jaxb-plugin-1.1.pom remove the non-UTF8 characters from this block. developer idMÆlfweald/id nameMalachi de Ælfweald/name email[EMAIL PROTECTED]/email roles roleDeveloper/role /roles /developer Documentation = * Java doc for some of the SPI packages listed in the the CHANGES file are missing from the docs directory * Java doc for org.osoa.sca.* packages is provided but not included on the index page * Java doc to the Tuscany Java SCA APIs is not provided with this release * Instructions for loading the binary distribution samples into an IDE without using maven to generate suitable project files are missing. For Eclipse - in a new or existing workspace Create a new java project to represent the sample you want to work on, e.g. calculator Import all of the sample code and resources into this project, e.g. File, Import and then select tuscany-sca-0.90-incubating\samples\calculator from the filesystem Configure the source path to include src/main/java src/main/resources Configure the output folder to be calculator/target Configure the build path to include all of the jars provided in lib modules If you select calculator.CalculatorClient.java and run as Java Application you should see 3 + 2=5.0 3 - 2=1.0 3 * 2=6.0 3 / 2=1.5 Other = * Some non-working modules have been included in the distribution and should be ignored modules/binding-jms modules/discovery-jms modules/implementation-spring modules/jmx Listing all these issues like this makes RC1 sound a bit too imperfect IMHO so I'm now -1 on releasing it. I've cut a new RC2 which includes all the fixes that have been made in the 0.90 branch, many thanks to all those who've been fixing things there as the problems have been discovered. It doesn't fix the Javadoc problem, there's a note in the CHANGES file saying thats incomplete, and it doesn't fix the Linux build issue, there's a note in the BUILDING file about that, and there's a couple of other's not fixed as they seemed either to small or difficult to be worth the risk of the change. Fingers crossed the respin hasn't introduced any new problems... I'll start a new vote thread for RC2. ...ant
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Hi, I grabbed the latest RC src distro and tried to build it locally after removing the local maven repo. But now I saw a test case failure as shown below. Can somebody else try it? The wierd thing is that if I tried to build the failing module again, then it passed. Thanks, Raymond [INFO] Surefire report directory: C:\Apache\tuscany-sca-0.90-incubating-src\ites t\wsdl\target\surefire-reports --- T E S T S --- Running org.apache.tuscany.sca.itest.WSDLTestCase log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAX Utils). log4j:WARN Please initialize the log4j system properly. Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.906 sec Running org.apache.tuscany.sca.itest.SDOWSDLTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.579 sec FA ILURE! testClient1a2a3a4a(org.apache.tuscany.sca.itest.SDOWSDLTestCase) Time elapsed: 4.547 sec ERROR! org.apache.axis2.AxisFault: The service cannot be found for the endpoint referen ce (EPR) http://localhost:8080/AccountService1a2b3a4a at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.j ava:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO peration.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAx isOperation.java:294) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invokeTarget (Axis2BindingInvoker.java:92) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invoke(Axis2 BindingInvoker.java:71) at org.apache.tuscany.core.databinding.wire.DataTransformationInteceptor .invoke(DataTransformationInteceptor.java:68) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at bigbank.account.services.accountdata.AccountServiceClientImpl.createA ccount(AccountServiceClientImpl.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invokeTarget(JavaTargetInvoker.java:112) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invoke(JavaTargetInvoker.java:134) at org.apache.tuscany.sca.implementation.java.invocation.PassByValueInvo ker.invoke(PassByValueInvoker.java:61) at org.apache.tuscany.sca.implementation.java.invocation.TargetInvokerIn voker.invoke(TargetInvokerInvoker.java:46) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.doit(SDOWSDLTestCase.jav a:79) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.testClient1a2a3a4a(SDOWS DLTestCase.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) 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:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Hi,
Anthoer issue: If I run ant for samples/binding-echo from the src distro,
I saw compilation errors.
It seems that the build.xml assumes that pathelement
location=../../lib/tuscany-sca-manifest.jar/ is in place.
Thanks,
Raymond
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echoant
Buildfile: build.xml
init:
compile:
[javac] Warning: echo\DefaultEchoBindingFactory.java modified in the
future.
[javac] Warning: echo\EchoBinding.java modified in the future.
[javac] Warning: echo\EchoBindingFactory.java modified in the future.
[javac] Warning: echo\impl\EchoBindingImpl.java modified in the future.
[javac] Warning: echo\impl\EchoBindingProcessor.java modified in the
future.
[javac] Warning: echo\module\EchoModuleActivator.java modified in the
future
.
[javac] Warning: echo\provider\EchoBindingInvoker.java modified in the
futur
e.
[javac] Warning: echo\provider\EchoBindingProviderFactory.java modified
in t
he future.
[javac] Warning: echo\provider\EchoReferenceBindingProvider.java
modified in
the future.
[javac] Warning: echo\provider\EchoServiceBindingProvider.java modified
in t
he future.
[javac] Warning: echo\server\EchoServer.java modified in the future.
[javac] Warning: echo\server\EchoService.java modified in the future.
[javac] Compiling 12 source files to
C:\Apache\tuscany-sca-0.90-incubating-s
rc\samples\binding-echo\target\classes
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\EchoBinding.java:22: package org.apache.tuscany.sca.assembly
does
not exist
[javac] import org.apache.tuscany.sca.assembly.Binding;
[javac]^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\EchoBinding.java:27: cannot find symbol
[javac] symbol: class Binding
[javac] public interface EchoBinding extends Binding {
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:25: package
org.apache.tuscany.sca.polic
y does not exist
[javac] import org.apache.tuscany.sca.policy.Intent;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:26: package
org.apache.tuscany.sca.polic
y does not exist
[javac] import org.apache.tuscany.sca.policy.PolicySet;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:54: cannot find symbol
[javac] symbol : class PolicySet
[javac] location: class echo.impl.EchoBindingImpl
[javac] public ListPolicySet getPolicySets() {
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:59: cannot find symbol
[javac] symbol : class Intent
[javac] location: class echo.impl.EchoBindingImpl
[javac] public ListIntent getRequiredIntents() {
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:22: package org.osoa.sca does
not e
xist
[javac] import static org.osoa.sca.Constants.SCA_NS;
[javac]^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:22: static import only from
classes
and interfaces
[javac] import static org.osoa.sca.Constants.SCA_NS;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:25: package javax.xml.stream
does n
ot exist
[javac] import javax.xml.stream.XMLStreamReader;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:26: package javax.xml.stream
does n
ot exist
[javac] import javax.xml.stream.XMLStreamWriter;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:28: package
org.apache.tuscany.sca.
contribution.processor does not exist
[javac] import
org.apache.tuscany.sca.contribution.processor.StAXArtifactPro
cessor;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:29: package
org.apache.tuscany.sca.
contribution.resolver does not exist
[javac] import
org.apache.tuscany.sca.contribution.resolver.ModelResolver;
[javac] ^
[javac]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
The ant build scripts are supposed to work from the binary distribution :
In the binary distribution of Apache Tuscany the samples can also
be run using the provided Ant build.xml file
On 5/24/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
Anthoer issue: If I run ant for samples/binding-echo from the src distro,
I saw compilation errors.
It seems that the build.xml assumes that pathelement
location=../../lib/tuscany-sca-manifest.jar/ is in place.
Thanks,
Raymond
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echoant
Buildfile: build.xml
init:
compile:
[javac] Warning: echo\DefaultEchoBindingFactory.java modified in the
future.
[javac] Warning: echo\EchoBinding.java modified in the future.
[javac] Warning: echo\EchoBindingFactory.java modified in the future.
[javac] Warning: echo\impl\EchoBindingImpl.java modified in the future.
[javac] Warning: echo\impl\EchoBindingProcessor.java modified in the
future.
[javac] Warning: echo\module\EchoModuleActivator.java modified in the
future
.
[javac] Warning: echo\provider\EchoBindingInvoker.java modified in the
futur
e.
[javac] Warning: echo\provider\EchoBindingProviderFactory.java modified
in t
he future.
[javac] Warning: echo\provider\EchoReferenceBindingProvider.java
modified in
the future.
[javac] Warning: echo\provider\EchoServiceBindingProvider.java modified
in t
he future.
[javac] Warning: echo\server\EchoServer.java modified in the future.
[javac] Warning: echo\server\EchoService.java modified in the future.
[javac] Compiling 12 source files to
C:\Apache\tuscany-sca-0.90-incubating-s
rc\samples\binding-echo\target\classes
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\EchoBinding.java:22: package org.apache.tuscany.sca.assembly
does
not exist
[javac] import org.apache.tuscany.sca.assembly.Binding;
[javac]^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\EchoBinding.java:27: cannot find symbol
[javac] symbol: class Binding
[javac] public interface EchoBinding extends Binding {
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:25: package
org.apache.tuscany.sca.polic
y does not exist
[javac] import org.apache.tuscany.sca.policy.Intent;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:26: package
org.apache.tuscany.sca.polic
y does not exist
[javac] import org.apache.tuscany.sca.policy.PolicySet;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:54: cannot find symbol
[javac] symbol : class PolicySet
[javac] location: class echo.impl.EchoBindingImpl
[javac] public ListPolicySet getPolicySets() {
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingImpl.java:59: cannot find symbol
[javac] symbol : class Intent
[javac] location: class echo.impl.EchoBindingImpl
[javac] public ListIntent getRequiredIntents() {
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:22: package org.osoa.sca does
not e
xist
[javac] import static org.osoa.sca.Constants.SCA_NS;
[javac]^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:22: static import only from
classes
and interfaces
[javac] import static org.osoa.sca.Constants.SCA_NS;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:25: package javax.xml.stream
does n
ot exist
[javac] import javax.xml.stream.XMLStreamReader;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:26: package javax.xml.stream
does n
ot exist
[javac] import javax.xml.stream.XMLStreamWriter;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:28: package
org.apache.tuscany.sca.
contribution.processor does not exist
[javac] import
org.apache.tuscany.sca.contribution.processor.StAXArtifactPro
cessor;
[javac] ^
[javac]
C:\Apache\tuscany-sca-0.90-incubating-src\samples\binding-echo\src\m
ain\java\echo\impl\EchoBindingProcessor.java:29: package
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I've just tried running it lots of times, the individual test, all the itests, and the full build and it always is working for me. ...ant On 5/24/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, I grabbed the latest RC src distro and tried to build it locally after removing the local maven repo. But now I saw a test case failure as shown below. Can somebody else try it? The wierd thing is that if I tried to build the failing module again, then it passed. Thanks, Raymond [INFO] Surefire report directory: C:\Apache\tuscany-sca-0.90-incubating-src\ites t\wsdl\target\surefire-reports --- T E S T S --- Running org.apache.tuscany.sca.itest.WSDLTestCase log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAX Utils). log4j:WARN Please initialize the log4j system properly. Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.906sec Running org.apache.tuscany.sca.itest.SDOWSDLTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.579 sec FA ILURE! testClient1a2a3a4a(org.apache.tuscany.sca.itest.SDOWSDLTestCase) Time elapsed: 4.547 sec ERROR! org.apache.axis2.AxisFault: The service cannot be found for the endpoint referen ce (EPR) http://localhost:8080/AccountService1a2b3a4a at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.j ava:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO peration.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAx isOperation.java:294) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invokeTarget (Axis2BindingInvoker.java:92) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invoke(Axis2 BindingInvoker.java:71) at org.apache.tuscany.core.databinding.wire.DataTransformationInteceptor .invoke(DataTransformationInteceptor.java:68) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at bigbank.account.services.accountdata.AccountServiceClientImpl.createA ccount(AccountServiceClientImpl.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invokeTarget(JavaTargetInvoker.java:112) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invoke(JavaTargetInvoker.java:134) at org.apache.tuscany.sca.implementation.java.invocation.PassByValueInvo ker.invoke(PassByValueInvoker.java:61) at org.apache.tuscany.sca.implementation.java.invocation.TargetInvokerIn voker.invoke(TargetInvokerInvoker.java:46) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.doit(SDOWSDLTestCase.jav a:79) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.testClient1a2a3a4a(SDOWS DLTestCase.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) 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:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Much better now, I've looked in most standalone samples and also used ant to compile and then deployed the webapp samples successfully in jetty. Source distribution compiles from a clean maven repo, etc Here is my +1 On 5/24/07, ant elder [EMAIL PROTECTED] wrote: I've just tried running it lots of times, the individual test, all the itests, and the full build and it always is working for me. ...ant On 5/24/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, I grabbed the latest RC src distro and tried to build it locally after removing the local maven repo. But now I saw a test case failure as shown below. Can somebody else try it? The wierd thing is that if I tried to build the failing module again, then it passed. Thanks, Raymond [INFO] Surefire report directory: C:\Apache\tuscany-sca-0.90-incubating-src\ites t\wsdl\target\surefire-reports --- T E S T S --- Running org.apache.tuscany.sca.itest.WSDLTestCase log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAX Utils). log4j:WARN Please initialize the log4j system properly. Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.906sec Running org.apache.tuscany.sca.itest.SDOWSDLTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.579 sec FA ILURE! testClient1a2a3a4a(org.apache.tuscany.sca.itest.SDOWSDLTestCase) Time elapsed: 4.547 sec ERROR! org.apache.axis2.AxisFault: The service cannot be found for the endpoint referen ce (EPR) http://localhost:8080/AccountService1a2b3a4a at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.j ava:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO peration.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAx isOperation.java:294) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invokeTarget (Axis2BindingInvoker.java:92) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invoke(Axis2 BindingInvoker.java:71) at org.apache.tuscany.core.databinding.wire.DataTransformationInteceptor .invoke(DataTransformationInteceptor.java:68) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at bigbank.account.services.accountdata.AccountServiceClientImpl.createA ccount(AccountServiceClientImpl.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invokeTarget(JavaTargetInvoker.java:112) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invoke(JavaTargetInvoker.java:134) at org.apache.tuscany.sca.implementation.java.invocation.PassByValueInvo ker.invoke(PassByValueInvoker.java:61) at org.apache.tuscany.sca.implementation.java.invocation.TargetInvokerIn voker.invoke(TargetInvokerInvoker.java:46) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.doit(SDOWSDLTestCase.jav a:79) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.testClient1a2a3a4a(SDOWS DLTestCase.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) 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:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Hi, In the RC, I'm seeing that composite element is missing required targetNamespace attribute, for example, the Calculator.composite has the following: composite xmlns=http://www.osoa.org/xmlns/sca/1.0 name=Calculator ... /composite By the SCA spec, the composite should have the targetNamespace attr: attribute name=targetNamespace type=anyURI use=required/ A similar issue applies to sca-contribution.xml: deployable composite=xs:QName/. We need to reference the composite by QName. This is NOT a show-stopper, should we document it as a known issue? Thanks, Raymond - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, May 24, 2007 7:19 AM Subject: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2 Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Raymond, The latest src distribution builds fine for me with a clean .m2 repo on OS X right out of the box. On 5/24/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, I grabbed the latest RC src distro and tried to build it locally after removing the local maven repo. But now I saw a test case failure as shown below. Can somebody else try it? The wierd thing is that if I tried to build the failing module again, then it passed. Thanks, Raymond [INFO] Surefire report directory: C:\Apache\tuscany-sca-0.90-incubating-src\ites t\wsdl\target\surefire-reports --- T E S T S --- Running org.apache.tuscany.sca.itest.WSDLTestCase log4j:WARN No appenders could be found for logger (org.apache.axiom.om.util.StAX Utils). log4j:WARN Please initialize the log4j system properly. Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.906sec Running org.apache.tuscany.sca.itest.SDOWSDLTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 4.579 sec FA ILURE! testClient1a2a3a4a(org.apache.tuscany.sca.itest.SDOWSDLTestCase) Time elapsed: 4.547 sec ERROR! org.apache.axis2.AxisFault: The service cannot be found for the endpoint referen ce (EPR) http://localhost:8080/AccountService1a2b3a4a at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.j ava:434) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisO peration.java:373) at org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAx isOperation.java:294) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invokeTarget (Axis2BindingInvoker.java:92) at org.apache.tuscany.sca.binding.axis2.Axis2BindingInvoker.invoke(Axis2 BindingInvoker.java:71) at org.apache.tuscany.core.databinding.wire.DataTransformationInteceptor .invoke(DataTransformationInteceptor.java:68) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at bigbank.account.services.accountdata.AccountServiceClientImpl.createA ccount(AccountServiceClientImpl.java:41) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invokeTarget(JavaTargetInvoker.java:112) at org.apache.tuscany.sca.implementation.java.invocation.JavaTargetInvok er.invoke(JavaTargetInvoker.java:134) at org.apache.tuscany.sca.implementation.java.invocation.PassByValueInvo ker.invoke(PassByValueInvoker.java:61) at org.apache.tuscany.sca.implementation.java.invocation.TargetInvokerIn voker.invoke(TargetInvokerInvoker.java:46) at org.apache.tuscany.sca.core.invocation.AbstractInvocationHandler.invo ke(AbstractInvocationHandler.java:84) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JD KInvocationHandler.java:73) at $Proxy9.createAccount(Unknown Source) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.doit(SDOWSDLTestCase.jav a:79) at org.apache.tuscany.sca.itest.SDOWSDLTestCase.testClient1a2a3a4a(SDOWS DLTestCase.java:52) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:64) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:615) at junit.framework.TestCase.runTest(TestCase.java:168) at junit.framework.TestCase.runBare(TestCase.java:134) 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:124) at junit.framework.TestSuite.runTest(TestSuite.java:232) at junit.framework.TestSuite.run(TestSuite.java:227) at org.junit.internal.runners.OldTestClassRunner.run(OldTestClassRunner. java:35) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet. java:62) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTes tSet(AbstractDirectoryTestSuite.java:138) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(Ab stractDirectoryTestSuite.java:125) at org.apache.maven.surefire.Surefire.run(Surefire.java:132) at
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Hi, I tried the binary distro too and the samples worked well. +1 to release it! Thanks, Raymond - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, May 24, 2007 7:19 AM Subject: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2 Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I tried building the source distro from an empty local maven repo. The build failed in the Axis2 binding with the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: commons-fileupload:commons-fileupload Reason: Error getting POM for 'commons-fileupload:commons-fileupload' from the repository: Error transferring file commons-fileupload:commons-fileupload:pom:1.1.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.incubator (http://people.apache.org/repo/m2-incubating-repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), apache.ws (http://ws.zones.apache.org/repository/) Simon ant elder wrote: I've just tried running it lots of times, the individual test, all the itests, and the full build and it always is working for me. ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
I'd guess that this is one of those intermittent maven repository problems, could you just try again? ...ant On 5/24/07, Simon Nash [EMAIL PROTECTED] wrote: I tried building the source distro from an empty local maven repo. The build failed in the Axis2 binding with the following error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: commons-fileupload:commons-fileupload Reason: Error getting POM for 'commons-fileupload:commons-fileupload' from the repository: Error transferring file commons-fileupload:commons-fileupload:pom:1.1.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.incubator ( http://people.apache.org/repo/m2-incubating-repository), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), apache.ws (http://ws.zones.apache.org/repository/) Simon ant elder wrote: I've just tried running it lots of times, the individual test, all the itests, and the full build and it always is working for me. ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
Hi, I tried building the source disb and the samples from the binary and all works well. +1 for the release. Thanks - Venkat On 5/24/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating RC2
ant elder wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc2/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant RC2 looks good to me. I tested the binary and source distros on RHEL Linux. I built and ran the samples, built the source distro, found no problem, and most of the things I had found in RC1 have also been addressed. I'm really happy with the release, here's my +1 !! -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo sitory(DefaultMavenProjectBuilder.java:526) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to downl oad the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def aultWagonManager.java:324) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De faultArtifactResolver.java:185) ... 20 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Tue May 22 17:03:52 PDT 2007 [INFO] Final Memory: 2M/5M [INFO] - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Monday, May 21, 2007 1:13 PM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating Another very detailed review, thank you! Comments in line, but to summarise - there's an unclear sample readme, a broken sample readme, and some missing Javadoc. This isn't perfect, but are any of those blockers requiring the delay of another RC? I think not and its better to get this release out sooner than to delay and respin another RC, so my vote is still +1 on going with this RC, and we can fix those issues in the next release. Completely open to other's opinions though so please say what you think. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: Here are my findings around the 0.9 Release Candidate, my main concern is with the issues I mentioned in the modules directory of the source. Samples: I have tried the standalone samples and the web samples (in jetty and tomcat). All samples look OK, with the exceptions of the ones mentioned below : calculator-rmi-reference - WARNING The README is confusing, by reading it, I was under the impression that the server and client were on the same project, and it also have the client and server ant xml files there. But in order to properly run the sample, you need to go to calculator-rmi-service and actually start the server there, then come to the reference (client) D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\calculator-rmi-referenceant -f build-server.xmlrun Buildfile: build-server.xml run: [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer [java] Exception in thread main [java] Java Result: 1 Looks like a cutNpaste problem between the service and client readme's, i agree this makes it confusing. implementation-crud-client - ERROR Looks like the ant.xml property has the wrong package, I have fixed this in the branch and trunk after adding the right package, it works property name=test.class value=crud.client.CRUDClient / D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\implementation-crud-clientant run Buildfile: build.xml run: [java] java.lang.NoClassDefFoundError: crud/CRUDClient [java] Exception in thread main [java] Java Result: 1 Yep, this one is broken. I guess after all the last minute changes to the way the extension samples were like. Source Modules itest\interop-soap-client - pom version has SNAPSHOT itest\interop-soap-round2-client - pom version has SNAPSHOT itest\interop-soap-service - pom version has SNAPSHOT - reference axion snapshot - reference axion-impl snapshot itest\interop-xsq-client - pom version has SNAPSHOT - still has varios scdl files modules\binding-jms -- are we shipping that ? still have SCDL files with references to snapshot, wsdl also reference snapshot modules\discovery-jms -- are we shipping that ? If so, it has SNAPSHOT version on it modules\binding-ws-xml - test1.wsdl references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService /) modules\contribution-impl - namespace defined as NS = http://tuscany.apache.org/xmlns/1.0-SNAPSHOT;; modules\interface-wsdl-xml - test1.wsdl andpoing references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService /) None of those are significant IMHO as either they're not included in the build or the reference to snapshot is not actually used at runtime. Javadoc Just a subset of packages javadoc was generated, I don't see contribution javadoc available... Is this ok ? Another flaw, ideally we'd have Javadoc for every package we said was an API or SPI. Binaries We have a dependency on JRuby release candidate (jruby-complete-1.0RC2.jar ) ? Is that ok ? Thats fine, its just SNAPSHOT build we shouldn't release with. On 5/21/07, ant elder [EMAIL PROTECTED] wrote: I don't think that document says we MUST include the STATUS document. It says Check status document meaning check that the STATUS doc doesn't say there are outstanding legal
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
) ... 17 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository org.apache.tuscany.sca:tuscany-sca:pom:0.90-incubating from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.incubator (http://people.apache.org/repo/m2-incubating-repository ) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De faultArtifactResolver.java:197) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De faultArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepo sitory(DefaultMavenProjectBuilder.java:526) ... 18 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to downl oad the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(Def aultWagonManager.java:324) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De faultArtifactResolver.java:185) ... 20 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Tue May 22 17:03:52 PDT 2007 [INFO] Final Memory: 2M/5M [INFO] - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Monday, May 21, 2007 1:13 PM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating Another very detailed review, thank you! Comments in line, but to summarise - there's an unclear sample readme, a broken sample readme, and some missing Javadoc. This isn't perfect, but are any of those blockers requiring the delay of another RC? I think not and its better to get this release out sooner than to delay and respin another RC, so my vote is still +1 on going with this RC, and we can fix those issues in the next release. Completely open to other's opinions though so please say what you think. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: Here are my findings around the 0.9 Release Candidate, my main concern is with the issues I mentioned in the modules directory of the source. Samples: I have tried the standalone samples and the web samples (in jetty and tomcat). All samples look OK, with the exceptions of the ones mentioned below : calculator-rmi-reference - WARNING The README is confusing, by reading it, I was under the impression that the server and client were on the same project, and it also have the client and server ant xml files there. But in order to properly run the sample, you need to go to calculator-rmi-service and actually start the server there, then come to the reference (client) D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\calculator-rmi-referenceant -f build-server.xmlrun Buildfile: build-server.xml run: [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer [java] Exception in thread main [java] Java Result: 1 Looks like a cutNpaste problem between the service and client readme's, i agree this makes it confusing. implementation-crud-client - ERROR Looks like the ant.xml property has the wrong package, I have fixed this in the branch and trunk after adding the right package, it works property name=test.class value=crud.client.CRUDClient / D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\implementation-crud-clientant run Buildfile: build.xml run: [java] java.lang.NoClassDefFoundError: crud/CRUDClient [java] Exception in thread main [java] Java Result: 1 Yep, this one is broken. I guess after all the last minute changes to the way the extension samples were like. Source Modules itest\interop-soap-client - pom version has SNAPSHOT itest\interop-soap-round2-client - pom version has SNAPSHOT itest\interop-soap-service - pom version has SNAPSHOT - reference axion snapshot - reference axion-impl snapshot itest\interop-xsq-client - pom version has SNAPSHOT - still has varios scdl files modules\binding-jms -- are we shipping that ? still have SCDL files with references to snapshot, wsdl also reference snapshot modules\discovery-jms -- are we shipping that ? If so, it has SNAPSHOT version on it modules\binding-ws-xml - test1.wsdl references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService /) modules\contribution-impl - namespace defined as NS = http://tuscany.apache.org/xmlns/1.0-SNAPSHOT;; modules\interface-wsdl-xml - test1.wsdl andpoing references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService /) None of those are significant IMHO as either they're not included in the build or the reference to snapshot
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I think the shop window factor is an important consideration. The cumulative effect of the issues that people have reported seems to be significant enough from this perspective that a respin is desirable. In particular, the build and sample README problems could be quite off-putting to a novice user. Simon Simon Laws wrote: I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Hi, Simon. Do you have any luck to fix the problem? If not, we probably have to document the limitation and let the release out. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 10:35 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating OK, so I can't get the compile to work on my linux box with a simple change to the version/location of the maven-jaxb-plugin that the build uses. I'm going to upgrade my JDK and see if that has a positive effect but of course that has no bearing on the SCA release. As this problem is restricted to a particular JDK on a particular platform then we can post a note about how to get round the problem manually. I would really like to fix the readmes but if that's the only thing then I can live with a note on the web page for that. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I didn't. I looked at both versions of maven-jaxb-plugin at https://maven-repository.dev.java.net/repository/com.sun.tools.xjc.maven2/poms/and both have the odd characters in. There seem to be other implementations of the maven-jaxb-plugin around and I tried the ones I could find but got NPEs in maven. Not sure whether this is the version of the plugin, the version of jaxb or a real problem. I'm not that faimiliar with JAXB and what version works with what so I don't have a quick fix. Also tried upgrading my JDK but that didn't work either. Am already on Maven 2.0.6. Happy to try any other ideas people have. What I have to do is work backwards through this and work out what version of what will actually work for us (I find trying to work this out for maven plugins very difficult) and see if I can get a combination that doesn't have the author name with the non-UTF8 character or where this particular fault has been fixed. Failing this we will have to get on whatever mail list deals with it and ask for a fix. As it stands we can offer a manual fix for anyone who has Linux/IBM JDK, i.e. run the build until it fails and then remove the problematic characters manually from the offending pom in the local repo. I can't say how long this will take but I think we need to get on with the release and address is next time. Simon
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
ant elder wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant I've reviewed the binary release on Linux. It looks pretty good to me but I have a few comments, some minor, some more important: 1) CHANGES file, I'd suggest to move the API / user items to the top and move the SPI related section to the bottom, and change Host extensions to Host integrations or Host environments. 2) RELEASE_NOTES, I'd suggest to change The Tuscany all and manifest jars... to The tuscany-sca-all and tuscany-sca-manifest jars... 3) In docs/, wer'e missing Javadoc for a number of SPI packages listed in CHANGES, and more importantly, Javadoc for the SCA Java APIs . 4) I couldn't find text explaining that tuscany-sca-all contains all the other Tuscany JARs and that you don't need them as well if you're using it. 5) The RMI READMEs seem out of sync. Also I found having the build_client and build_server in both the rmi-reference and rmi-service samples confusing, how about just having a single build.xml like the other samples do (e.g. helloworld-ws-reference and helloworld-ws-service). Build.xml would start the server in rmi-service and the client in rmi-reference. 6) The implementation-crud-client does not work (I'm probably responsible for breaking this one...) 7) Like Ant said in another email, it would be good to rename calculator-web to calculator-webapp 8) I'd suggest to rename the binding-echo-appl and implementation-crud-client to something else, as most of these samples are appls as well, and implementation-crud is not a client, but I don't have a good name proposal. I had proposed to rename echo-binding to echo-binding-extension but it doesn't fit either as none of our other extension modules are named *-extension. These two samples look too complicated to me now, but I'm not sure if we can do anything about it for this release. 8) In the helloworld-jsonrpc sample, clicking the services/HelloWorldService link at the top of the page shows an exception, this probably normal as the server expects a JSON request, but confusing. I'd suggest to remove that link. 9) I could not find text in a README describing how I would use the binary distro, load one of the samples in Eclipse or IDEA and run it from there. As a developer that's one of the things I'd like to do first to browse the sample code and experiment with it. The steps described in the samples README only apply to the source distro and require Maven expertise, we should document simpler steps for somebody using the binary distro without Maven. 10) The samples/README says that you can build with mvn from both the source and binary distros, but the steps seem to apply to only the source distro. 11) None of the samples shows the use of META-INF/sca-deployables. I'd suggest to have one of the Webapp samples use that instead of sca-contribution.xml. I think it would be good to respin another release candidate with fixes for (1), (3), (4), (5), (6), (9) and (11) at least... Thanks. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
On 5/23/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant I've reviewed the binary release on Linux. It looks pretty good to me but I have a few comments, some minor, some more important: 1) CHANGES file, I'd suggest to move the API / user items to the top and move the SPI related section to the bottom, and change Host extensions to Host integrations or Host environments. 2) RELEASE_NOTES, I'd suggest to change The Tuscany all and manifest jars... to The tuscany-sca-all and tuscany-sca-manifest jars... 3) In docs/, wer'e missing Javadoc for a number of SPI packages listed in CHANGES, and more importantly, Javadoc for the SCA Java APIs . 4) I couldn't find text explaining that tuscany-sca-all contains all the other Tuscany JARs and that you don't need them as well if you're using it. 5) The RMI READMEs seem out of sync. Also I found having the build_client and build_server in both the rmi-reference and rmi-service samples confusing, how about just having a single build.xml like the other samples do (e.g. helloworld-ws-reference and helloworld-ws-service). Build.xml would start the server in rmi-service and the client in rmi-reference. 6) The implementation-crud-client does not work (I'm probably responsible for breaking this one...) 7) Like Ant said in another email, it would be good to rename calculator-web to calculator-webapp 8) I'd suggest to rename the binding-echo-appl and implementation-crud-client to something else, as most of these samples are appls as well, and implementation-crud is not a client, but I don't have a good name proposal. I had proposed to rename echo-binding to echo-binding-extension but it doesn't fit either as none of our other extension modules are named *-extension. These two samples look too complicated to me now, but I'm not sure if we can do anything about it for this release. 8) In the helloworld-jsonrpc sample, clicking the services/HelloWorldService link at the top of the page shows an exception, this probably normal as the server expects a JSON request, but confusing. I'd suggest to remove that link. 9) I could not find text in a README describing how I would use the binary distro, load one of the samples in Eclipse or IDEA and run it from there. As a developer that's one of the things I'd like to do first to browse the sample code and experiment with it. The steps described in the samples README only apply to the source distro and require Maven expertise, we should document simpler steps for somebody using the binary distro without Maven. 10) The samples/README says that you can build with mvn from both the source and binary distros, but the steps seem to apply to only the source distro. 11) None of the samples shows the use of META-INF/sca-deployables. I'd suggest to have one of the Webapp samples use that instead of sca-contribution.xml. I think it would be good to respin another release candidate with fixes for (1), (3), (4), (5), (6), (9) and (11) at least... Which things MUST be fixed to avoid -1s on the next rc? Is 11 on this list a blocker? Is the linux compile problem a blocker? Also which things are people volunteering to fix? The javadoc one (3) seems a difficult one to fix to me which could easily end up just making things worse if we rush it. The 0.90 branch is open to everyone for updating so ideally I'd like to just get up tomorrow morning to find all the blockers fixed so I can cut anther rc, but so far its not clear what are the blockers or what the correct fix is, so its going to be difficult to know if things are in a state where I can cut another rc or not. We could spend weeks polishing this point release, is that what we want to be doing? ..ant
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I found a serious problem in the calculator-web sample in the 0.90 release candidate. The ant script for this sample builds a war that is not deployable because of two missing files. The pre-built war file that is shipped as part of the binary distro is fine. I discovered this as a last-minute glitch with my demo for the Tuscany presentation that I gave today at the IBM Impact conference. I'll write a JIRA for this now and post a patch asap (later today EDT). Simon Simon Nash wrote: I think the shop window factor is an important consideration. The cumulative effect of the issues that people have reported seems to be significant enough from this perspective that a respin is desirable. In particular, the build and sample README problems could be quite off-putting to a novice user. Simon Simon Laws wrote: I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simon C Nash IBM Distinguished Engineer Hursley Park, Winchester, UK [EMAIL PROTECTED] Tel. +44-1962-815156 Fax +44-1962-818999 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I fixed the sample problems when we mentioned them before (that's 5 and 6 from Sebatien's list). I can look at other things first thing as it sounds like we are going to respin. Too tired now to get it right. I still don't think we wait for a fix for my build problem. It's the first time it's come up, it's only on the combination of software I have and there is a (manual) work around. Simon
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Jean-Sebastien Delfino wrote: (cut) 3) In docs/, wer'e missing Javadoc for a number of SPI packages listed in CHANGES, and more importantly, Javadoc for the SCA Java APIs . The javadoc for org.osoa.sca.* is there but these packages aren't being included in the top-level index. (cut) 8) I'd suggest to rename the binding-echo-appl and implementation-crud-client to something else, as most of these samples are appls as well, and implementation-crud is not a client, but I don't have a good name proposal. I had proposed to rename echo-binding to echo-binding-extension but it doesn't fit either as none of our other extension modules are named *-extension. These two samples look too complicated to me now, but I'm not sure if we can do anything about it for this release. I don't see a problem with naming these samples *-extension to differentiate them from the other non-extension samples. As you said in an earlier post, this makes it easy for users to find the sample extensions. These are only sample toy extensions and I don't think this would cause users to put -extension on the end of the names of real extensions that they build. I think we should leave the structure of these two samples as is for this elease (modulo possible renaming), and discuss other alternatives later. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
ant elder wrote: On 5/23/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant I've reviewed the binary release on Linux. It looks pretty good to me but I have a few comments, some minor, some more important: 1) CHANGES file, I'd suggest to move the API / user items to the top and move the SPI related section to the bottom, and change Host extensions to Host integrations or Host environments. 2) RELEASE_NOTES, I'd suggest to change The Tuscany all and manifest jars... to The tuscany-sca-all and tuscany-sca-manifest jars... 3) In docs/, wer'e missing Javadoc for a number of SPI packages listed in CHANGES, and more importantly, Javadoc for the SCA Java APIs . 4) I couldn't find text explaining that tuscany-sca-all contains all the other Tuscany JARs and that you don't need them as well if you're using it. 5) The RMI READMEs seem out of sync. Also I found having the build_client and build_server in both the rmi-reference and rmi-service samples confusing, how about just having a single build.xml like the other samples do (e.g. helloworld-ws-reference and helloworld-ws-service). Build.xml would start the server in rmi-service and the client in rmi-reference. 6) The implementation-crud-client does not work (I'm probably responsible for breaking this one...) 7) Like Ant said in another email, it would be good to rename calculator-web to calculator-webapp 8) I'd suggest to rename the binding-echo-appl and implementation-crud-client to something else, as most of these samples are appls as well, and implementation-crud is not a client, but I don't have a good name proposal. I had proposed to rename echo-binding to echo-binding-extension but it doesn't fit either as none of our other extension modules are named *-extension. These two samples look too complicated to me now, but I'm not sure if we can do anything about it for this release. 8) In the helloworld-jsonrpc sample, clicking the services/HelloWorldService link at the top of the page shows an exception, this probably normal as the server expects a JSON request, but confusing. I'd suggest to remove that link. 9) I could not find text in a README describing how I would use the binary distro, load one of the samples in Eclipse or IDEA and run it from there. As a developer that's one of the things I'd like to do first to browse the sample code and experiment with it. The steps described in the samples README only apply to the source distro and require Maven expertise, we should document simpler steps for somebody using the binary distro without Maven. 10) The samples/README says that you can build with mvn from both the source and binary distros, but the steps seem to apply to only the source distro. 11) None of the samples shows the use of META-INF/sca-deployables. I'd suggest to have one of the Webapp samples use that instead of sca-contribution.xml. I think it would be good to respin another release candidate with fixes for (1), (3), (4), (5), (6), (9) and (11) at least... Which things MUST be fixed to avoid -1s on the next rc? Is 11 on this list a blocker? Is the linux compile problem a blocker? Also which things are people volunteering to fix? The javadoc one (3) seems a difficult one to fix to me which could easily end up just making things worse if we rush it. The 0.90 branch is open to everyone for updating so ideally I'd like to just get up tomorrow morning to find all the blockers fixed so I can cut anther rc, but so far its not clear what are the blockers or what the correct fix is, so its going to be difficult to know if things are in a state where I can cut another rc or not. We could spend weeks polishing this point release, is that what we want to be doing? ..ant None of them, that's why I didn't -1 the RC1. If you end up respinning an RC for other reasons then I'd say that the more important ones for me are (3), (5), (6) and (9) and it looks like Simon Laws has already fixed (5) and (6). If there's no other good reason for respinning an RC then you get my +1 for RC1 as long as we have JIRAs for these issues, and more importantly an Errata document clearly posted on our download page, documenting them and how to get around them. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
On 21/05/07, Luciano Resende [EMAIL PROTECTED] wrote: I have done necessary updates to STATUS page [1], and the Incubator Tuscany page [2]. Note that the changes on the incubator page takes a little while to get reflect on the live website. [1] https://svn.apache.org/repos/asf/incubator/tuscany/STATUS [2] http://incubator.apache.org/projects/tuscany.html I just did another update to [1] to add the news about Andy Grove becoming a committer, but I don't know where the source for [2] is. Can someone give me a pointer please? snip/
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I'm not clear what you're saying - Build failure seems to be a show-stopper to me and So if we fix it... - surely we must fix it if its a showstopper and we want to have a release? What is the fix, from the earlier post it didn't sound like there was a good known fix? ...ant On 5/22/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Build failure seems to be a show-stopper to me :-). Thank you for catching it. The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes for the unit tests. So if we fix it, the scope of testing shouldn't be a big deal. All we have to do is to run the maven build on the environments we have tested so far. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 3:37 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Ok, go ahead. You also mentioned a JavaDoc issue before, would you like to fix that as well or can that be left to be fixed on the next release? ...ant On 5/22/07, Luciano Resende [EMAIL PROTECTED] wrote: If we are going to resping the RC, I'd like to remove the modules that are not being part of the build from the source distribution. On 5/22/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Sorry for the confusion. Simon found the build break and he didn't take it as a show-stopper. I then said the build failure is serious enough to be a show stopper. Simon found the fix by moving the plugin to the latest version (I just realized that he only said that in the JIRA) but he was concerned that how the fix would impact the quality of the release. I then tried to assure him that the usage of the plugin is fairly isolated and the risk should be minor. Thanks, Raymond - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 9:01 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating I'm not clear what you're saying - Build failure seems to be a show-stopper to me and So if we fix it... - surely we must fix it if its a showstopper and we want to have a release? What is the fix, from the earlier post it didn't sound like there was a good known fix? ...ant On 5/22/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Build failure seems to be a show-stopper to me :-). Thank you for catching it. The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes for the unit tests. So if we fix it, the scope of testing shouldn't be a big deal. All we have to do is to run the maven build on the environments we have tested so far. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 3:37 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Ok :) I hadn't read the JIRA. Simon, as you're the one that can recreate this would you be able to commit that and test it works for you? ...ant On 5/22/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Sorry for the confusion. Simon found the build break and he didn't take it as a show-stopper. I then said the build failure is serious enough to be a show stopper. Simon found the fix by moving the plugin to the latest version (I just realized that he only said that in the JIRA) but he was concerned that how the fix would impact the quality of the release. I then tried to assure him that the usage of the plugin is fairly isolated and the risk should be minor. Thanks, Raymond - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 9:01 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating I'm not clear what you're saying - Build failure seems to be a show-stopper to me and So if we fix it... - surely we must fix it if its a showstopper and we want to have a release? What is the fix, from the earlier post it didn't sound like there was a good known fix? ...ant On 5/22/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Build failure seems to be a show-stopper to me :-). Thank you for catching it. The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes for the unit tests. So if we fix it, the scope of testing shouldn't be a big deal. All we have to do is to run the maven build on the environments we have tested so far. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 3:37 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Hi, Sorry for the confusion. Simon found the build break and he didn't take it as a show-stopper. I then said the build failure is serious enough to be a show stopper. Simon found the fix by moving the plugin to the latest version (I just realized that he only said that in the JIRA) but he was concerned that how the fix would impact the quality of the release. I then tried to assure him that the usage of the plugin is fairly isolated and the risk should be minor. Thanks, Raymond - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 9:01 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating I'm not clear what you're saying - Build failure seems to be a show-stopper to me and So if we fix it... - surely we must fix it if its a showstopper and we want to have a release? What is the fix, from the earlier post it didn't sound like there was a good known fix? ...ant On 5/22/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Build failure seems to be a show-stopper to me :-). Thank you for catching it. The databinding-jaxb uses the maven-jaxb-plugin to generate JAXB classes for the unit tests. So if we fix it, the scope of testing shouldn't be a big deal. All we have to do is to run the maven build on the environments we have tested so far. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Tuesday, May 22, 2007 3:37 AM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating I've given the src and binary distros a spin on linux. My configuration is Fedora Core5 IBM JDK 1.5.0 Maven 2.0.6 Binary: I concur with Luciano that the READMEs for calculator-rmi-reference calculator-rmi-service implementation-crud now don't match the way that the samples are currently organized. I'm reluctant to agree to go with this release when our shop window isn't fully functional. I have checked fixes in for the calculator sample to the 0.9branch and head. Luciano's fix for implementation-crud looks good to me. Source: This fails to build under maven in my environment. The culprit is the maven-jaxb-plugin. The pom provided with the version that we refer in our poms, e.g. databinding-jaxb, has a non-UTF8 character in one of the author names which causes the maven build to fail with the IBM JDK 1.5.0 on Linux. I can confirm that this does not cause a problem with the same JDK (same version and build at least) on Windows XP. I tried using different maven-jaxb-plugins from a variety of repositories. All failed for other reasons. There is a manual work around to the problem, i.e. remove the non-UTF8 characters, so I don't think that this, on its own is a blocker. I've raised http://issues.apache.org/jira/browse/TUSCANY-1296 for this. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Hi, I've give the distros a shot on windows xp. - The src disb. builds clean - The tried all the samples from the binary dist just following the READMEs. Like the others I do find the README for the rmi samples out of sync and also the crud-client app does not run. But all the other samples run cleanly. With the rmi samples I am quite surprised because during the code chill time period I think I fixed the samples to run as per the README. The RMI Server sample used a RMI Client ( an not a SCA Reference) and similarly the RMI Reference sample used a RMI Server (not a SCA Service) and each was pretty compact in itself. I am not sure about where it changed after that. Anyways, looking at it overall I'd like to give a '+1' based on the following: - - Though I agree that this is not the most perfect of packages I still feel none of the glitches are paralysing. For example, even if the rmi samples did not work as per the README they contain all that is required to run them and then there are a whole bunch of other samples that work cleanly demonstrating SCA and the extensions we offer to date. - Its been a while since we released and this one has fundamental changes to how things were a few months ago. Getting this release out asap is good for us and to users so that there is enough time for trying out and giving feedback that can be picked up for our next release which I guess is going to be in another few weeks from now. - Finally this is just about 0.90 and I am ok to have the sort of issues that have been identified with it. I am happy to know what we need to watch for in our next release. Thanks - Venkat On 5/21/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
OK, so I can't get the compile to work on my linux box with a simple change to the version/location of the maven-jaxb-plugin that the build uses. I'm going to upgrade my JDK and see if that has a positive effect but of course that has no bearing on the SCA release. As this problem is restricted to a particular JDK on a particular platform then we can post a note about how to get round the problem manually. I would really like to fix the readmes but if that's the only thing then I can live with a note on the web page for that. Simon
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(De faultArtifactResolver.java:185) ... 20 more [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Tue May 22 17:03:52 PDT 2007 [INFO] Final Memory: 2M/5M [INFO] - Original Message - From: ant elder [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Monday, May 21, 2007 1:13 PM Subject: Re: [VOTE] Release Tuscany Java SCA 0.90-incubating Another very detailed review, thank you! Comments in line, but to summarise - there's an unclear sample readme, a broken sample readme, and some missing Javadoc. This isn't perfect, but are any of those blockers requiring the delay of another RC? I think not and its better to get this release out sooner than to delay and respin another RC, so my vote is still +1 on going with this RC, and we can fix those issues in the next release. Completely open to other's opinions though so please say what you think. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: Here are my findings around the 0.9 Release Candidate, my main concern is with the issues I mentioned in the modules directory of the source. Samples: I have tried the standalone samples and the web samples (in jetty and tomcat). All samples look OK, with the exceptions of the ones mentioned below : calculator-rmi-reference - WARNING The README is confusing, by reading it, I was under the impression that the server and client were on the same project, and it also have the client and server ant xml files there. But in order to properly run the sample, you need to go to calculator-rmi-service and actually start the server there, then come to the reference (client) D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\calculator-rmi-referenceant -f build-server.xmlrun Buildfile: build-server.xml run: [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer [java] Exception in thread main [java] Java Result: 1 Looks like a cutNpaste problem between the service and client readme's, i agree this makes it confusing. implementation-crud-client - ERROR Looks like the ant.xml property has the wrong package, I have fixed this in the branch and trunk after adding the right package, it works property name=test.class value=crud.client.CRUDClient / D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\implementation-crud-clientant run Buildfile: build.xml run: [java] java.lang.NoClassDefFoundError: crud/CRUDClient [java] Exception in thread main [java] Java Result: 1 Yep, this one is broken. I guess after all the last minute changes to the way the extension samples were like. Source Modules itest\interop-soap-client - pom version has SNAPSHOT itest\interop-soap-round2-client - pom version has SNAPSHOT itest\interop-soap-service - pom version has SNAPSHOT - reference axion snapshot - reference axion-impl snapshot itest\interop-xsq-client - pom version has SNAPSHOT - still has varios scdl files modules\binding-jms -- are we shipping that ? still have SCDL files with references to snapshot, wsdl also reference snapshot modules\discovery-jms -- are we shipping that ? If so, it has SNAPSHOT version on it modules\binding-ws-xml - test1.wsdl references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService /) modules\contribution-impl - namespace defined as NS = http://tuscany.apache.org/xmlns/1.0-SNAPSHOT;; modules\interface-wsdl-xml - test1.wsdl andpoing references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService /) None of those are significant IMHO as either they're not included in the build or the reference to snapshot is not actually used at runtime. Javadoc Just a subset of packages javadoc was generated, I don't see contribution javadoc available... Is this ok ? Another flaw, ideally we'd have Javadoc for every package we said was an API or SPI. Binaries We have a dependency on JRuby release candidate (jruby-complete-1.0RC2.jar ) ? Is that ok ? Thats fine, its just SNAPSHOT build we shouldn't release with. On 5/21/07, ant elder [EMAIL PROTECTED] wrote: I don't think that document says we MUST include the STATUS document. It says Check status document meaning check that the STATUS doc doesn't say there are outstanding legal issues that may prevent a release. Even if that releasemanagement doc did say we must, the doc is still under development and in draft state so I'm not sure its binding policy. Given other recent incubator releases didn't include the STATUS doc and an IPMCer recently said it could be removed from a distro i think this is not a blocking issue. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Ant, I've had a good poke around and built the source distro and run the tests successfully. The only potential blocking issue I have found is that absence of a STATUS file, which it was my understanding should be copied in from the project's STATUS file into every distribution, but I haven't been able to re-find that guidance in the apache site. Can anyone help clarify this please? The rest of these comments are all minor observations that wouldn't stop me +1-ing the release. Indeed, some of them may result in clarification that what you have done is corrent and that will help SDO in future releases? I've had comments in the past that Apache like it if the names of the release file names include the apache- prefix I think the copyright in the NOTICES file at the top level of the source distro should include 2005 I thought that the intention of the BUILDING file was to guide a person who has downloaded the source distribution to be able to recreate the distribution files, not just to compile and test? I can't re-find the guidance on that having searched that apache site. The LICENSE file in binary distro contains CPL 1.0 twice, once for wsdl4j and then at the bottom for Jruby. It would be really helpful to include a package.html file for each package so that the javadoc gives an overview of what each package does. Cheers, Kelvin. On 20/05/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Hey many thanks for the prompt and detailed review. I can't remember exactly about the STATUS file, i think it may be an old requirement that is no longer necessary. I can find this incubator-general email [1] about the recent CXF release which included and old and incorrect status file, and the guidance from an IPMC member was its ok to just remove it from the distro, so i think its fine we don't include this. All these other comments seem like good things we should do in future, if we do have to respin the 0.90 distro's for some other reason I'll try to incorporate some of them. Thanks, ...ant [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/[EMAIL PROTECTED] On 5/21/07, kelvin goodson [EMAIL PROTECTED] wrote: Ant, I've had a good poke around and built the source distro and run the tests successfully. The only potential blocking issue I have found is that absence of a STATUS file, which it was my understanding should be copied in from the project's STATUS file into every distribution, but I haven't been able to re-find that guidance in the apache site. Can anyone help clarify this please? The rest of these comments are all minor observations that wouldn't stop me +1-ing the release. Indeed, some of them may result in clarification that what you have done is corrent and that will help SDO in future releases? I've had comments in the past that Apache like it if the names of the release file names include the apache- prefix I think the copyright in the NOTICES file at the top level of the source distro should include 2005 I thought that the intention of the BUILDING file was to guide a person who has downloaded the source distribution to be able to recreate the distribution files, not just to compile and test? I can't re-find the guidance on that having searched that apache site. The LICENSE file in binary distro contains CPL 1.0 twice, once for wsdl4j and then at the bottom for Jruby. It would be really helpful to include a package.html file for each package so that the javadoc gives an overview of what each package does. Cheers, Kelvin. On 20/05/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Regarding the STATUS document, I think the policy say we must include them, check [1] on the Release Documentation and STATUS document sessions. Also our STATUS file is not up to date, and I can take care of helping updating that after I finish reviewing the rest of the release candidate. [1] - http://incubator.apache.org/guides/releasemanagement.html On 5/21/07, ant elder [EMAIL PROTECTED] wrote: Hey many thanks for the prompt and detailed review. I can't remember exactly about the STATUS file, i think it may be an old requirement that is no longer necessary. I can find this incubator-general email [1] about the recent CXF release which included and old and incorrect status file, and the guidance from an IPMC member was its ok to just remove it from the distro, so i think its fine we don't include this. All these other comments seem like good things we should do in future, if we do have to respin the 0.90 distro's for some other reason I'll try to incorporate some of them. Thanks, ...ant [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/[EMAIL PROTECTED] On 5/21/07, kelvin goodson [EMAIL PROTECTED] wrote: Ant, I've had a good poke around and built the source distro and run the tests successfully. The only potential blocking issue I have found is that absence of a STATUS file, which it was my understanding should be copied in from the project's STATUS file into every distribution, but I haven't been able to re-find that guidance in the apache site. Can anyone help clarify this please? The rest of these comments are all minor observations that wouldn't stop me +1-ing the release. Indeed, some of them may result in clarification that what you have done is corrent and that will help SDO in future releases? I've had comments in the past that Apache like it if the names of the release file names include the apache- prefix I think the copyright in the NOTICES file at the top level of the source distro should include 2005 I thought that the intention of the BUILDING file was to guide a person who has downloaded the source distribution to be able to recreate the distribution files, not just to compile and test? I can't re-find the guidance on that having searched that apache site. The LICENSE file in binary distro contains CPL 1.0 twice, once for wsdl4j and then at the bottom for Jruby. It would be really helpful to include a package.html file for each package so that the javadoc gives an overview of what each package does. Cheers, Kelvin. On 20/05/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I don't think that document says we MUST include the STATUS document. It says Check status document meaning check that the STATUS doc doesn't say there are outstanding legal issues that may prevent a release. Even if that releasemanagement doc did say we must, the doc is still under development and in draft state so I'm not sure its binding policy. Given other recent incubator releases didn't include the STATUS doc and an IPMCer recently said it could be removed from a distro i think this is not a blocking issue. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: Regarding the STATUS document, I think the policy say we must include them, check [1] on the Release Documentation and STATUS document sessions. Also our STATUS file is not up to date, and I can take care of helping updating that after I finish reviewing the rest of the release candidate. [1] - http://incubator.apache.org/guides/releasemanagement.html On 5/21/07, ant elder [EMAIL PROTECTED] wrote: Hey many thanks for the prompt and detailed review. I can't remember exactly about the STATUS file, i think it may be an old requirement that is no longer necessary. I can find this incubator-general email [1] about the recent CXF release which included and old and incorrect status file, and the guidance from an IPMC member was its ok to just remove it from the distro, so i think its fine we don't include this. All these other comments seem like good things we should do in future, if we do have to respin the 0.90 distro's for some other reason I'll try to incorporate some of them. Thanks, ...ant [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/[EMAIL PROTECTED] On 5/21/07, kelvin goodson [EMAIL PROTECTED] wrote: Ant, I've had a good poke around and built the source distro and run the tests successfully. The only potential blocking issue I have found is that absence of a STATUS file, which it was my understanding should be copied in from the project's STATUS file into every distribution, but I haven't been able to re-find that guidance in the apache site. Can anyone help clarify this please? The rest of these comments are all minor observations that wouldn't stop me +1-ing the release. Indeed, some of them may result in clarification that what you have done is corrent and that will help SDO in future releases? I've had comments in the past that Apache like it if the names of the release file names include the apache- prefix I think the copyright in the NOTICES file at the top level of the source distro should include 2005 I thought that the intention of the BUILDING file was to guide a person who has downloaded the source distribution to be able to recreate the distribution files, not just to compile and test? I can't re-find the guidance on that having searched that apache site. The LICENSE file in binary distro contains CPL 1.0 twice, once for wsdl4j and then at the bottom for Jruby. It would be really helpful to include a package.html file for each package so that the javadoc gives an overview of what each package does. Cheers, Kelvin. On 20/05/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
Here are my findings around the 0.9 Release Candidate, my main concern is with the issues I mentioned in the modules directory of the source. Samples: I have tried the standalone samples and the web samples (in jetty and tomcat). All samples look OK, with the exceptions of the ones mentioned below : calculator-rmi-reference - WARNING The README is confusing, by reading it, I was under the impression that the server and client were on the same project, and it also have the client and server ant xml files there. But in order to properly run the sample, you need to go to calculator-rmi-service and actually start the server there, then come to the reference (client) D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\calculator-rmi-referenceant -f build-server.xmlrun Buildfile: build-server.xml run: [java] java.lang.NoClassDefFoundError: calculator/CalculatorServer [java] Exception in thread main [java] Java Result: 1 implementation-crud-client - ERROR Looks like the ant.xml property has the wrong package, I have fixed this in the branch and trunk after adding the right package, it works property name=test.class value=crud.client.CRUDClient / D:\temp\0.9 Release\tuscany- sca-0.90-incubating\samples\implementation-crud-clientant run Buildfile: build.xml run: [java] java.lang.NoClassDefFoundError: crud/CRUDClient [java] Exception in thread main [java] Java Result: 1 Source Modules itest\interop-soap-client - pom version has SNAPSHOT itest\interop-soap-round2-client - pom version has SNAPSHOT itest\interop-soap-service - pom version has SNAPSHOT - reference axion snapshot - reference axion-impl snapshot itest\interop-xsq-client - pom version has SNAPSHOT - still has varios scdl files modules\binding-jms -- are we shipping that ? still have SCDL files with references to snapshot, wsdl also reference snapshot modules\discovery-jms -- are we shipping that ? If so, it has SNAPSHOT version on it modules\binding-ws-xml - test1.wsdl references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService; /) modules\contribution-impl - namespace defined as NS = http://tuscany.apache.org/xmlns/1.0-SNAPSHOT;; modules\interface-wsdl-xml - test1.wsdl andpoing references snapshot (wsdlsoap:address location= http://localhost:8080/sample-helloworldws-1.0-SNAPSHOT/services/HelloWorldWebService; /) Javadoc Just a subset of packages javadoc was generated, I don't see contribution javadoc available... Is this ok ? Binaries We have a dependency on JRuby release candidate (jruby-complete-1.0RC2.jar) ? Is that ok ? On 5/21/07, ant elder [EMAIL PROTECTED] wrote: I don't think that document says we MUST include the STATUS document. It says Check status document meaning check that the STATUS doc doesn't say there are outstanding legal issues that may prevent a release. Even if that releasemanagement doc did say we must, the doc is still under development and in draft state so I'm not sure its binding policy. Given other recent incubator releases didn't include the STATUS doc and an IPMCer recently said it could be removed from a distro i think this is not a blocking issue. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: Regarding the STATUS document, I think the policy say we must include them, check [1] on the Release Documentation and STATUS document sessions. Also our STATUS file is not up to date, and I can take care of helping updating that after I finish reviewing the rest of the release candidate. [1] - http://incubator.apache.org/guides/releasemanagement.html On 5/21/07, ant elder [EMAIL PROTECTED] wrote: Hey many thanks for the prompt and detailed review. I can't remember exactly about the STATUS file, i think it may be an old requirement that is no longer necessary. I can find this incubator-general email [1] about the recent CXF release which included and old and incorrect status file, and the guidance from an IPMC member was its ok to just remove it from the distro, so i think its fine we don't include this. All these other comments seem like good things we should do in future, if we do have to respin the 0.90 distro's for some other reason I'll try to incorporate some of them. Thanks, ...ant [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/[EMAIL PROTECTED] On 5/21/07, kelvin goodson [EMAIL PROTECTED] wrote: Ant, I've had a good poke around and built the source distro and run the tests successfully. The only potential blocking issue I have found is that absence of a STATUS file, which it was my understanding should be copied in from the project's STATUS file into every distribution, but I haven't been able to re-find that guidance in the apache site. Can anyone help clarify this please? The rest of these comments are all minor observations
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I have done necessary updates to STATUS page [1], and the Incubator Tuscany page [2]. Note that the changes on the incubator page takes a little while to get reflect on the live website. [1] https://svn.apache.org/repos/asf/incubator/tuscany/STATUS [2] http://incubator.apache.org/projects/tuscany.html On 5/21/07, ant elder [EMAIL PROTECTED] wrote: I don't think that document says we MUST include the STATUS document. It says Check status document meaning check that the STATUS doc doesn't say there are outstanding legal issues that may prevent a release. Even if that releasemanagement doc did say we must, the doc is still under development and in draft state so I'm not sure its binding policy. Given other recent incubator releases didn't include the STATUS doc and an IPMCer recently said it could be removed from a distro i think this is not a blocking issue. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: Regarding the STATUS document, I think the policy say we must include them, check [1] on the Release Documentation and STATUS document sessions. Also our STATUS file is not up to date, and I can take care of helping updating that after I finish reviewing the rest of the release candidate. [1] - http://incubator.apache.org/guides/releasemanagement.html On 5/21/07, ant elder [EMAIL PROTECTED] wrote: Hey many thanks for the prompt and detailed review. I can't remember exactly about the STATUS file, i think it may be an old requirement that is no longer necessary. I can find this incubator-general email [1] about the recent CXF release which included and old and incorrect status file, and the guidance from an IPMC member was its ok to just remove it from the distro, so i think its fine we don't include this. All these other comments seem like good things we should do in future, if we do have to respin the 0.90 distro's for some other reason I'll try to incorporate some of them. Thanks, ...ant [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/[EMAIL PROTECTED] On 5/21/07, kelvin goodson [EMAIL PROTECTED] wrote: Ant, I've had a good poke around and built the source distro and run the tests successfully. The only potential blocking issue I have found is that absence of a STATUS file, which it was my understanding should be copied in from the project's STATUS file into every distribution, but I haven't been able to re-find that guidance in the apache site. Can anyone help clarify this please? The rest of these comments are all minor observations that wouldn't stop me +1-ing the release. Indeed, some of them may result in clarification that what you have done is corrent and that will help SDO in future releases? I've had comments in the past that Apache like it if the names of the release file names include the apache- prefix I think the copyright in the NOTICES file at the top level of the source distro should include 2005 I thought that the intention of the BUILDING file was to guide a person who has downloaded the source distribution to be able to recreate the distribution files, not just to compile and test? I can't re-find the guidance on that having searched that apache site. The LICENSE file in binary distro contains CPL 1.0 twice, once for wsdl4j and then at the bottom for Jruby. It would be really helpful to include a package.html file for each package so that the javadoc gives an overview of what each package does. Cheers, Kelvin. On 20/05/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/
Re: [VOTE] Release Tuscany Java SCA 0.90-incubating
I checked out the source from the 0.90 tag and it builds fine from an empty mvn repository on Mac OS X and the reactor summary is clean. I also randomly chose several of the samples from the distribution binaries (calculator-script, supplychain, simple-bigbank, implementation-composite) and they work as advertised. +1 from me On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: I have done necessary updates to STATUS page [1], and the Incubator Tuscany page [2]. Note that the changes on the incubator page takes a little while to get reflect on the live website. [1] https://svn.apache.org/repos/asf/incubator/tuscany/STATUS [2] http://incubator.apache.org/projects/tuscany.html On 5/21/07, ant elder [EMAIL PROTECTED] wrote: I don't think that document says we MUST include the STATUS document. It says Check status document meaning check that the STATUS doc doesn't say there are outstanding legal issues that may prevent a release. Even if that releasemanagement doc did say we must, the doc is still under development and in draft state so I'm not sure its binding policy. Given other recent incubator releases didn't include the STATUS doc and an IPMCer recently said it could be removed from a distro i think this is not a blocking issue. ...ant On 5/21/07, Luciano Resende [EMAIL PROTECTED] wrote: Regarding the STATUS document, I think the policy say we must include them, check [1] on the Release Documentation and STATUS document sessions. Also our STATUS file is not up to date, and I can take care of helping updating that after I finish reviewing the rest of the release candidate. [1] - http://incubator.apache.org/guides/releasemanagement.html On 5/21/07, ant elder [EMAIL PROTECTED] wrote: Hey many thanks for the prompt and detailed review. I can't remember exactly about the STATUS file, i think it may be an old requirement that is no longer necessary. I can find this incubator-general email [1] about the recent CXF release which included and old and incorrect status file, and the guidance from an IPMC member was its ok to just remove it from the distro, so i think its fine we don't include this. All these other comments seem like good things we should do in future, if we do have to respin the 0.90 distro's for some other reason I'll try to incorporate some of them. Thanks, ...ant [1] http://mail-archives.apache.org/mod_mbox/incubator-general/200705.mbox/[EMAIL PROTECTED] On 5/21/07, kelvin goodson [EMAIL PROTECTED] wrote: Ant, I've had a good poke around and built the source distro and run the tests successfully. The only potential blocking issue I have found is that absence of a STATUS file, which it was my understanding should be copied in from the project's STATUS file into every distribution, but I haven't been able to re-find that guidance in the apache site. Can anyone help clarify this please? The rest of these comments are all minor observations that wouldn't stop me +1-ing the release. Indeed, some of them may result in clarification that what you have done is corrent and that will help SDO in future releases? I've had comments in the past that Apache like it if the names of the release file names include the apache- prefix I think the copyright in the NOTICES file at the top level of the source distro should include 2005 I thought that the intention of the BUILDING file was to guide a person who has downloaded the source distribution to be able to recreate the distribution files, not just to compile and test? I can't re-find the guidance on that having searched that apache site. The LICENSE file in binary distro contains CPL 1.0 twice, once for wsdl4j and then at the bottom for Jruby. It would be really helpful to include a package.html file for each package so that the javadoc gives an overview of what each package does. Cheers, Kelvin. On 20/05/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 0.90 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/0.90-rc1/http://people.apache.org/%7Eantelder/tuscany/0.90-rc1/ This includes the binary and source distributions, the RAT reports, and the Maven staging repository. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/0.90-incubating/ Looks ok to me so here's my +1. Thanks in advance, ...ant -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresendehttp://people.apache.org/%7Elresende http://lresende.blogspot.com/ --
