Re: Improving support for running in OSGi
On Thu, May 1, 2008 at 12:40 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: snip Here's what I imagined we'd do: 1. add OSGi entries to each of our JAR manifests 2. have developers maintain them and pay attention to imports/exports 3. use the OSGi build to detect API and SPI import/export violations 4. find the best way to OSGi-enable 3rd party dependency JARs I realize that my suggestion [1] is not very popular and most people on this list would prefer to come up with bigger bundles grouping several of our JARs/modules. I don't think that the 'bigger aggregate bundle' approach will work, but I'll be happy to watch people try it :) if they want to. Perfectly ok but would you say a bit more about why you don't think the bigger aggregate bundle approach will work? I like the sound of less bundles as it seems like it could be easier to use but if you know of issues it would be nice to hear them now. ...ant
Fwd: Is there are simple straightforward way of creating a Compoisite
Bring this comment to the dev list: The tuscany web app support doesn't use this evolving node implementation just yet. I don't imagine it would be difficult to plug it in - http://apache.markmail.org/message/4hvdrcafhapy3kyy Coincidentally i was having a look at this just the other day after that user posted about support for Tomcat with multiple webapps in the same SCA domain - http://apache.markmail.org/message/ttssxoruzpndkado. Could you give any pointers at all on where to start with using this evolving node implementation like this? Theres no doc and I'm a bit lost on even which Tuscany modules, samples or tests are current. What I'd like to do is start exploring the updating of the old runtime-tomcat code to use the latest domain stuff so that as Tomcat starts up webapps are detected as SCA contributions and added to a single Tomcat SCA domain. One issue that I remember came up last time doing this is that as this happens during Tomcat startup no http communication can take place so all the registrations of contributions with the domain need to be in-vm. ...ant
Re: [VOTE] Graduate Apache Tuscany as a Top Level Project
On Wed, Apr 30, 2008 at 11:37 AM, Simon Nash [EMAIL PROTECTED] wrote: ant elder wrote: We've done a lot of work since last October. We now have a diverse community of contributors and have demonstrated the ability to attract new committers to create an even more diverse community, we have shown we can do releases based on Apache guidelines, and we have shown we conduct our discussions in public within full view of the community and can resolve disagreements on the lists. I think we're ready, so please vote on the proposal below to graduate Tuscany to a TLP. +1 from me. ...ant X. Establish the Apache Tuscany Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software that simplifies the development and deployment of service oriented applications and provides a managed service-oriented runtime based on the standards defined by the OASIS OpenCSA group, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Tuscany Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is responsible for the creation and maintenance of software related to Apache Tuscany; and be it further RESOLVED, that the office of Vice President, Apache Tuscany be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Tuscany Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Tuscany Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Tuscany Project: - Adriano Crestani adrianocrestani at apache dot org - ant elder antelder at apache dot org - Brady Johnson bjohnson at apache dot org - Frank Budinsky frankb at apache dot org - Ignacio Silva-Lepe isilval at apache dot org - Jean-Sebastien Delfino jsdelfino at apache dot org - kelvin goodson kelvingoodson at apache dot org - Luciano Resende lresende at apache dot org - Mark Combellack mcombellack at apache dot org - Matthieu Riou mriou at apache dot org - Mike Edwards edwardsmj at apache dot org - Paul Fremantle pzf at apache dot org - Pete Robbins robbinspg at apache dot org - Raymond Feng rfeng at apache dot org - Simon Laws slaws at apache dot org - Simon Nash nash at apache dot org - Venkata Krishnan svkrish at apache dot org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder be appointed to the office of Vice President, Apache Tuscany, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Tuscany podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Tuscany podling encumbered upon the Apache Incubator Project are hereafter discharged. My sincere apologies. This version of the charter is not correct, and I failed to notice the problem when casting my +1 vote. The first paragraph says: WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software that simplifies the development and deployment of service oriented applications and provides a managed service-oriented runtime based on the standards defined by the OASIS OpenCSA group, for distribution at no charge to the public. In our most recent vote (see [1]) on the wording of this paragraph, we agreed the following text: WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software for distribution at no charge to the public, that simplifies the development, deployment and management of distributed applications built as compositions of service components. These components may be implemented with a range of technologies and connected using a variety of communication protocols. This software will implement relevant open standards including, but not limited to, the SCA
Re: Is there are simple straightforward way of creating a Compoisite
On Wed, Apr 30, 2008 at 12:00 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 11:12 AM, ant elder [EMAIL PROTECTED] wrote: Bring this comment to the dev list: The tuscany web app support doesn't use this evolving node implementation just yet. I don't imagine it would be difficult to plug it in - http://apache.markmail.org/message/4hvdrcafhapy3kyy Coincidentally i was having a look at this just the other day after that user posted about support for Tomcat with multiple webapps in the same SCA domain - http://apache.markmail.org/message/ttssxoruzpndkado. Could you give any pointers at all on where to start with using this evolving node implementation like this? Theres no doc and I'm a bit lost on even which Tuscany modules, samples or tests are current. What I'd like to do is start exploring the updating of the old runtime-tomcat code to use the latest domain stuff so that as Tomcat starts up webapps are detected as SCA contributions and added to a single Tomcat SCA domain. One issue that I remember came up last time doing this is that as this happens during Tomcat startup no http communication can take place so all the registrations of contributions with the domain need to be in-vm. ...ant Hi Ant Am keen to work with you on this. While svn has been down I've spent time to resurrect a load balancing demo I have on my local disc (not checked in yet) and would like to update the webapps I'm using to the lasted domain code but of course I can't. Here's a summary of what I think is current in terms of domain/node/runtime support (but have to admit that there is an amount of guessing here). sca/distribution/standalone - not sure but think it's redundant - forerunner of runtime-standalone? sca/distribution/tomcat - not sure but think it's redundant - forerunner of runtime-tomcat? sca/distribution/war - not sure but think it's redundant - forerunner of runtime-war? sca/distribution/webapp - not sure but think it's redundant sca/modules/domain - old domain SPI sca/modules/domain-api - old domain API sca/modules/domain-impl - old domain Implementation - has been superseded by domain-manager sca/modules/domain-manager - new domain management application - replaces domain-impl sca/modules/host-embedded - original single JVM domain implementation - still used in most samples sca/modules/host-webapp - original webapp runtime - fires up tuscany based on web.xml filter sca/modules/host-webapp-junit - not sure but have a feeling it's something to do with running itests in different web containers sca/modules/node - old node SPI sca/modules/node-api - old node API sca/modules/node-impl - old node implementation that runs one or more composites in a single JVM as part of a distributed domain sca/modules/node2-api - new node API sca/modules/node2-impl - new node implementation. This node is coded to read it's configuration as an atom feed from the new domain-manager sca/modules/node2-launcher - start up a node from the command line sca/modules/node2-launcher-webapp - had noticed this before - maybe node2 integration with webapps has been looked at. Let's see! sca/modules/runtime - I think this was the last attempt at providing a common runtime baseline to be specialized for different environments sca/modules/runtime-standalone - command line runtime sca/modules/runtime-tomcat - deep tomcat integration (IIRC) sca/modules/runtime-war - war rutime sca/modules/workspace - SPI for some of the machinery required to process contributions at the domain level. Used by domain-manager sca/modules/workspace-impl - Implementation of the workspace sca/modules/workspace-xml - Reading/writing workspace as XML So can we get together here and work out what the true picture is and how to mode modules/runtime* to node2. First things first I'm going to go look at node2-launcher-webapp. I think the start up process for nodes in a webapp will potentially be easier now as the node is just reading atom feeds and not making soap calls. Time will tell! Simon Great, working together would be good and i'm sure make getting somewhere useful happen much quicker :) Thanks for the list of module statuses thats helpful, i'll also go look the node2-launcher-webapp one. The comment on the use of atom feeds is interesting. To be honest i'd hope we could have a way to avoid that being needed in this Tomcat use case, or at least being optional. One issue we had last time when we tried to do this was that there had to be a separate standalone domain manager running before you could start up a Tomcat instance, and that sucks quite a bit IMHO so i'd like to try to get a design from the beginning where its not needed. This will all be happening in a single JVM and with the code bootstrapping Tuscany being at the top classloader so everything should be accessible to just make direct SPI calls to configure a domain
Re: Is there are simple straightforward way of creating a Compoisite
On Wed, Apr 30, 2008 at 12:00 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 11:12 AM, ant elder [EMAIL PROTECTED] wrote: Bring this comment to the dev list: The tuscany web app support doesn't use this evolving node implementation just yet. I don't imagine it would be difficult to plug it in - http://apache.markmail.org/message/4hvdrcafhapy3kyy Coincidentally i was having a look at this just the other day after that user posted about support for Tomcat with multiple webapps in the same SCA domain - http://apache.markmail.org/message/ttssxoruzpndkado. Could you give any pointers at all on where to start with using this evolving node implementation like this? Theres no doc and I'm a bit lost on even which Tuscany modules, samples or tests are current. What I'd like to do is start exploring the updating of the old runtime-tomcat code to use the latest domain stuff so that as Tomcat starts up webapps are detected as SCA contributions and added to a single Tomcat SCA domain. One issue that I remember came up last time doing this is that as this happens during Tomcat startup no http communication can take place so all the registrations of contributions with the domain need to be in-vm. ...ant Hi Ant Am keen to work with you on this. While svn has been down I've spent time to resurrect a load balancing demo I have on my local disc (not checked in yet) and would like to update the webapps I'm using to the lasted domain code but of course I can't. Here's a summary of what I think is current in terms of domain/node/runtime support (but have to admit that there is an amount of guessing here). sca/distribution/standalone - not sure but think it's redundant - forerunner of runtime-standalone? sca/distribution/tomcat - not sure but think it's redundant - forerunner of runtime-tomcat? sca/distribution/war - not sure but think it's redundant - forerunner of runtime-war? sca/distribution/webapp - not sure but think it's redundant sca/modules/domain - old domain SPI sca/modules/domain-api - old domain API sca/modules/domain-impl - old domain Implementation - has been superseded by domain-manager sca/modules/domain-manager - new domain management application - replaces domain-impl sca/modules/host-embedded - original single JVM domain implementation - still used in most samples sca/modules/host-webapp - original webapp runtime - fires up tuscany based on web.xml filter sca/modules/host-webapp-junit - not sure but have a feeling it's something to do with running itests in different web containers sca/modules/node - old node SPI sca/modules/node-api - old node API sca/modules/node-impl - old node implementation that runs one or more composites in a single JVM as part of a distributed domain sca/modules/node2-api - new node API sca/modules/node2-impl - new node implementation. This node is coded to read it's configuration as an atom feed from the new domain-manager sca/modules/node2-launcher - start up a node from the command line sca/modules/node2-launcher-webapp - had noticed this before - maybe node2 integration with webapps has been looked at. Let's see! sca/modules/runtime - I think this was the last attempt at providing a common runtime baseline to be specialized for different environments sca/modules/runtime-standalone - command line runtime sca/modules/runtime-tomcat - deep tomcat integration (IIRC) sca/modules/runtime-war - war rutime sca/modules/workspace - SPI for some of the machinery required to process contributions at the domain level. Used by domain-manager sca/modules/workspace-impl - Implementation of the workspace sca/modules/workspace-xml - Reading/writing workspace as XML So can we get together here and work out what the true picture is and how to mode modules/runtime* to node2. First things first I'm going to go look at node2-launcher-webapp. I think the start up process for nodes in a webapp will potentially be easier now as the node is just reading atom feeds and not making soap calls. Time will tell! Simon One more question - what is a node? May seem like a silly question but i'm not sure there's ever been much consensus on a clear definition. Is it something for running a single composite, or a single contribution, or a collection of related contributions? How many nodes would there be on a Tomcat instance doing what that user has posted about, one per webapp, one per Tomcat instance? ...ant
Re: Is there are simple straightforward way of creating a Compoisite
On Wed, Apr 30, 2008 at 1:08 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 12:49 PM, ant elder [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 12:00 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 11:12 AM, ant elder [EMAIL PROTECTED] wrote: Bring this comment to the dev list: The tuscany web app support doesn't use this evolving node implementation just yet. I don't imagine it would be difficult to plug it in - http://apache.markmail.org/message/4hvdrcafhapy3kyy Coincidentally i was having a look at this just the other day after that user posted about support for Tomcat with multiple webapps in the same SCA domain - http://apache.markmail.org/message/ttssxoruzpndkado. Could you give any pointers at all on where to start with using this evolving node implementation like this? Theres no doc and I'm a bit lost on even which Tuscany modules, samples or tests are current. What I'd like to do is start exploring the updating of the old runtime-tomcat code to use the latest domain stuff so that as Tomcat starts up webapps are detected as SCA contributions and added to a single Tomcat SCA domain. One issue that I remember came up last time doing this is that as this happens during Tomcat startup no http communication can take place so all the registrations of contributions with the domain need to be in-vm. ...ant Hi Ant Am keen to work with you on this. While svn has been down I've spent time to resurrect a load balancing demo I have on my local disc (not checked in yet) and would like to update the webapps I'm using to the lasted domain code but of course I can't. Here's a summary of what I think is current in terms of domain/node/runtime support (but have to admit that there is an amount of guessing here). sca/distribution/standalone - not sure but think it's redundant - forerunner of runtime-standalone? sca/distribution/tomcat - not sure but think it's redundant - forerunner of runtime-tomcat? sca/distribution/war - not sure but think it's redundant - forerunner of runtime-war? sca/distribution/webapp - not sure but think it's redundant sca/modules/domain - old domain SPI sca/modules/domain-api - old domain API sca/modules/domain-impl - old domain Implementation - has been superseded by domain-manager sca/modules/domain-manager - new domain management application - replaces domain-impl sca/modules/host-embedded - original single JVM domain implementation - still used in most samples sca/modules/host-webapp - original webapp runtime - fires up tuscany based on web.xml filter sca/modules/host-webapp-junit - not sure but have a feeling it's something to do with running itests in different web containers sca/modules/node - old node SPI sca/modules/node-api - old node API sca/modules/node-impl - old node implementation that runs one or more composites in a single JVM as part of a distributed domain sca/modules/node2-api - new node API sca/modules/node2-impl - new node implementation. This node is coded to read it's configuration as an atom feed from the new domain-manager sca/modules/node2-launcher - start up a node from the command line sca/modules/node2-launcher-webapp - had noticed this before - maybe node2 integration with webapps has been looked at. Let's see! sca/modules/runtime - I think this was the last attempt at providing a common runtime baseline to be specialized for different environments sca/modules/runtime-standalone - command line runtime sca/modules/runtime-tomcat - deep tomcat integration (IIRC) sca/modules/runtime-war - war rutime sca/modules/workspace - SPI for some of the machinery required to process contributions at the domain level. Used by domain-manager sca/modules/workspace-impl - Implementation of the workspace sca/modules/workspace-xml - Reading/writing workspace as XML So can we get together here and work out what the true picture is and how to mode modules/runtime* to node2. First things first I'm going to go look at node2-launcher-webapp. I think the start up process for nodes in a webapp will potentially be easier now as the node is just reading atom feeds and not making soap calls. Time will tell! Simon One more question - what is a node? May seem like a silly question but i'm not sure there's ever been much consensus on a clear definition. Is it something for running a single composite, or a single contribution, or a collection of related contributions? How many nodes would there be on a Tomcat instance doing what that user has posted about, one per webapp, one per Tomcat instance? ...ant I don't think there has been consensus
Re: Is there are simple straightforward way of creating a Compoisite
On Wed, Apr 30, 2008 at 12:52 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 12:40 PM, ant elder [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 12:00 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 11:12 AM, ant elder [EMAIL PROTECTED] wrote: Bring this comment to the dev list: The tuscany web app support doesn't use this evolving node implementation just yet. I don't imagine it would be difficult to plug it in - http://apache.markmail.org/message/4hvdrcafhapy3kyy Coincidentally i was having a look at this just the other day after that user posted about support for Tomcat with multiple webapps in the same SCA domain - http://apache.markmail.org/message/ttssxoruzpndkado. Could you give any pointers at all on where to start with using this evolving node implementation like this? Theres no doc and I'm a bit lost on even which Tuscany modules, samples or tests are current. What I'd like to do is start exploring the updating of the old runtime-tomcat code to use the latest domain stuff so that as Tomcat starts up webapps are detected as SCA contributions and added to a single Tomcat SCA domain. One issue that I remember came up last time doing this is that as this happens during Tomcat startup no http communication can take place so all the registrations of contributions with the domain need to be in-vm. ...ant Hi Ant Am keen to work with you on this. While svn has been down I've spent time to resurrect a load balancing demo I have on my local disc (not checked in yet) and would like to update the webapps I'm using to the lasted domain code but of course I can't. Here's a summary of what I think is current in terms of domain/node/runtime support (but have to admit that there is an amount of guessing here). sca/distribution/standalone - not sure but think it's redundant - forerunner of runtime-standalone? sca/distribution/tomcat - not sure but think it's redundant - forerunner of runtime-tomcat? sca/distribution/war - not sure but think it's redundant - forerunner of runtime-war? sca/distribution/webapp - not sure but think it's redundant sca/modules/domain - old domain SPI sca/modules/domain-api - old domain API sca/modules/domain-impl - old domain Implementation - has been superseded by domain-manager sca/modules/domain-manager - new domain management application - replaces domain-impl sca/modules/host-embedded - original single JVM domain implementation - still used in most samples sca/modules/host-webapp - original webapp runtime - fires up tuscany based on web.xml filter sca/modules/host-webapp-junit - not sure but have a feeling it's something to do with running itests in different web containers sca/modules/node - old node SPI sca/modules/node-api - old node API sca/modules/node-impl - old node implementation that runs one or more composites in a single JVM as part of a distributed domain sca/modules/node2-api - new node API sca/modules/node2-impl - new node implementation. This node is coded to read it's configuration as an atom feed from the new domain-manager sca/modules/node2-launcher - start up a node from the command line sca/modules/node2-launcher-webapp - had noticed this before - maybe node2 integration with webapps has been looked at. Let's see! sca/modules/runtime - I think this was the last attempt at providing a common runtime baseline to be specialized for different environments sca/modules/runtime-standalone - command line runtime sca/modules/runtime-tomcat - deep tomcat integration (IIRC) sca/modules/runtime-war - war rutime sca/modules/workspace - SPI for some of the machinery required to process contributions at the domain level. Used by domain-manager sca/modules/workspace-impl - Implementation of the workspace sca/modules/workspace-xml - Reading/writing workspace as XML So can we get together here and work out what the true picture is and how to mode modules/runtime* to node2. First things first I'm going to go look at node2-launcher-webapp. I think the start up process for nodes in a webapp will potentially be easier now as the node is just reading atom feeds and not making soap calls. Time will tell! Simon Great, working together would be good and i'm sure make getting somewhere useful happen much quicker :) Thanks for the list of module statuses thats helpful, i'll also go look the node2-launcher-webapp one. The comment on the use of atom feeds is interesting. To be honest i'd hope we could have a way to avoid that being needed in this Tomcat use case, or at least being optional. One issue we had last time when we tried to do this was that there had to be a separate
Re: Is there are simple straightforward way of creating a Compoisite
On Wed, Apr 30, 2008 at 1:18 PM, Simon Laws [EMAIL PROTECTED] wrote: snip Cool thats really helpful. Ok so if we can have a Tomcat TuscanyHost (i.e. an extension of org.apache.catalina.core.StandardHost not related to the Tuscany host stuff) that will get its addChild method called for each webapp and we can get a File to the root of the webbapp so call nodeFactory.createSCANode with that and treat each webapp as a seperate contribution which seems reasonable. That would give us a node per webapp which i'm not sure is good or bad till theres some answers to the what is a node question. sounds ok to me. How do nodes talk to each other or become part of a bigger domain? Theres nothing in SCANode2Factory.newInstance().createSCANode or node.start that mentions anything about any domain? ...ant They don't talk to each other, other other than at the application level. If you want to have a node read it's configuration from the domain you can use the following factory method. public abstract SCANode2 createSCANode(String configurationURI); and provide the URI of the configuration that you want it to read. e.g. node = factory.createSCANode(http://localhost:9990/node-image/NodeA;); This URL is provided by the domain and is tailored specifically to provide just the right configuration (the list of composite and contribution URLs) for the node in question. NodeA in this case. Simon Now I'm lost again :) Stepping back a bit, what and how is the domain involved in this? What does it mean to have a node read it's configuration from the domain? ...ant
Re: Is there are simple straightforward way of creating a Compoisite
On Wed, Apr 30, 2008 at 1:38 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 1:25 PM, ant elder [EMAIL PROTECTED] wrote: On Wed, Apr 30, 2008 at 1:18 PM, Simon Laws [EMAIL PROTECTED] wrote: snip Cool thats really helpful. Ok so if we can have a Tomcat TuscanyHost (i.e. an extension of org.apache.catalina.core.StandardHost not related to the Tuscany host stuff) that will get its addChild method called for each webapp and we can get a File to the root of the webbapp so call nodeFactory.createSCANode with that and treat each webapp as a seperate contribution which seems reasonable. That would give us a node per webapp which i'm not sure is good or bad till theres some answers to the what is a node question. sounds ok to me. How do nodes talk to each other or become part of a bigger domain? Theres nothing in SCANode2Factory.newInstance().createSCANode or node.start that mentions anything about any domain? ...ant They don't talk to each other, other other than at the application level. If you want to have a node read it's configuration from the domain you can use the following factory method. public abstract SCANode2 createSCANode(String configurationURI); and provide the URI of the configuration that you want it to read. e.g. node = factory.createSCANode(http://localhost:9990/node-image/NodeA ); This URL is provided by the domain and is tailored specifically to provide just the right configuration (the list of composite and contribution URLs) for the node in question. NodeA in this case. Simon Now I'm lost again :) Stepping back a bit, what and how is the domain involved in this? What does it mean to have a node read it's configuration from the domain? ...ant Apologies. I'm probably confusing you here as I don't have a clear picture. Two scenarios. 1 - the one we know and love where the webapp is self contained and runs a node (SCADomain in our current host-webapp) to run the composite that it contains. 2 - the distributed domain scenario. The last time we approached this we had the node contacting the domain for endpoint information for those targets that could not be resolved locally. This gave us start up problems. This is still the role of the new domain but the way that the node gets this information is different now. This is where I too am suggesting that the use case is not clear. So if we agree that there are two slightly different scenarios we can investigate them further. Simon Agreed, here we are talking about that second one right? Or at least something different than the first anyway. Something like what we had described here - http://apache.markmail.org/message/ttssxoruzpndkado So in the (2) above how does the domain get configured? In a previous email you said the webapp will have been contributed to the domain for processing is there any code i can look at showing that type of thing happening? And then how do you create a node from a configured domain? ...ant
Re: Load balancing demo
On Wed, Apr 30, 2008 at 1:56 PM, Simon Laws [EMAIL PROTECTED] wrote: snip However this all fell apart as the balancer webapp is based on HTTP redirects and Axis2 doesn't handle them. Had this worked I had a completely Java demo and I could run the whole thing automatically. So any thoughts on either A) how to automate Apache installs B) a tomcat based load balancer. How about also C) how to fix Axis2 to handle redirects? Is it some fundamental problem or just a bug which we could try to fix? ...ant
Re: [VOTE] Graduate Apache Tuscany as a Top Level Project
On Wed, Apr 30, 2008 at 4:59 PM, Simon Nash [EMAIL PROTECTED] wrote: snip I'm not happy that we would do this over something as important as the technical charter for the project. I think we need to formally vote as a project on the words we want to take forward to the IPMC. We should be able to restart the vote with this correction and have it complete in time to get the proposal to the board in time for the May board meeting. Ok I'll cancel this vote then. ...ant
Re: Adding SVN version to Java files
Yes i think we have consensus to do this now, and as a sign of good faith i'll help by (as soon as we get SVN write access back) adding the keywords to the IDE templates we have in SVN and adding text to the developer guide on what is required to set up our SVN clients to correctly set the svn properties on new files. ...ant On Tue, Apr 29, 2008 at 1:46 PM, Mark Combellack [EMAIL PROTECTED] wrote: Hi, It looks like the discussions on adding SVN version to Java files has gone quiet again so I'll give it a little prod :-) Previously, the question was asked as to what was the justification for adding the SVN version. I hope I have answered this question satisfactorily. Generally people seemed to be happy with adding SVN version to the Java files. However, ant, would prefer not to do this. ant, has the recent justification emails provided you with enough of a reason to convince you that they should be added? Thanks, Mark -Original Message- From: Mark Combellack [mailto:[EMAIL PROTECTED] Sent: 24 April 2008 09:55 To: tuscany-dev@ws.apache.org Subject: RE: Adding SVN version to Java files Hi, The main reasons that I like the SVN details in the header of the files include: * You can look at the source file and see what revision it is without having to use SVN commands * Typically, developers will do an SVN checkout of the code using SVN so they can get the information via SVN commands or via the headers * Typically, users do not do an SVN checkout of the source code and will not have SVN installed. They are typically provided with a jar file containing the source code. They will not be able to run SVN command to work out which versions of source code they are running * Typically, there are many, many more users than there are developers * If a source file is printed out or attached as an email as part of a bug report or published on a web server, the source code will contain the SVN revision number. This makes the bug easier to fix as you know the revision number. The SVN commands will not be able to tell you the revision number in these scenarios. The nice thing about the SVN keyword substitution is that a Developer is free to choose whether they want them or not as the expansion is done on the client side. If a Developer wants the $Date$ and $Revision$ expanded, then they have to update their SVN configuration to do so. If they do not, then they don't need to do anything as it is disabled in SVN by default. The key thing is that @version $Date$ $Revision$ is in the header to provide this choice. At the end of the day, from my personal opinion, using @version $Date$ $Revision$ is a nice to have feature in the source code. I would like to have it there. However, I would rather go without it if its presence is going to cause disharmony amongst the Tuscany Developers. Thanks, Mark -Original Message- From: Vamsavardhana Reddy [mailto:[EMAIL PROTECTED] Sent: 24 April 2008 08:04 To: tuscany-dev@ws.apache.org; [EMAIL PROTECTED] Subject: Re: Adding SVN version to Java files I would like to know the last revision and date at which a particular file is updated just by opening the file in any editor and without having to do anything extra, for e.g., like installing a plugin for eclipse, opening a command prompt to issue an svn info command (note that the source I have need not always be from svn, it could be a source archive for a release downloaded separately), etc. I found this info very useful while investigating JIRAs. ++Vamsi On Thu, Apr 24, 2008 at 11:12 AM, ant elder [EMAIL PROTECTED] wrote: On Wed, Apr 23, 2008 at 5:52 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: snip From the above, we have 4 +1s and no -1s - although we have a preference not to do this from ant. So, the consensus is to make this change. We haven't held a formal vote, so I don't think we should be trying to decide this based on a count of +1s and -1s. Agreed. We should hold a formal vote. We do consensus based development. Voting can be a useful gauging consensus but voting does not make consensus. Its obvious from this thread that there is not (yet) consensus so we don't need a vote, how about instead trying to convince us by explaining the value of adding this? ...ant
Re: [CONF] Apache Tuscany: Build your first Web Services with Tuscany (page edited)
Still not got this to work with the 1.2 release plugin. Looking at the code I wondered if we should have two run options - Run As - Tuscany standalone and Run As - Tuscany distributed? The standalone one would use the regular SCADomain from the host-embedded module like most of the tests and samples use. ...ant On Fri, Apr 25, 2008 at 2:09 PM, ant elder [EMAIL PROTECTED] wrote: Have you got that example working with the eclipse plugin from the 1.2 RC4 release? I've tried but it crashes with the exception below. It also starts up all sorts of endpoints, i guess for the workspace stuff, is there any way to prevent that? ...ant Caused by: javax.xml.stream.XMLStreamException: Non-default namespace can not map to empty URI (as per Namespace 1.0 # 2) in XML 1.0 documents at com.ctc.wstx.sw.BaseStreamWriter.throwOutputError(BaseStreamWriter.java:1473) at com.ctc.wstx.sw.BaseNsStreamWriter.setPrefix(BaseNsStreamWriter.java:210) at org.apache.tuscany.sca.contribution.processor.BaseStAXArtifactProcessor$XAttr.writeQNamePrefix(BaseStAXArtifactProcessor.java:414) at org.apache.tuscany.sca.contribution.processor.BaseStAXArtifactProcessor$XAttr.writePrefix(BaseStAXArtifactProcessor.java:493) at org.apache.tuscany.sca.contribution.processor.BaseStAXArtifactProcessor.writeAttributePrefixes(BaseStAXArtifactProcessor.java:302) at org.apache.tuscany.sca.contribution.processor.BaseStAXArtifactProcessor.writeStart(BaseStAXArtifactProcessor.java:220) at org.apache.tuscany.sca.assembly.xml.BaseAssemblyProcessor.writeStart(BaseAssemblyProcessor.java:137) at org.apache.tuscany.sca.assembly.xml.CompositeProcessor.write(CompositeProcessor.java:504) at org.apache.tuscany.sca.workspace.admin.impl.DeployedCompositeCollectionImpl.writeCompositeCollection(DeployedCompositeCollectionImpl.java:382) On Thu, Apr 24, 2008 at 3:20 PM, Luciano Resende [EMAIL PROTECTED] wrote: Totally +1, What I had in mind was to keep it simple and usable by someone that does not know much of SCA. What if we create a First Steps series of articles ? On Thu, Apr 24, 2008 at 2:14 AM, ant elder [EMAIL PROTECTED] wrote: I asked as I'd like to help expand it but don't want to step on your toes. Adding web clients sounds good, expanding the WS bit with how to use other databindings would be useful, maybe something on other bindings like JMS, then it could go on with what to do when you want to run it out side of eclipse - how to make contribution jars or run standalone or in webapps etc. I like that that page is nice and simple and clear and focused so it would be good to try to maintain that, maybe have separate pages for each topic but linked together and in the same sort of style as that one. WDYT? ...ant On Wed, Apr 23, 2008 at 5:17 PM, Luciano Resende [EMAIL PROTECTED] wrote: Yes, it's on my todo list for the next couple days... Do you have any ideas for what type of extensions to use ? Maybe JSON-RPC and use a quick web2.0 client app to consume the service ? On Wed, Apr 23, 2008 at 4:39 AM, ant elder [EMAIL PROTECTED] wrote: This looks really good, do you have plans to extend it further like with adding clients or other extension types? ...ant On Tue, Apr 22, 2008 at 5:53 PM, [EMAIL PROTECTED] wrote: Page Edited : TUSCANY http://cwiki.apache.org/confluence/display/TUSCANY: Build your first Web Services with Tuscany http://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscany Build your first Web Services with Tuscany http://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscany has been edited by Luciano Resende http://cwiki.apache.org/confluence/display/[EMAIL PROTECTED] (Apr 22, 2008). (View changes) http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=82971originalVersion=5revisedVersion=6 Content: Build your first Web Services with Tuscany This guide will give you step by step instructions on how to build your first web services. The first part, we will learn how we can add the Tuscany Runtime to Eclipse IDE. The second part, will show how easy is to create a webservices using Apache Tuscany. Install Tuscany Eclipse Plugins 1.1 Install the Tuscany Eclipse Plugin The first thing you do is to start Eclipse and go to *Help - Software Updates - Find and Install*, select Search for new features to install and then click next On the next dialog, click on *New Remote Site...* to create a new site entry. Give it a name such as Tuscany
[VOTE] Graduate Apache Tuscany as a Top Level Project
We've done a lot of work since last October. We now have a diverse community of contributors and have demonstrated the ability to attract new committers to create an even more diverse community, we have shown we can do releases based on Apache guidelines, and we have shown we conduct our discussions in public within full view of the community and can resolve disagreements on the lists. I think we're ready, so please vote on the proposal below to graduate Tuscany to a TLP. +1 from me. ...ant X. Establish the Apache Tuscany Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software that simplifies the development and deployment of service oriented applications and provides a managed service-oriented runtime based on the standards defined by the OASIS OpenCSA group, for distribution at no charge to the public. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Tuscany Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is responsible for the creation and maintenance of software related to Apache Tuscany; and be it further RESOLVED, that the office of Vice President, Apache Tuscany be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Tuscany Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Tuscany Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Tuscany Project: - Adriano Crestani adrianocrestani at apache dot org - ant elder antelder at apache dot org - Brady Johnson bjohnson at apache dot org - Frank Budinsky frankb at apache dot org - Ignacio Silva-Lepe isilval at apache dot org - Jean-Sebastien Delfino jsdelfino at apache dot org - kelvin goodson kelvingoodson at apache dot org - Luciano Resende lresende at apache dot org - Mark Combellack mcombellack at apache dot org - Matthieu Riou mriou at apache dot org - Mike Edwards edwardsmj at apache dot org - Paul Fremantle pzf at apache dot org - Pete Robbins robbinspg at apache dot org - Raymond Feng rfeng at apache dot org - Simon Laws slaws at apache dot org - Simon Nash nash at apache dot org - Venkata Krishnan svkrish at apache dot org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder be appointed to the office of Vice President, Apache Tuscany, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Tuscany Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Tuscany podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Tuscany podling encumbered upon the Apache Incubator Project are hereafter discharged.
Re: [CONF] Apache Tuscany: Build your first Web Services with Tuscany (page edited)
I started doing one of these for a simple JSP webapp but its a bit tedious with all the screen captures isn't it. There are programs that automate this by recording your screen into a flash movie - http://www.debugmode.com/wink/is a good one and its free - so how about adding these along with the text on the Tuscany web site? I've created one to try this out, takes a little practice and this one is still quite rough but it gives an idea of what could be possible - http://people.apache.org/~antelder/tuscany/demo/helloJSP.htm WDYT? ...ant On Thu, Apr 24, 2008 at 3:20 PM, Luciano Resende [EMAIL PROTECTED] wrote: Totally +1, What I had in mind was to keep it simple and usable by someone that does not know much of SCA. What if we create a First Steps series of articles ? On Thu, Apr 24, 2008 at 2:14 AM, ant elder [EMAIL PROTECTED] wrote: I asked as I'd like to help expand it but don't want to step on your toes. Adding web clients sounds good, expanding the WS bit with how to use other databindings would be useful, maybe something on other bindings like JMS, then it could go on with what to do when you want to run it out side of eclipse - how to make contribution jars or run standalone or in webapps etc. I like that that page is nice and simple and clear and focused so it would be good to try to maintain that, maybe have separate pages for each topic but linked together and in the same sort of style as that one. WDYT? ...ant On Wed, Apr 23, 2008 at 5:17 PM, Luciano Resende [EMAIL PROTECTED] wrote: Yes, it's on my todo list for the next couple days... Do you have any ideas for what type of extensions to use ? Maybe JSON-RPC and use a quick web2.0 client app to consume the service ? On Wed, Apr 23, 2008 at 4:39 AM, ant elder [EMAIL PROTECTED] wrote: This looks really good, do you have plans to extend it further like with adding clients or other extension types? ...ant On Tue, Apr 22, 2008 at 5:53 PM, [EMAIL PROTECTED] wrote: Page Edited : TUSCANY http://cwiki.apache.org/confluence/display/TUSCANY: Build your first Web Services with Tuscany http://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscany Build your first Web Services with Tuscany http://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscany has been edited by Luciano Resende http://cwiki.apache.org/confluence/display/[EMAIL PROTECTED] (Apr 22, 2008). (View changes) http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=82971originalVersion=5revisedVersion=6 Content: Build your first Web Services with Tuscany This guide will give you step by step instructions on how to build your first web services. The first part, we will learn how we can add the Tuscany Runtime to Eclipse IDE. The second part, will show how easy is to create a webservices using Apache Tuscany. Install Tuscany Eclipse Plugins 1.1 Install the Tuscany Eclipse Plugin The first thing you do is to start Eclipse and go to *Help - Software Updates - Find and Install*, select Search for new features to install and then click next On the next dialog, click on *New Remote Site...* to create a new site entry. Give it a name such as Tuscany and add the site URL as * http://people.apache.org/~jsdelfino/tuscany/tools/updatesite/*http://people.apache.org/%7Ejsdelfino/tuscany/tools/updatesite/* http://people.apache.org/%7Ejsdelfino/tuscany/tools/updatesite/* http://people.apache.org/%7Ejsdelfino/tuscany/tools/updatesite/* Make sure the *Remote Site* that was just created is selected, and click *Finish* Select the *Apache Tuscany SCA Tools* and click *Next*, and then, on the next dialog, click *Finish* Accept the *Plugin License* and next click on *Install All* When asked to *restart eclipse*, click the *yes* button. Create your Service Business Logic Create a Java Project In this step you create a Java Project in Eclipse to hold the composite service application. Click on the *New Java Project* button in the toolbar to launch the project creation dialog. Next you enter ws as the *Project name*, and for *Project Layout* select *Create separate* *folders for sources and class files.* Hit the *Next* button, and on the following page go to the *Libraries*tab. Use the *Add Library...* button on the right to add the *Tuscany Library* library to the project
Re: svn commit: r651906 - in /incubator/tuscany/java/sca: distribution/ distribution/bundle/ distribution/manifest/ modules/host-jetty/src/main/java/org/apache/tuscany/sca/http/jetty/module/ modules/h
This change removes the tomcat host from the sca all jar, is that ok? We did
remove that before at one point and only include the jetty host but it seems
like now we have both again, or did it only ever get done in a release
branch and not synced to trunk? This also changes the hosts so that the
webapp host will remove any other hosts if it can detect its running in a
webapp, thats so its simple to use the lib directory in the bin distribution
for both standalone and in a webapp without having to do any messing about
adding/removing jars.
...ant
On Sun, Apr 27, 2008 at 10:49 AM, [EMAIL PROTECTED] wrote:
Author: antelder
Date: Sun Apr 27 02:49:38 2008
New Revision: 651906
URL: http://svn.apache.org/viewvc?rev=651906view=rev
Log:
Update servlet hosts so that the webapp host takes precidence and include
webapp host in sca all jar and exclude tomcat host from all jar
Modified:
incubator/tuscany/java/sca/distribution/bundle/pom.xml
incubator/tuscany/java/sca/distribution/manifest/pom.xml
incubator/tuscany/java/sca/distribution/pom.xml
incubator/tuscany/java/sca/modules/host-jetty/src/main/java/org/apache/tuscany/sca/http/jetty/module/JettyRuntimeModuleActivator.java
incubator/tuscany/java/sca/modules/host-tomcat/src/main/java/org/apache/tuscany/sca/http/tomcat/module/TomcatRuntimeModuleActivator.java
incubator/tuscany/java/sca/modules/host-webapp/src/main/java/org/apache/tuscany/sca/host/webapp/WebAppModuleActivator.java
Modified: incubator/tuscany/java/sca/distribution/bundle/pom.xml
URL:
http://svn.apache.org/viewvc/incubator/tuscany/java/sca/distribution/bundle/pom.xml?rev=651906r1=651905r2=651906view=diff
==
--- incubator/tuscany/java/sca/distribution/bundle/pom.xml (original)
+++ incubator/tuscany/java/sca/distribution/bundle/pom.xml Sun Apr 27
02:49:38 2008
@@ -263,11 +263,11 @@
artifactIdtuscany-host-rmi/artifactId
version${pom.version}/version
/dependency
-!-- dependency removed for now, see TUSCANY-1572 and
TUSCANY-1568
+dependency
groupId${pom.groupId}/groupId
artifactIdtuscany-host-webapp/artifactId
version${pom.version}/version
-/dependency --
+/dependency
dependency
groupId${pom.groupId}/groupId
artifactIdtuscany-host-jetty/artifactId
@@ -277,7 +277,7 @@
groupId${pom.groupId}/groupId
artifactIdtuscany-host-tomcat/artifactId
version${pom.version}/version
-/dependency--
+/dependency --
dependency
groupId${pom.groupId}/groupId
artifactIdtuscany-interface/artifactId
@@ -352,6 +352,12 @@
groupId${pom.groupId}/groupId
artifactIdtuscany-implementation-node-runtime/artifactId
version${pom.version}/version
+exclusions
+exclusion
+groupId${pom.groupId}/groupId
+artifactIdtuscany-host-tomcat/artifactId
+/exclusion
+/exclusions
/dependency
dependency
groupId${pom.groupId}/groupId
@@ -447,6 +453,12 @@
groupId${pom.groupId}/groupId
artifactIdtuscany-domain-manager/artifactId
version${pom.version}/version
+exclusions
+exclusion
+groupId${pom.groupId}/groupId
+artifactIdtuscany-host-tomcat/artifactId
+/exclusion
+/exclusions
/dependency
dependency
groupId${pom.groupId}/groupId
Modified: incubator/tuscany/java/sca/distribution/manifest/pom.xml
URL:
http://svn.apache.org/viewvc/incubator/tuscany/java/sca/distribution/manifest/pom.xml?rev=651906r1=651905r2=651906view=diff
==
--- incubator/tuscany/java/sca/distribution/manifest/pom.xml (original)
+++ incubator/tuscany/java/sca/distribution/manifest/pom.xml Sun Apr 27
02:49:38 2008
@@ -350,11 +350,11 @@
artifactIdtuscany-host-jetty/artifactId
version${pom.version}/version
/dependency
-dependency
+!-- dependency
groupId${pom.groupId}/groupId
artifactIdtuscany-host-tomcat/artifactId
version${pom.version}/version
-/dependency
+/dependency --
dependency
groupId${pom.groupId}/groupId
artifactIdtuscany-interface/artifactId
@@ -430,6 +430,12 @@
groupId${pom.groupId}/groupId
artifactIdtuscany-implementation-node-runtime/artifactId
version${pom.version}/version
+exclusions
+exclusion
+groupId${pom.groupId}/groupId
+
Re: [vtest] getCompositeContext API for non-SCA clients
On Fri, Apr 25, 2008 at 2:11 PM, Simon Laws [EMAIL PROTECTED] wrote: On Fri, Apr 25, 2008 at 8:32 AM, ant elder [EMAIL PROTECTED] wrote: Sounds ok to me. ...ant On Thu, Apr 24, 2008 at 9:41 PM, Yee-Kang Chang [EMAIL PROTECTED] wrote: Thanks, Scott, Ant. I think both could work. Perhaps we can start with getComponentContext(String componentURI) and go from there? I gather a client will typically connect to a domain first and then work with its components? If so, adding getComponentContext() to SCADomain can be a good start? -- Kevin, Yee-Kang, Did you envision creating a new API that would accept a component URI as input, e.g.: ComponentContext getComponentContext(String componentURI); Or were you talking about some sort of virtual component like Ant mentioned? Scott On Thu, Apr 24, 2008 at 10:49 AM, ant elder [EMAIL PROTECTED] wrote: Ok, although with non-SCA clients which component would that be? Does there need to be a new something like implementation.web but for JSE clients? or could there be a virtual component that has references for all the toplevel component services in the domain (which is kind of what we have now with SCADomain.getService right?). ...ant On Thu, Apr 17, 2008 at 9:10 PM, Yee-Kang Chang [EMAIL PROTECTED] wrote: Just thought to follow-up to see if we will do this .. Perhaps SCADomain can be extended to return the ComponentContext for a particular component? Thanks. On Wed, Apr 2, 2008 at 6:37 PM, Kevin Williams [EMAIL PROTECTED] wrote: The current JUnit tests (iTest and vTest) make use of the non-standard SCADomain.getService API to get a handle to an SCA service. Are there any plans to provide an API to get a ComponentContext as outlined by the SCA Java Annotations and APIs specification? I would like to stick to stick to specified APIs as much as possible in vTest. 1.4.2.1. ComponentContext Non-SCA client code can use the ComponentContext API to perform operations against a component in an SCA domain. How client code obtains a reference to a ComponentContext is runtime specific. The following example demonstrates the use of the component Context API by non-SCA code: ComponentContext context = // obtained through host environment-specific means HelloService helloService = context.getService(HelloService.class,HelloService); Thanks. -- Kevin I don't remember any discussion about this so i guess there are no plans yet to change it. I agree it seems like we should though. ...ant Hi Implementing the spec described API for getting at service reference sounds like a good idea to me. However the semantics of the ComponentContext differ from what we are used to on SCADomain and SCANode. For example, SCADomain.getService(serviceName) - currently provides a proxy to the requested service in the local runtime ComponentContext.getService(referenceName) - returns the proxy for the named reference of the service to which the context refers So it will take a bit of getting used to. The equivalent of serviceProxy = SCADomain.getService(interface, serviceName) being context = SCADomain.getComponentContext(componentName) serviceProxy = context.createSelfRefence(interface, serviceName) Perhaps, more importantly, the implications of getServiceReference() are different as the reference returned is a reference of the component rather than a reference to the component. From there you could go and set conversation and callback details on that reference. Not sure this is bad but it's certainly different from what we are used to. I'm also not sure that getRequestContext() would ever return anything useful in this case. Is it the intention that a context can be retrieved for a component that is not running in the local runtime, i.e. is running remotely somewhere else in the domain? This is problematic because the majority of the ComponentContext interface relies on some undisclosed protocol to get at information such as properties and references. I think getting a reference to the service is doable as we can reasonably expect to be able to talk to the component service remotely. However a better approach could be to restrict component context retrieval to local components and then rely on access to local component references to access remote components. Just my initial impression... Simon [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/sca-api/src/main/java/org/osoa/sca/ComponentContext.java Doesn't the virtual component that has references for all the component services in the (local?) domain help with some of those issues
Re: What's next for SCA BPEL Integration
On Thu, Apr 24, 2008 at 7:59 PM, Matthieu Riou [EMAIL PROTECTED] wrote: On Thu, Apr 24, 2008 at 10:41 AM, Luciano Resende [EMAIL PROTECTED] wrote: On Thu, Apr 24, 2008 at 8:53 AM, ant elder [EMAIL PROTECTED] wrote: On Thu, Apr 24, 2008 at 4:37 PM, Luciano Resende [EMAIL PROTECTED] wrote: Now that we are making more progress with the SCA BPEL integration and have figured out how to make References to work, let's discuss what could be the next steps on this area. Below are couple examples of what we could do next - WS-BPEL Process Introspection : Currently we are requiring SCA componentType files, we could introspect the BPEL process file to generate the component type information from it. - Integrate BEPL with the store scenario tutorial : We could add a OrderProcessing step to the store checkout, and illustrate a more real integration scenario. Other then these, we could review the SCA_ClientAndImplementationModelFor BPEL and identify other areas that we might need enhancements. Scenarios / Samples / Demos are always welcome too. Or if you have other suggestions, feel free to jump to the discussion. BTW: Copying the ODE list in case they want to jump and help, or in case they have other ideas. Not a very exciting one but is there any clean up of the dependencies possible? Currently using the implementation.bpel extension brings in 78 addition dependency jars at about 20meg, i wondered if some of those could get excluded? ...ant Part of this is because we have a Embedded ODE BPEL engine, and that itself brings several dependencies. But this is certainly something to investigate. It would be also good if ODE could be more flexible/dynamic with some dependencies (e.g Saxon) and only really require these dependencies if they are going to be in use, this would help our side as well. Saxon is going to be hard to remove, there are very few BPEL processes that won't need any XPath expressions to execute so I'm not sure it's one we can save. But you're right for the embedded engine, right now we use our own stuff for everything ODE needs to execute: connection pool, transaction manager, jpa instance, thread pool, ... I'm guessing for many of these we could reuse what comes with Tuscany. These are all the additional dependencies brought in with the Tuscany implementation.bpel extension, are any of them obviously not necessary? activeio-2.0-r118.jar axion-1.0-M3-dev.jar backport-util-concurrent-3.0.jar common-2.2.3.jar commons-codec-1.3.jar commons-collections-3.1.jar commons-jexl-1.1.jar commons-lang-2.1.jar commons-logging-1.0.4.jar commons-primitives-1.0.jar derby-10.3.1.4.jar dom4j-1.6.1.jar ecore-2.2.3.jar ecore-change-2.2.3.jar ecore-xmi-2.2.3.jar geronimo-common-1.2-beta.jar geronimo-connector-1.2-beta.jar geronimo-core-1.2-beta.jar geronimo-deployment-1.2-beta.jar geronimo-ejb_3.0_spec-1.0.jar geronimo-interceptor-1.2-beta.jar geronimo-j2ee-1.2-beta.jar geronimo-j2ee-connector_1.5_spec-1.1.jar geronimo-j2ee-jacc_1.0_spec-1.1.jar geronimo-j2ee-management_1.0_spec-1.1.jar geronimo-jpa_3.0_spec-1.0.jar geronimo-jta_1.0.1B_spec-1.0.jar geronimo-kernel-1.2-beta.jar geronimo-management-1.2-beta.jar geronimo-naming-1.2-beta.jar geronimo-security-1.2-beta.jar geronimo-spec-j2ee-connector-1.5-rc4.jar geronimo-spec-jta-1.0.1B-rc4.jar geronimo-system-1.2-beta.jar geronimo-transaction-1.2-beta.jar geronimo-util-1.2-beta.jar howl-1.0.1-1.jar icu4j-2.6.1.jar javacc-3.2.jar jaxen-1.1.1.jar jdom-1.0.jar log4j-1.2.13.jar ode-bpel-api-1.1.jar ode-bpel-compiler-1.1.jar ode-bpel-dao-1.1.jar ode-bpel-epr-1.1.jar ode-bpel-obj-1.1.jar ode-bpel-runtime-1.1.jar ode-bpel-schemas-1.1.jar ode-bpel-store-1.1.jar ode-dao-jpa-1.1.jar ode-jacob-1.1.jar ode-jacob-ap-1.1.jar ode-scheduler-simple-1.1.jar ode-utils-1.1.jar openjpa-all-0.9.7-incubating.jar openjpa-persistence-0.9.7-incubating.jar org.apache.felix.bundlerepository-1.0.0.jar org.apache.felix.framework-1.0.1.jar org.apache.felix.main-1.0.1.jar org.apache.felix.shell-1.0.0.jar org.apache.felix.shell.tui-1.0.0.jar regexp-1.3.jar saxon-8.7.jar saxon-dom-8.7.jar saxon-xpath-8.7.jar serp-1.12.0.jar tranql-connector-1.1.jar tuscany-databinding-sdo-2.0-incubating-SNAPSHOT.jar tuscany-implementation-bpel-2.0-incubating-SNAPSHOT.jar xalan-2.7.0.jar xbean-naming-2.7.jar xercesImpl-2.8.1.jar xml-apis-1.3.02.jar xml-resolver-1.1.jar xmlbeans-2.3.0.jar xmlParserAPIs-2.6.2.jar XmlSchema-1.3.2.jar xom-1.0.jar xsd-2.2.3.jar ...ant
Re: [vtest] getCompositeContext API for non-SCA clients
Sounds ok to me. ...ant On Thu, Apr 24, 2008 at 9:41 PM, Yee-Kang Chang [EMAIL PROTECTED] wrote: Thanks, Scott, Ant. I think both could work. Perhaps we can start with getComponentContext(String componentURI) and go from there? I gather a client will typically connect to a domain first and then work with its components? If so, adding getComponentContext() to SCADomain can be a good start? -- Kevin, Yee-Kang, Did you envision creating a new API that would accept a component URI as input, e.g.: ComponentContext getComponentContext(String componentURI); Or were you talking about some sort of virtual component like Ant mentioned? Scott On Thu, Apr 24, 2008 at 10:49 AM, ant elder [EMAIL PROTECTED] wrote: Ok, although with non-SCA clients which component would that be? Does there need to be a new something like implementation.web but for JSE clients? or could there be a virtual component that has references for all the toplevel component services in the domain (which is kind of what we have now with SCADomain.getService right?). ...ant On Thu, Apr 17, 2008 at 9:10 PM, Yee-Kang Chang [EMAIL PROTECTED] wrote: Just thought to follow-up to see if we will do this .. Perhaps SCADomain can be extended to return the ComponentContext for a particular component? Thanks. On Wed, Apr 2, 2008 at 6:37 PM, Kevin Williams [EMAIL PROTECTED] wrote: The current JUnit tests (iTest and vTest) make use of the non-standard SCADomain.getService API to get a handle to an SCA service. Are there any plans to provide an API to get a ComponentContext as outlined by the SCA Java Annotations and APIs specification? I would like to stick to stick to specified APIs as much as possible in vTest. 1.4.2.1. ComponentContext Non-SCA client code can use the ComponentContext API to perform operations against a component in an SCA domain. How client code obtains a reference to a ComponentContext is runtime specific. The following example demonstrates the use of the component Context API by non-SCA code: ComponentContext context = // obtained through host environment-specific means HelloService helloService = context.getService(HelloService.class,HelloService); Thanks. -- Kevin I don't remember any discussion about this so i guess there are no plans yet to change it. I agree it seems like we should though. ...ant
Re: Adding SVN version to Java files
On Thu, Apr 24, 2008 at 9:55 AM, Mark Combellack [EMAIL PROTECTED] wrote: snip * Typically, users do not do an SVN checkout of the source code and will not have SVN installed. They are typically provided with a jar file containing the source code. They will not be able to run SVN command to work out which versions of source code they are running * Typically, there are many, many more users than there are developers * If a source file is printed out or attached as an email as part of a bug report or published on a web server, the source code will contain the SVN revision number. This makes the bug easier to fix as you know the revision number. The SVN commands will not be able to tell you the revision number in these scenarios. From what everyone has said so far the above seem like the only real justification for where these might be useful, and I'm sceptical whether users really would care or use these as from what i've seen they say things like it broke in 1.1 or it worked last week and don't go down to mentioning individual class files let alone revisions of the file, and usually don't post whole class files to bug reports. Anyway, I'm obviously in a minority on this so if everyone else really really wants to add these i wont get in the way. How would that work - it would be manditory to add them to each new file and everyone must have their SVN client configured so the correct SVN properties get set? ...ant
Re: Adding SVN version to Java files
On Thu, Apr 24, 2008 at 5:55 PM, Simon Nash [EMAIL PROTECTED] wrote: snip Regarding whether or not we have consensus and whether we should hold a vote, consensus is not the same as unanimity. I think we need to make a decision on this issue (which is relatively minor) and move forward. Holding a vote seems to be a reasonable way to do this. Consensus is not the same as unanimity but that doesn't mean voting is the way to resolve disagreements, you just have to look at the trouble doing that has caused in the project when its happened in the past. A definition I like for consensus is: A decision making process whereby decisions are reached when all members present consent to a proposal. This process does not assume everyone must be in complete agreement. When differences remain after discussion, individuals can agree to disagree, that is, give their consent by standing aside, and allow the proposal to be accepted by the group. If someone who's an important part of the project (ie a PMC member?) doesn't agree with something enough to refuse to stand aside then maybe in most cases its best to just find another way. Thats one of the reasons I think we should be a bit discerning about who we make PMC members - so that we trust each other enough to know it most cases we would stand aside and if we wont then for everyone to be able to respect that. ...ant
Re: What's next for SCA BPEL Integration
On Fri, Apr 25, 2008 at 11:44 AM, Mike Edwards [EMAIL PROTECTED] wrote: ant elder wrote: These are all the additional dependencies brought in with the Tuscany implementation.bpel extension, are any of them obviously not necessary? activeio-2.0-r118.jar axion-1.0-M3-dev.jar backport-util-concurrent-3.0.jar common-2.2.3.jar commons-codec-1.3.jar commons-collections-3.1.jar commons-jexl-1.1.jar commons-lang-2.1.jar commons-logging-1.0.4.jar commons-primitives-1.0.jar derby-10.3.1.4.jar dom4j-1.6.1.jar ecore-2.2.3.jar ecore-change-2.2.3.jar ecore-xmi-2.2.3.jar geronimo-common-1.2-beta.jar geronimo-connector-1.2-beta.jar geronimo-core-1.2-beta.jar geronimo-deployment-1.2-beta.jar geronimo-ejb_3.0_spec-1.0.jar geronimo-interceptor-1.2-beta.jar geronimo-j2ee-1.2-beta.jar geronimo-j2ee-connector_1.5_spec-1.1.jar geronimo-j2ee-jacc_1.0_spec-1.1.jar geronimo-j2ee-management_1.0_spec-1.1.jar geronimo-jpa_3.0_spec-1.0.jar geronimo-jta_1.0.1B_spec-1.0.jar geronimo-kernel-1.2-beta.jar geronimo-management-1.2-beta.jar geronimo-naming-1.2-beta.jar geronimo-security-1.2-beta.jar geronimo-spec-j2ee-connector-1.5-rc4.jar geronimo-spec-jta-1.0.1B-rc4.jar geronimo-system-1.2-beta.jar geronimo-transaction-1.2-beta.jar geronimo-util-1.2-beta.jar howl-1.0.1-1.jar icu4j-2.6.1.jar javacc-3.2.jar jaxen-1.1.1.jar jdom-1.0.jar log4j-1.2.13.jar ode-bpel-api-1.1.jar ode-bpel-compiler-1.1.jar ode-bpel-dao-1.1.jar ode-bpel-epr-1.1.jar ode-bpel-obj-1.1.jar ode-bpel-runtime-1.1.jar ode-bpel-schemas-1.1.jar ode-bpel-store-1.1.jar ode-dao-jpa-1.1.jar ode-jacob-1.1.jar ode-jacob-ap-1.1.jar ode-scheduler-simple-1.1.jar ode-utils-1.1.jar openjpa-all-0.9.7-incubating.jar openjpa-persistence-0.9.7-incubating.jar org.apache.felix.bundlerepository-1.0.0.jar org.apache.felix.framework-1.0.1.jar org.apache.felix.main-1.0.1.jar org.apache.felix.shell-1.0.0.jar org.apache.felix.shell.tui-1.0.0.jar regexp-1.3.jar saxon-8.7.jar saxon-dom-8.7.jar saxon-xpath-8.7.jar serp-1.12.0.jar tranql-connector-1.1.jar tuscany-databinding-sdo-2.0-incubating-SNAPSHOT.jar tuscany-implementation-bpel-2.0-incubating-SNAPSHOT.jar xalan-2.7.0.jar xbean-naming-2.7.jar xercesImpl-2.8.1.jar xml-apis-1.3.02.jar xml-resolver-1.1.jar xmlbeans-2.3.0.jar xmlParserAPIs-2.6.2.jar XmlSchema-1.3.2.jar xom-1.0.jar xsd-2.2.3.jar ...ant I suggest that we get the functionality of implementation.bpel.../ working first before we start to worry about the amount of clobber that it involves. It is barely working at the moment. Fair enough, I've not tried using it yet so didn't realize it was still so rough. ...ant
Re: [NOTICE] Mario Antollini voted as Tuscany committer
Welcome and have fun ...ant On Fri, Apr 25, 2008 at 5:02 PM, Antollini, Mario [EMAIL PROTECTED] wrote: Hello!, I just read the great news... This is a great opportunity for me! Thanks for all your confidence and support. This all means interesting challenges in the future which I will be glad to face... Thanks again for the trust!, Mario -Original Message- From: Simon Nash [mailto:[EMAIL PROTECTED] Sent: Friday, April 25, 2008 12:59 PM To: tuscany-dev Subject: Re: [NOTICE] Mario Antollini voted as Tuscany committer Congratulations, Mario, and welcome! Simon Raymond Feng wrote: Mario, congratulations and welcome on board! Thanks, Raymond -- From: Luciano Resende [EMAIL PROTECTED] Sent: Friday, April 25, 2008 8:47 AM To: tuscany-dev tuscany-dev@ws.apache.org Cc: Antollini, Mario [EMAIL PROTECTED] Subject: [NOTICE] Mario Antollini voted as Tuscany committer The Tuscany PPMC and Incubator PMC have voted for Mario Antollini to become a Tuscany committer. Please spend sometime to get familiar with Apache developer's pages [1], the Apache Incubator site [2] and to the Incubator Committers Guide [3]. Also, could you please submit an Apache CLA so we can get your userid and access sorted out, you can find out about the Contributor License Agreement at [4]. Congratulations and welcome Mario! [1] http://www.apache.org/dev/ [2] http://incubator.apache.org/ [3] http://incubator.apache.org/guides/committer.html [4] http://www.apache.org/licenses/#clas -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresendehttp://people.apache.org/%7Elresende http://lresende.blogspot.com/
Re: SCADomain.getService () should throw exception when bogus component name is passed?
I'm going to close TUSCANY-2145 as working as designed in a few days unless
someone says otherwise.
I still get the feeling that there is actually no way for
o.a.t.s.host.imbedded.impl.DefaultSCADomain to find any new services at
invocation time so it could just throw the exception as suggested in the
JIRA, but it seems harder to prove that than to just go with the flow and
keep the current behaviour.
...ant
On Sun, Apr 13, 2008 at 3:35 PM, Yang Lei [EMAIL PROTECTED] wrote:
I think we should keep the following piece. As the comment
said,create a remote service ref , so it can delegate to the binding
implementation to handle remote case.
// Lookup the component in the domain
Component component = componentManager.getComponent(componentName);
if (component == null) {
// The component is not local in the partition, try to
create a remote service ref
return createServiceReference(businessInterface, name);
}
I agree if we already find the component ( component !=null case), we
should check if the service is defined on the component and throw the
service not found exception if it is not defined. I think the current
implementation already does it in the ComponentContextImpl...
Yang.
On Thu, Apr 10, 2008 at 4:17 AM, Wang Feng [EMAIL PROTECTED] wrote:
+1 throw an exception.
The scenario like this class.getMethod(methodName).
If a matching method is not found,it will throw NoSuchMethodException.
Thanks,
Wang Feng
On 2008-04-10,ant elder [EMAIL PROTECTED] wrote:
TUSCANY-2145 asks about SCADomain.getService () returning a proxy even
when
the service doesn't exist, but looking back through the SVN history it
looks
like this is intentional. Before I close the JIRA does anyone have any
comments on if this is/isn't the correct behaviour?
...ant
-
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: [CONF] Apache Tuscany: Build your first Web Services with Tuscany (page edited)
I asked as I'd like to help expand it but don't want to step on your toes.
Adding web clients sounds good, expanding the WS bit with how to use other
databindings would be useful, maybe something on other bindings like JMS,
then it could go on with what to do when you want to run it out side of
eclipse - how to make contribution jars or run standalone or in webapps etc.
I like that that page is nice and simple and clear and focused so it would
be good to try to maintain that, maybe have separate pages for each topic
but linked together and in the same sort of style as that one. WDYT?
...ant
On Wed, Apr 23, 2008 at 5:17 PM, Luciano Resende [EMAIL PROTECTED]
wrote:
Yes, it's on my todo list for the next couple days...
Do you have any ideas for what type of extensions to use ? Maybe
JSON-RPC and use a quick web2.0 client app to consume the service ?
On Wed, Apr 23, 2008 at 4:39 AM, ant elder [EMAIL PROTECTED] wrote:
This looks really good, do you have plans to extend it further like with
adding clients or other extension types?
...ant
On Tue, Apr 22, 2008 at 5:53 PM, [EMAIL PROTECTED] wrote:
Page Edited : TUSCANY
http://cwiki.apache.org/confluence/display/TUSCANY: Build
your first Web Services with Tuscany
http://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscany
Build your first Web Services with Tuscany
http://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscanyhas
been edited by Luciano
Resende
http://cwiki.apache.org/confluence/display/[EMAIL PROTECTED] (Apr
22, 2008).
(View changes)
http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=82971originalVersion=5revisedVersion=6
Content:
Build your first Web Services with Tuscany
This guide will give you step by step instructions on how to build
your
first web services.
The first part, we will learn how we can add the Tuscany Runtime to
Eclipse IDE.
The second part, will show how easy is to create a webservices using
Apache Tuscany.
Install Tuscany Eclipse Plugins 1.1
Install the Tuscany Eclipse Plugin
The first thing you do is to start Eclipse and go to *Help -
Software
Updates - Find and Install*,
select Search for new features to install and then click next
On the next dialog, click on *New Remote Site...* to create a new
site
entry. Give it a name such as
Tuscany and add the site URL as *
http://people.apache.org/~jsdelfino/tuscany/tools/updatesite/*http://people.apache.org/%7Ejsdelfino/tuscany/tools/updatesite/*
http://people.apache.org/%7Ejsdelfino/tuscany/tools/updatesite/*
Make sure the *Remote Site* that was just created is selected, and
click *Finish*
Select the *Apache Tuscany SCA Tools* and click *Next*, and then,
on
the next dialog, click *Finish*
Accept the *Plugin License*
and next click on *Install All*
When asked to *restart eclipse*, click the *yes* button.
Create your Service Business Logic Create a Java Project
In this step you create a Java Project in Eclipse to hold the
composite
service application.
Click on the *New Java Project* button in the toolbar to launch the
project creation dialog.
Next you enter ws as the *Project name*, and for *Project Layout*
select
*Create separate*
*folders for sources and class files.*
Hit the *Next* button, and on the following page go to the
*Libraries*tab. Use the
*Add Library...*
button on the right to add the *Tuscany Library* library to the
project.
Hit the *Finish* button to complete the *New Java Project* dialog to
create the ws java project.
Construct Services
First you create the helloworld package folders into which later in
this
step you place service implementations.
Select the ws project and click on the *New Java Package* button in
the
toolbar to launch
the package creation dialog.
Next you enter helloworld as the package *Name*, and press the
*Finish*button to complete the
dialog.
*HelloWorld*
In this step you create the HelloWorld service interface and
implementation.
Select the helloworld package. Next you click on the dropdown arrow
next
to the *New Java Class*
buttonand select the *New Java Interface*option from the
dropdown
list. In the dialog
enter HelloWorld as the *Name* of the interface and select the
Finish
button to complete the dialog.
The Java editor will open on the new created Java interface. Replace
the
content of the editor by
*copy-paste* of the following Java interface code snippet.
package helloworld;import org.osoa.sca.annotations.Remotable;
@Remotablepublic interface HelloWorld {
String sayHello(String name
[jira] Commented: (TUSCANY-2268) Exceptions errors on binding to external web services
[ https://issues.apache.org/jira/browse/TUSCANY-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591978#action_12591978 ] ant elder commented on TUSCANY-2268: There's two problems I've noticed so far: - the interface HelloWorld has the @Remotable commented out with the comment utile ?, you need this. Without it when everything else is configured ok you'll get the following: [java] Exception in thread main java.lang.IllegalArgumentException: Can't handle mixed payloads betweem OMElements and other types. - in the .composite files the binding.ws has an incorrect port name of HelloWorldSoapPort instead of HelloWorldSoap as defined in the helloworld.wsdl. Changing those two things gets the client running for me though i can't test it fully as I don't have any service running for it. If you still have trouble invoking the service post the service code so i can help debug that. Apologies that the error messages given for those two problems are so unhelpful, more meaningfull messages would have made that much easier to debug. Exceptions errors on binding to external web services - Key: TUSCANY-2268 URL: https://issues.apache.org/jira/browse/TUSCANY-2268 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: Windows XP, Eclipse 3.3.0 , tuscany incubating 1.1 , java 6 Reporter: Marina Deslaugiers Attachments: ws-webhelloworld.zip Hi, I am considering web services that seems to be doc literal encoded. I began to try the direct connection to them but I did not succeed. As these web services are not public ones, I have done a try on a simple (helloworrd) public one without success. Depending, on the binding way (uri, wsdlElement and promoted or not promoted reference) I get different exceptions (some are indicated - within a comment - in the composite files). So, what is wrong ? I attach the code I wrote; please, would you mind to verify (and correct if necessary) it or send me an equivalent example that works because I need to make it work rapidly now. Thanks, Marina. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (TUSCANY-2268) Exceptions errors on binding toexternal web services
at org.apache.tuscany.sca.databinding.impl.MediatorImpl.getTransformerChain(MediatorImpl.java:146) -- I get the same If I promote the reference from the composite. Besides, to answer your demand, I get no service code as I connect to a non-SCA (external) web service. So, It brings me back to the primary question in my first e-mail in the mail thread: is it achievable in Tuscany to use binding.ws to connect from a SCA domain to a non-SCA (so external) web service ? Regards, Marina. Le 24 avr. 08 à 12:37, ant elder (JIRA) a écrit : [ https://issues.apache.org/jira/browse/TUSCANY-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591978#action_12591978 ] ant elder commented on TUSCANY-2268: There's two problems I've noticed so far: - the interface HelloWorld has the @Remotable commented out with the comment utile ?, you need this. Without it when everything else is configured ok you'll get the following: [java] Exception in thread main java.lang.IllegalArgumentException: Can't handle mixed payloads betweem OMElements and other types. - in the .composite files the binding.ws has an incorrect port name of HelloWorldSoapPort instead of HelloWorldSoap as defined in the helloworld.wsdl. Changing those two things gets the client running for me though i can't test it fully as I don't have any service running for it. If you still have trouble invoking the service post the service code so i can help debug that. Apologies that the error messages given for those two problems are so unhelpful, more meaningfull messages would have made that much easier to debug. Exceptions errors on binding to external web services - Key: TUSCANY-2268 URL: https://issues.apache.org/jira/browse/TUSCANY-2268 Project: Tuscany Issue Type: Bug Components: Java SCA Axis Binding Extension Affects Versions: Java-SCA-1.1 Environment: Windows XP, Eclipse 3.3.0 , tuscany incubating 1.1 , java 6 Reporter: Marina Deslaugiers Attachments: ws-webhelloworld.zip Hi, I am considering web services that seems to be doc literal encoded. I began to try the direct connection to them but I did not succeed. As these web services are not public ones, I have done a try on a simple (helloworrd) public one without success. Depending, on the binding way (uri, wsdlElement and promoted or not promoted reference) I get different exceptions (some are indicated - within a comment - in the composite files). So, what is wrong ? I attach the code I wrote; please, would you mind to verify (and correct if necessary) it or send me an equivalent example that works because I need to make it work rapidly now. Thanks, Marina. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [vtest] getCompositeContext API for non-SCA clients
Ok, although with non-SCA clients which component would that be? Does there need to be a new something like implementation.web but for JSE clients? or could there be a virtual component that has references for all the toplevel component services in the domain (which is kind of what we have now with SCADomain.getService right?). ...ant On Thu, Apr 17, 2008 at 9:10 PM, Yee-Kang Chang [EMAIL PROTECTED] wrote: Just thought to follow-up to see if we will do this .. Perhaps SCADomain can be extended to return the ComponentContext for a particular component? Thanks. On Wed, Apr 2, 2008 at 6:37 PM, Kevin Williams [EMAIL PROTECTED] wrote: The current JUnit tests (iTest and vTest) make use of the non-standard SCADomain.getService API to get a handle to an SCA service. Are there any plans to provide an API to get a ComponentContext as outlined by the SCA Java Annotations and APIs specification? I would like to stick to stick to specified APIs as much as possible in vTest. 1.4.2.1. ComponentContext Non-SCA client code can use the ComponentContext API to perform operations against a component in an SCA domain. How client code obtains a reference to a ComponentContext is runtime specific. The following example demonstrates the use of the component Context API by non-SCA code: ComponentContext context = // obtained through host environment-specific means HelloService helloService = context.getService(HelloService.class,HelloService); Thanks. -- Kevin I don't remember any discussion about this so i guess there are no plans yet to change it. I agree it seems like we should though. ...ant
Re: [CONF] Apache Tuscany: Build your first Web Services with Tuscany (page edited)
This looks really good, do you have plans to extend it further like with
adding clients or other extension types?
...ant
On Tue, Apr 22, 2008 at 5:53 PM, [EMAIL PROTECTED] wrote:
Page Edited : TUSCANYhttp://cwiki.apache.org/confluence/display/TUSCANY:
Build
your first Web Services with
Tuscanyhttp://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscany
Build your first Web Services with
Tuscanyhttp://cwiki.apache.org/confluence/display/TUSCANY/Build+your+first+Web+Services+with+Tuscanyhas
been edited by Luciano
Resendehttp://cwiki.apache.org/confluence/display/[EMAIL PROTECTED] (Apr
22, 2008).
(View
changes)http://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=82971originalVersion=5revisedVersion=6
Content:
Build your first Web Services with Tuscany
This guide will give you step by step instructions on how to build your
first web services.
The first part, we will learn how we can add the Tuscany Runtime to
Eclipse IDE.
The second part, will show how easy is to create a webservices using
Apache Tuscany.
Install Tuscany Eclipse Plugins 1.1
Install the Tuscany Eclipse Plugin
The first thing you do is to start Eclipse and go to *Help - Software
Updates - Find and Install*,
select Search for new features to install and then click next
On the next dialog, click on *New Remote Site...* to create a new site
entry. Give it a name such as
Tuscany and add the site URL as *
http://people.apache.org/~jsdelfino/tuscany/tools/updatesite/*http://people.apache.org/%7Ejsdelfino/tuscany/tools/updatesite/*
Make sure the *Remote Site* that was just created is selected, and
click *Finish*
Select the *Apache Tuscany SCA Tools* and click *Next*, and then, on
the next dialog, click *Finish*
Accept the *Plugin License*
and next click on *Install All*
When asked to *restart eclipse*, click the *yes* button.
Create your Service Business Logic Create a Java Project
In this step you create a Java Project in Eclipse to hold the composite
service application.
Click on the *New Java Project* button in the toolbar to launch the
project creation dialog.
Next you enter ws as the *Project name*, and for *Project Layout* select
*Create separate*
*folders for sources and class files.*
Hit the *Next* button, and on the following page go to the *Libraries*tab.
Use the
*Add Library...*
button on the right to add the *Tuscany Library* library to the project.
Hit the *Finish* button to complete the *New Java Project* dialog to
create the ws java project.
Construct Services
First you create the helloworld package folders into which later in this
step you place service implementations.
Select the ws project and click on the *New Java Package* button in the
toolbar to launch
the package creation dialog.
Next you enter helloworld as the package *Name*, and press the
*Finish*button to complete the
dialog.
*HelloWorld*
In this step you create the HelloWorld service interface and
implementation.
Select the helloworld package. Next you click on the dropdown arrow next
to the *New Java Class*
buttonand select the *New Java Interface*option from the dropdown
list. In the dialog
enter HelloWorld as the *Name* of the interface and select the Finish
button to complete the dialog.
The Java editor will open on the new created Java interface. Replace the
content of the editor by
*copy-paste* of the following Java interface code snippet.
package helloworld;import org.osoa.sca.annotations.Remotable;
@Remotablepublic interface HelloWorld {
String sayHello(String name);
}
Select the helloworld package again. Select the *New Java Class* button
. In the dialog enter
HelloWorldImpl as the *Name* of the class, add Catalog as the
interface this class implements, and
then select *Finish* to complete the dialog.
The Java editor will open on the new created Java class. Replace the
content of the editor by
*copy-paste* of the following Java class code snippet.
package helloworld;public class HelloWorldImpl implements HelloWorld {
public String sayHello(String name) {
return Hello + name;
}
}
After completing these steps the content of the ws project will look as
follows.
Compose Services
Now that you have all the required service implementations you compose
them together to provide
the store composite service. The composition is stored in a .composite
file.
Select the src folder of the ws project. *Right click* to get the
context menu, select *New*, and
then *File*. In the *New File* dialog enter helloworld.composite for the
*File name*, and then select *Finish*
to complete the dialog.
The Text editor will open on the new created composite file. Replace the
content of the editor by
*copy-paste* of the following composite snippet.
?xml version=1.0 encoding=UTF-8?
compositexmlns=http://www.osoa.org/xmlns/sca/1.0;
Re: Adding SVN version to Java files
On Wed, Apr 23, 2008 at 5:52 PM, Vamsavardhana Reddy [EMAIL PROTECTED] wrote: snip From the above, we have 4 +1s and no -1s - although we have a preference not to do this from ant. So, the consensus is to make this change. We haven't held a formal vote, so I don't think we should be trying to decide this based on a count of +1s and -1s. Agreed. We should hold a formal vote. We do consensus based development. Voting can be a useful gauging consensus but voting does not make consensus. Its obvious from this thread that there is not (yet) consensus so we don't need a vote, how about instead trying to convince us by explaining the value of adding this? ...ant
[jira] Closed: (TUSCANY-2241) EndpointReference in binding.ws when wsdlElement is not of 'Binding' form
[ https://issues.apache.org/jira/browse/TUSCANY-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2241. -- Resolution: Fixed Patch applied, thanks for the fix! EndpointReference in binding.ws when wsdlElement is not of 'Binding' form - Key: TUSCANY-2241 URL: https://issues.apache.org/jira/browse/TUSCANY-2241 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2, Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2241.patch Web Service Binding Specification v1.0 - Sec 2.1 - Lines 61 to 65: 61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6] EndpointReference 62 that specifies the endpoint for the service or reference. When this element is present along 63 with the wsdlElement attribute on the parent element, the wsdlElement attribute value MUST 64 be of the 'Binding' form as specified above, i.e. WSDL-namespace- 65 URI#wsdl.binding(binding-name). I notice that when an EndpointReference is specified inside binding.ws along with a wsdlElement which is not of 'Binding' form, no warning or error is generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2249) Updates to ComponentContext's vtest
[ https://issues.apache.org/jira/browse/TUSCANY-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12591239#action_12591239 ] ant elder commented on TUSCANY-2249: Applied in r650408. Note though that the testGetRequestContext method is failing for me so I've added @Ignore to that. Is there some associated change that needs to be made? Updates to ComponentContext's vtest --- Key: TUSCANY-2249 URL: https://issues.apache.org/jira/browse/TUSCANY-2249 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Reporter: Yee-Kang Chang Attachments: ComponentContextUpdatesJIRA2249.patch More vtest test cases for ComponentContext API. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (TUSCANY-2241) EndpointReference in binding.ws when wsdlElement is not of 'Binding' form
[ https://issues.apache.org/jira/browse/TUSCANY-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2241. -- Resolution: Fixed Applied in r650504 EndpointReference in binding.ws when wsdlElement is not of 'Binding' form - Key: TUSCANY-2241 URL: https://issues.apache.org/jira/browse/TUSCANY-2241 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2, Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2241-test.patch, TUSCANY-2241.patch Web Service Binding Specification v1.0 - Sec 2.1 - Lines 61 to 65: 61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6] EndpointReference 62 that specifies the endpoint for the service or reference. When this element is present along 63 with the wsdlElement attribute on the parent element, the wsdlElement attribute value MUST 64 be of the 'Binding' form as specified above, i.e. WSDL-namespace- 65 URI#wsdl.binding(binding-name). I notice that when an EndpointReference is specified inside binding.ws along with a wsdlElement which is not of 'Binding' form, no warning or error is generated. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TUSCANY-2241) EndpointReference in binding.ws when wsdlElement is not of 'Binding' form
[ https://issues.apache.org/jira/browse/TUSCANY-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590878#action_12590878 ] ant elder commented on TUSCANY-2241: Many thanks for the fix, it looks ok to me but some of our existing tests have EndpointReferences where its actually invalid so with this fix applied there are test failures (try building binding-ws-axis2 with this fix applied to find them). Could you also supply a patch to fix those? EndpointReference in binding.ws when wsdlElement is not of 'Binding' form - Key: TUSCANY-2241 URL: https://issues.apache.org/jira/browse/TUSCANY-2241 Project: Tuscany Issue Type: Bug Components: Java SCA Verification Tests Affects Versions: Java-SCA-1.2, Java-SCA-Next Reporter: Vamsavardhana Reddy Assignee: Vamsavardhana Reddy Fix For: Java-SCA-Next Attachments: TUSCANY-2241.patch Web Service Binding Specification v1.0 - Sec 2.1 - Lines 61 to 65: 61 • /binding.ws/wsa:EndpointReference - optional WS-Addressing [6] EndpointReference 62 that specifies the endpoint for the service or reference. When this element is present along 63 with the wsdlElement attribute on the parent element, the wsdlElement attribute value MUST 64 be of the 'Binding' form as specified above, i.e. WSDL-namespace- 65 URI#wsdl.binding(binding-name). I notice that when an EndpointReference is specified inside binding.ws along with a wsdlElement which is not of 'Binding' form, no warning or error is generated. -- 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] Closed: (TUSCANY-2246) Update DefaultContextFactoryExtensionPoint to use ServiceDiscovery
[ https://issues.apache.org/jira/browse/TUSCANY-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2246. -- Resolution: Fixed Applied in r650101, thanks for the code Greg. Update DefaultContextFactoryExtensionPoint to use ServiceDiscovery -- Key: TUSCANY-2246 URL: https://issues.apache.org/jira/browse/TUSCANY-2246 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Reporter: Greg Dritschler Attachments: tuscany-2246.patch Change DefaultContextFactoryExtensionPoint to use ServiceDiscovery to find implementation of context factory. -- 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]
Fwd: Using Tuscany Java SDO with EMF 2.4
Anyone likely to have any time to take a look at this? If its possible to do
something to fix this it would be good to try to get it done in the 1.1.1
release.
...ant
-- Forwarded message --
From: Eric S Rose [EMAIL PROTECTED]
Date: Fri, Apr 18, 2008 at 5:03 PM
Subject: Re: Using Tuscany Java SDO with EMF 2.4
To: [EMAIL PROTECTED]
Frank,
Sorry for the delay in getting back to you, I got busy with some other stuff
that had to be done yesterday.
I've been debugging the problem all morning, and it seems to come down to a
NullPointerException from eStaticClass() in ReferenceImpl. Here's the code
where I'm seeing the exception:
*protected* EClass eStaticClass()
{
* return* SDOPackage.*eINSTANCE*.getReference();
}
SDOPackage.eINSTANCE is null, so SDOPackageImpl.init() is returning null for
some reason. I'm not sure that really answers your question, but I hope it's
helpful.
Thanks,
Eric
[image: Inactive hide details for Frank Budinsky ---04/15/2008 04:28:04
PM---Eric, Theoretically EMF 2.4 should work, because it's supp]Frank
Budinsky ---04/15/2008 04:28:04 PM---Eric, Theoretically EMF 2.4 should
work, because it's supposed to be backward
From:
Frank Budinsky [EMAIL PROTECTED]
To:
[EMAIL PROTECTED]
Date:
04/15/2008 04:28 PM
Subject:
Re: Using Tuscany Java SDO with EMF 2.4
--
Eric,
Theoretically EMF 2.4 should work, because it's supposed to be backward
compatible. Have you tracked down exactly what class is missing and why?
Frank.
Eric S Rose [EMAIL PROTECTED] wrote on 04/15/2008 03:36:49 PM:
David,
EMF 2.2.3 is what I've been using also up until this point. My code
is integrating with a project that's already using EMF 2.4, so I
need to align with the larger project. Based on what I've seen so
far, it doesn't look like that's a possibility.
Thanks,
Eric
[image removed] David Adcox ---04/15/2008 03:10:11 PM---The latest
version I've been using is 2.2.3 - which I believe is what is
currently specified in the
[image removed]
From:
[image removed]
David Adcox [EMAIL PROTECTED]
[image removed]
To:
[image removed]
[EMAIL PROTECTED]
[image removed]
Date:
[image removed]
04/15/2008 03:10 PM
[image removed]
Subject:
[image removed]
Re: Using Tuscany Java SDO with EMF 2.4
The latest version I've been using is 2.2.3 - which I believe is what
is currently specified in the pom files. Is there a reason you need
to use a newer version of EMF?
On Tue, Apr 15, 2008 at 2:09 PM, Eric S Rose [EMAIL PROTECTED] wrote:
Hello all,
Has anyone had any success running Java SDO with EMF 2.4? I'm
running into
a NoClassDefFoundError on SDOUtil.createHelperContext(). I've seen
this on
both the 1.0 and 1.1 releases.
Thanks,
Eric
-
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]
SDO 1.1.1 RC1
There's now a preview SDO 1.1.1 release available at http://people.apache.org/~antelder/tuscany/sdo/1.1.1-RC1/. The only difference between this and the just released 1.1 release is the fix http://issues.apache.org/jira/browse/TUSCANY-2240. I'll leave this a little while before calling a vote to give time for reviews and also would be good if possible to also get a fix for using EMF 2.4 as a user has asked about that. ...ant
[jira] Updated: (TUSCANY-1997) Axis binding does not allow external configuration to increase the number of the maximum connections opened.
[
https://issues.apache.org/jira/browse/TUSCANY-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder updated TUSCANY-1997:
---
Attachment: tuscany-binding-ws-axis2-1.0-T1997-T1893.jar
Attached tuscany-binding-ws-axis2-1.0-T1997-T1893.jar which contains the
changes for TUSCANY-1997 and TUSCANY-1893 back-ported to the 1.0 code. The diff
to the base 1.0 code is the following:
Index:
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
===
---
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
(revision 630862)
+++
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2BindingInvoker.java
(working copy)
@@ -61,6 +61,7 @@
public static final QName CALLBACK_REFERENCE_REFPARM_QN = new
QName(Constants.SCA10_TUSCANY_NS, CallbackReference);
public static final QName CALLBACK_ID_REFPARM_QN = new
QName(Constants.SCA10_TUSCANY_NS, CallbackID);
public static final QName CONVERSATION_ID_REFPARM_QN = new
QName(Constants.SCA10_TUSCANY_NS, ConversationID);
+public static long GLOBAL_AXIS_TIMEOUT = 12L;
public Axis2BindingInvoker(ServiceClient serviceClient,
QName wsdlOperationName,
@@ -97,7 +98,7 @@
// ensure connections are tracked so that they can be closed by the
reference binding
MessageContext requestMC =
operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
-requestMC.getOptions().setTimeOutInMilliSeconds(12L);
+requestMC.getOptions().setTimeOutInMilliSeconds(GLOBAL_AXIS_TIMEOUT);
operationClient.execute(true);
Index:
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2OneWayBindingInvoker.java
===
---
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2OneWayBindingInvoker.java
(revision 630862)
+++
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2OneWayBindingInvoker.java
(working copy)
@@ -48,7 +48,11 @@
// ensure connections are tracked so that they can be closed by the
reference binding
MessageContext requestMC =
operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
-requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
+//requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
+Options opt = requestMC.getOptions();
+opt.setProperty(HTTPConstants.REUSE_HTTP_CLIENT, Boolean.TRUE);
+opt.setUseSeparateListener(true);
+opt.setProperty(HTTPConstants.AUTO_RELEASE_CONNECTION,Boolean.TRUE);
operationClient.execute(false);
Index:
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceClient.java
===
---
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceClient.java
(revision 630862)
+++
src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceClient.java
(working copy)
@@ -52,8 +52,10 @@
import org.apache.axis2.description.WSDL11ToAxisServiceBuilder;
import org.apache.axis2.description.WSDL2Constants;
import org.apache.axis2.transport.http.HTTPConstants;
+import org.apache.axis2.util.threadpool.ThreadPool;
import org.apache.commons.httpclient.HttpClient;
import org.apache.commons.httpclient.MultiThreadedHttpConnectionManager;
+import org.apache.commons.httpclient.params.HttpConnectionManagerParams;
import org.apache.tuscany.sca.assembly.AbstractContract;
import org.apache.tuscany.sca.binding.ws.WebServiceBinding;
import org.apache.tuscany.sca.contribution.Contribution;
@@ -78,6 +80,8 @@
private ServiceClient serviceClient;
private static final QName SOAP12_INTENT = new
QName(http://www.osoa.org/xmlns/sca/1.0;, soap12);
+public static int httpMaxConnections = 2;
+
public Axis2ServiceClient(RuntimeComponent component,
AbstractContract contract,
WebServiceBinding wsBinding,
@@ -108,7 +112,26 @@
AxisService axisService =
createClientSideAxisService(wsdlDefinition, serviceQName,
portName, new Options());
+HttpClient httpClient = (HttpClient)
configContext.getProperty(HTTPConstants.CACHED_HTTP_CLIENT);
+if (httpClient == null)
+{
+MultiThreadedHttpConnectionManager connectionManager = new
MultiThreadedHttpConnectionManager();
+HttpConnectionManagerParams connectionManagerParams = new
HttpConnectionManagerParams();
+
connectionManagerParams.setDefaultMaxConnectionsPerHost(httpMaxConnections
Re: [jira] Resolved: (TUSCANY-2240) Creation of SDO object out of XML (read from an JMS message) is taking too long
This seems like quite a useful fix given the problems it seemed to be causing with the JMS binding, how about an SDO 1.1.1 maintenance release? ...ant On Fri, Apr 18, 2008 at 6:56 PM, Raymond Feng (JIRA) tuscany-dev@ws.apache.org wrote: [ https://issues.apache.org/jira/browse/TUSCANY-2240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] Raymond Feng resolved TUSCANY-2240. --- Resolution: Fixed Fixed in trunk under r649628 Creation of SDO object out of XML (read from an JMS message) is taking too long --- Key: TUSCANY-2240 URL: https://issues.apache.org/jira/browse/TUSCANY-2240 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-1.0, Java-SCA-1.1 Environment: Windows XP Pro SP2, JDK 1.6_06, SCA 1.1, SDO 1.1 Reporter: Ph.Konradi Assignee: Raymond Feng After I've switched from JMS messages containing Objects to XML (migrated from Tuscany 1.0.1 to 1.1) my application needs around 7 sec to call my service. Before it reacted instantly. I've debugged into to see where the problem is and saw that receiving of the JMS message works still instantly but the processing takes pretty long. Below in the stack trace one can see that a new http connection is opened (???) and I guess that's responsible for the delay. Any explanation for this behaviour? What am I doing wrong? The service's method I'm calling has an argument of complex type. Thanks, Philipp Daemon Thread [ActiveMQ Session Task] (Suspended) PlainSocketImpl.socketConnect(InetAddress, int, int) line: not available [native method] PlainSocketImpl.doConnect(InetAddress, int, int) line: 333 PlainSocketImpl.connectToAddress(InetAddress, int, int) line: 195 PlainSocketImpl.connect(SocketAddress, int) line: 182 Socket.connect(SocketAddress, int) line: 519 Socket.connect(SocketAddress) line: 469 HttpClient(NetworkClient).doConnect(String, int) line: 157 HttpClient.openServer(String, int) line: 394 HttpClient.openServer() line: 529 HttpClient.init(URL, Proxy, int) line: 233 HttpClient.New(URL, Proxy, int, boolean) line: 306 HttpClient.New(URL, Proxy, int) line: 323 HttpURLConnection.getNewHttpClient(URL, Proxy, int) line: 788 HttpURLConnection.plainConnect() line: 729 HttpURLConnection.connect() line: 654 HttpURLConnection.getInputStream() line: 977 URIConverterImpl.createURLInputStream(URI) line: 566 URIConverterImpl.createInputStream(URI) line: 453 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getPackageForURI(String) line: 2294 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).getFactoryForPrefix(String) line: 2188 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createObjectByType(String, String, boolean) line: 1145 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).createTopObject(String, String) line: 1247 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).processElement(String, String, String) line: 883 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, String, String) line: 866 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler(XMLHandler).startElement(String, String, String, Attributes) line: 627 SDOXMLResourceImpl$SDOXMLLoadImpl$XmlHandler.startElement(String, String, String, Attributes) line: 401 StAX2SAXAdapter.handleStartElement(XMLStreamReader, ContentHandler) line: 162 StAX2SAXAdapter.parse(XMLStreamReader, ContentHandler) line: 111 SDOXMLResourceImpl$SDOXMLLoadImpl$1.run() line: 472 AccessController.doPrivileged(PrivilegedExceptionActionT) line: not available [native method] SDOXMLResourceImpl$SDOXMLLoadImpl.load(XMLResource, XMLStreamReader, Map) line: 470 SDOXMLResourceImpl.load(XMLStreamReader, Map) line: 598 XMLDocumentImpl.load(XMLStreamReader, Map) line: 248 XMLStreamHelperImpl.loadDocument(XMLStreamReader, Map) line: 136 XMLStreamHelperImpl.loadObject(XMLStreamReader, Map) line: 98 XMLStreamHelperImpl.loadObject(XMLStreamReader) line: 102 XMLStreamReader2DataObject.transform(XMLStreamReader, TransformationContext) line: 49 XMLStreamReader2DataObject.transform(Object, TransformationContext) line: 34 DefaultTransformerExtensionPoint$LazyPullTransformer.transform(Object, TransformationContext) line: 199 MediatorImpl.mediate(Object, DataType, DataType, MapString,Object) line: 73 Input2InputTransformer.transform(Object[], TransformationContext) line: 179 Input2InputTransformer.transform(Object, TransformationContext) line: 43
[jira] Reopened: (TUSCANY-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reopened TUSCANY-88: -- Reopened see user list thread - http://apache.markmail.org/message/25in5vox5if6xbw2 Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-M2 Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-88: - Attachment: translate.zip Example of using xml component to invoke an rpc-encoded WS Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-M2 Attachments: translate.zip Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-88: - Fix Version/s: (was: Java-SCA-M2) Java-SCA-Next Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-Next Attachments: translate.zip Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-88) Support invoking simple RPC/encoded Web services
[
https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590361#action_12590361
]
ant elder commented on TUSCANY-88:
--
As a start we can support RPC-encoded by using XML components, but doing that
raises some issues:
- Axis2 no longer supports creating a ServiceClient from RPC-encoded WSDL
throwing an exception when it finds use=encoded. Could try to get that
changed in Axis2 as its only the Axis2 data bindings that should care.
- we've no facility to set the SOAP Action header other than from WSDL. Could
add a Tuscany specific attribute to binding.ws and/or support the jaxws
@Action attribute
- Tuscany script components no longer support WS references. Did work at one
point, i'd really like to be able to do (yes yes, i know inline scripts make
some people scowl):
component name=TranslationComponent
tuscany:implementation.script language=js![CDATA[
function translate(from, to, text) {
var resp = translator.translate(
tem:Translate xmlns:tem=http://tempuri.org/;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/;
lang xsi:type=xsd:string { from }_{ to } /lang
text xsi:type=xsd:string{ text } /text
/tem:Translate;
return resp..TranslateResult
}
]]/tuscany:implementation.script
reference name=translator
binding.ws
wsdlElement=http://tempuri.org/#wsdl.port(Translator/TranslatorSoap) /
/reference
/component
Support invoking simple RPC/encoded Web services
Key: TUSCANY-88
URL: https://issues.apache.org/jira/browse/TUSCANY-88
Project: Tuscany
Issue Type: Improvement
Components: Java SCA Axis Binding Extension
Reporter: ant elder
Priority: Minor
Fix For: Java-SCA-M2
Currently externalServices using the WS binding don't support invoking RPC
encoded services. To support RPC/encoded properly would be a lot of work and
as its not WS-I compliant probably isn't a high priority, however as there
are a lot of existing RPC/encoded services out there it would be good if we
had some limitted support for the subset of RPC/encoded thats easy to do. It
would great if at least it worked for trivial services like xmethods
stockquote. Thats WS 101 and a lot of people will likely try using that when
they first look at Tuscany. It would create a much better first impression if
that works rather than giving the obscure exception you get if you try it
today.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-88) Support invoking simple RPC/encoded Web services
[ https://issues.apache.org/jira/browse/TUSCANY-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590363#action_12590363 ] ant elder commented on TUSCANY-88: -- - also Tuscany wsdl parsing code was complaining about the wsdl message parts type using http://www.w3.org/2001/XMLSchema, i've not investigated what that was about Support invoking simple RPC/encoded Web services Key: TUSCANY-88 URL: https://issues.apache.org/jira/browse/TUSCANY-88 Project: Tuscany Issue Type: Improvement Components: Java SCA Axis Binding Extension Reporter: ant elder Priority: Minor Fix For: Java-SCA-M2 Currently externalServices using the WS binding don't support invoking RPC encoded services. To support RPC/encoded properly would be a lot of work and as its not WS-I compliant probably isn't a high priority, however as there are a lot of existing RPC/encoded services out there it would be good if we had some limitted support for the subset of RPC/encoded thats easy to do. It would great if at least it worked for trivial services like xmethods stockquote. Thats WS 101 and a lot of people will likely try using that when they first look at Tuscany. It would create a much better first impression if that works rather than giving the obscure exception you get if you try it today. -- 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] Closed: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2165. -- Resolution: Fixed Patches applied, thanks for the fix! Java runtime should inject service references to field with common name in absence of @Reference - Key: TUSCANY-2165 URL: https://issues.apache.org/jira/browse/TUSCANY-2165 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch The Java AnnotationsAPIs specification Lines 1407, 1408, 1409, 1410 ... * References may also be injected via public setter methods even when the * @Reference annotation is not present. However, the @Reference * annotation must be used in order to inject a reference onto a non public * field. In the case where there is no @Reference annotation, the name of * the reference is the same as the name of the field or setter. The vTest: org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 demonstrates this issue -- 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] Closed: (TUSCANY-2218) Endpoint URI resolution precedence for binding.ws reference is incorrect
[
https://issues.apache.org/jira/browse/TUSCANY-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-2218.
--
Resolution: Fixed
Applied, thanks for the fixes!
Endpoint URI resolution precedence for binding.ws reference is incorrect
Key: TUSCANY-2218
URL: https://issues.apache.org/jira/browse/TUSCANY-2218
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-1.0
Reporter: Lou Amodeo
Fix For: Java-SCA-Next
Attachments: TUSCANY-2218-testcase.patch, TUSCANY-2218.patch
I believe the order of Endpoint URI resolution precedence is incorrect for
binding.ws references. What I am seeing is that the uri attribute is taking
precedence over the location specified in the WSDL. The spec indicates that
the endpoint in the WSDL should take highest precedence.
Web Service Binding Spec
2.1.1 Endpoint URI resolution
71 The rules for resolving the URI at which an SCA service is hosted, or SCA
reference targets,
72 when used with binding.ws (in precedence order) are:
73 1. The URIs in the endpoint(s) of the referenced WSDL
74 or
75 The URI specified by the wsa:Address element of the wsa:EndpointReference,
76 2. The explicitly stated URI in the uri attribute of the binding.ws
element, which may be
77 relative,
78 3. The implicit URI as defined by the Assembly specification
In Axis2ServiceClient getPortLocation looks for uri first and returns it
ahead of wsdl location if present.
protected EndpointReference getPortLocationEPR(WebServiceBinding binding) {
String ep = binding.getURI(); WAS specific
if (ep == null binding.getPort() != null) {
List? wsdlPortExtensions =
binding.getPort().getExtensibilityElements();
for (final Object extension : wsdlPortExtensions) {
if (extension instanceof SOAPAddress) {
ep = ((SOAPAddress)extension).getLocationURI();
break;
}
if (extension instanceof SOAP12Address) {
SOAP12Address address = (SOAP12Address)extension;
ep = address.getLocationURI();
break;
}
}
}
return ep == null || .equals(ep) ? null : new EndpointReference(ep);
}
--
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: Mirror of release artifacts
I think thats a separate issue but if its the reason we stopped using the mirrors then i think we need to start using them again. It may not be clearly documented yet but i think the current ASF/incubator policy is that releases MUST be distributed via the mirrors. ...ant On Tue, Apr 15, 2008 at 5:20 PM, Luciano Resende [EMAIL PROTECTED] wrote: How do we get stats from the number of downloads when using mirros ? On Tue, Apr 15, 2008 at 7:21 AM, Simon Laws [EMAIL PROTECTED] wrote: On Tue, Apr 15, 2008 at 2:20 PM, ant elder [EMAIL PROTECTED] wrote: WIth the changes to how the Incubator release artifacts get distributed via mirrors now I understood we were supposed to have our website download pages use a script accessing the mirrors. Looking back at the SCA 1.1 download page change history it did at one point do that (r17) but then it got changed back to the non-script approach. Anyone know why? Are there some issues with using the script/mirrors? ...ant Hi Distribution mirroring is part of incubator release best practice [1] so we should try and put this back in if we can. Happy to help to make this work if anyone can identify what the original issue was. If we can't identify a specific issue I would go for going back to the links from r17. Regards Simon [1] http://incubator.apache.org/guides/releasemanagement.html#distribution-mirroring -- 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]
Re: Apache Tuscany committer status reaffirmation
No problem, I shall add your name to the list. We do actually review every commit so it is fine for you to directly commit instead of raising patches, you could post a note to the dev list if there's ones you're particularly nervous about. Thats actually easier as then no one needs to do the work to apply the patch, but its no biggie so if you're more comfortable using patches for now thats fine too. ...ant On Tue, Apr 15, 2008 at 5:55 PM, Brent Daniel [EMAIL PROTECTED] wrote: Ant, My preference would be to remain a committer. However, I am not sure when my schedule will allow for a deeper involvement. Lately, I have been submitting fixes in patches rather than committing directly. With a small number of fixes this isn't a big deal, and it ensures that at least one person reviews the fix, whereas a simple commit could be overlooked. I can certainly continue to work like this without committership, but would prefer to keep the ability to commit for when I am able to spend more time on the Tuscany code base. Brent On Sat, Apr 12, 2008 at 2:23 AM, ant elder [EMAIL PROTECTED] wrote: You are receiving this email because you are listed as an Apache Tuscany committer. Tuscany is looking to graduate in the near future and following Apache Incubator practice is cleaning up the committer list. Tuscany has 35 committers listed on the status file some of those have left and some were just listed there when the original proposal was accepted and have never even once committed anything. We've decided any one who has interacted with the project within the last 12 months will automatically remain a committer, anyone else will need to reply to this email to retain their committer status. These are the committers who've participated in the last 12 months and will automatically retain their committer status: adrianocrestani Adriano Crestani amita Amita Vadhavkar ajborleyAndrew Borley antelderAnt Elder bjohnsonBrady Johnson dkulp Dan Kulp frankb Frank Budinsky fuhwei Fuhwei Lwo giorgio Giorgio Zoppi isilval Ignacio Silva-Lepe jsdelfino Jean-Sebastien Delfino kelvingoodson Kelvin Goodson kwilliams Kevin Williams lresendeLuciano Resende mcombellack Mark Combellack myoder Michael Yoder edwardsmj Mike Edwards nashSimon Nash rsivaramRajini Sivaram rfeng Raymond Feng robbinspg Pete Robbins slaws Simon Laws svkrish Venkata Krishnan So, if you are not on that list but would like to retain your Tuscany committer status please reply to this email and let us know about how you would like to be involved with Tuscany. Also, if you are on that list but no longer want to stay a committer once Tuscany graduates you can also reply to this email and we'll remove your name. Many thanks, The Apache Tuscany PPMC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New Eclipse update site in SCA 1.2 release
On Tue, Apr 15, 2008 at 9:29 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: In the 1.2 release candidate we've now an Eclipse update site. I can't find any mention of this happening anywhere, do we have any doc at all on it happening somewhere that I missed? ...ant We've been referring to it under different names, mostly 'plugin', as the update site is how Eclipse plugins are installed. A quick search gave me the following, but there's probably more: http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Release+-+Java+SCA+1.2 http://issues.apache.org/jira/browse/TUSCANY-2119 http://issues.apache.org/jira/browse/TUSCANY-2142 http://issues.apache.org/jira/browse/TUSCANY-2157 http://issues.apache.org/jira/browse/TUSCANY-2166 http://issues.apache.org/jira/browse/TUSCANY-2175 http://issues.apache.org/jira/browse/TUSCANY-2179 http://marc.info/?l=tuscany-devm=120650695831123 http://marc.info/?l=tuscany-devm=120656320414940 http://marc.info/?l=tuscany-devm=120694778015549 http://marc.info/?l=tuscany-devm=120699934118018 http://marc.info/?l=tuscany-devm=120613784003868 Sure but none of those actually mention having a new update site. All I'm saying is that IMHO something like this which is a whole new distribution artifact that gets its own mention in the release votes it would have been appropriate to have something like a hey I've made a new eclipse update site and added it to the 1.2 release type email to the dev list. ...ant
Re: distribution target-last-successful copies
Ok I've removed these in r648618. From all the comments it didn't seem like the copies these were providing were accessible now anyway. If we do need something like this on the continuum builds i'd be happy to help make a new build profile that the continuum builds could use. ...ant On Fri, Apr 11, 2008 at 9:31 AM, ant elder [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 9:22 AM, ant elder [EMAIL PROTECTED] wrote: The current distribution build copies the binary artifacts to the target-last-successful folder which takes about 130Meg. I'm guessing this is something to do with the continuum builds but does anyone know for sure? If so could we change it so it only happens on the continuum machine (have the continuum build use a specific profile?), or if not can i just delete the copy task? ...ant OK maybe if I ask a different way... It looks like the target-last-successful copies aren't actually required anymore so unless i hear otherwise I'll remove the copy from the distribution pom.xml. ...ant
[NOTICE] Wang Feng voted as Tuscany committer
The Tuscany PPMC and Incubator PMC have voted for Wang Feng to become a Tuscany committer. Congratulations and welcome Wang Feng! ...ant
[ANNOUNCE] Apache Tuscany Java SDO 1.1 released
The Apache Tuscany team are pleased to announce the 1.1-incubating release of the Java SDO project. Service Data Objects (SDO) are designed to simplify and unify the way in which applications handle data. Using SDO, application programmers can uniformly access and manipulate data from heterogeneous data sources, including relational databases, XML data sources, Web services, and enterprise information systems. Tuscany SDO provides an implementation of the SDO 2.1 specification, this 1.1 release includes several new features and improvements over the 1.0 release such as: - the ability to generate SDO test classes using the maven-sdo-plugin - support for custom data binding of DataObjects in a Swing UI - Using the HelperContext for scope in the Tuscany API - improved diagnostics along with many bug fixes. See the RELEASE_NOTES for full details. For more information and to download the SDO 1.1 release please go to: http://incubator.apache.org/tuscany/sdo-java-releases.html Apache Tuscany welcomes your help. Any contribution, including code, testing, improving the documentation, or bug reporting is always appreciated. For more information on how to get involved in Apache Tuscany visit the website at: http://incubator.apache.org/tuscany. Thank you for your interest in Apache Tuscany! The Apache Tuscany Team. --- Tuscany is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Web services PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SCA 2.0, was Re: Next SCA release
On Tue, Apr 15, 2008 at 8:29 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: snip After a week away I thought we'd have a clearer picture on this. Yesterday I put together some improvements of the admin app and some of the tutorial modules. I must say I'm a little lost now as to where I should commit that stuff. Thats easy - to trunk. Development happens in the trunk. ...ant
Mirror of release artifacts
WIth the changes to how the Incubator release artifacts get distributed via mirrors now I understood we were supposed to have our website download pages use a script accessing the mirrors. Looking back at the SCA 1.1 download page change history it did at one point do that (r17) but then it got changed back to the non-script approach. Anyone know why? Are there some issues with using the script/mirrors? ...ant
[jira] Commented: (TUSCANY-2199) Tests for @Reference annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589077#action_12589077 ] ant elder commented on TUSCANY-2199: Thanks for the patch Gilbert. Unfortunately it wont apply correctly for me complaining that some characters in the patch can't be mapped to Cp1252 encoding. I suspect an SVN config mismatch, could you check your SVN client config matches whats used by Tuscany and reattach a patch based on that? There's been some email on the dev list recently about how to do this, see: http://apache.markmail.org/message/kydc2535whfhass3 Tests for @Reference annotation --- Key: TUSCANY-2199 URL: https://issues.apache.org/jira/browse/TUSCANY-2199 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: TUSCANY-2199.multiplicity.test.patch Placeholder for tracking additions to the @Reference vtests -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2165) Java runtime should inject service references to field with common name in absence of @Reference
[ https://issues.apache.org/jira/browse/TUSCANY-2165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12589106#action_12589106 ] ant elder commented on TUSCANY-2165: Thanks for the lates patch, I've applied it locally but now running the test i get a failure: Tests run: 7, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 1.546 sec FAILURE! atReference2(org.apache.tuscany.sca.vtest.javaapi.annotations.reference.ReferenceAnnotationTestCase) Time elapsed: 0 sec FAILURE! java.lang.AssertionError: getB5Name expected to fail with NPE at org.junit.Assert.fail(Assert.java:69) at org.apache.tuscany.sca.vtest.javaapi.annotations.reference.ReferenceAnnotationTestCase.atReference2(ReferenceAnnotationTestCase.java:122) Is that expected? Java runtime should inject service references to field with common name in absence of @Reference - Key: TUSCANY-2165 URL: https://issues.apache.org/jira/browse/TUSCANY-2165 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Kevin Williams Priority: Minor Attachments: TUSCANY-2165-revised-test.patch, TUSCANY-2165.patch The Java AnnotationsAPIs specification Lines 1407, 1408, 1409, 1410 ... * References may also be injected via public setter methods even when the * @Reference annotation is not present. However, the @Reference * annotation must be used in order to inject a reference onto a non public * field. In the case where there is no @Reference annotation, the name of * the reference is the same as the name of the field or setter. The vTest: org.apache.tuscany.sca.vtest.javaapi.ReferenceAnnotationTestCase.atReference2 demonstrates this issue -- 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: [VOTE] Release Tuscany Java SCA 1.2-incubating (RC4)
On Tue, Apr 15, 2008 at 3:19 PM, Mike Edwards [EMAIL PROTECTED] wrote: Luciano Resende wrote: Please review and vote on the 1.2 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC4/ This includes the signed binary and source distributions, the RAT report, and the Maven staging repository. The eclipse updatesite for the Tuscany Eclipse plugins is available at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/updatesite/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC4/updatesite/ The release tag is available at : http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.2-RC4/ Looks OK to me, here is my +1. Luciano, Sorry to spoil the party, but I run into a problem running the Tutorial following the instructions in the README. So I install the apache-tuscany-sca-1.2-incubating.zip and go to the /tutorial directory and follow the instructions in the README, starting the domain manager: cd domain java -jar ../../modules/tuscany-node2-launcher-1.2-incubating.jar domain This seems to run well (no errors reported) I view the SCA Manager application at: http://localhost:9990/ui/cloud/ ...the various nodes appear as they should. I try to start the StoreNode, as recommended in the README, but when I select the Start button, I get an error, with an exception trace in the command window running the SCA server, which starts with: 15-Apr-2008 15:09:58 org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet /processes/* threw exception java.lang.LinkageError: JAXB 2.0 API is being loaded from the bootstrap classloader, but this RI (from jar:file:/C:/Tuscany_1_2/tuscany-sca-1.2-incubating/lib/j axb-impl-2.1.6.jar!/com/sun/xml/bind/v2/model/impl/ModelBuilder.class) needs 2.1 API. Use the endorsed directory mechanism to place jaxb-api.jar in the bootstrap classloader. (See http://java.sun.com/j2se/1.5.0/docs/guide/standards/) ...followed by the usual long exception trace Sounds like a configuration error, with the wrong level of JAXB libraries being used. Is this just me - or is this a problem with the build? Yours, Mike. I've just run through what you have described and it works ok for me. Could it be a java level thing, which JDK are you using? I have: java -version java version 1.5.0_10 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode) ...ant
[jira] Closed: (TUSCANY-2195) Test cases for ComponentContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2195. -- Resolution: Fixed Applied, many thanks for the code Test cases for ComponentContext API --- Key: TUSCANY-2195 URL: https://issues.apache.org/jira/browse/TUSCANY-2195 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: ComponentContext.zip, ComponentContext20080404.zip, ComponentContextJira2195.patch Contributions for ComponentContext API testing can be attached here -- 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] Closed: (TUSCANY-2199) Tests for @Reference annotation
[ https://issues.apache.org/jira/browse/TUSCANY-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2199. -- Resolution: Fixed So it is, in r644938. Tests for @Reference annotation --- Key: TUSCANY-2199 URL: https://issues.apache.org/jira/browse/TUSCANY-2199 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: TUSCANY-2199.multiplicity.test.patch Placeholder for tracking additions to the @Reference vtests -- 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: Apache Tuscany committer status reaffirmation
Thanks for replying Rajith and thanks for your participation, our JMS binding is still based on the code you wrote. Be great to get support for qpid/amqp sometime so when ever you do get time just say and i'm sure there'll be no barriers to your rejoining. ...ant On Mon, Apr 14, 2008 at 5:31 PM, Rajith Attapattu [EMAIL PROTECTED] wrote: Ant, I have been inactive for the last 12 months or so. The Qpid project is taking so much of my time and judging by the past 12 months I think I will be unable to devote enough quality time to deserve comittership. So I would appreciate if you can revoke it. I do have a plan to jump back in and update the JMS binding (if someone hasn't done yet) and to do an AMQP binding. Not sure when it is, but when that happens perhaps I may do enough work to earn comittership again. But until that happens please take me off the list. I wish the Tuscany community all the best and hopefully will start working again with you guys. Regards, Rajith On Sat, Apr 12, 2008 at 5:23 AM, ant elder [EMAIL PROTECTED] wrote: You are receiving this email because you are listed as an Apache Tuscany committer. Tuscany is looking to graduate in the near future and following Apache Incubator practice is cleaning up the committer list. Tuscany has 35 committers listed on the status file some of those have left and some were just listed there when the original proposal was accepted and have never even once committed anything. We've decided any one who has interacted with the project within the last 12 months will automatically remain a committer, anyone else will need to reply to this email to retain their committer status. These are the committers who've participated in the last 12 months and will automatically retain their committer status: adrianocrestani Adriano Crestani amita Amita Vadhavkar ajborleyAndrew Borley antelderAnt Elder bjohnsonBrady Johnson dkulp Dan Kulp frankb Frank Budinsky fuhwei Fuhwei Lwo giorgio Giorgio Zoppi isilval Ignacio Silva-Lepe jsdelfino Jean-Sebastien Delfino kelvingoodson Kelvin Goodson kwilliams Kevin Williams lresendeLuciano Resende mcombellack Mark Combellack myoder Michael Yoder edwardsmj Mike Edwards nashSimon Nash rsivaramRajini Sivaram rfeng Raymond Feng robbinspg Pete Robbins slaws Simon Laws svkrish Venkata Krishnan So, if you are not on that list but would like to retain your Tuscany committer status please reply to this email and let us know about how you would like to be involved with Tuscany. Also, if you are on that list but no longer want to stay a committer once Tuscany graduates you can also reply to this email and we'll remove your name. Many thanks, The Apache Tuscany PPMC -- Regards, Rajith Attapattu http://rajith.2rlabs.com/
Re: [VOTE] Release Tuscany Java SCA 1.2-incubating (RC4)
+1 Samples run, src and samples build from the staging repo, signatures verify, legal files look ok, looks good to go to me. ...ant On Mon, Apr 14, 2008 at 11:06 AM, Luciano Resende [EMAIL PROTECTED] wrote: Please review and vote on the 1.2 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/ This includes the signed binary and source distributions, the RAT report, and the Maven staging repository. The eclipse updatesite for the Tuscany Eclipse plugins is available at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/updatesite/ The release tag is available at : http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.2-RC4/ Looks OK to me, here is my +1. -- 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: [(GSoC] Time to rank the Google Summer of Code Proposals
On Mon, Apr 14, 2008 at 3:51 PM, Simon Laws [EMAIL PROTECTED] wrote: On Sat, Apr 12, 2008 at 1:06 PM, Giorgio Zoppi [EMAIL PROTECTED] wrote: For map/hadoop if you need a part time mentor till 30 June, ask me. After that time I'll travel around Spain all summer. -- Ciao, Giorgio. --- Giorgio Zoppi [EMAIL PROTECTED] Hi Luciano I've just signed up as a mentor (it says my application is pending). Anything else I need to do while I'm waiting for that to come through? Simon You need to send an email to [EMAIL PROTECTED] saying you've registered as a mentor, the gmail address you used and your apache id. ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [RESULT] [VOTE] SDO 1.1 release
And now approved by the IPMC: http://apache.markmail.org/message/q2f4ax32c65vse6z ...ant On Mon, Apr 7, 2008 at 12:00 AM, ant elder [EMAIL PROTECTED] wrote: Passed with +1s from Adriano, Raymond and me. ...ant On Thu, Apr 3, 2008 at 7:05 PM, ant elder [EMAIL PROTECTED] wrote: Please review and vote on the SDO 1.1 release RC4a artifacts at http://people.apache.org/~antelder/tuscany/sdo/1.1-rc4ahttp://people.apache.org/%7Eantelder/tuscany/sdo/1.1-rc3/ The tag for the release is at: https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1/ KEYS file is at: https://svn.apache.org/repos/asf/incubator/tuscany/KEYS Many thanks to Adriano, Raymond, and Sebb for all their help reviewing and fixing the previous RCs. This one looks good so +1 from me! ...ant
Apache Tuscany committer status reaffirmation
You are receiving this email because you are listed as an Apache Tuscany committer. Tuscany is looking to graduate in the near future and following Apache Incubator practice is cleaning up the committer list. Tuscany has 35 committers listed on the status file some of those have left and some were just listed there when the original proposal was accepted and have never even once committed anything. We've decided any one who has interacted with the project within the last 12 months will automatically remain a committer, anyone else will need to reply to this email to retain their committer status. These are the committers who've participated in the last 12 months and will automatically retain their committer status: adrianocrestani Adriano Crestani amita Amita Vadhavkar ajborleyAndrew Borley antelderAnt Elder bjohnsonBrady Johnson dkulp Dan Kulp frankb Frank Budinsky fuhwei Fuhwei Lwo giorgio Giorgio Zoppi isilval Ignacio Silva-Lepe jsdelfino Jean-Sebastien Delfino kelvingoodson Kelvin Goodson kwilliams Kevin Williams lresendeLuciano Resende mcombellack Mark Combellack myoder Michael Yoder edwardsmj Mike Edwards nashSimon Nash rsivaramRajini Sivaram rfeng Raymond Feng robbinspg Pete Robbins slaws Simon Laws svkrish Venkata Krishnan So, if you are not on that list but would like to retain your Tuscany committer status please reply to this email and let us know about how you would like to be involved with Tuscany. Also, if you are on that list but no longer want to stay a committer once Tuscany graduates you can also reply to this email and we'll remove your name. Many thanks, The Apache Tuscany PPMC - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [(GSoC] Time to rank the Google Summer of Code Proposals
On Wed, Apr 9, 2008 at 4:56 AM, Luciano Resende [EMAIL PROTECTED] wrote: For those who had volunteered as mentors for GSoC 2008, it's time for us to rank the proposals. In order to facilitate our jobs, I went trough the list of proposals, and posted links to the Tuscany related ones in the following wiki page [1]. The complete list is available on the GSoC mentor dashboard [2].Please take a look and help us rank the applications. Note that applications that we would never consider (no effort, no details, cut and paste of original project description etc.) can be marked as Ineligible, but only do this is you really think the application is of no interest, we can't get them back again. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Google+Summer+of+Code+%282008%29+Applications [2] http://code.google.com/soc/2008/asf/open.html How many actual GSoC mentors do we have from Tuscany? By my count its 4 which if we're to have two mentors per proposal and likely to only get Tuscany mentors for Tuscany proposals then that means we can only support two proposals right? Have I missed some mentors? Would any other Tuscany committers volunteer to be mentors? ...ant
New Eclipse update site in SCA 1.2 release
In the 1.2 release candidate we've now an Eclipse update site. I can't find any mention of this happening anywhere, do we have any doc at all on it happening somewhere that I missed? ...ant
Re: SCADomain.getService () should throw exception when bogus component name is passed?
On Fri, Apr 11, 2008 at 8:16 AM, Mike Edwards [EMAIL PROTECTED] wrote: Simon Laws wrote: On Thu, Apr 10, 2008 at 10:45 AM, ant elder [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 10:28 AM, Simon Laws [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 9:17 AM, Wang Feng [EMAIL PROTECTED] wrote: +1 throw an exception. The scenario like this class.getMethod(methodName). If a matching method is not found,it will throw NoSuchMethodException. Thanks, Wang Feng On 2008-04-10,ant elder [EMAIL PROTECTED] wrote: TUSCANY-2145 asks about SCADomain.getService () returning a proxy even when the service doesn't exist, but looking back through the SVN history it looks like this is intentional. Before I close the JIRA does anyone have any comments on if this is/isn't the correct behaviour? ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I believe this is the way it is because of the approach we took to resolving references to services running remotely elsewhere in the domain. I.e. as a last resort we used to look them up at run time. Hence it wasn't until you tried to use the proxy that you found out whether the service was available. For component to component wires this is going away now as the workspace resolves these wires before composites are deployed. There is still however the case here where some client is calling getService(). There are two uses cases that come to mind: 1 - node.getService() - the process that is running the node asks for a service reference. In this case we could mandate that only services local to the node are available and hence sidestep the remote lookup problem. 2 - domain. getService() - domain is in speech marks here as we are removing this interface at the moment. However I still think we will at some point need the ability to allow an arbitrary non-sca client to get at services exposed by an SCA domain. In this case though we would now rely on the workspace which has access to all of the component service endpoint information. The long and short of this is that I think that get service should now raise an error if you ask for a service that doesn't exist. Preferably by throwing an exception. However this is tied up with unpicking some of the existing domain support which is still ongoing so I would leave TUSCANY-2145 open for the time being. Simon Is the current o.a.t.s.host.embeded.impl.SCADomainImpl actually used by any of the distributed node/domain impl code? Without having searched in the code i thought the host-embeded module was separate and if so we could change SCADomainImpl to through an exception now? ...ant It is separate so we could add the exception now if everyone is happy. We might get away with this without breaking any tests. It's the underlying callable reference code that is reused across host-embedded and the distributed code. Simon Folks, Can someone help me here - I may simply not understand the new design point, but something does not feel right here. I believe that it must be possible to deploy a contribution to the Domain which has components with references to services supplied by other composites. If this is so, it must also be the case that the target component may not yet have been contributed, so that at the point the first component is run, its reference cannot be satisfied. It will be satisfied later when the second contribution is deployed. So, how is this situation being handled? Thowing an exception at load time for the first component does not sound right to me. Yours, Mike. This JIRA is about the SCADomain code in the tuscany-host-embeded module and that code doesn't support incrementally adding contributions. So doing something like: scaDomain = o.a.t.s.host.embeded.SCADomain.newInstance(OuterComposite.composite), scaDomain.getService(Source.class, SourceComponentXXX); The scaDomain knows that SourceComponentXXX doesn't exist and the getService method could throw an exception there. Right now in that situation the code does not throw an exception but returns a proxy anyway and the exception occurs when any service method is called on that proxy. ...ant
Re: distribution target-last-successful copies
On Thu, Apr 10, 2008 at 9:22 AM, ant elder [EMAIL PROTECTED] wrote: The current distribution build copies the binary artifacts to the target-last-successful folder which takes about 130Meg. I'm guessing this is something to do with the continuum builds but does anyone know for sure? If so could we change it so it only happens on the continuum machine (have the continuum build use a specific profile?), or if not can i just delete the copy task? ...ant OK maybe if I ask a different way... It looks like the target-last-successful copies aren't actually required anymore so unless i hear otherwise I'll remove the copy from the distribution pom.xml. ...ant
Re: SCA 2.0, was Re: Next SCA release
On Thu, Apr 10, 2008 at 10:33 PM, Simon Nash [EMAIL PROTECTED] wrote: snip +1. Many of the items suggested for 2.0 have previously been the subject of discussions that have not been easy to close. Until we have agreement on how to approach these things, I think it's better for 2.0 development to happen in an investigative branch. Doing this will allow us to try different approaches and see which we prefer, without causing a lot of churn to the trunk. So based on the comments so far I think we should hold off on moving to 2.0 for now. That said I'm extremely wary of the having work going on in investigative branches, given Tuscany's history of branches and forks I really really hope this doesn't happen much and we'd instead all try to work together in the trunk. ...ant
Re: SCA 2.0, was Re: Next SCA release
On Wed, Apr 9, 2008 at 10:23 PM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: snip 1.3 sounds good to me. I'm assuming that we'll cut that branch out of trunk? I'm asking because I'm interested in working on some improvements of 1.2 in the next few weeks. This shouldn't delay any 2.0 work however, which can go in parallel. That sounds scary. Are you saying you don't think its the right time for 2.0? I started this discussion to see if there was consensus to move to 2.0, if there's not consensus then we should not do it. The last thing we need is dev going on in multiple branches as happened in the old days. ...ant
[jira] Commented: (TUSCANY-2145) SCADomain.getService () should throw exception when bogus component name is passed
[
https://issues.apache.org/jira/browse/TUSCANY-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587513#action_12587513
]
ant elder commented on TUSCANY-2145:
This behaviour was introduced in r570929 -
http://svn.apache.org/viewvc?view=revrevision=570929 so it looks like it is
intentional. I'll bring it up on the dev list but right now looks like this
will be closed as Working-As-Designed.
SCADomain.getService () should throw exception when bogus component name is
passed
--
Key: TUSCANY-2145
URL: https://issues.apache.org/jira/browse/TUSCANY-2145
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-Next
Reporter: Kevin Williams
Priority: Minor
SCADomain.getService() currently returns a proxy even when the component name
passed is not in the domain.
I have created a test (currently ignored) in the new vTest suite to
demonstrate.
@Test
@Ignore
public void bogusComponentName() throws Exception {
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
SCADomain.getService () should throw exception when bogus component name is passed?
TUSCANY-2145 asks about SCADomain.getService () returning a proxy even when the service doesn't exist, but looking back through the SVN history it looks like this is intentional. Before I close the JIRA does anyone have any comments on if this is/isn't the correct behaviour? ...ant
distribution target-last-successful copies
The current distribution build copies the binary artifacts to the target-last-successful folder which takes about 130Meg. I'm guessing this is something to do with the continuum builds but does anyone know for sure? If so could we change it so it only happens on the continuum machine (have the continuum build use a specific profile?), or if not can i just delete the copy task? ...ant
Re: SCADomain.getService () should throw exception when bogus component name is passed?
On Thu, Apr 10, 2008 at 10:28 AM, Simon Laws [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 9:17 AM, Wang Feng [EMAIL PROTECTED] wrote: +1 throw an exception. The scenario like this class.getMethod(methodName). If a matching method is not found,it will throw NoSuchMethodException. Thanks, Wang Feng On 2008-04-10,ant elder [EMAIL PROTECTED] wrote: TUSCANY-2145 asks about SCADomain.getService () returning a proxy even when the service doesn't exist, but looking back through the SVN history it looks like this is intentional. Before I close the JIRA does anyone have any comments on if this is/isn't the correct behaviour? ...ant - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] I believe this is the way it is because of the approach we took to resolving references to services running remotely elsewhere in the domain. I.e. as a last resort we used to look them up at run time. Hence it wasn't until you tried to use the proxy that you found out whether the service was available. For component to component wires this is going away now as the workspace resolves these wires before composites are deployed. There is still however the case here where some client is calling getService(). There are two uses cases that come to mind: 1 - node.getService() - the process that is running the node asks for a service reference. In this case we could mandate that only services local to the node are available and hence sidestep the remote lookup problem. 2 - domain. getService() - domain is in speech marks here as we are removing this interface at the moment. However I still think we will at some point need the ability to allow an arbitrary non-sca client to get at services exposed by an SCA domain. In this case though we would now rely on the workspace which has access to all of the component service endpoint information. The long and short of this is that I think that get service should now raise an error if you ask for a service that doesn't exist. Preferably by throwing an exception. However this is tied up with unpicking some of the existing domain support which is still ongoing so I would leave TUSCANY-2145 open for the time being. Simon Is the current o.a.t.s.host.embeded.impl.SCADomainImpl actually used by any of the distributed node/domain impl code? Without having searched in the code i thought the host-embeded module was separate and if so we could change SCADomainImpl to through an exception now? ...ant
Re: Fw: Tuscany Runtime Error.
Also check that both Classes loaded with application class loader first and Single class loader for application are selected in the app config in the websphere admin panels to make sure its picking up the Tuscany jars from the app not the one included in WAS. ...ant On Thu, Apr 10, 2008 at 9:39 AM, Sandeep Raman [EMAIL PROTECTED] wrote: Hi Jose, javax.wsdl.Definition.getAllPortTypes() is a method which is present in the jar file wsdl4j-1.6.2.jar which comes with tuscany. Just have a look if you the same version jar . In case you do have , verify whether any other jar file has the same class javax.wsdl.Definition which overrides the one given by tuscany. that should solve the problem Regards, Sandeep Jose Miguel Alcaraz [EMAIL PROTECTED] wrote on 04/10/2008 01:54:54 PM: Hi, I have the same error produced by tuscany and I would like to now how do you resolve it? Subject Re: Tuscany Runtime Error. I see some errors but culdnt figure out, its failing in some tuscany class The log : Mar 24, 2008 4:07:21 PM org.apache.catalina.core.StandardContext filterStart SEVERE: Exception starting filter tuscany java.lang.NoSuchMethodError: javax.wsdl.Definition.getAllPortTypes() Ljava/util/Map; at org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl. Java2WSDLHelper.processNoArgAndVoidReturnMethods(Java2WSDLHelper.java:334) at org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl. Java2WSDLHelper.createDefinition(Java2WSDLHelper.java:301) at org.apache.tuscany.sca.interfacedef.wsdl.java2wsdl. Java2WSDLHelper.createWSDLInterfaceContract(Java2WSDLHelper.java:127) at org.apache.tuscany.sca.binding.ws.axis2. Axis2ServiceBindingProvider.init(Axis2ServiceBindingProvider.java:56) at org.apache.tuscany.sca.binding.ws.axis2. Axis2BindingProviderFactory. createServiceBindingProvider(Axis2BindingProviderFactory.java:57) at org.apache.tuscany.sca.binding.ws.axis2. Axis2BindingProviderFactory. createServiceBindingProvider(Axis2BindingProviderFactory.java:40) at org.apache.tuscany.sca.provider. DefaultProviderFactoryExtensionPoint$LazyBindingProviderFactory. ForwardSourceID:NTADC6 =-=-= Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
Re: SCA 2.0, was Re: Next SCA release
On Thu, Apr 10, 2008 at 12:01 PM, Simon Laws [EMAIL PROTECTED] wrote: On Thu, Apr 10, 2008 at 8:12 AM, ant elder [EMAIL PROTECTED] wrote: On Wed, Apr 9, 2008 at 10:23 PM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: snip 1.3 sounds good to me. I'm assuming that we'll cut that branch out of trunk? I'm asking because I'm interested in working on some improvements of 1.2 in the next few weeks. This shouldn't delay any 2.0 work however, which can go in parallel. That sounds scary. Are you saying you don't think its the right time for 2.0? I started this discussion to see if there was consensus to move to 2.0, if there's not consensus then we should not do it. The last thing we need is dev going on in multiple branches as happened in the old days. ...ant Maybe this means we should consider the trunk to be 1.X and branch for 2.0 at the point at which someone wants to start investigating 2.0. I've been thinking of this 2.0 exercise as investigative in the first instance hence [1]. By that I mean that I would fully expect us to do other 1.X releases before any 2.0 features appear in released form. B.t.w - have copied in the user list as we neglected to do this and this is as much a user discussion as a developer discussion. Simon Keeping maintenance branches going and porting fixes from trunk back to them seems fine but as has been demonstrated several times in Tuscany's history we are not able to maintain a consensus based approach to development when new development is going on in multiple branches. If we're not ready to make backward compatibility breaking changes to the trunk code then IMHO we should just wait. ...ant
[jira] Closed: (TUSCANY-2207) First steps towards Axis MTOM Support
[ https://issues.apache.org/jira/browse/TUSCANY-2207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2207. -- Resolution: Fixed Applied. Thanks Giorgio. First steps towards Axis MTOM Support -- Key: TUSCANY-2207 URL: https://issues.apache.org/jira/browse/TUSCANY-2207 Project: Tuscany Issue Type: New Feature Affects Versions: Java-SCA-1.2 Reporter: Giorgio Zoppi Priority: Minor Fix For: Java-SCA-Next Attachments: value.diff This is my first steps towards MTOM support in Tuscany using intent, as it was debated in http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg26726.html. Currently it supports only client generated communication. I opened this jira for tracking. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2195) Test cases for ComponentContext API
[ https://issues.apache.org/jira/browse/TUSCANY-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587070#action_12587070 ] ant elder commented on TUSCANY-2195: I'm a bit confused about the difference between the three patches - is it just the ComponentContextJira2195.patch from the 7th that needs applying or are the other two still relevant as well? Test cases for ComponentContext API --- Key: TUSCANY-2195 URL: https://issues.apache.org/jira/browse/TUSCANY-2195 Project: Tuscany Issue Type: Test Components: Java SCA Verification Tests Affects Versions: Java-SCA-Next Reporter: Kevin Williams Attachments: ComponentContext.zip, ComponentContext20080404.zip, ComponentContextJira2195.patch Contributions for ComponentContext API testing can be attached here -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2162) Spring SCA specification should accomodate common beans/aspects used by different composites/components
[ https://issues.apache.org/jira/browse/TUSCANY-2162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587085#action_12587085 ] ant elder commented on TUSCANY-2162: We (as in Apache Tuscany) can not enhance the actual specification, for that you'd need to send feed back to the OASIS committee, you can do that through the comments mailing lists - see http://www.oasis-opencsa.org/mailing-lists. What we can do in Tuscany is implement additional functionality thats not described in a spec and this sounds like it could help with what you want, and if we get something working we can then feed that back to OASIS to get the specs enhanced. Could you give a little more detail about what you're proposing, maybe with some snippets of code and/or SCDL to demonstrate what you mean? Spring SCA specification should accomodate common beans/aspects used by different composites/components --- Key: TUSCANY-2162 URL: https://issues.apache.org/jira/browse/TUSCANY-2162 Project: Tuscany Issue Type: New Feature Components: Java SCA Spring Implementation Extension Reporter: Catalin Boloaja The use case : service composites using components or composites as Spring beans. Those beans rely on other injected common beans or applied aspects. We should not instantiate a new bean or aspect for every Spring component or composite if the beans and aspects are shared . The Spring way would be to declare a parent context to accommodate the common beans / aspects. The Spring SCA implementation specification says a new Spring context will be created for each composite. Unclear for component. Can we enhance the specification in the sense of a parent application context ? -- 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-2212) SCA Java builds are getting very large
SCA Java builds are getting very large -- Key: TUSCANY-2212 URL: https://issues.apache.org/jira/browse/TUSCANY-2212 Project: Tuscany Issue Type: Improvement Components: Build System Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next As discussed on the ML SCA Java builds are getting very large. See http://apache.markmail.org/message/u7ebawcoicyqi55a Current size for me is 1.5GB so this jira is to track fixes to reduce that. Looking at the build and repo there's here's some things OTTOMH to start with: - the distribution build copies the distros to the target-last-successful folder. this is only needed for the continuum build and adds 120MB - where ever JMS is used the ActiveMQ default is persistence=true which adds about 50MB for the dbs, changing to persistence=false avoids that - a large amount of the mvn repository size is webapp samples but we don't need these installed into the mvn repo, is there a way to prevent that happening? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SCA Java builds are getting very large
On Sat, Feb 16, 2008 at 11:48 PM, Simon Nash [EMAIL PROTECTED] wrote: It isn't long since I could do a complete checkout and build of Tuscany SCA Java in around 400 MB of disk space. Today I was amazed when I ran out of space despite having cleared over a gigabyte before starting. I tend to keep a few builds around for various reasons and the space factor is rapidly becoming more and more of an inhibitor to my development productivity. The full checkout and build that I did a week ago occupied 718 MB on disk. Today's version weighs in at a hefty 1020 MB. I've done some digging around, and there's nothing that seems very easy to eliminate. The biggest files are webapp samples and ActiveMQ logs. This size explosion adds more weight to the evidence that we need to split up the codebase into more modular chunks that can be built and tested independently. Simon To do a complete build of trunk now takes 1.5GB of disk space on my machine, thats for the trunk src build folder and the local maven repository. As part of the cleanup being talked about for the next release I'd like to try to reduce this a lot, i've raised TUSCANY-2212 to track this, if you've any ideas to help please feel free to add a comment/help. ...ant
[jira] Assigned: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder reassigned TUSCANY-2092: -- Assignee: ant elder (was: Ramkumar Ramalingam) ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: ant elder Attachments: JIRA-2092.patch java.util.ConcurrentModificationException at java.util.AbstractList$SimpleListIterator.next(Unknown Source) at org.apache.tuscany.sca.contribution.service.ExtensibleContributionListener.contributionAdded(ExtensibleContributionListener.java:40) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:389) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:202) The problem occurs if two threads try to add a contribution simultaneously. DefaultContributionListenerExtensionPoint does not synchronize the list of listeners. In particular loadListeners does not prevent multiple threads from trying to load the list of listeners. One thread completes first while the other is still loading. This leads to the exception shown above when a thread tries to iterate the listener list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-2092) ConcurrentModificationException in ExtensibleContributionListener
[ https://issues.apache.org/jira/browse/TUSCANY-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-2092. -- Resolution: Fixed Fix Version/s: Java-SCA-Next Applied in r646335, thanks for the fix Ramkumar! ConcurrentModificationException in ExtensibleContributionListener - Key: TUSCANY-2092 URL: https://issues.apache.org/jira/browse/TUSCANY-2092 Project: Tuscany Issue Type: Bug Reporter: Greg Dritschler Assignee: ant elder Fix For: Java-SCA-Next Attachments: JIRA-2092.patch java.util.ConcurrentModificationException at java.util.AbstractList$SimpleListIterator.next(Unknown Source) at org.apache.tuscany.sca.contribution.service.ExtensibleContributionListener.contributionAdded(ExtensibleContributionListener.java:40) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.addContribution(ContributionServiceImpl.java:389) at org.apache.tuscany.sca.contribution.service.impl.ContributionServiceImpl.contribute(ContributionServiceImpl.java:202) The problem occurs if two threads try to add a contribution simultaneously. DefaultContributionListenerExtensionPoint does not synchronize the list of listeners. In particular loadListeners does not prevent multiple threads from trying to load the list of listeners. One thread completes first while the other is still loading. This leads to the exception shown above when a thread tries to iterate the listener list. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (TUSCANY-2212) SCA Java builds are getting very large
[ https://issues.apache.org/jira/browse/TUSCANY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587192#action_12587192 ] ant elder commented on TUSCANY-2212: - clean up use of multiple releases of dependencies by different modules some of the dependencies are several meg and we use several diff releases - jaxb-xjc, derby, xerces, saxon, cleaning this up would reduce the size and speed up builds from an empty repo SCA Java builds are getting very large -- Key: TUSCANY-2212 URL: https://issues.apache.org/jira/browse/TUSCANY-2212 Project: Tuscany Issue Type: Improvement Components: Build System Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next As discussed on the ML SCA Java builds are getting very large. See http://apache.markmail.org/message/u7ebawcoicyqi55a Current size for me is 1.5GB so this jira is to track fixes to reduce that. Looking at the build and repo there's here's some things OTTOMH to start with: - the distribution build copies the distros to the target-last-successful folder. this is only needed for the continuum build and adds 120MB - where ever JMS is used the ActiveMQ default is persistence=true which adds about 50MB for the dbs, changing to persistence=false avoids that - a large amount of the mvn repository size is webapp samples but we don't need these installed into the mvn repo, is there a way to prevent that happening? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: STP SCA Component - STP SCA Tools sub project
+1, good for both projects. And to reply to a comment in the original email - I'm not sure that we really need an explicit vote for this can just assume from all the positive comments so far and lazy consensus that its fine unless someone complains (which i'm sure they wont). ...ant On Tue, Apr 8, 2008 at 5:17 PM, Simon Nash [EMAIL PROTECTED] wrote: This proposal looks good to me. I'd be happy to see the Apache Tuscany project listed as an interested party. Simon Stéphane Drapeau wrote: Hi, I created an entry [0] in the Eclipse bugzilla with the proposal. Your comments are welcome. Best regards Stéphane Drapeau Obeo [0]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=225956 On Thu, Apr 3, 2008 at 11:10 AM, Stéphane Drapeau [EMAIL PROTECTED] wrote: Haleh, Raymond, Thank you for your answers. Haleh, you're right. I make no distinction between tools for SCA developers and tools for SCA users. The goal of the project is to develop tools to help users of the SCA technology. I will modify my sentence. Stéphane Drapeau Obeo On Thu, Apr 3, 2008 at 6:21 AM, haleh mahbod [EMAIL PROTECTED] wrote: Hi Stephan, This looks good since it looks like tools for SCA will get more focus :) I have a question. You mention the goals of the new sub-project are to develop a set of tools for SCA developers and SCA users. What is the difference between SCA developer and SCA user in this context? Haleh On 4/2/08, Stéphane Drapeau [EMAIL PROTECTED] wrote: Hi Jean-Sebastien, Haleh, all, The proposal is a 3 pages document describing the scope/intent of the proposed project. The outline is: 1. Introduction: the proposition of the transformation of the STP/SCA component into a sub-project named SCA Tools under the top level project STP. 2. Background: presentation of STP + presentation of the existing STP/SCA component. 3. Description: the goals of the new sub-project are to develop a set of tools for SCA developers and SCA users. Another goal is also to link this sub-project with other components of STP (Service Creation, Policy Editor) 4. Proposed components: SCA Domain Model (SCA meta model), SCA Composite Designer, SCA Composite Editors (tree, xml and form), SCA Integration (integration with other STP components) 5. Relationship with Other Eclipse Projects: STP, EMF, GMF, M2M, ... 6. Organization: this sub-project will take place under the top level project STP. 7. A list of proposed initial committers. 8. Code Contribution: the Eclipse STP/SCA component will be the initial code. 9. Interested parties: this section lists companies and communities that support the creation of the project. They don't take other engagements. 10. Tentative Plan for 2008 and 2009. Our goal is to identify formally the scope of the tools that we develop around SCA. The new status will provide some advantages. - I think that the SCA tools will be more visible in the Eclipse community if we are identified as a sub-project. - From the users point of view, it will not change anything. - Concerning us, we should be more formal: clear roadmap, new features described/discussed first in bugzilla, ... - It will also present some advantages for Obeo by becoming a sub-project leader. In the near future all STP components will become STP sub-projects. To summarize, all of this is purely administrative. I will send you the proposal document ASAP. If you have any questions, don't hesitate. Haleh, yesterday I sent you more information about the SCA Composite Designer on the thread named [Website] - Tooling for Java SCA. You can add it on the web page. Tell me if you need more/different information. My post describes what version of Tuscany can be used. I also introduce a tutorial that I made. This tutorial is based on the SCA designer and Tuscany 1.1. Best regards, Stéphane Drapeau Obeo On Wed, Apr 2, 2008 at 8:05 AM, haleh mahbod [EMAIL PROTECTED] wrote: Hi Stephane, Welcome to Tuscany. How will changing the status of STP SCA from a component to a sub project change its future development and focus? Tuscany community had asked about tools for SCA and because of that I recently added a website page [1] to collect more information about available open source tools. I added a link to STP
Re: SCA 2.0, was Re: Next SCA release
On Wed, Apr 9, 2008 at 4:56 PM, Simon Laws [EMAIL PROTECTED] wrote: On Wed, Apr 9, 2008 at 4:47 PM, haleh mahbod [EMAIL PROTECTED] wrote: +1 on versioning SCA docs Assuming two versions of SCA Java, I can see that the following page will change to point to two different versions of SCA Java, 1.x and 2.x and their related documentation. http://incubator.apache.org/tuscany/tuscany-downloads-documentations.html Tuscany SCA Java general page would contain general information that would pertain to both versions. So, it might need to change. http://incubator.apache.org/tuscany/sca-java.html On the left navigation of sca-java page, we would have two boxes SCA Java 2.x SCA Java 1.x each would point to their own releases and their own documentations and source code tree. There is a set of documentations under SCA Java that are generic, like development guide. We could share these pages between the two versions. Does this make sense? Generally make sense to me. On the particular question of where to host V2 and V2 docs we have identified 3 choices so far. 1 - [] Put V2 doc changes in V1 pages and mark them as such 2 - [] Create SCA Java 1.x/ SCA Java 2.x documentation pages on our current site wiki 3 - [] Create separate SCA Java 1.x/ SCA Java 2.x wiki spaces Are there other cunning options we need to consider. I'm for option 2 at the current time. Simon How would that option [2] actually work? Lets say I change the way the dwr binding works and want to update the doc for V2, the current wiki page is at http://incubator.apache.org/tuscany/sca-java-bindingajax.html so what would i do for the new v2 page? ...ant
Re: [jira] Commented: (TUSCANY-2212) SCA Java builds are getting very large
Thats a handy report, how do you generate it? ...ant On Wed, Apr 9, 2008 at 4:45 PM, Simon Laws (JIRA) tuscany-dev@ws.apache.org wrote: [ https://issues.apache.org/jira/browse/TUSCANY-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587242#action_12587242] Simon Laws commented on TUSCANY-2212: - Here is the list of dependencies from the latest trunk ( http://people.apache.org/~slaws/deptotal.htmhttp://people.apache.org/%7Eslaws/deptotal.htm ). Not as bad as it was but we do, for example, depend on 3 versions of xerces and jaxb. SCA Java builds are getting very large -- Key: TUSCANY-2212 URL: https://issues.apache.org/jira/browse/TUSCANY-2212 Project: Tuscany Issue Type: Improvement Components: Build System Affects Versions: Java-SCA-Next Reporter: ant elder Fix For: Java-SCA-Next As discussed on the ML SCA Java builds are getting very large. See http://apache.markmail.org/message/u7ebawcoicyqi55a Current size for me is 1.5GB so this jira is to track fixes to reduce that. Looking at the build and repo there's here's some things OTTOMH to start with: - the distribution build copies the distros to the target-last-successful folder. this is only needed for the continuum build and adds 120MB - where ever JMS is used the ActiveMQ default is persistence=true which adds about 50MB for the dbs, changing to persistence=false avoids that - a large amount of the mvn repository size is webapp samples but we don't need these installed into the mvn repo, is there a way to prevent that happening? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Next SCA release
With 1.2 almost out the door how about starting to think about our next release... We've had several discussions in the past about restructuring and cleaning up the distributions, build, and SPIs etc, is this the time to do that? Looking about the code there's many things that could be tidied up but we've been leaving them to keep backward compatibility, if we start this type of thing now it will make the next release not backward compatible so we need to agree this is the right time. We could make a new 1.x branch to use as a maintenance branch for the previous releases so we can still get fixes out for them. Leaving aside for now any detail about what the clean up and breaking changes might be what do you all think about doing this in the next release? I think its the right time so am in favour of starting this. ...ant
Re: [SCA 1.2] RC3a
I've spent all morning reviewing this and its looking pretty good but i've just hit this NoClassDefFoundError when running the calculator sample with mvn from an empty local mvn repository: Running calculator.CalculatorTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.907 sec FAILURE! testCalculator(calculator.CalculatorTestCase) Time elapsed: 0.875 sec ERROR! java.lang.NoClassDefFoundError: javax/jws/WebService at org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:70) ...ant On Tue, Apr 8, 2008 at 8:43 AM, Luciano Resende [EMAIL PROTECTED] wrote: The RC3a is now available in [1]. Please give it a quick try, and I'll call a vote in the morning. [1] http://people.apache.org/~lresende/tuscany/sca-1.2-RC3a/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3a/ -- 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]
Re: [SCA 1.2] RC3a
Adding that gave me a missing artifact for javax.jws:jsr181:jar:1.0, adding an exclude and explicit dependency looks like it fixes it: dependency groupIdjavax.xml.ws/groupId artifactIdjaxws-api/artifactId version2.1-1/version exclusions exclusion groupIdjavax.jws/groupId artifactIdjsr181/artifactId /exclusion /exclusions /dependency dependency groupIdjavax.jws/groupId artifactIdjsr181-api/artifactId version1.0-MR1/version /dependency ...ant On Tue, Apr 8, 2008 at 3:43 PM, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Ant. I think you hit the problem reported at http://jira.codehaus.org/browse/MEV-573. You could delete the javax/xml/ws folder from your local maven repo and try again. If you are lucky, you can get the correct version from java.net repo. There is a workaround: Change the pom.xml to use version 2.1-1 for the jaxws-api dependencies as follow. dependency groupIdjavax.xml.ws/groupId artifactIdjaxws-api/artifactId version2.1-1/version /dependency Thanks, Raymond -- From: ant elder [EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 5:35 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA 1.2] RC3a I've spent all morning reviewing this and its looking pretty good but i've just hit this NoClassDefFoundError when running the calculator sample with mvn from an empty local mvn repository: Running calculator.CalculatorTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.907 sec FAILURE! testCalculator(calculator.CalculatorTestCase) Time elapsed: 0.875 sec ERROR! java.lang.NoClassDefFoundError: javax/jws/WebService at org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:70) ...ant On Tue, Apr 8, 2008 at 8:43 AM, Luciano Resende [EMAIL PROTECTED] wrote: The RC3a is now available in [1]. Please give it a quick try, and I'll call a vote in the morning. [1] http://people.apache.org/~lresende/tuscany/sca-1.2-RC3a/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3a/ http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3a/ -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresendehttp://people.apache.org/%7Elresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - 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: SCA 2.0, was Re: Next SCA release
Yep, this is exactly what i'm was suggesting, was just leaving the name till later :) ...ant On Tue, Apr 8, 2008 at 5:27 PM, Luciano Resende [EMAIL PROTECTED] wrote: I was waiting to start this discussion after SCA 1.2 was out of the door, but looks like you were faster then me. I'm +1 on this, and here is my proposal. - Continue with SCA 1.x maintenance releases based on the current SCA 1.2 branch. This would be a more stable codebase, and we should avoid big changes that could brake backward compatibility here. - Use trunk as our SCA 2.0 release stream, where we would do the type of work discussed in [1], the cleanup and restructuring mentioned by you on this thread, as well as any other work that the community feels its applicable. Note that my proposal does not exclude merging items between branch and trunk as necessary, but this would probably be done case by case when the community thinks it's applicable. Thoughts ? [1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg29820.html On Tue, Apr 8, 2008 at 12:55 AM, ant elder [EMAIL PROTECTED] wrote: With 1.2 almost out the door how about starting to think about our next release... We've had several discussions in the past about restructuring and cleaning up the distributions, build, and SPIs etc, is this the time to do that? Looking about the code there's many things that could be tidied up but we've been leaving them to keep backward compatibility, if we start this type of thing now it will make the next release not backward compatible so we need to agree this is the right time. We could make a new 1.x branch to use as a maintenance branch for the previous releases so we can still get fixes out for them. Leaving aside for now any detail about what the clean up and breaking changes might be what do you all think about doing this in the next release? I think its the right time so am in favour of starting this. ...ant -- 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]
Re: SCA 2.0, was Re: Next SCA release
On Tue, Apr 8, 2008 at 6:11 PM, Simon Laws [EMAIL PROTECTED] wrote: snip We may need to branch the documentation also. Normally I would suggest that we ask for a new space but as our documentation could not be considered complete for 1.1 and as the suggested first actions are internal restructuring we may find it less onerous to maintain 2.X documents alongside the the 1.X documents with suitable comments to point out where they diverge. Do people have a preference. I wondered about the doc too, if there was a new wiki space for 2.x could it be initially be populated with the existing content? If so then it seems to me like it would be easiest to have the new space than to try point out the differences for each release all in the one space. ...ant
Re: [SCA 1.2] RC3a
I only tried changing interface-java-jaxws as i haven't done a full build of the src distro, just that module and the calculator sample. ...ant On Tue, Apr 8, 2008 at 7:13 PM, Luciano Resende [EMAIL PROTECTED] wrote: Just want to check the places where you had to make changes. Did you only changed the modules/interface-java-jaxws/pom.xml dependency or you had to change the other references to it as the patch below ? Anyway, I'm trying a build to also check the differences on the distribution lib directory. Index: itest/databindings/interop/pom.xml === --- itest/databindings/interop/pom.xml (revision 645758) +++ itest/databindings/interop/pom.xml (working copy) @@ -189,7 +189,7 @@ artifactItem groupIdjavax.xml.ws/groupId artifactIdjaxws-api/artifactId -version2.1/version +version2.1-1/version typejar/type /artifactItem artifactItem Index: modules/interface-java-jaxws/pom.xml === --- modules/interface-java-jaxws/pom.xml(revision 645758) +++ modules/interface-java-jaxws/pom.xml(working copy) @@ -52,11 +52,22 @@ scopetest/scope /dependency -dependency -groupIdjavax.xml.ws/groupId -artifactIdjaxws-api/artifactId -version2.1/version -/dependency + dependency + groupIdjavax.xml.ws/groupId + artifactIdjaxws-api/artifactId + version2.1-1/version + exclusions + exclusion + groupIdjavax.jws/groupId + artifactIdjsr181/artifactId + /exclusion + /exclusions + /dependency + dependency + groupIdjavax.jws/groupId + artifactIdjsr181-api/artifactId + version1.0-MR1/version + /dependency /dependencies @@ -101,7 +112,7 @@ artifactItem groupIdjavax.xml.ws/groupId artifactIdjaxws-api/artifactId -version2.1/version +version2.1-1/version typejar/type /artifactItem artifactItem On Tue, Apr 8, 2008 at 9:17 AM, ant elder [EMAIL PROTECTED] wrote: Adding that gave me a missing artifact for javax.jws:jsr181:jar:1.0, adding an exclude and explicit dependency looks like it fixes it: dependency groupIdjavax.xml.ws/groupId artifactIdjaxws-api/artifactId version2.1-1/version exclusions exclusion groupIdjavax.jws/groupId artifactIdjsr181/artifactId /exclusion /exclusions /dependency dependency groupIdjavax.jws/groupId artifactIdjsr181-api/artifactId version1.0-MR1/version /dependency ...ant On Tue, Apr 8, 2008 at 3:43 PM, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Ant. I think you hit the problem reported at http://jira.codehaus.org/browse/MEV-573. You could delete the javax/xml/ws folder from your local maven repo and try again. If you are lucky, you can get the correct version from java.net repo. There is a workaround: Change the pom.xml to use version 2.1-1 for the jaxws-api dependencies as follow. dependency groupIdjavax.xml.ws/groupId artifactIdjaxws-api/artifactId version2.1-1/version /dependency Thanks, Raymond -- From: ant elder [EMAIL PROTECTED] Sent: Tuesday, April 08, 2008 5:35 AM To: tuscany-dev@ws.apache.org Subject: Re: [SCA 1.2] RC3a I've spent all morning reviewing this and its looking pretty good but i've just hit this NoClassDefFoundError when running the calculator sample with mvn from an empty local mvn repository: Running calculator.CalculatorTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.907 sec FAILURE! testCalculator(calculator.CalculatorTestCase) Time elapsed: 0.875 sec ERROR! java.lang.NoClassDefFoundError: javax/jws/WebService at org.apache.tuscany.sca.interfacedef.java.jaxws.JAXWSJavaInterfaceProcessor.visitInterface(JAXWSJavaInterfaceProcessor.java:70) ...ant
Re: New SCA JEE spec draft and Tuscany JSP taglib available
On Mon, Apr 7, 2008 at 9:22 AM, ant elder [EMAIL PROTECTED] wrote: On Mon, Mar 31, 2008 at 4:43 PM, ant elder [EMAIL PROTECTED] wrote: snip One bit I liked was section 5.4.4 about using JSPs with SCA, what we currently have in Tuscany is a bit clunky so i've committed some code to support the taglib as described in that section. So now in a JSP you don't need any code for the SCADomain you just declare the taglib: %@ taglib uri=http://www.osog.org/sca/sca.tld; prefix=sca % and then define SCA references with: sca:reference name=CalculatorServiceComponent type=calculator.CalculatorService / I've updated the calclulator webapp sample to demonstrate this - https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/calculator-webapp/src/main/webapp/calc.jsp This seems so much better than our old approach I'd like to change all our JSP samples to work like this, what do you guys think? ...ant Any comments on this, when no one answers I always worry its because you think i'm doing something daft ;) I've been thinking about extending this further so that the taglib is extensible and other Tuscany extensions can hook in to add their own processing. That would enable things like the jsonrpc, dwr, etc bindings to get javascript inserted into the web page without needing any extension specific script tags in the page so for example we'd be able to get rid of the scadomain.js script tag stuff. ...ant Beavering on with this despite the silence... :) So one thing I'd like to do related to this JEE spec is to try to get a sample working that uses callbacks to a web2.0 style client, so like the chat-sample but using a asynchronous callbacks to send responses to the browser clients. To demonstrate what i mean i've just committed a new chat2-sample that does this, its not in the build and doesn't work yet as most of the runtime code isn't implemented but it shows the idea to get feedback on the approach. It uses a new implementation.web to define the browser client component and the DWR binding for the async support for the callbacks. I plan to work on implementing this now, but welcome any feedback. ...ant
Re: [vtest] getCompositeContext API for non-SCA clients
On Wed, Apr 2, 2008 at 6:37 PM, Kevin Williams [EMAIL PROTECTED] wrote: The current JUnit tests (iTest and vTest) make use of the non-standard SCADomain.getService API to get a handle to an SCA service. Are there any plans to provide an API to get a ComponentContext as outlined by the SCA Java Annotations and APIs specification? I would like to stick to stick to specified APIs as much as possible in vTest. 1.4.2.1. ComponentContext Non-SCA client code can use the ComponentContext API to perform operations against a component in an SCA domain. How client code obtains a reference to a ComponentContext is runtime specific. The following example demonstrates the use of the component Context API by non-SCA code: ComponentContext context = // obtained through host environment-specific means HelloService helloService = context.getService(HelloService.class,HelloService); Thanks. -- Kevin I don't remember any discussion about this so i guess there are no plans yet to change it. I agree it seems like we should though. ...ant
Re: [VOTE] Release Tuscany Java SCA 1.2-incubating (RC3)
I see this too, building the src distro and also building the bin distro samples with mvn (the Ant builds work ok). ...ant On Mon, Apr 7, 2008 at 8:36 AM, Adriano Crestani [EMAIL PROTECTED] wrote: Hi, I downloaded the apache-tuscany-sca-1.2-incubating-src.zip file from http://people.apache.org/~lresende/tuscany/sca-1.2-RC3/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3/, extracted it into e:\ and executed mvn -U in e:\tuscany-sca-1.2-incubating-src\ folder. Unfortunatelly I got the failure below: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\invocation\NonBlockingInterceptor.java:[30,35] package org.apache.tusca ny.sca.work does not exist E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\invocation\NonBlockingInterceptor.java:[42,12] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.invocation.NonBlockingInterceptor E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\invocation\NonBlockingInterceptor.java:[45,34] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.invocation.NonBlockingInterceptor E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\invocation\NonBlockingInterceptor.java:[49,34] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.invocation.NonBlockingInterceptor E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\invocation\NonBlockingInterceptor.java:[60,33] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.invocation.NonBlockingInterceptor E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\assembly\RuntimeWireImpl.java:[54,35] package org.apache.tuscany.sca.wo rk does not exist E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\assembly\RuntimeWireImpl.java:[66,22] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.assembly.RuntimeWireImpl E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\assembly\RuntimeWireImpl.java:[92,27] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.assembly.RuntimeWireImpl E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\assembly\CompositeActivatorImpl.java:[67,35] package org.apache.tuscany .sca.work does not exist E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\assembly\CompositeActivatorImpl.java:[79,18] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl E:\tuscany-sca-1.2-incubating-src\modules\core\src\main\java\org\apache\tuscany\ sca\core\assembly\CompositeActivatorImpl.java:[106,34] cannot find symbol symbol : class WorkScheduler location: class org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 minute 33 seconds [INFO] Finished at: Mon Apr 07 04:14:55 PDT 2008 [INFO] Final Memory: 25M/54M [INFO] On Sun, Apr 6, 2008 at 9:14 PM, Luciano Resende [EMAIL PROTECTED] wrote: Please review and vote on the 1.2 release artifacts of Tuscany SCA for Java. The artifacts are available for review at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC3/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3/ http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3/ This includes the signed binary and source distributions, the RAT report, and the Maven staging repository. The eclipse updatesite for the Tuscany Eclipse plugins is available at: http://people.apache.org/~lresende/tuscany/sca-1.2-RC3/updatesite/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3/updatesite/ http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3/updatesite/ The release tag is available at : http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.2-RC3/ Looks OK to me, here is my +1. -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresendehttp://people.apache.org/%7Elresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/
vtest?
I see we've now a new vtest top-level folder in the trunk and various dev happening there. Looking back in the mailing list I cant find any discussion on adding that or what its about, am i just missing the emails or whats going on there? ...ant
Re: New SCA JEE spec draft and Tuscany JSP taglib available
On Mon, Mar 31, 2008 at 4:43 PM, ant elder [EMAIL PROTECTED] wrote: snip One bit I liked was section 5.4.4 about using JSPs with SCA, what we currently have in Tuscany is a bit clunky so i've committed some code to support the taglib as described in that section. So now in a JSP you don't need any code for the SCADomain you just declare the taglib: %@ taglib uri=http://www.osog.org/sca/sca.tld; prefix=sca % and then define SCA references with: sca:reference name=CalculatorServiceComponent type=calculator.CalculatorService / I've updated the calclulator webapp sample to demonstrate this - https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/samples/calculator-webapp/src/main/webapp/calc.jsp This seems so much better than our old approach I'd like to change all our JSP samples to work like this, what do you guys think? ...ant Any comments on this, when no one answers I always worry its because you think i'm doing something daft ;) I've been thinking about extending this further so that the taglib is extensible and other Tuscany extensions can hook in to add their own processing. That would enable things like the jsonrpc, dwr, etc bindings to get javascript inserted into the web page without needing any extension specific script tags in the page so for example we'd be able to get rid of the scadomain.js script tag stuff. ...ant
Re: vtest?
On Mon, Apr 7, 2008 at 9:16 AM, Mike Edwards [EMAIL PROTECTED] wrote: ant elder wrote: I see we've now a new vtest top-level folder in the trunk and various dev happening there. Looking back in the mailing list I cant find any discussion on adding that or what its about, am i just missing the emails or whats going on there? ...ant Ant, Check out this email: http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg29825.html ..plus the threads which start [vtest] and some related JIRAs... Mike. I've seen that and the related [vtest] ones but none of them really say whats going on, that particular email is just about a new jira component. ...ant
Re: [VOTE] Release Tuscany Java SCA 1.2-incubating (RC3)
On Mon, Apr 7, 2008 at 6:14 AM, Luciano Resende [EMAIL PROTECTED] wrote:
Please review and vote on the 1.2 release artifacts of Tuscany SCA for
Java.
The artifacts are available for review at:
http://people.apache.org/~lresende/tuscany/sca-1.2-RC3/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3/
This includes the signed binary and source distributions, the RAT report,
and the Maven staging repository.
The eclipse updatesite for the Tuscany Eclipse plugins is available at:
http://people.apache.org/~lresende/tuscany/sca-1.2-RC3/updatesite/http://people.apache.org/%7Elresende/tuscany/sca-1.2-RC3/updatesite/
The release tag is available at :
http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.2-RC3/
Looks OK to me, here is my +1.
--
Luciano Resende
This looks pretty good to me but the problem with building with mvn prevents
complete testing and there's a problem with the legal files being duplicated
in the src distro so we probably need a respin to fix those things.
The things I've found so far are:
- src distro has got two copies of legal files in top level folder
- The update site jars NOTICE file has the project name as ${pom.name}
instead of Apache Tuscany
- building samples with mvn in bin dsitro fails with
java.lang.NoClassDefFoundError: org/apache/tuscany/sca/work/WorkScheduler
at
org.apache.tuscany.sca.host.embedded.impl.ReallySmallRuntime.start(ReallySmallRuntime.java:102)
- building src distro fails in modules/core with missing class WorkScheduler
- INSTALL file mentions doc folder which missing and does not mention
tutorials folder
- tutorial catalog includes a built webapp is that intentional? And trying
to deploy that webapp in tomcat gives a SEVERE: Error Starting SCA WebApp
Node
java.lang.ClassNotFoundException:
org.apache.tuscany.sca.implementation.node.webapp.NodeWebAppServletHost
- the README in the tutorial folder doesn't give much info and just points
to a website page but that page doesn't look finished and gives little help
...ant
