Re: [VOTE] Release Tuscany Java SCA 1.0 RC3a
First, thanks a ton for all the work, Ant. - I've tried building the samples from the bin distro and all seems fine but for the minor issue reported in https://issues.apache.org/jira/browse/TUSCANY-1752 and the minor typo in the README of helloworld-ws-reference-secure - Source distro builds fine, though its been painfully slow - Licenses seem to be in place. So, here is my +1 for releasing Java SCA 1.0 - RC3a - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/ http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Welcome aboard! ..ant On 9/19/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike.
Re: Change freeze on 1.0 branch
Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.x releases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant
Re: Change freeze on 1.0 branch
On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant +1 Sounds like the right thing to do Simon
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Welcome aboard! ..ant On 9/19/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike. Well deserved Simon, Welcome. Simon
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Well deserved! Congratulations Simon. Paul On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Welcome aboard! ..ant On 9/19/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike. Well deserved Simon, Welcome. Simon -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Congratulations Simon!! Vamsi On 9/20/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike.
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3a
+1 (non-binding) from me. I have downloaded the RC3a, and ran some samples, tests and those looked fine. Regards, Amita On 9/20/07, Venkata Krishnan [EMAIL PROTECTED] wrote: First, thanks a ton for all the work, Ant. - I've tried building the samples from the bin distro and all seems fine but for the minor issue reported in https://issues.apache.org/jira/browse/TUSCANY-1752 and the minor typo in the README of helloworld-ws-reference-secure - Source distro builds fine, though its been painfully slow - Licenses seem to be in place. So, here is my +1 for releasing Java SCA 1.0 - RC3a - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/ http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Congratulations Simon and Welcome ! :) - Venkat On 9/20/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike.
Re: Change freeze on 1.0 branch
+1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Congrats Simon ; ) On 9/20/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Congratulations Simon and Welcome ! :) - Venkat On 9/20/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike.
[jira] Created: (TUSCANY-1771) Creating JavaDoc for the integration tests listed under sca/itest folder
Creating JavaDoc for the integration tests listed under sca/itest folder -- Key: TUSCANY-1771 URL: https://issues.apache.org/jira/browse/TUSCANY-1771 Project: Tuscany Issue Type: Improvement Components: Java SCA Integration Tests Affects Versions: Java-SCA-0.91 Environment: Windows XP. Java 1.5, Reporter: Naveen Creation of JavaDoc for integration tests is necessary to describe the intent of the test case. It should have details about, what exactly the test case seeks to test, verify or accomplish. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[DISCUSS] JIRA - was:Fwd: Change freeze on 1.0 branch
-- Forwarded message -- From: Venkata Krishnan [EMAIL PROTECTED] Date: Sep 20, 2007 8:16 AM Subject: Re: Change freeze on 1.0 branch To: tuscany-dev@ws.apache.org, [EMAIL PROTECTED] +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant Hi It feels like we have been getting better at using JIRA in the run up to 0.99 and 1.0 release in terms of the consistency with which we raise bug reports and assign them to releases. Based on Ant's branch freeze suggestion how about we now 1/ create the following versions in JIRA JAVA-SCA-1.1 - as the trunk target JAVA-SCA-1.0.1 - as the 1.0 branch target in case we need it 2/ Review the JIRA components to make them match the modules we currently have. Several options here, e.g. a/ add a component for any module we have in svn that is not represented b/ stick with the shorter list, as we have now, making sure we have one for each extension and general ones for Itests, samples, demos , distribution etc. 3/ Continue the theme of creating JIRAs for the bug/enhancements we see and assigning them to the release where we want them to be fixed. B.t.w I'm happy to do admin tasks as appropriate. Simon
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Congratulations and welcome Simon! hear hear!! Kelvin. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1772) Setting::getDataObjectValue returning null pointer
Setting::getDataObjectValue returning null pointer -- Key: TUSCANY-1772 URL: https://issues.apache.org/jira/browse/TUSCANY-1772 Project: Tuscany Issue Type: Bug Components: C++ SDO Affects Versions: Cpp-Next Environment: windows xp professional edition Microsoft Visual Studio 2005 Reporter: Adriano Crestani Priority: Critical Fix For: Cpp-Next The method setting.getDataObjectValue is returning a null pointer when the setting.getType().isDataObjectType()==true http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg23852.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Thanks everyone for the congratulations and welcome. It has been great working with you, and I'm looking forward to the next exciting stage of the Tuscany journey. And thanks to those (especially Raymond :-) who have committed my patches over the last few months. Simon Adriano Crestani wrote: Congrats Simon ; ) On 9/20/07, Venkata Krishnan [EMAIL PROTECTED] wrote: Congratulations Simon and Welcome ! :) - Venkat On 9/20/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-1772) Setting::getDataObjectValue returning null pointer
[ https://issues.apache.org/jira/browse/TUSCANY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Crestani updated TUSCANY-1772: -- Attachment: tuscan1772.adrianocrestani.09_20_2007.patch a new testcase was inserted on SDO tests project, but on this patch, the only testcase being executed is the jira1772, because the others are failing(I dont know why) This testcase, jira1772, demonstrates how the method Setting::getDataObjectValue() is not working as expected, returning a null pointer when its Type is a DataObject Setting::getDataObjectValue returning null pointer -- Key: TUSCANY-1772 URL: https://issues.apache.org/jira/browse/TUSCANY-1772 Project: Tuscany Issue Type: Bug Components: C++ SDO Affects Versions: Cpp-Next Environment: windows xp professional edition Microsoft Visual Studio 2005 Reporter: Adriano Crestani Priority: Critical Fix For: Cpp-Next Attachments: tuscan1772.adrianocrestani.09_20_2007.patch The method setting.getDataObjectValue is returning a null pointer when the setting.getType().isDataObjectType()==true http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg23852.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] JIRA - was:Fwd: Change freeze on 1.0 branch
On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: -- Forwarded message -- From: Venkata Krishnan [EMAIL PROTECTED] Date: Sep 20, 2007 8:16 AM Subject: Re: Change freeze on 1.0 branch To: tuscany-dev@ws.apache.org, [EMAIL PROTECTED] +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant Hi It feels like we have been getting better at using JIRA in the run up to 0.99 and 1.0 release in terms of the consistency with which we raise bug reports and assign them to releases. Based on Ant's branch freeze suggestion how about we now 1/ create the following versions in JIRA JAVA-SCA-1.1 - as the trunk target JAVA-SCA-1.0.1 - as the 1.0 branch target in case we need it 2/ Review the JIRA components to make them match the modules we currently have. Several options here, e.g. a/ add a component for any module we have in svn that is not represented b/ stick with the shorter list, as we have now, making sure we have one for each extension and general ones for Itests, samples, demos , distribution etc. 3/ Continue the theme of creating JIRAs for the bug/enhancements we see and assigning them to the release where we want them to be fixed. B.t.w I'm happy to do admin tasks as appropriate. Simon All those sound good to me. For 2/ i'd go for b/ - the shorter list, and do some review/cleanup of the current list of the components we have or at least come up with some clear reasons why we need each separate component. ...ant
Re: Change freeze on 1.0 branch
+1. If there are any issues when people start using 1.0, this is a good way to take care of them. Would the intention be to limit changes in the branch to fixes for significant functional problems, or to also apply patches for the various minor non-functional glitches that have been found in the reviews of RC3a? Simon Venkata Krishnan wrote: +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Change freeze on 1.0 branch
Its a judgement call, i think it would be good to fix some of the glitches spotted in the reviews but I guess ultimately its anything someone proposes where they can get at least 3 +1s and more +1s than -1s. I'd say we should be conservative and keep changes to a minimum just to keep the diff to the previous release small so its real easy to review and get the release votes done. ...ant On 9/20/07, Simon Nash [EMAIL PROTECTED] wrote: +1. If there are any issues when people start using 1.0, this is a good way to take care of them. Would the intention be to limit changes in the branch to fixes for significant functional problems, or to also apply patches for the various minor non-functional glitches that have been found in the reviews of RC3a? Simon Venkata Krishnan wrote: +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] JIRA - was:Fwd: Change freeze on 1.0 branch
ant elder wrote: On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: -- Forwarded message -- From: Venkata Krishnan [EMAIL PROTECTED] Date: Sep 20, 2007 8:16 AM Subject: Re: Change freeze on 1.0 branch To: tuscany-dev@ws.apache.org, [EMAIL PROTECTED] +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant Hi It feels like we have been getting better at using JIRA in the run up to 0.99 and 1.0 release in terms of the consistency with which we raise bug reports and assign them to releases. Based on Ant's branch freeze suggestion how about we now 1/ create the following versions in JIRA JAVA-SCA-1.1 - as the trunk target JAVA-SCA-1.0.1 - as the 1.0 branch target in case we need it 2/ Review the JIRA components to make them match the modules we currently have. Several options here, e.g. a/ add a component for any module we have in svn that is not represented b/ stick with the shorter list, as we have now, making sure we have one for each extension and general ones for Itests, samples, demos , distribution etc. 3/ Continue the theme of creating JIRAs for the bug/enhancements we see and assigning them to the release where we want them to be fixed. B.t.w I'm happy to do admin tasks as appropriate. Simon All those sound good to me. For 2/ i'd go for b/ - the shorter list, and do some review/cleanup of the current list of the components we have or at least come up with some clear reasons why we need each separate component. ...ant +1 for a cleaned up version of the shorter list. And +1 for Simon's other proposals. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3a
+1 from me On 9/20/07, Amita Vadhavkar [EMAIL PROTECTED] wrote: +1 (non-binding) from me. I have downloaded the RC3a, and ran some samples, tests and those looked fine. Regards, Amita On 9/20/07, Venkata Krishnan [EMAIL PROTECTED] wrote: First, thanks a ton for all the work, Ant. - I've tried building the samples from the bin distro and all seems fine but for the minor issue reported in https://issues.apache.org/jira/browse/TUSCANY-1752 and the minor typo in the README of helloworld-ws-reference-secure - Source distro builds fine, though its been painfully slow - Licenses seem to be in place. So, here is my +1 for releasing Java SCA 1.0 - RC3a - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/ http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] Oxygenating the Web Service Platform, www.wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3a
+1 Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: websphere web service deployment problem
Hi Sebastien,
thanks for your help! It was the the custom Web container property as
described in the WebSphere fixpack.
I can also confirm now that it works with 6.1.0.11 fixpack as well, if
the property is set.
In the log file, however, we are getting something I am not sure we
were getting before:
[20/09/07 10:47:17:187 BST] 0036 ValidatingXML W XMLSchema
validation problem in:
file:/c:/Program%20Files/IBM/WebSphere/AppServer/profiles/vws/installedApps/vws/example-sc-0_0_1_war.ear/example-sc-0.0.1.war/WEB-INF/classes/example-sc.composite,
line: 12, column: 7
cvc-complex-type.2.4.a: Invalid content was found starting with
element 'implementation.java'. One of
'{http://www.osoa.org/xmlns/sca/1.0:service,
http://www.osoa.org/xmlns/sca/1.0:reference,
http://www.osoa.org/xmlns/sca/1.0:property}' is expected.
Do you have an idea what could be wrong?
It looks to me that in http://www.osoa.org/xmlns/sca/1.0/sca-core.xsd
the following code suggests that only service, reference or property
elements are possible within the component:
- sequence
element ref=sca:implementation minOccurs=0 maxOccurs=1 /
- choice minOccurs=0 maxOccurs=unbounded
element name=service type=sca:ComponentService /
element name=reference type=sca:ComponentReference /
element name=property type=sca:Property /
/choice
any namespace=##other processContents=lax minOccurs=0
maxOccurs=unbounded /
/sequence
We also have implementation.java there and it seems to be a valid
option based on several examples, including examples in the spec.
Thanks,
Radim
On 9/19/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Radim Kolarik wrote:
Hi Simon,
unfortunatelly I am seeing the same problem on WAS 6.1.0.9.
Sebastien, do you still have the WAS environment? Could you try to
deploy RC3 based example web service on it?
Thanks a lot,
Radim
It works for me.
I need more precise information to be able to help.
- which web service based sample? helloworld? calculator? built
yourself? using mvn or ant?
- the steps you are following to install and run the sample and the
exact output you are getting when you run it
- whether or not you have configured the WAR classloader parent last
and single classloader
- whether or not you have configured the custom Web container property
as described in the WebSphere fixpack at [1]
- the time of the error
- your SystemOut.log and SystemError.log files
- the FFDC files created in yout logs directory at the time of the error
Could you please put that information in a JIRA. I'm watching the JIRA
notifications so I'll get notified when you do so, and will investigate
quickly. Thanks.
[1] http://www-1.ibm.com/support/docview.wss?uid=swg24014758
Thanks.
--
Jean-Sebastien
-
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]
[jira] Assigned: (TUSCANY-1765) Component implementation has wrong intent
[ https://issues.apache.org/jira/browse/TUSCANY-1765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Venkatakrishnan reassigned TUSCANY-1765: Assignee: Venkatakrishnan Component implementation has wrong intent - Key: TUSCANY-1765 URL: https://issues.apache.org/jira/browse/TUSCANY-1765 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-0.99 Reporter: Greg Dritschler Assignee: Venkatakrishnan Priority: Minor Attachments: TUSCANY-1765.patch Suppose there is a composite with multiple components that use the same implementation class but different implementation intents, as shown below. composite xmlns=http://www.osoa.org/xmlns/sca/1.0; name=CompositeX component name=ComponentA implementation.java class=test.DataServiceImpl requires=managedTransaction.none/ /component component name=ComponentB implementation.java class=test.DataServiceImpl requires=managedTransaction.global/ /component /composite In this case the components will share a common Implementation model object because only the class name is being used to determine whether a component's implementation is the same as another's. This means one of the components will have the wrong implementation intents recorded in the model. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [NOTICE] Simon Nash voted as Tuscany Committer.
Congratulations Simon, and welcome. On 9/19/07, Mike Edwards [EMAIL PROTECTED] wrote: Folks, The Tuscany PPMC and the Incubator PMC have voted for Simon to become a Tuscany committer. Congratulations and welcome Simon! I'm sure that everyone will be looking forward to more excellent contributions from Simon to Tuscany. Yours, Mike.
Re: Build issue with implementation-bpel module
Are you still seeing this? I'm getting it in the trunk with the
latest update.
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
I'm get a similar build failure related to surefire in the 1.0 branch:
[INFO] Configured Artifact: org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apache\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.
1.zip into
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter15021.jar
java.lang.NoClassDefFoundError:
org/apache/maven/surefire/booter/SurefireBooter
Exception in thread main
[INFO]
[ERROR] BUILD FAILURE
...ant
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I ran into an issue in the implementation-bpel module from the top-down
build. The error message is as follows. But if I run the build for the
module only, everything works fine.
Any clue?
Thanks,
Raymond
[INFO] [compiler:testCompile]
[INFO] Compiling 4 source files to
C:\Tuscany\java\sca\modules\implementation-bp
el\target\test-classes
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apa
che\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.1.zip into
C:\Tuscan
y\java\sca\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\java\sca\modules\implementation-bpe
l\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter57948.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at
sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java:1118
)
at
sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java
:960)
at
java.security.AccessController.doPrivileged(AccessController.java:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
The java class is not found:
org.apache.maven.surefire.booter.SurefireBooter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-1637) Rationalize the SCA Domain implementations
[ https://issues.apache.org/jira/browse/TUSCANY-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529116 ] Simon Laws commented on TUSCANY-1637: - The interface changes didn't make it into 1.0. The distributed support is now split between node-* and domain-* modules and this is fronted by an SCADomain like interface in the domain-api module. We need to discuss on the list about where to take SCADomain. Rationalize the SCA Domain implementations -- Key: TUSCANY-1637 URL: https://issues.apache.org/jira/browse/TUSCANY-1637 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime, Java SCA Embedded Runtime Affects Versions: Java-SCA-0.99 Reporter: Simon Laws Assignee: Simon Laws Fix For: Java-SCA-Next We now have a number of domain implementations in Tuscany Java SCA including - The SCADomain interface - DefaultSCADomain - EmbeddedSCADomain - HotUpdatableSCADomain - DistributedDomain/Node - distribution webapp? We should try to boil this down to the minimum number of APIs that are required. A thread on the ML has been started on this subject -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build issue with implementation-bpel module
On 9/20/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote:
Are you still seeing this? I'm getting it in the trunk with the
latest update.
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
I'm get a similar build failure related to surefire in the 1.0 branch:
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apache\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.
1.zip into
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter15021.jar
java.lang.NoClassDefFoundError:
org/apache/maven/surefire/booter/SurefireBooter
Exception in thread main
[INFO]
[ERROR] BUILD FAILURE
...ant
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I ran into an issue in the implementation-bpel module from the
top-down
build. The error message is as follows. But if I run the build for the
module only, everything works fine.
Any clue?
Thanks,
Raymond
[INFO] [compiler:testCompile]
[INFO] Compiling 4 source files to
C:\Tuscany\java\sca\modules\implementation-bp
el\target\test-classes
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apa
che\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.1.zip into
C:\Tuscan
y\java\sca\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\java\sca\modules\implementation-bpe
l\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter57948.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at
sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java:1118
)
at
sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java
:960)
at
java.security.AccessController.doPrivileged(AccessController.java:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java
:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
The java class is not found:
org.apache.maven.surefire.booter.SurefireBooter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
In trunk, I'm seeing this..
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\simon\tuscany\java-head\sca\modules\impleme
ntation-bpel\target\surefire-reports
[INFO] Building jar: C:\DOCUME~1\slaws\LOCALS~1\Temp\surefirebooter60808.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java
:1118
)
at sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java
:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:960)
at java.security.AccessController.doPrivileged(AccessController.java
:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
The java class is not found:
org.apache.maven.surefire.booter.SurefireBooter
Simon
[jira] Created: (TUSCANY-1773) Implement policyset validation against candidate sca elements using the xpath provided in 'appliesTo' attibute
Implement policyset validation against candidate sca elements using the xpath provided in 'appliesTo' attibute -- Key: TUSCANY-1773 URL: https://issues.apache.org/jira/browse/TUSCANY-1773 Project: Tuscany Issue Type: Bug Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Reporter: Venkatakrishnan Assignee: Venkatakrishnan Policysets specified in a composite for various elements and policysets inherited by various elements in a composite need to be validated for their applicablility to the element in question (i.e. whether it applies to a given binding element or implementation element ). The 'appliesTo' attribute in the policyset provides an xpath expression that must be used for this validation. Presently the expression provided in the 'appliesTo' is taken as bearing the qname of the element to which it applies. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1774) Support application of Policy Intents and Policysets to operations
Support application of Policy Intents and Policysets to operations -- Key: TUSCANY-1774 URL: https://issues.apache.org/jira/browse/TUSCANY-1774 Project: Tuscany Issue Type: Improvement Components: Java SCA Assembly Model Affects Versions: Java-SCA-Next Reporter: Venkatakrishnan Assignee: Venkatakrishnan Fix For: Java-SCA-Next -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] JIRA - was:Fwd: Change freeze on 1.0 branch
+1 on Simon's proposal. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 12:43 AM Subject: [DISCUSS] JIRA - was:Fwd: Change freeze on 1.0 branch -- Forwarded message -- From: Venkata Krishnan [EMAIL PROTECTED] Date: Sep 20, 2007 8:16 AM Subject: Re: Change freeze on 1.0 branch To: tuscany-dev@ws.apache.org, [EMAIL PROTECTED] +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant Hi It feels like we have been getting better at using JIRA in the run up to 0.99 and 1.0 release in terms of the consistency with which we raise bug reports and assign them to releases. Based on Ant's branch freeze suggestion how about we now 1/ create the following versions in JIRA JAVA-SCA-1.1 - as the trunk target JAVA-SCA-1.0.1 - as the 1.0 branch target in case we need it 2/ Review the JIRA components to make them match the modules we currently have. Several options here, e.g. a/ add a component for any module we have in svn that is not represented b/ stick with the shorter list, as we have now, making sure we have one for each extension and general ones for Itests, samples, demos , distribution etc. 3/ Continue the theme of creating JIRAs for the bug/enhancements we see and assigning them to the release where we want them to be fixed. B.t.w I'm happy to do admin tasks as appropriate. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1775) Implement mechanism to allow selection of a binding out of several available bindings based on policy intents
Implement mechanism to allow selection of a binding out of several available bindings based on policy intents - Key: TUSCANY-1775 URL: https://issues.apache.org/jira/browse/TUSCANY-1775 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Reporter: Venkatakrishnan Assignee: Venkatakrishnan Fix For: Java-SCA-Next -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] JIRA - was:Fwd: Change freeze on 1.0 branch
+1 on the proposal. I think a cleaning up the components to a shortlist will be nice. Thanks - Venkat On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: -- Forwarded message -- From: Venkata Krishnan [EMAIL PROTECTED] Date: Sep 20, 2007 8:16 AM Subject: Re: Change freeze on 1.0 branch To: tuscany-dev@ws.apache.org, [EMAIL PROTECTED] +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zones repo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant Hi It feels like we have been getting better at using JIRA in the run up to 0.99 and 1.0 release in terms of the consistency with which we raise bug reports and assign them to releases. Based on Ant's branch freeze suggestion how about we now 1/ create the following versions in JIRA JAVA-SCA-1.1 - as the trunk target JAVA-SCA-1.0.1 - as the 1.0 branch target in case we need it 2/ Review the JIRA components to make them match the modules we currently have. Several options here, e.g. a/ add a component for any module we have in svn that is not represented b/ stick with the shorter list, as we have now, making sure we have one for each extension and general ones for Itests, samples, demos , distribution etc. 3/ Continue the theme of creating JIRAs for the bug/enhancements we see and assigning them to the release where we want them to be fixed. B.t.w I'm happy to do admin tasks as appropriate. Simon
Re: binding-notification-broker sample does not work in RC1b or RC1a..
This is just an issue with the README, instead of java -Dnotification.httpPort=8080 -cp target\sample- binding-notification-broker-1.0-incubating-SNAPSHOT.jar;%TUSCANY_SCA_MANIFEST_JAR% notification.broker.TrafficAdvisoryServer it should read java -Dnotification.httpPort=8080 -cp target\sample- binding-notification-broker-1.0-incubating.jar;%TUSCANY_SCA_MANIFEST_JAR% notification.broker.TrafficAdvisoryServer Notice that the ant scripts did not seem to have made it into the RC, otherwise we could also get rid of the 1.0-incubating prefix. Let me know if it's not too late to change the README on the 1.0 branch. On 9/17/07, haleh mahbod [EMAIL PROTECTED] wrote: could you please try it with rc1b? On 9/17/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote: This is interesting, it runs for me out of the trunk. I have not updated today though. I notice that set TUSCANY_Bin_DISTRO has mixed upper case and lower case, but other than that I can't see a difference with what I am typing ... On 9/17/07, haleh mahbod [EMAIL PROTECTED] wrote: Hi, Can someone else give this a try? I cannot get this running. I am getting: C:\tuscany-new\sca-dist\tuscany- sca-1.0-incubating\samples\binding-notification- brokerset TUSCANY_Bin_DISTRO=c:\tuscany-new\sca-dist\tuscany- sca-1.0-incubating C:\tuscany-new\sca-dist\tuscany- sca-1.0-incubating\samples\binding-notification- brokerset TUSCANY_SCA_MANIFEST_JAR=%TUSCANY_BIN_DISTRO%\lib\tuscany-sca-manifes t.jar C:\tuscany-new\sca-dist\tuscany- sca-1.0-incubating\samples\binding-notification- brokerjava -Dnotification.httpPort=8080 -cp target\sample-binding-notification -broker-1.0-incubating-SNAPSHOT.jar;%TUSCANY_SCA_MANIFEST_JAR% notification.bro ker.TrafficAdvisoryServer Exception in thread main java.lang.NoClassDefFoundError: notification/broker/T rafficAdvisoryServer Should this be out of binary distribution if noone can run it? Haleh
Re: Merging branch changes back into truck
Thank you for volunteering. That would be great that we do in a batch. Please note some of the changes may have already been merged not by the check-in sequence. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 1:58 AM Subject: Merging branch changes back into truck There are quite a few changes in the branch that are not in the trunk. http://people.apache.org/~slaws/Report.html - anything blue or red on the right hand side means there is something. I'm just sorting out the domain/node changes. Most others are small things, poms etc. Let me know if you want me to do a general sweep. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1776) Top-level build with clean repo fails in implementation-bpel
Top-level build with clean repo fails in implementation-bpel
Key: TUSCANY-1776
URL: https://issues.apache.org/jira/browse/TUSCANY-1776
Project: Tuscany
Issue Type: Bug
Components: Java SCA BPEL Implementation Extension
Affects Versions: Java-SCA-1.0
Environment: Windowx XP, maven 2.0.5
Reporter: Simon Nash
Fix For: Java-SCA-Next
A top-level build of tuscany-sca-1.0-rc3a with an empty maven repo fails with
the following error. A subsequent rebuild without cleaning the repo works fine.
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact: org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\nash\.m2\repository\org\apache\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.1.zip
into
H:\tuscany-1.0-rc3a\tuscany-sca-1.0-incubating-src\modules\implementation-bpel\target\test-classes
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plugins:maven-surefire-plugin:2.3:test': Unable to find the
mojo 'org.apache.maven.plugins:maven-surefire-plugin:2.3:test' in the plugin
'org.apache.maven.plugins:maven-surefire-plugin'
Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-surefire-plugin:2.3:test.
[INFO]
[INFO] For more information, run Maven with the -e switch
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: websphere web service deployment problem
According to the SCDL schema, the implementation.* element must come
first in a service or reference. This is what the
element ref=sca:implementation minOccurs=0 maxOccurs=1 /
line in the schema is saying.
The message is telling you that the SCDL has elements appearing in a
different order. (See TUSCANY-1738.) The message is only a warning,
and the SCDL will be processed successfully. To eliminate the message,
reorder the SCDL so that the implementation.java element comes first.
Simon
Radim Kolarik wrote:
Hi Sebastien,
thanks for your help! It was the the custom Web container property as
described in the WebSphere fixpack.
I can also confirm now that it works with 6.1.0.11 fixpack as well, if
the property is set.
In the log file, however, we are getting something I am not sure we
were getting before:
[20/09/07 10:47:17:187 BST] 0036 ValidatingXML W XMLSchema
validation problem in:
file:/c:/Program%20Files/IBM/WebSphere/AppServer/profiles/vws/installedApps/vws/example-sc-0_0_1_war.ear/example-sc-0.0.1.war/WEB-INF/classes/example-sc.composite,
line: 12, column: 7
cvc-complex-type.2.4.a: Invalid content was found starting with
element 'implementation.java'. One of
'{http://www.osoa.org/xmlns/sca/1.0:service,
http://www.osoa.org/xmlns/sca/1.0:reference,
http://www.osoa.org/xmlns/sca/1.0:property}' is expected.
Do you have an idea what could be wrong?
It looks to me that in http://www.osoa.org/xmlns/sca/1.0/sca-core.xsd
the following code suggests that only service, reference or property
elements are possible within the component:
- sequence
element ref=sca:implementation minOccurs=0 maxOccurs=1 /
- choice minOccurs=0 maxOccurs=unbounded
element name=service type=sca:ComponentService /
element name=reference type=sca:ComponentReference /
element name=property type=sca:Property /
/choice
any namespace=##other processContents=lax minOccurs=0
maxOccurs=unbounded /
/sequence
We also have implementation.java there and it seems to be a valid
option based on several examples, including examples in the spec.
Thanks,
Radim
On 9/19/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Radim Kolarik wrote:
Hi Simon,
unfortunatelly I am seeing the same problem on WAS 6.1.0.9.
Sebastien, do you still have the WAS environment? Could you try to
deploy RC3 based example web service on it?
Thanks a lot,
Radim
It works for me.
I need more precise information to be able to help.
- which web service based sample? helloworld? calculator? built
yourself? using mvn or ant?
- the steps you are following to install and run the sample and the
exact output you are getting when you run it
- whether or not you have configured the WAR classloader parent last
and single classloader
- whether or not you have configured the custom Web container property
as described in the WebSphere fixpack at [1]
- the time of the error
- your SystemOut.log and SystemError.log files
- the FFDC files created in yout logs directory at the time of the error
Could you please put that information in a JIRA. I'm watching the JIRA
notifications so I'll get notified when you do so, and will investigate
quickly. Thanks.
[1] http://www-1.ibm.com/support/docview.wss?uid=swg24014758
Thanks.
--
Jean-Sebastien
-
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 1.0 RC3a
Everything looks good but it seems that a few copyright notices are missing in the NOTICE file. Is it generated by Maven? I could spot at least XmlBeans, Xalan, Xerces and Derby. As that's the only problem I can find, I think you can just patch the release archives without the necessity of restarting the vote if you want. Cheers, Matthieu On 9/20/07, kelvin goodson [EMAIL PROTECTED] wrote: +1 Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/ http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1777) Implement distributed domain support in webapps
Implement distributed domain support in webapps
---
Key: TUSCANY-1777
URL: https://issues.apache.org/jira/browse/TUSCANY-1777
Project: Tuscany
Issue Type: New Feature
Affects Versions: Java-SCA-1.0
Environment: All
Reporter: Simon Laws
Fix For: Java-SCA-Next
host-webapp currently uses the standalone domain implementation. Covert it to
use the distributed version.
Note. in binding-sca-axis2 there is a test to find out it Tuscany is running in
a web app (in which case it uses the node uri as the endpoint url for
registration - as it can't get it from the web container)
if
(servletHost.getClass().getName().equals(WebbAppServletHost)){
Need to look at whether there is a better way of doing this
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1778) Creation of new msg structure to handle faults from web service calls
Creation of new msg structure to handle faults from web service calls
-
Key: TUSCANY-1778
URL: https://issues.apache.org/jira/browse/TUSCANY-1778
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Axis Binding Extension
Affects Versions: Java-SCA-1.0
Reporter: Simon Laws
Priority: Minor
Fix For: Java-SCA-Next
If Axis2 returns a fault it sets the fault into the contents of the original
message. In the Axis2BindingInvoker the invoke code looks like this...
public Message invoke(Message msg) {
try {
Object resp = invokeTarget(msg);
msg.setBody(resp);
} catch (AxisFault e) {
if (e.getDetail() != null) {
FaultException f = new FaultException(e.getMessage(),
e.getDetail());
f.setLogical(e.getDetail().getQName());
msg.setFaultBody(f);
} else {
msg.setFaultBody(e);
}
} catch (Throwable e) {
msg.setFaultBody (e);
}
return msg;
}
Why does it set values in the input message as well as returning it as a return
value? I can see the point in the case of a real return value as you avoid the
resource of creating a extra message object. In the fault case though this
limits the ability of the infrastructure to resend the message if it wants to
as it gets overwritten.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Trunk : Null pointer exception in SCA Data binding for SDO
Hi, Is anything seeing on the trunk ? I updated and am trying a clean build. testTransform(org.apache.tuscany.sca.databinding.sdo.DataObject2NodeTestCase) Time elapsed: 0.02 sec ERROR! org.apache.tuscany.sca.databinding.TransformationException: java.lang.NullPointerException at org.apache.tuscany.sca.databinding.sdo.Node2DataObject.transform( Node2DataObject.java:47) at org.apache.tuscany.sca.databinding.sdo.DataObject2NodeTestCase.testTransform (DataObject2NodeTestCase.java 53) Thanks - Venkat
Re: Trunk : Null pointer exception in SCA Data binding for SDO
Hi, Venkat. Can you provide the full stacktrace? If you can debug out which variable is null, it would be even better. Thanks, Raymond - Original Message - From: Venkata Krishnan [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 9:15 AM Subject: Trunk : Null pointer exception in SCA Data binding for SDO Hi, Is anything seeing on the trunk ? I updated and am trying a clean build. testTransform(org.apache.tuscany.sca.databinding.sdo.DataObject2NodeTestCase) Time elapsed: 0.02 sec ERROR! org.apache.tuscany.sca.databinding.TransformationException: java.lang.NullPointerException at org.apache.tuscany.sca.databinding.sdo.Node2DataObject.transform( Node2DataObject.java:47) at org.apache.tuscany.sca.databinding.sdo.DataObject2NodeTestCase.testTransform (DataObject2NodeTestCase.java 53) Thanks - Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1779) Determining the contribution location (confusion over relative location URLs)
Determining the contribution location (confusion over relative location URLs)
-
Key: TUSCANY-1779
URL: https://issues.apache.org/jira/browse/TUSCANY-1779
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.0
Environment: All
Reporter: Simon Laws
Fix For: Java-SCA-Next
SCADomain, in both of its guises, allows the details of which contribution to
load to be specified.
the standalone version
o.a.t.s.host.embedded.SCADomain.newInstance(String domainURI, String
contributionLocation, String... composites)
and the distributed version
o.a.t.s.domain.SCADomain.newInstance(String domainURI, String nodeURI, String
contributionLocation, String... composites) {
I have found this confusing so, by looking at the code, here is what I think
the rules are;
contributionLocation - an absolute path to a contribution in URL form, e.g
file://C:/mydirA
jar:file://C:/myjar.jar
composite(s) - the name of a composite file(s) e.g.
mycomposite.composite
somedir/mycomposite.composite
So the various combinations give rise to
contributionLocation set / composite null
loads all contributions under the contribution location identified
contributionLocation null / composite set
finds the location of your compsite on the classpath and uses that as the
contribution location. It loads the named composite from there
contributionLocation / composite
loads the named composite from the specified contribution path
contributionLocation null / composite null
This option is also used if the above rules don't identify a contribution URL
for whatever reason.
No contribution has been specified so look for the following in order and use
the location of the first one found as the contribution location
META-INF/sca-contribution.xml
META-INF/sca-contribution-generated.xml
META-INF/sca-deployables directory
The slight wrinkle with the code currently is that the algorithm is coded such
that if you specify a relative ContributionLocation (which is not valid
according to what I have set out above) then it is simply ignored and the
algorithm falls back to the other mechanisms for finding the contribution
location with potentially confusing results, for example, if I use the
reasonable looking
SCADomain domain = SCADomain.newInstance(http://localhost:8080;,
somedir/someotherdir, some.composite);
Then this will actually just look on the classpath for some.composite which
is probably not what was expected.
We could fix this in code by not testing for an absolute contribution location
path and letting it throw a malformed url exception. However this doesn't seem
absolutely essential to be done right now so I propose to raise a JIRA and tidy
up the above as a section in the documentation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Updating documents for Tuscany Java SCA 1.0
Hi, As the 1.0 release is being voted on, I suggest that we spend some time updating the documents on the web site. I'll start with the Tuscany data binding guide. Thanks, Raymond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Merging branch changes back into truck
On 9/20/07, Raymond Feng [EMAIL PROTECTED] wrote: Thank you for volunteering. That would be great that we do in a batch. Please note some of the changes may have already been merged not by the check-in sequence. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 1:58 AM Subject: Merging branch changes back into truck There are quite a few changes in the branch that are not in the trunk. http://people.apache.org/~slaws/Report.html - anything blue or red on the right hand side means there is something. I'm just sorting out the domain/node changes. Most others are small things, poms etc. Let me know if you want me to do a general sweep. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the domain/node changes and the tuscany-sca-spi changes Let me take a look at the others then. I'll shout if I get stuck Simon
Re: Merging branch changes back into truck
The BPEL related projects are already merged. They have some differences as trunk has been evolving. On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Raymond Feng [EMAIL PROTECTED] wrote: Thank you for volunteering. That would be great that we do in a batch. Please note some of the changes may have already been merged not by the check-in sequence. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 1:58 AM Subject: Merging branch changes back into truck There are quite a few changes in the branch that are not in the trunk. http://people.apache.org/~slaws/Report.html - anything blue or red on the right hand side means there is something. I'm just sorting out the domain/node changes. Most others are small things, poms etc. Let me know if you want me to do a general sweep. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the domain/node changes and the tuscany-sca-spi changes Let me take a look at the others then. I'll shout if I get stuck Simon -- 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 1.0 RC3a
+1 On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/ http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant
Re: Build issue with implementation-bpel module
You should have the BPEL related projects using surefire 2.3.1 SNAPSHOT
!-- http://jira.codehaus.org/browse/SUREFIRE-322 --
version2.3.1-SNAPSHOT/version
I'm updating my trunk to latest revision and would give it a try.
On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/20/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote:
Are you still seeing this? I'm getting it in the trunk with the
latest update.
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
I'm get a similar build failure related to surefire in the 1.0 branch:
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apache\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.
1.zip into
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter15021.jar
java.lang.NoClassDefFoundError:
org/apache/maven/surefire/booter/SurefireBooter
Exception in thread main
[INFO]
[ERROR] BUILD FAILURE
...ant
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I ran into an issue in the implementation-bpel module from the
top-down
build. The error message is as follows. But if I run the build for the
module only, everything works fine.
Any clue?
Thanks,
Raymond
[INFO] [compiler:testCompile]
[INFO] Compiling 4 source files to
C:\Tuscany\java\sca\modules\implementation-bp
el\target\test-classes
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apa
che\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.1.zip into
C:\Tuscan
y\java\sca\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\java\sca\modules\implementation-bpe
l\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter57948.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at
sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java:1118
)
at
sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java
:960)
at
java.security.AccessController.doPrivileged(AccessController.java:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java
:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
The java class is not found:
org.apache.maven.surefire.booter.SurefireBooter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
In trunk, I'm seeing this..
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\simon\tuscany\java-head\sca\modules\impleme
ntation-bpel\target\surefire-reports
[INFO] Building jar: C:\DOCUME~1\slaws\LOCALS~1\Temp\surefirebooter60808.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java
:1118
)
at sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java
:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:960)
at java.security.AccessController.doPrivileged(AccessController.java
:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
The java class is not found:
org.apache.maven.surefire.booter.SurefireBooter
Simon
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
Re: [VOTE] Release Tuscany Java SCA 1.0 RC3a
On 9/20/07, Matthieu Riou [EMAIL PROTECTED] wrote: Everything looks good but it seems that a few copyright notices are missing in the NOTICE file. Is it generated by Maven? I could spot at least XmlBeans, Xalan, Xerces and Derby. Replying to myself :) Actually I don't see a reason this should delay the release at hand as it looks pretty good. You should just make sure that this issue is properly addressed before the next release but I don't think this is a real problem for now. So here is my +1. As that's the only problem I can find, I think you can just patch the release archives without the necessity of restarting the vote if you want. Cheers, Matthieu On 9/20/07, kelvin goodson [EMAIL PROTECTED] wrote: +1 Kelvin. On 19/09/2007, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the 1.0 release artifacts of Tuscany SCA for Java. The SVN tag for the release is: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0-RC3a/ The artifacts are available for review at: http://people.apache.org/~antelder/tuscany/1.0-RC3a/http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ http://people.apache.org/%7Eantelder/tuscany/1.0-RC3a/ This includes the signed binary and source distributions, the RAT reports, and the Maven staging repository. Many thanks, ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] JIRA - was:Fwd: Change freeze on 1.0 branch
On 9/20/07, Venkata Krishnan [EMAIL PROTECTED] wrote: +1 on the proposal. I think a cleaning up the components to a shortlist will be nice. Thanks - Venkat On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: -- Forwarded message -- From: Venkata Krishnan [EMAIL PROTECTED] Date: Sep 20, 2007 8:16 AM Subject: Re: Change freeze on 1.0 branch To: tuscany-dev@ws.apache.org, [EMAIL PROTECTED] +1... makes lot of sense to me - Venkat On 9/20/07, ant elder [EMAIL PROTECTED] wrote: Just a reminder there is still a change freeze on the 1.0 branch. Its still possible we may need to respin for some reason, but how about also planning on doing some 1.0.x releases after 1.0 is out? If we keep changes in the branch to an absolute minimum it should be easy to do 1.0.xreleases after all the 1.0 reviewing so we can just show a small diff of 1.0 - 1.0.xand review/voting should be painless so we could do 1.0.x release every 1 or 2 weeks if necessary. With that in mind how about we switch to Review-Then-Commit mode on the branch - so all changes get attached as diff to a JIRA and can only be applied to the branch with 3 +1s on the ML? ...ant On 9/19/07, ant elder [EMAIL PROTECTED] wrote: Looks like 1.0 is getting pretty close now so can we have a change freeze on the 1.0 branch to avoid any last minute regressions please - no updates to it without asking first. We need an RC4 to fix the missing xquery sample and the ws.zonesrepo, but i'd hope RC4 can be the final one. Please continue reviewing RC3 and raising jira's for any issues you find (and finding fixes for the issues!), and i'll cut an RC4 late today. Lets try to keep the RC4 vote thread clean - so just +1/-1 and anything else in a jira. If you do find a serious issue be great if you could say something like +1 as long as jira xxx is resolved. Thanks! ...ant Hi It feels like we have been getting better at using JIRA in the run up to 0.99 and 1.0 release in terms of the consistency with which we raise bug reports and assign them to releases. Based on Ant's branch freeze suggestion how about we now 1/ create the following versions in JIRA JAVA-SCA-1.1 - as the trunk target JAVA-SCA-1.0.1 - as the 1.0 branch target in case we need it 2/ Review the JIRA components to make them match the modules we currently have. Several options here, e.g. a/ add a component for any module we have in svn that is not represented b/ stick with the shorter list, as we have now, making sure we have one for each extension and general ones for Itests, samples, demos , distribution etc. 3/ Continue the theme of creating JIRAs for the bug/enhancements we see and assigning them to the release where we want them to be fixed. B.t.w I'm happy to do admin tasks as appropriate. Simon I've added the new version numbers and will fix the component list tomorrow. How about we go roughly with the top level structure that we have + a few extra categories for orthogonal issues as appropriate Java SCA Implementation (modules) Java SCA Integration Tests (Itest) Java SCA Samples (samples) Java SCA Demos (demos) Java SCA Build (distribution) Java SCA Tools (tools) Java SCA Website Java SCA Problem Determination ? any others. It's not clear to me that any greater fidelity is adding value at the moment. There is value if we start having owners for particular modules or it the bug structure matches the build structure in any meaningful way. Simon
[jira] Created: (TUSCANY-1780) [JAVA-SDO] Incorrect generation of class with default value for a list
[JAVA-SDO] Incorrect generation of class with default value for a list -- Key: TUSCANY-1780 URL: https://issues.apache.org/jira/browse/TUSCANY-1780 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0, Java-SDO-Next Environment: Windows XP, JRE 1.4.2 and JRE 1.5 Reporter: Chris Mildebrandt Priority: Critical Hello, There seems to be a problem when generating static classes when lists are involved. I have the following lines in my schema: xsd:attribute name=categoryType type=address:CategoryType use=required default=myCat/ simpleType name=CategoryType list itemType=category / /simpleType This generates the following line in the impl class: protected static final Object CATEGORY_TYPE_DEFAULT_ = ((EFactory)ModelFactory.INSTANCE).createFromString(ModelPackageImpl.eINSTANCE.getObject(), myCat); The class ModelPackageImpl doesn't exist. I've tried this with the 1.0 version of SDO and a version I built today. Let me know if you need any more information. Thanks, -Chris -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Build issue with implementation-bpel module
It should be ok now, I had to change the sca pom to use 2.3.1-snapshot as well.
On 9/20/07, Luciano Resende [EMAIL PROTECTED] wrote:
You should have the BPEL related projects using surefire 2.3.1 SNAPSHOT
!-- http://jira.codehaus.org/browse/SUREFIRE-322 --
version2.3.1-SNAPSHOT/version
I'm updating my trunk to latest revision and would give it a try.
On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/20/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote:
Are you still seeing this? I'm getting it in the trunk with the
latest update.
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
I'm get a similar build failure related to surefire in the 1.0 branch:
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apache\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.
1.zip into
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter15021.jar
java.lang.NoClassDefFoundError:
org/apache/maven/surefire/booter/SurefireBooter
Exception in thread main
[INFO]
[ERROR] BUILD FAILURE
...ant
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I ran into an issue in the implementation-bpel module from the
top-down
build. The error message is as follows. But if I run the build for the
module only, everything works fine.
Any clue?
Thanks,
Raymond
[INFO] [compiler:testCompile]
[INFO] Compiling 4 source files to
C:\Tuscany\java\sca\modules\implementation-bp
el\target\test-classes
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apa
che\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.1.zip into
C:\Tuscan
y\java\sca\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\java\sca\modules\implementation-bpe
l\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter57948.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at
sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java:1118
)
at
sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java
:960)
at
java.security.AccessController.doPrivileged(AccessController.java:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java
:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
The java class is not found:
org.apache.maven.surefire.booter.SurefireBooter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
In trunk, I'm seeing this..
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\simon\tuscany\java-head\sca\modules\impleme
ntation-bpel\target\surefire-reports
[INFO] Building jar: C:\DOCUME~1\slaws\LOCALS~1\Temp\surefirebooter60808.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java
:1118
)
at sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java
:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:960)
at java.security.AccessController.doPrivileged(AccessController.java
:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:327)
Re: Build issue with implementation-bpel module
On 9/20/07, Luciano Resende [EMAIL PROTECTED] wrote:
It should be ok now, I had to change the sca pom to use 2.3.1-snapshot as
well.
On 9/20/07, Luciano Resende [EMAIL PROTECTED] wrote:
You should have the BPEL related projects using surefire 2.3.1 SNAPSHOT
!-- http://jira.codehaus.org/browse/SUREFIRE-322 --
version2.3.1-SNAPSHOT/version
I'm updating my trunk to latest revision and would give it a try.
On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/20/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote:
Are you still seeing this? I'm getting it in the trunk with the
latest update.
On 9/16/07, ant elder [EMAIL PROTECTED] wrote:
I'm get a similar build failure related to surefire in the 1.0branch:
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apache\ode\ode-dao-jpa-ojpa-derby\1.1\ode-dao-jpa-ojpa-derby-1.
1.zip into
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\SVN\1.0-BRN\modules\implementation-bpel\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter15021.jar
java.lang.NoClassDefFoundError:
org/apache/maven/surefire/booter/SurefireBooter
Exception in thread main
[INFO]
[ERROR] BUILD FAILURE
...ant
On 9/16/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
I ran into an issue in the implementation-bpel module from the
top-down
build. The error message is as follows. But if I run the build
for the
module only, everything works fine.
Any clue?
Thanks,
Raymond
[INFO] [compiler:testCompile]
[INFO] Compiling 4 source files to
C:\Tuscany\java\sca\modules\implementation-bp
el\target\test-classes
[INFO] [dependency:unpack {execution: unpack}]
[INFO] Configured Artifact:
org.apache.ode:ode-dao-jpa-ojpa-derby:1.1:zip
[INFO] Expanding: C:\Documents and
Settings\Administrator\.m2\repository\org\apa
che\ode\ode-dao-jpa-ojpa-derby\1.1\ode-
dao-jpa-ojpa-derby-1.1.zip into
C:\Tuscan
y\java\sca\modules\implementation-bpel\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\Tuscany\java\sca\modules\implementation-bpe
l\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\surefirebooter57948.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at
sun.misc.URLClassPath$JarLoader.parseClassPath(URLClassPath.java
:1118
)
at
sun.misc.URLClassPath$JarLoader.getClassPath(URLClassPath.java
:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java
:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java
:322)
at java.net.URLClassLoader$ClassFinder.run(
URLClassLoader.java
:960)
at
java.security.AccessController.doPrivileged(
AccessController.java:275
)
at java.net.URLClassLoader.findClass(URLClassLoader.java
:488)
at java.lang.ClassLoader.loadClass(ClassLoader.java:607)
at sun.misc.Launcher$AppClassLoader.loadClass(
Launcher.java
:327)
at java.lang.ClassLoader.loadClass(ClassLoader.java:573)
The java class is not found:
org.apache.maven.surefire.booter.SurefireBooter
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
In trunk, I'm seeing this..
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\simon\tuscany\java-head\sca\modules\impleme
ntation-bpel\target\surefire-reports
[INFO] Building jar:
C:\DOCUME~1\slaws\LOCALS~1\Temp\surefirebooter60808.jar
java.net.MalformedURLException: unknown protocol: c
at java.net.URL.init(URL.java:608)
at java.net.URL.init(URL.java:498)
at sun.misc.URLClassPath$JarLoader.parseClassPath(
URLClassPath.java
:1118
)
at sun.misc.URLClassPath$JarLoader.getClassPath(
URLClassPath.java
:1091)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:476)
at sun.misc.URLClassPath.getResource(URLClassPath.java:322)
at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java
:960)
at java.security.AccessController.doPrivileged(
AccessController.java
:275
Re: Merging branch changes back into truck
On 9/20/07, Luciano Resende [EMAIL PROTECTED] wrote: The BPEL related projects are already merged. They have some differences as trunk has been evolving. On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Raymond Feng [EMAIL PROTECTED] wrote: Thank you for volunteering. That would be great that we do in a batch. Please note some of the changes may have already been merged not by the check-in sequence. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 1:58 AM Subject: Merging branch changes back into truck There are quite a few changes in the branch that are not in the trunk. http://people.apache.org/~slaws/Report.html http://people.apache.org/%7Eslaws/Report.html - anything blue or red on the right hand side means there is something. I'm just sorting out the domain/node changes. Most others are small things, poms etc. Let me know if you want me to do a general sweep. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the domain/node changes and the tuscany-sca-spi changes Let me take a look at the others then. I'll shout if I get stuck Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the merge from the branch into the trunk. Areas where it's unclear whether the head or the branch is correct. binding-notification-* implementation-notification Ignacio if you can take a look that would be great. It builds/test on my machine but I still have a bpel problem which I need to double check I'm driving from the office to home now so if people could give it a spin in the mean time that would be great Thanks Simon
Re: Merging branch changes back into truck
Ok, I updated to r577913, built implementation-notification and binding-notification, and the samples. Everything looks ok. Did you also want me to cross check with the branch, or just check the trunk? On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Luciano Resende [EMAIL PROTECTED] wrote: The BPEL related projects are already merged. They have some differences as trunk has been evolving. On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Raymond Feng [EMAIL PROTECTED] wrote: Thank you for volunteering. That would be great that we do in a batch. Please note some of the changes may have already been merged not by the check-in sequence. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 1:58 AM Subject: Merging branch changes back into truck There are quite a few changes in the branch that are not in the trunk. http://people.apache.org/~slaws/Report.html http://people.apache.org/%7Eslaws/Report.html - anything blue or red on the right hand side means there is something. I'm just sorting out the domain/node changes. Most others are small things, poms etc. Let me know if you want me to do a general sweep. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the domain/node changes and the tuscany-sca-spi changes Let me take a look at the others then. I'll shout if I get stuck Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the merge from the branch into the trunk. Areas where it's unclear whether the head or the branch is correct. binding-notification-* implementation-notification Ignacio if you can take a look that would be great. It builds/test on my machine but I still have a bpel problem which I need to double check I'm driving from the office to home now so if people could give it a spin in the mean time that would be great Thanks Simon
[jira] Updated: (TUSCANY-1772) Setting::getDataObjectValue returning null pointer
[ https://issues.apache.org/jira/browse/TUSCANY-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Crestani updated TUSCANY-1772: -- Attachment: tuscan1772.adrianocrestani.09_20_2007.patch the second patch is ignoring the root object contained in ChangedObjectList Setting::getDataObjectValue returning null pointer -- Key: TUSCANY-1772 URL: https://issues.apache.org/jira/browse/TUSCANY-1772 Project: Tuscany Issue Type: Bug Components: C++ SDO Affects Versions: Cpp-Next Environment: windows xp professional edition Microsoft Visual Studio 2005 Reporter: Adriano Crestani Priority: Critical Fix For: Cpp-Next Attachments: tuscan1772.adrianocrestani.09_20_2007.patch, tuscan1772.adrianocrestani.09_20_2007.patch The method setting.getDataObjectValue is returning a null pointer when the setting.getType().isDataObjectType()==true http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg23852.html -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-1781) Will binding-jms be available in Tuscany SCA Java 1.0?
Will binding-jms be available in Tuscany SCA Java 1.0? -- Key: TUSCANY-1781 URL: https://issues.apache.org/jira/browse/TUSCANY-1781 Project: Tuscany Issue Type: New Feature Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.0 Reporter: Yan I am just wondering if binding-jms will be available in the Tuscany SCA Java 1.0 release? It doesn't seem to exist in current 0.99 version. Thanks!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Merging branch changes back into truck
On 9/20/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote: Ok, I updated to r577913, built implementation-notification and binding-notification, and the samples. Everything looks ok. Did you also want me to cross check with the branch, or just check the trunk? On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Luciano Resende [EMAIL PROTECTED] wrote: The BPEL related projects are already merged. They have some differences as trunk has been evolving. On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Raymond Feng [EMAIL PROTECTED] wrote: Thank you for volunteering. That would be great that we do in a batch. Please note some of the changes may have already been merged not by the check-in sequence. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 1:58 AM Subject: Merging branch changes back into truck There are quite a few changes in the branch that are not in the trunk. http://people.apache.org/~slaws/Report.html http://people.apache.org/%7Eslaws/Report.html - anything blue or red on the right hand side means there is something. I'm just sorting out the domain/node changes. Most others are small things, poms etc. Let me know if you want me to do a general sweep. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the domain/node changes and the tuscany-sca-spi changes Let me take a look at the others then. I'll shout if I get stuck Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the merge from the branch into the trunk. Areas where it's unclear whether the head or the branch is correct. binding-notification-* implementation-notification Ignacio if you can take a look that would be great. It builds/test on my machine but I still have a bpel problem which I need to double check I'm driving from the office to home now so if people could give it a spin in the mean time that would be great Thanks Simon Hi Ignacio Can you cross check with the branch for me. There we some things that I wasn't sure about. Thanks Simon
Re: [jira] Created: (TUSCANY-1781) Will binding-jms be available in Tuscany SCA Java 1.0?
On 9/20/07, Yan (JIRA) tuscany-dev@ws.apache.org wrote: Will binding-jms be available in Tuscany SCA Java 1.0? -- Key: TUSCANY-1781 URL: https://issues.apache.org/jira/browse/TUSCANY-1781 Project: Tuscany Issue Type: New Feature Components: Java SCA JMS Binding Extension Affects Versions: Java-SCA-1.0 Reporter: Yan I am just wondering if binding-jms will be available in the Tuscany SCA Java 1.0 release? It doesn't seem to exist in current 0.99 version. Thanks!! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Hi Yan No it didn't make it into the 1.0 release. We have a partial implementation in the trunk which just supports request/response messaging and a subset of the configuration parameters defined in the spec. JMS is one of the things next on the list to get sorted out. If you want to help then your most welcome. Regards Simon
Re: Merging branch changes back into truck
I'm seeing this : D:\dev\Opensource\Apache\Tuscany\source\java\sca\samples\domain-webapp\src\main\java\node\DomainServer.java:[23,40] cannot find symbol symbol : class NodeImpl location: package org.apache.tuscany.sca.node.impl D:\dev\Opensource\Apache\Tuscany\source\java\sca\samples\domain-webapp\src\main\java\node\DomainServer.java:[34,12] cannot find symbol symbol : class NodeImpl location: class node.DomainServer D:\dev\Opensource\Apache\Tuscany\source\java\sca\samples\domain-webapp\src\main\java\node\DomainServer.java:[34,32] cannot find symbol symbol : class NodeImpl location: class node.DomainServer Is this a merge issue ? On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote: Ok, I updated to r577913, built implementation-notification and binding-notification, and the samples. Everything looks ok. Did you also want me to cross check with the branch, or just check the trunk? On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Luciano Resende [EMAIL PROTECTED] wrote: The BPEL related projects are already merged. They have some differences as trunk has been evolving. On 9/20/07, Simon Laws [EMAIL PROTECTED] wrote: On 9/20/07, Raymond Feng [EMAIL PROTECTED] wrote: Thank you for volunteering. That would be great that we do in a batch. Please note some of the changes may have already been merged not by the check-in sequence. Thanks, Raymond - Original Message - From: Simon Laws [EMAIL PROTECTED] To: tuscany-dev tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 1:58 AM Subject: Merging branch changes back into truck There are quite a few changes in the branch that are not in the trunk. http://people.apache.org/~slaws/Report.html http://people.apache.org/%7Eslaws/Report.html - anything blue or red on the right hand side means there is something. I'm just sorting out the domain/node changes. Most others are small things, poms etc. Let me know if you want me to do a general sweep. Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the domain/node changes and the tuscany-sca-spi changes Let me take a look at the others then. I'll shout if I get stuck Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, I've done the merge from the branch into the trunk. Areas where it's unclear whether the head or the branch is correct. binding-notification-* implementation-notification Ignacio if you can take a look that would be great. It builds/test on my machine but I still have a bpel problem which I need to double check I'm driving from the office to home now so if people could give it a spin in the mean time that would be great Thanks Simon Hi Ignacio Can you cross check with the branch for me. There we some things that I wasn't sure about. Thanks Simon -- 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]
[jira] Commented: (TUSCANY-1780) [JAVA-SDO] Incorrect generation of class with default value for a list
[ https://issues.apache.org/jira/browse/TUSCANY-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529307 ] David T. Adcox commented on TUSCANY-1780: - Chris, I've performed a quick sniff test of this, and I'm not seeing the same behavior. Perhaps you could attach the full schema that is causing your problem (or an abbreviated one would be nice). I may not have things structured as you do, so using your copy would be best. Thanks, David [JAVA-SDO] Incorrect generation of class with default value for a list -- Key: TUSCANY-1780 URL: https://issues.apache.org/jira/browse/TUSCANY-1780 Project: Tuscany Issue Type: Bug Components: Java SDO Tools Affects Versions: Java-SDO-1.0, Java-SDO-Next Environment: Windows XP, JRE 1.4.2 and JRE 1.5 Reporter: Chris Mildebrandt Priority: Critical Hello, There seems to be a problem when generating static classes when lists are involved. I have the following lines in my schema: xsd:attribute name=categoryType type=address:CategoryType use=required default=myCat/ simpleType name=CategoryType list itemType=category / /simpleType This generates the following line in the impl class: protected static final Object CATEGORY_TYPE_DEFAULT_ = ((EFactory)ModelFactory.INSTANCE).createFromString(ModelPackageImpl.eINSTANCE.getObject(), myCat); The class ModelPackageImpl doesn't exist. I've tried this with the 1.0 version of SDO and a version I built today. Let me know if you need any more information. Thanks, -Chris -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is there mirrors I should config when I build trunk?
Hello, every one, Building the trunk always got missing failure of version 1.1-incubating-SNAPSHOT, is there any mirrors I should add to my maven? Thanks alot. - Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.
Re: Is there mirrors I should config when I build trunk?
Hi, Can you post more information about which module is failing? Do you try to build from an empty maven repo? Thanks, Raymond - Original Message - From: shaoguang geng [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 8:11 PM Subject: Is there mirrors I should config when I build trunk? Hello, every one, Building the trunk always got missing failure of version 1.1-incubating-SNAPSHOT, is there any mirrors I should add to my maven? Thanks alot. - Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is there mirrors I should config when I build trunk?
Could you also post what maven version you are using ? On 9/20/07, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Can you post more information about which module is failing? Do you try to build from an empty maven repo? Thanks, Raymond - Original Message - From: shaoguang geng [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Thursday, September 20, 2007 8:11 PM Subject: Is there mirrors I should config when I build trunk? Hello, every one, Building the trunk always got missing failure of version 1.1-incubating-SNAPSHOT, is there any mirrors I should add to my maven? Thanks alot. - Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. - 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]
