Re: Domain/Contribution Repository was: Re: SCA contribution packaging schemes: was: SCA runtimes
Jean-Sebastien Delfino wrote: Simon Laws wrote: On Fri, Mar 7, 2008 at 4:18 PM, Simon Laws [EMAIL PROTECTED] wrote: On Fri, Mar 7, 2008 at 12:23 PM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Jean-Sebastien Delfino wrote: Simon Laws wrote: I've been running the workspace code today with a view to integrating the new code in assembly which calculates service endpoints i.e. point4 above. I think we need to amend point 4 to make this work properly.. 4. Point my Web browser to the various ATOM collections to get: - lists of contributions, composites and nodes - list of contributions that are required by a given contribution - the source of a particular composite - the output of a composite after the domain composite has been built by CompositeBuilder Looking at the code in DeployableCompositeCollectionImpl I see that on doGet() it builds the request composite. What the last point needs to do is - read the whole domain - set up all of the service URIs for each of the included composites taking into account the node to which each composite is assigned - build the whole domain using CompositeBuilder - extract the required composite from the domain and serialize it out. Yes, exactly! Are you changing this code or can I put this in? Just go ahead, I'll update and merge if I have any other changes in the same classes. Simon, a quick update: I've done an initial bring-up of node2-impl. It's still a little rough but you can give it a try if you want. The steps to run the store app for example with node2 are as follows: 1) use workspace-admin to add the store and assets contributions to the domain; 2) add the store composite to the domain composite using the admin as well; 3) start the StoreLauncher2 class that I just added to the store module; 4) that will start an instance of node2 with all the node config served from the admin app. So the next step is to integrate your node allocation code with workspace-admin and that will complete the story. Then we'll be able to remove all the currently hardcoded endpoint URIs from the composites. I'll send a more detailed description and steps to run more scenarios later on Friday. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Ok, sounds good. I've done the uri integration although there are some issues we need to discuss. First I'll update with your code, commit my changes and then post here about the issues. Regards Simon I've now checked in my changes (last commit was 634762) to integrate the URI calculation code with the workspace. I've run the new store launcher following Sebastien's instructions from a previous post to this thread. I don't seem to have broken it too much although I'm not seeing any prices for the catalog items. I was seeing that issue too before, it's a minor bug in the property writing code, which is not writing property values correctly. Issues with the URI generation code I have to turn model resolution back on by uncommenting a line in ContributionContentProcessor.resolve. Otherwise the JavaImplementation types are not read and compositeConfiguationBuilder.calculateBindingURIs(defaultBindings, composite, null); can't generate default services. I then had to tun it back off to make the store sample work. I need some help on this one. I'm investigating now. If you hand craft services it seems to be OK although I have noticed, looking at the generated SCDL, that it seems to be assuming that all generated service names will be based on the implementation classname regardless of whether the interface is marked as @Remotable or not. Feels like a bug somewhere so am going to look at that next. OK To get Java implementation resolution to work I needed to hack in the Java factories setup in the DeployableCompositeCollectionImpl.initialize() method. This is not very good and raises the bigger question about the set up in here. It's creating a set of extension points in parallel to those created by the runtime running this component. Can we either use the registry created by the underlying runtime or do similar generic setup. Yes, I'd like to keep the infrastructure used by the admin decoupled from the infrastructure of the runtime hosting the admin, but I'll try to simplify the setup by creating an instance of runtime for the admin and getting the necessary objects out of it, instead of assembling it from scratch as it is now. The code doesn't currently distinguish between those services that are @Remotable and those that aren't Simon Simon, After a few more changes, the domain / node allocation, default URI calculation and resolution of references across nodes now works OK. I was able to remove all the hardcoded URIs in the tutorial composites as they now get determined from the configuration of the nodes that the
[jira] Updated: (TUSCANY-2067) URL Handling in Tuscany breaks when Tuscany is run under OSGi
[ https://issues.apache.org/jira/browse/TUSCANY-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-2067: --- Fix Version/s: Java-SCA-1.2 URL Handling in Tuscany breaks when Tuscany is run under OSGi - Key: TUSCANY-2067 URL: https://issues.apache.org/jira/browse/TUSCANY-2067 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Reporter: Rajini Sivaram Fix For: Java-SCA-1.2 Code in the old DefaultSCADomain and the new domain/node APIs manipulate URLs returned by classloader.getResource() to open a directory or jar file corresponding to a contribution. This breaks when Tuscany is run under OSGi since OSGi returns bundle:// or bundleresource:// URLs instead of the file:// and jar:// URLs supported under Tuscany. A full description of the problem and possible solutions are described in the thread http://www.mail-archive.com/[EMAIL PROTECTED]/msg02213.html. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-2068) itest/osgi-implementation is broken due to recent changes
[ https://issues.apache.org/jira/browse/TUSCANY-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder updated TUSCANY-2068: --- Fix Version/s: Java-SCA-1.2 itest/osgi-implementation is broken due to recent changes - Key: TUSCANY-2068 URL: https://issues.apache.org/jira/browse/TUSCANY-2068 Project: Tuscany Issue Type: Bug Components: Java SCA OSGi Integration Reporter: Rajini Sivaram Assignee: Rajini Sivaram Fix For: Java-SCA-1.2 Recent changes related to Pass-by-value and callbacks have broken many of the itest/osgi-implementationt tests. The tests need to be added back to the itest pom to ensure that breakages are caught earlier. -- 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: svn commit: r635435 - in /incubator/tuscany/java/sca/modules: assembly/src/main/java/org/apache/tuscany/sca/assembly/builder/impl/ assembly/src/test/java/org/apache/tuscany/sca/assembly/builder/im
On Mon, Mar 10, 2008 at 5:43 AM, [EMAIL PROTECTED] wrote:
Author: jsdelfino
Date: Sun Mar 9 22:43:19 2008
New Revision: 635435
URL: http://svn.apache.org/viewvc?rev=635435view=rev
Log:
Fixed algorithm in CompositeConfigurationBuilder to produce correct URIs,
in particular avoid adding binding name to itself, and consider binding URI
when specified in the composite in the single service case too. Integrated
CompositeConfigurationBuilder in the main build() now that it covers all
cases. Adjusted the domain-impl, the callable reference resolution and the
core-spring reference resolution code to the new URI form.
Modified:
incubator/tuscany/java/sca/modules/assembly/src/main/java/org/apache/tuscany/sca/assembly/builder/impl/CompositeConfigurationBuilderImpl.java
incubator/tuscany/java/sca/modules/assembly/src/test/java/org/apache/tuscany/sca/assembly/builder/impl/CalculateBindingURITestCase.java
incubator/tuscany/java/sca/modules/core-spring/src/main/java/org/apache/tuscany/sca/core/spring/assembly/impl/BeanReferenceImpl.java
incubator/tuscany/java/sca/modules/core/src/main/java/org/apache/tuscany/sca/core/context/CallableReferenceImpl.java
incubator/tuscany/java/sca/modules/domain-impl/src/main/java/org/apache/tuscany/sca/domain/impl/SCADomainImpl.java
incubator/tuscany/java/sca/modules/workspace-admin/src/main/java/org/apache/tuscany/sca/workspace/admin/impl/DeployableCollectionImpl.java
Modified:
incubator/tuscany/java/sca/modules/assembly/src/main/java/org/apache/tuscany/sca/assembly/builder/impl/CompositeConfigurationBuilderImpl.java
URL:
http://svn.apache.org/viewvc/incubator/tuscany/java/sca/modules/assembly/src/main/java/org/apache/tuscany/sca/assembly/builder/impl/CompositeConfigurationBuilderImpl.java?rev=635435r1=635434r2=635435view=diff
==
---
incubator/tuscany/java/sca/modules/assembly/src/main/java/org/apache/tuscany/sca/assembly/builder/impl/CompositeConfigurationBuilderImpl.java
(original)
+++
incubator/tuscany/java/sca/modules/assembly/src/main/java/org/apache/tuscany/sca/assembly/builder/impl/CompositeConfigurationBuilderImpl.java
Sun Mar 9 22:43:19 2008
@@ -52,9 +52,9 @@
import org.apache.tuscany.sca.policy.PolicySetAttachPoint;
public class CompositeConfigurationBuilderImpl {
-String SCA10_NS = http://www.osoa.org/xmlns/sca/1.0;;
-String BINDING_SCA = binding.sca;
-QName BINDING_SCA_QNAME = new QName(SCA10_NS, BINDING_SCA);
+private final static String SCA10_NS =
http://www.osoa.org/xmlns/sca/1.0;;
+private final static String BINDING_SCA = binding.sca;
+private final static QName BINDING_SCA_QNAME = new QName(SCA10_NS,
BINDING_SCA);
private AssemblyFactory assemblyFactory;
private SCABindingFactory scaBindingFactory;
@@ -81,9 +81,10 @@
* @param composite
* @param problems
*/
-public void configureComponents(Composite composite) {
+public void configureComponents(Composite composite) throws
CompositeBuilderException {
configureComponents(composite, null);
configureSourcedProperties(composite, null);
+configureBindingURIs(composite, null, null);
}
/**
@@ -124,8 +125,6 @@
// Create default SCA binding
if (service.getBindings().isEmpty()) {
SCABinding scaBinding = createSCABinding();
-
-
service.getBindings().add(scaBinding);
}
@@ -136,33 +135,6 @@
if (binding.getName() == null) {
binding.setName(service.getName());
}
-
-String bindingURI;
-if (binding.getURI() == null) {
-if (compositeServices.size() 1) {
-// Binding URI defaults to parent URI / binding
name
-bindingURI = String.valueOf(binding.getName());
-if (parentURI != null) {
-bindingURI = URI.create(parentURI +
'/').resolve(bindingURI).toString();
-}
-} else {
-// If there's only one service then binding URI
defaults
-// to the parent URI
-if (parentURI != null) {
-bindingURI = parentURI;
-} else {
-bindingURI = String.valueOf(binding.getName
());
-}
-}
-} else {
-// Combine the specified binding URI with the
component URI
-bindingURI = binding.getURI();
-if (parentURI != null) {
-bindingURI = URI.create(parentURI +
'/').resolve(bindingURI).toString();
-}
-}
-
-binding.setURI(bindingURI);
Re: [continuum] BUILD FAILURE: Apache Tuscany SCA Implementation Project
Continuum VMBuild Server wrote: Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=63376projectId=277 SVN revision r635507 contains a fix for this failure. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
About StAXArtifactProcessor
Hi, I recently faced a situation where I wished to passed some context from one StAXArtifact Processor to others down the chain. More specifically, to get the 'targetNamespace' of the definitions.xml file apply to PoliyIntent and PolicySet names, I wished to pass the 'targetNamespace' value from the Definitions Processor (which is where it is read) down to the PolicyIntent and PolicySet processors. I could not figure out a way to do this. Am I missing something here or would it make sense to add an argument named 'context' to the read methods of our StAXProcessor ? I guess there could be other situations when we might need some information from parent element to be passed down. Thoughts ? Thanks - Venkat
[jira] Commented: (TUSCANY-1974) Chat webapp sample misses chat messages
[ https://issues.apache.org/jira/browse/TUSCANY-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576948#action_12576948 ] ant elder commented on TUSCANY-1974: As a quick test i tried debugging through the current trunk code and comparing it to debugging through the same from the 1.0.1 Tuscany release code. That was setting break points in various methods in the tuscany-binding-dwr code and seeing what happens differently in trunk compared with 1.0.1. I start up tomcat, open two browser windows to http://localhost:8080/sample-chat-webapp/ then enter a name/text in one chat window. The main differenece is in org.apache.tuscany.sca.binding.dwr.invoke the line Collection sessions = wctx.getScriptSessionsByPage(currentPage); returns no sessions with the trunk code and two sessions (one for each open browser window) with the 1.0.1 code. So the question is why aren't the sessions being found correctly any more? Chat webapp sample misses chat messages --- Key: TUSCANY-1974 URL: https://issues.apache.org/jira/browse/TUSCANY-1974 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.1 Environment: Tuscany 1.1 RC1 RHEL5 IBM JDK 1.5 Tested Firefox 2.0.0.11 and 3.0 beta2 Reporter: Jean-Sebastien Delfino Assignee: ant elder Fix For: Java-SCA-Next To reproduce the issue: Deploy the Chat webapp to Tomcat and open it in Firefox enter nickname: test1, text: 1 nothing is logged, the message seems to be lost enter text: 2, then 2 is logged Another weird issue: open another window enter nickname: test2, text: a again 'a' is lost enter text b, this time b is logged Go back to the first window enter several text messages they are logged in the first window but none of them is logged in the second window The chat application does not seem to really work. -- 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-1974) Chat webapp sample misses chat messages
[ https://issues.apache.org/jira/browse/TUSCANY-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576963#action_12576963 ] ant elder commented on TUSCANY-1974: Another very useful tool for debugging this is TCPMON from the Apache WS project - http://ws.apache.org/commons/tcpmon/download.cgi You can use that to view the messages sent between the browser client and tomcat server. Start up TCPMON, click on Admin , enter 8089 for the listen port and change the Listener target port to 8080 and click add. Now on the browser change the URL used to run the sample to use the port 8089 eg http://localhost:8089/sample-chat-webapp/, TCPMON should then show all the HTTP messages like GET/ and POST/. Comparing the message differences from the Tuscany 1.0.1 and current trunk code may give a good indication of what the problem may be. Chat webapp sample misses chat messages --- Key: TUSCANY-1974 URL: https://issues.apache.org/jira/browse/TUSCANY-1974 Project: Tuscany Issue Type: Bug Components: Java SCA Samples Affects Versions: Java-SCA-1.1 Environment: Tuscany 1.1 RC1 RHEL5 IBM JDK 1.5 Tested Firefox 2.0.0.11 and 3.0 beta2 Reporter: Jean-Sebastien Delfino Assignee: ant elder Fix For: Java-SCA-Next To reproduce the issue: Deploy the Chat webapp to Tomcat and open it in Firefox enter nickname: test1, text: 1 nothing is logged, the message seems to be lost enter text: 2, then 2 is logged Another weird issue: open another window enter nickname: test2, text: a again 'a' is lost enter text b, this time b is logged Go back to the first window enter several text messages they are logged in the first window but none of them is logged in the second window The chat application does not seem to really work. -- 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]
[continuum] BUILD ERROR: Apache Tuscany SCA Implementation Project
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=63406projectId=277 Build statistics: State: Error Previous State: Building Started at: Mon 10 Mar 2008 05:20:38 -0700 Finished at: Mon 10 Mar 2008 06:45:59 -0700 Total time: 1h 25m 20s Build Trigger: Schedule Build Number: 106 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version 1.5.0_12 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) Builder version : Maven version: 2.0.7 Java version: 1.5.0_12 OS name: linux version: 2.6.20-16-server arch: i386 SCM Changes: Changed: jsdelfino @ Mon 10 Mar 2008 02:50:28 -0700 Comment: Added a service to CompositeCollection to help redirect to composite source files. Minor UI fixes. Files changed: /incubator/tuscany/java/sca/modules/workspace-admin/src/main/java/org/apache/tuscany/sca/workspace/admin/impl/CompositeCollectionImpl.java ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/java/org/apache/tuscany/sca/workspace/admin/impl/DeployableCollectionImpl.java ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/resources/Admin.composite ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/resources/admin.css ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/resources/files.html ( 635503 ) Changed: jsdelfino @ Mon 10 Mar 2008 02:52:13 -0700 Comment: Added a program to launch all nodes of the tutorial. Fixed hrefs to shopping cart feeds. Files changed: /incubator/tuscany/java/sca/tutorial/assets/tutorial.html ( 635504 ) /incubator/tuscany/java/sca/tutorial/nodes/launch/LaunchAllTutorialNodes.java ( 635504 ) /incubator/tuscany/java/sca/tutorial/store/store.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-db/store-db.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-eu/store-eu.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-merger/store-merger.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-supplier/store-supplier.composite ( 635504 ) Changed: jsdelfino @ Mon 10 Mar 2008 03:05:43 -0700 Comment: Removed extraneous '/' at beginning of URI. Files changed: /incubator/tuscany/java/sca/modules/binding-ws-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceProvider.java ( 635507 ) Dependencies Changes: No dependencies changed Build Defintion: POM filename: pom.xml Goals: -Pdistribution clean install Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Java 5, Large Memory Description: Test Summary: Tests: 1063 Failures: 0 Total time: 1057489 Build Error: org.apache.maven.continuum.execution.ContinuumBuildCancelledException: The build was cancelled at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:216) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.build(MavenTwoBuildExecutor.java:149) at org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute(ExecuteBuilderContinuumAction.java:140) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:417) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:156) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at
[continuum] BUILD ERROR: Apache Tuscany SCA Implementation Project
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=63406projectId=277 Build statistics: State: Error Previous State: Building Started at: Mon 10 Mar 2008 05:20:38 -0700 Finished at: Mon 10 Mar 2008 06:45:59 -0700 Total time: 1h 25m 20s Build Trigger: Schedule Build Number: 106 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version 1.5.0_12 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04) Java HotSpot(TM) Client VM (build 1.5.0_12-b04, mixed mode, sharing) Builder version : Maven version: 2.0.7 Java version: 1.5.0_12 OS name: linux version: 2.6.20-16-server arch: i386 SCM Changes: Changed: jsdelfino @ Mon 10 Mar 2008 02:50:28 -0700 Comment: Added a service to CompositeCollection to help redirect to composite source files. Minor UI fixes. Files changed: /incubator/tuscany/java/sca/modules/workspace-admin/src/main/java/org/apache/tuscany/sca/workspace/admin/impl/CompositeCollectionImpl.java ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/java/org/apache/tuscany/sca/workspace/admin/impl/DeployableCollectionImpl.java ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/resources/Admin.composite ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/resources/admin.css ( 635503 ) /incubator/tuscany/java/sca/modules/workspace-admin/src/main/resources/files.html ( 635503 ) Changed: jsdelfino @ Mon 10 Mar 2008 02:52:13 -0700 Comment: Added a program to launch all nodes of the tutorial. Fixed hrefs to shopping cart feeds. Files changed: /incubator/tuscany/java/sca/tutorial/assets/tutorial.html ( 635504 ) /incubator/tuscany/java/sca/tutorial/nodes/launch/LaunchAllTutorialNodes.java ( 635504 ) /incubator/tuscany/java/sca/tutorial/store/store.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-db/store-db.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-eu/store-eu.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-merger/store-merger.composite ( 635504 ) /incubator/tuscany/java/sca/tutorial/store-supplier/store-supplier.composite ( 635504 ) Changed: jsdelfino @ Mon 10 Mar 2008 03:05:43 -0700 Comment: Removed extraneous '/' at beginning of URI. Files changed: /incubator/tuscany/java/sca/modules/binding-ws-axis2/src/main/java/org/apache/tuscany/sca/binding/ws/axis2/Axis2ServiceProvider.java ( 635507 ) Dependencies Changes: No dependencies changed Build Defintion: POM filename: pom.xml Goals: -Pdistribution clean install Arguments: --batch-mode Build Fresh: false Always Build: false Default Build Definition: true Schedule: DEFAULT_SCHEDULE Profile Name: Java 5, Large Memory Description: Test Summary: Tests: 1063 Failures: 0 Total time: 1057489 Build Error: org.apache.maven.continuum.execution.ContinuumBuildCancelledException: The build was cancelled at org.apache.maven.continuum.execution.AbstractBuildExecutor.executeShellCommand(AbstractBuildExecutor.java:216) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.build(MavenTwoBuildExecutor.java:149) at org.apache.maven.continuum.core.action.ExecuteBuilderContinuumAction.execute(ExecuteBuilderContinuumAction.java:140) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.performAction(DefaultBuildController.java:417) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:156) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:50) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable$1.run(ThreadedTaskQueueExecutor.java:116) at edu.emory.mathcs.backport.java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:442) at edu.emory.mathcs.backport.java.util.concurrent.FutureTask.run(FutureTask.java:176) at
[jira] Closed: (TUSCANY-1952) Domain broken after stopping+starting a node
[ https://issues.apache.org/jira/browse/TUSCANY-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-1952. --- Resolution: Won't Fix The store tutorial now uses a different mechanism for parsing contributions and starting nodes Domain broken after stopping+starting a node - Key: TUSCANY-1952 URL: https://issues.apache.org/jira/browse/TUSCANY-1952 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Reporter: Jean-Sebastien Delfino Assignee: Simon Laws Fix For: Java-SCA-Next The SCA domain seems to be unusable after a node is stopped then started again. Steps to reproduce the problem: 1. From the tutorial/cloud module start LaunchCloud.java, it'll start some services and a domain controller. 2. From the tutorial/store module start LaunchStore.java, it'll start the store composite. 3. Point your Web browser to http://localhost:8100/ui/store.html your should see the store UI showing a catalog of fruits 4. Stop LaunchStore by pressing Ctrl+C 5. Do steps 2 and 3 again, you won't see the catalog anymore. None of the services seem to properly register/resolve in the domain anymore. -- 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-1957) Domain controller incorrectly loading contributions added to nodes.
[ https://issues.apache.org/jira/browse/TUSCANY-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-1957. --- Resolution: Won't Fix The store tutorial now uses a different mechanism for parsing contributions and starting nodes Domain controller incorrectly loading contributions added to nodes. --- Key: TUSCANY-1957 URL: https://issues.apache.org/jira/browse/TUSCANY-1957 Project: Tuscany Issue Type: Bug Affects Versions: Java-SCA-1.1 Reporter: Jean-Sebastien Delfino Fix For: Java-SCA-Next Very weird behavior of the domain controller, which seems to want to load contributions in its memory as they are added to nodes running on different JVMs. I must admit I'm puzzled... To reproduce the problem use SVN revision r610601 of the trunk, use the tutorial modules: - from the cloud module start LaunchCloud - from the store-db module start LaunchStoreDB Here's the output from LaunchCloud showing that it's incorrectly trying to load the store-db contribution (as it's added to the node in LaunchStoreDB) and BTW failing to do load it properly (see all the composite builder problems showing in the output). Starting ... Jan 9, 2008 1:43:14 PM org.apache.tuscany.sca.domain.impl.SCADomainImpl init INFO: Domain management configured from file:/home/delfinoj/Tuscany/apache-repos/java/sca/modules/domain-impl/target/classes/ Jan 9, 2008 1:43:19 PM org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:9998/domain/* Jan 9, 2008 1:43:19 PM org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:9998/SCADomainManagerComponent/SCADomainManagerService/* Jan 9, 2008 1:43:19 PM org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:9998/SCADomainManagerComponent/SCADomainManagerService Jan 9, 2008 1:43:19 PM org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:9998/SCADomain/scaDomain.js Jan 9, 2008 1:43:19 PM org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:9998/SCADomainManagerComponent/SCADomainEventService Domain controller ready for big business !!! Jan 9, 2008 1:43:19 PM org.apache.tuscany.sca.http.jetty.JettyServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:9998/SCADomainManagerComponent/SCADomainAPIService Jan 9, 2008 1:43:20 PM org.apache.tuscany.sca.domain.impl.SCADomainImpl registerNode INFO: Registered node: http://localhost:8200/cloud at endpoint http://localhost:8200/cloud Jan 9, 2008 1:43:20 PM org.apache.tuscany.sca.node.impl.SCADomainProxyImpl createRuntime INFO: Domain management configured from file:/home/delfinoj/Tuscany/apache-repos/java/sca/modules/node-impl/target/classes/ Jan 9, 2008 1:43:22 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.10 Jan 9, 2008 1:43:22 PM org.apache.catalina.startup.ContextConfig defaultWebConfig INFO: No default web.xml Jan 9, 2008 1:43:22 PM org.apache.catalina.startup.DigesterFactory register WARNING: Could not get url for /javax/servlet/jsp/resources/jsp_2_0.xsd Jan 9, 2008 1:43:22 PM org.apache.catalina.startup.DigesterFactory register WARNING: Could not get url for /javax/servlet/jsp/resources/web-jsptaglibrary_2_0.xsd Jan 9, 2008 1:43:23 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8200 Jan 9, 2008 1:43:23 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8200 Jan 9, 2008 1:43:23 PM org.apache.tuscany.sca.http.tomcat.TomcatServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:8200/cloud/SCADomainEventServiceProxyComponent Jan 9, 2008 1:43:23 PM org.apache.tuscany.sca.http.tomcat.TomcatServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:8200/cloud/SCADomainAPIServiceProxyComponent Jan 9, 2008 1:43:23 PM org.apache.tuscany.sca.http.tomcat.TomcatServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:8200/cloud/SCANodeManagerComponent/SCANodeManagerService Jan 9, 2008 1:43:23 PM org.apache.tuscany.sca.http.tomcat.TomcatServer addServletMapping INFO: Added Servlet mapping: http://delfinoj60.burlingame.ibm.com:8200/cloud/SCANodeManagerComponent/ComponentManagerService/* Jan 9, 2008 1:43:23 PM org.apache.tuscany.sca.http.tomcat.TomcatServer addServletMapping INFO: Added
[jira] Closed: (TUSCANY-1779) Determining the contribution location (confusion over relative location URLs)
[
https://issues.apache.org/jira/browse/TUSCANY-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-1779.
---
Resolution: Won't Fix
There is now a new mechanism (workspace) for locating and parsing
contributions and for configuring nodes
Determining the contribution location (confusion over relative location URLs)
-
Key: TUSCANY-1779
URL: https://issues.apache.org/jira/browse/TUSCANY-1779
Project: Tuscany
Issue Type: Bug
Components: Java SCA Core Runtime
Affects Versions: Java-SCA-1.0
Environment: All
Reporter: Simon Laws
Fix For: Java-SCA-Next
SCADomain, in both of its guises, allows the details of which contribution to
load to be specified.
the standalone version
o.a.t.s.host.embedded.SCADomain.newInstance(String domainURI, String
contributionLocation, String... composites)
and the distributed version
o.a.t.s.domain.SCADomain.newInstance(String domainURI, String nodeURI, String
contributionLocation, String... composites) {
I have found this confusing so, by looking at the code, here is what I think
the rules are;
contributionLocation - an absolute path to a contribution in URL form, e.g
file://C:/mydirA
jar:file://C:/myjar.jar
composite(s) - the name of a composite file(s) e.g.
mycomposite.composite
somedir/mycomposite.composite
So the various combinations give rise to
contributionLocation set / composite null
loads all contributions under the contribution location identified
contributionLocation null / composite set
finds the location of your compsite on the classpath and uses that as the
contribution location. It loads the named composite from there
contributionLocation / composite
loads the named composite from the specified contribution path
contributionLocation null / composite null
This option is also used if the above rules don't identify a contribution
URL for whatever reason.
No contribution has been specified so look for the following in order and
use the location of the first one found as the contribution location
META-INF/sca-contribution.xml
META-INF/sca-contribution-generated.xml
META-INF/sca-deployables directory
The slight wrinkle with the code currently is that the algorithm is coded
such that if you specify a relative ContributionLocation (which is not valid
according to what I have set out above) then it is simply ignored and the
algorithm falls back to the other mechanisms for finding the contribution
location with potentially confusing results, for example, if I use the
reasonable looking
SCADomain domain = SCADomain.newInstance(http://localhost:8080;,
somedir/someotherdir, some.composite);
Then this will actually just look on the classpath for some.composite
which is probably not what was expected.
We could fix this in code by not testing for an absolute contribution
location path and letting it throw a malformed url exception. However this
doesn't seem absolutely essential to be done right now so I propose to raise
a JIRA and tidy up the above as a section in the documentation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (TUSCANY-2070) @ConversationAttributes(singlePrincipal=false) is not yet implemented
@ConversationAttributes(singlePrincipal=false) is not yet implemented - Key: TUSCANY-2070 URL: https://issues.apache.org/jira/browse/TUSCANY-2070 Project: Tuscany Issue Type: Improvement Reporter: Simon Laws Priority: Minor The @ConversationAttributes(singlePrincipal=false) attribute is not yet implemented. See SCA Java Annotations and APIs spec section 1.8.18 -- 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-1958) Domain controller does not correctly resolve remote services
[ https://issues.apache.org/jira/browse/TUSCANY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-1958. --- Resolution: Won't Fix The store tutorial now uses a different mechanism for parsing contributions and starting nodes Domain controller does not correctly resolve remote services Key: TUSCANY-1958 URL: https://issues.apache.org/jira/browse/TUSCANY-1958 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-Next Reporter: Jean-Sebastien Delfino Fix For: Java-SCA-Next This seems to be random, some modules have the issue, some don't. I have spent hours in the whole domain controller / registration / resolution machinery and I'm not able to understand what's going on. To reproduce the problem use SVN revision r610601 of the trunk, and use the tutorial modules: - from the cloud module start LaunchCloud - from the store-db module start LaunchStoreDB - point your Web browser to http://localhost:8102/ui/store.html. The Catalog component will fail to invoke the CloudVegetableCatalog service with an Axis2 fault wrappering an HTTP 404 error. -- 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-1511) Conversational - spec funnies and other improvements
[ https://issues.apache.org/jira/browse/TUSCANY-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws closed TUSCANY-1511. --- Resolution: Fixed Fix Version/s: (was: Java-SCA-Next) Java-SCA-1.2 Closing this general tracking JIRA and opening two specific JIRA for those issues that remain outstanding. http://issues.apache.org/jira/browse/TUSCANY-2070 http://issues.apache.org/jira/browse/TUSCANY-2071 Conversational - spec funnies and other improvements Key: TUSCANY-1511 URL: https://issues.apache.org/jira/browse/TUSCANY-1511 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Environment: All Reporter: Simon Laws Assignee: Simon Laws Priority: Minor Fix For: Java-SCA-1.2 We closed http://issues.apache.org/jira/browse/TUSCANY-1377 when we got to the stage where conversation support was basically back up and running. There are still some outstanding issues recorded against that report that come down to lack of clarity in the spec and/or are awaiting other bits of the Tuscany runtime to be completed. Here is the list so far. Features Currently Supported --- @Conversational - service callback interfaces @Scope(CONVERSATION) @Scope(STATELESS) @Init @Destroy @ConversationAttributes(maxAge=2 days, maxIdleTime=5 minutes ) @ConversationId @EndsConversation - service and callback interfaces ServiceReference getConversationID() setConversationID(Object) CallableReference (can be persisted,can be passed) isConversational() getConversation() Conversation getConversationID() end() ConversationEndedException Restrictions And Required Clarifications The specification is not clear on a number of points related to Stateful callbacks. 1/ In the current implementation the spec has been interpreted to mean that the client component, i.e. the component implementing the callback interface, must be marked as conversational in order that callback messages return to the same instance of the client component that originated the conversational call. In this case the target of a callback (the source of the original message) has to be stored against a conversationId so that the callback can find it and invoke the callback operation on it. Currently, at the source component, the incoming conversationid is reused for outgoing messages to allow this to happen (the component instance will automatically have been registered against this id when it was created). A better solution would be to allow the reference logic to always create a new conversation id (or accept a user defined conversation id) but, for stateful callbacks this implies that the source component instance has to be registered against multiple conversation ids in the conversational scope container. As pumbing this in is a little tricky we need discuss round alternative solutions. 2/ The spec isn't explicit about what happens at the server when Conversation.end() is used on the target service. In the current implementation it will not free any resources held at the target. A protocol is required between source and target to carry this end() instruction. As it stands the target conversation will eventually time out. Subsequent requests to the target will create a new conversation. 3/ @EndsConversation on the target component where a stateful callback is defined will end the callback conversation at the target only, I.e. the component instance representing the conversation at the source end will remain in place. It remains until the callback calls an @EndConversation annotated message. This is tricky because the source component instance may have been created as part of another conversation which hasn't ended yet. Not clear whether the intention of the spec is to get both to happen at once. The specification also talks about the ability to pass round references that refer to ongoing conversations. No passing of services references, referring to conversational services, is currently supported. This is primarily because the service reference is not currently serializeable but the spec could also benefit from some clarrification in this area. For example, If a callable reference is passed off to another service how does that callable reference know what the state of the conversation is? There are also a few other pieces that are awaiting the completion of other bits of work. @Scope(COMPOSITE) excluded due to ML
[jira] Created: (TUSCANY-2071) @ConversationId injection in @Scope(Composite) services
@ConversationId injection in @Scope(Composite) services --- Key: TUSCANY-2071 URL: https://issues.apache.org/jira/browse/TUSCANY-2071 Project: Tuscany Issue Type: Improvement Reporter: Simon Laws Priority: Minor Injecting @ConversationId into @Scope(COMPOSITE) service is problematic due to potential multi-threaded operation. This is true for any information that is injected into a service instance. This has been discussed on the Tuscany ML here (http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg20573.html). There has also been a dependency reinjection discussion and related JIRA (http://www.osoa.org/jira/browse/JAVA-4) over at the OASIS Java TC for a while. We need to make sure we do something sensible in the context of the results of the OASIS conversations. A follow on from the general conversation JIRA (https://issues.apache.org/jira/browse/TUSCANY-1511) -- 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-1162) Contribution Services - Enhance contribution repository
[ https://issues.apache.org/jira/browse/TUSCANY-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577029#action_12577029 ] Simon Laws commented on TUSCANY-1162: - Is this covered by what Sebastien has been doing with the workspace? Contribution Services - Enhance contribution repository --- Key: TUSCANY-1162 URL: https://issues.apache.org/jira/browse/TUSCANY-1162 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Affects Versions: Java-SCA-M2 Reporter: Luciano Resende Assignee: Luciano Resende Priority: Minor Fix For: Java-SCA-Next - Enhance and extend contribution repository - add contribute application (like launcher) - allow long lived contributions -- 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] Assigned: (TUSCANY-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws reassigned TUSCANY-2056: --- Assignee: Simon Laws Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws Key: TUSCANY-2056 URL: https://issues.apache.org/jira/browse/TUSCANY-2056 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk 1.5.0_10 Reporter: Daniel Stucky Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: test.zip This problem is related to TUSCANY-2028. It is exactly the same use case, but instead of the default binding (sca) I now use binding.ws. And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I guess the fix that went into Tuscany 1.1 did only affect binding.sca and not binding.ws. -- 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-2056) Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws
[ https://issues.apache.org/jira/browse/TUSCANY-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577038#action_12577038 ] Simon Laws commented on TUSCANY-2056: - Hi Daniel I just tried this against the code in Trunk and see the following output... test.composite ready !!! Alpha: Conversation to gamma is null Gamma:doSomething(), conversationId=a666d42e-92a1-46cf-89a3-572a5bd9252a Alpha: Conversation to gamma exists. conversationId=a666d42e-92a1-46cf-89a3-572a5bd9252a Gamma:stop(), conversationId=a666d42e-92a1-46cf-89a3-572a5bd9252a Stopping ... Are you able to do the same and see if you still see a different conversationIds. Simon Conversation does not continue if a Service Reference is passed as a return value (not as a parameter) when using binding.ws Key: TUSCANY-2056 URL: https://issues.apache.org/jira/browse/TUSCANY-2056 Project: Tuscany Issue Type: Bug Components: Java SCA Core Runtime Affects Versions: Java-SCA-1.1 Environment: Windows XP SP2, Intel Core 2 CPU, 2.6, 2GB Ram, jdk 1.5.0_10 Reporter: Daniel Stucky Assignee: Simon Laws Fix For: Java-SCA-Next Attachments: test.zip This problem is related to TUSCANY-2028. It is exactly the same use case, but instead of the default binding (sca) I now use binding.ws. And as in Tuscany 1.0.1 with binding.sca the Conversation is not reused. So I guess the fix that went into Tuscany 1.1 did only affect binding.sca and not binding.ws. -- 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-2070) @ConversationAttributes(singlePrincipal=false) is not yet implemented
[ https://issues.apache.org/jira/browse/TUSCANY-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Laws updated TUSCANY-2070: Description: The @ConversationAttributes(singlePrincipal=false) attribute is not yet implemented. See SCA Java Annotations and APIs spec section 1.8.18. A follow on from the previous general conversation related JIRA (https://issues.apache.org/jira/browse/TUSCANY-1511) was:The @ConversationAttributes(singlePrincipal=false) attribute is not yet implemented. See SCA Java Annotations and APIs spec section 1.8.18 @ConversationAttributes(singlePrincipal=false) is not yet implemented - Key: TUSCANY-2070 URL: https://issues.apache.org/jira/browse/TUSCANY-2070 Project: Tuscany Issue Type: Improvement Reporter: Simon Laws Priority: Minor The @ConversationAttributes(singlePrincipal=false) attribute is not yet implemented. See SCA Java Annotations and APIs spec section 1.8.18. A follow on from the previous general conversation related JIRA (https://issues.apache.org/jira/browse/TUSCANY-1511) -- 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: About StAXArtifactProcessor
I was going to take a quick look at this, but before I do, let me ask if svn revision #635604 is related to the issue you are asking here. On Mon, Mar 10, 2008 at 2:40 AM, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I recently faced a situation where I wished to passed some context from one StAXArtifact Processor to others down the chain. More specifically, to get the 'targetNamespace' of the definitions.xml file apply to PoliyIntent and PolicySet names, I wished to pass the 'targetNamespace' value from the Definitions Processor (which is where it is read) down to the PolicyIntent and PolicySet processors. I could not figure out a way to do this. Am I missing something here or would it make sense to add an argument named 'context' to the read methods of our StAXProcessor ? I guess there could be other situations when we might need some information from parent element to be passed down. Thoughts ? Thanks - Venkat -- 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]
Splitting up the bigbank demo
Hi Luciano, I have split up the bigbank demo into two. 1) bigbank and 2) bigbank-account. The bigbank is the facade to the users and the bigbank-account is the account management module used by the bigbank. I have also pulling in policies and security - whatever that has been working with the secure-bigbank demo. Now that there are two contributions - bigbank and bigbank-account, am a bit lost getting this going with multiple contributions. I have looked up the itests for imports and exports and followed as much the same for this demo, but things don't seem to work. Could you please take a quick look into this and let me know the thing I am missing in all of this ? I have commented out the bigbank demo from the build though it seems to build successfully locally. I will include it back after I have got it to run as a demo. Thanks - Venkat
How can I get a list of effective policySets for a given operation?
Hi, If I have the (component, service/reference, binding, operation) model instances handy, how can I get a list of effective policySets for the operation? Are we consolidating the declarations at different levels to the binding? We can use the following example (I intentionally omit the @requires). component name=MyComponent policySets=ns1:PS1 service name=MyService policySets=ns1:PS2 operation name=op1 policySets=ns1:PS3 binding.xyz policySets=ns1:PS4 ns2:PS5 operation name=op1 policySets=ns1:PS6 /binding.xyz /service /component Thanks, Raymond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Splitting up the bigbank demo
I have updated the client application to start components from composite after all contributions have been contributed (revision #635652), but now I'm getting other issues, that might be unrelated. Please let me know if this helps, and if the issue I'm seeing is related or not. *** Calling BIG-BANK Passwd Handler for setting AUTHENTICATION password *** Calling ACCOUNTS-DATA Passwd Handler for AUTHENTICATING userID = bbaservice and password = bbaservice AUTHENTICATION SUCCESSFUL! org.osoa.sca.ServiceRuntimeException: Target fault type cannot be resolved: null at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:134) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:287) at org.apache.tuscany.sca.core.invocation.JDKInvocationHandler.invoke(JDKInvocationHandler.java:155) at $Proxy11.getAccountDetails(Unknown Source) at bigbank.account.AccountServiceImpl.getAccountReport(AccountServiceImpl.java:65) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.tuscany.sca.implementation.java.invocation.JavaImplementationInvoker.invoke(JavaImplementationInvoker.java:109) at org.apache.tuscany.sca.core.databinding.wire.PassByValueInterceptor.invoke(PassByValueInterceptor.java:108) at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:114) at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:89) at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:83) at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:134) at org.apache.tuscany.sca.binding.jsonrpc.JSONRPCServiceServlet.handleJSONRPCMethodInvocation(JSONRPCServiceServlet.java:235) at org.apache.tuscany.sca.binding.jsonrpc.JSONRPCServiceServlet.handleServiceRequest(JSONRPCServiceServlet.java:147) at org.apache.tuscany.sca.binding.jsonrpc.JSONRPCServiceServlet.service(JSONRPCServiceServlet.java:89) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:842) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:648) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:380) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:395) at org.apache.tuscany.sca.core.work.Jsr237Work.run(Jsr237Work.java:61) at org.apache.tuscany.sca.core.work.ThreadPoolWorkManager$DecoratingWork.run(ThreadPoolWorkManager.java:214) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.tuscany.sca.interfacedef.util.FaultException: unknown at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invoke(Axis2BindingInvoker.java:97) at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:78) ... 35 more Caused by: org.apache.axis2.AxisFault: unknown at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486) at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343) at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389) at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211) at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163) at org.apache.tuscany.sca.binding.ws.axis2.Axis2BindingInvoker.invokeTarget(Axis2BindingInvoker.java:118) at
Re: Asia Open Source Symposium Code Fest is looking for help, was Fwd: Low hanging bugs for students
FYI, here is a post [1] from J. Aaron about what happened on the AOSS Code Fest. [1] http://cubiclemuses.com/cm/blog/2008/codefest.html 2008/3/5 Luciano Resende [EMAIL PROTECTED]: Please review the page with the suggestions discussed on this thread. I plan to send this tomorrow for the event organizer. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Asia+Open+Source+Symposium%0D%0AAsia+Open+Source+Symposium+Code+Fest 2008/3/5 Luciano Resende [EMAIL PROTECTED]: We need to get something proposed really soon, as the event is over the weekend. I'd suggest the JIRAs under Tools and Sample categories, but make it open if someone wants to address JIRAs in any other area. As for projects, we could identify projects that need enhanced testing (e.g implementation-data-xml). Thoughts ? 2008/3/4 haleh mahbod [EMAIL PROTECTED]: this is only a 2 day event. Can you identify a project that can be done in such a short time? That would be great. On 3/4/08, Venkata Krishnan [EMAIL PROTECTED] wrote: My 2c. More than bugs it would be interesting for the students if we could suggest some minor enhancements to our tools or extensions. - Venkat 2008/3/5 haleh mahbod [EMAIL PROTECTED]: It looks like they are looking for short, 1-2 day, projects to expose students to how to provide patches in open source. How about suggesting a few of sample bugs for this exercise? This will expose the students to Tuscany and show them how to run samples. This will also give them a chance to fix smaller scoped problems and gain the experience that is looked for. On 3/3/08, Luciano Resende [EMAIL PROTECTED] wrote: This is a good opportunity for increasing awareness for Apache Tuscany. We could identify some JIRAs and/or very small projects (e.g enhancements to specific extensions) that we could send to J Aaron Farr to be used with the Chinese students. Thoughts ? Any suggestions ? -- Forwarded message -- From: J Aaron Farr [EMAIL PROTECTED] Date: Mon, Mar 3, 2008 at 1:27 AM Subject: Low hanging bugs for students To: Apache Community [EMAIL PROTECTED] This next weekend I'm going to be at the Asia Open Source Symposium Code Fest. What was going to be a hackathon-like event is now a student focused event with something like 50 university students attending for two days to learn something about open source. So now I'm trying to come up with ideas on what to have these students do. My preference is to have the students work on a bunch of patches over two days rather than work on a single application to be released at the end of the event. To me, the patch process is a fairly unique open source skill, so that's what I want to emphasize. I already have some bugs, features and code in mind, most related to the ApacheCon website. But if anyone has some ideas of other low hanging bugs or features that I could task a few students with, please let me know. Think of it as a two-day summer of code. If anyone has any other thoughts or suggestions, please pass them on. Thanks! -- J Aaron Farr jadetower.com[US] +1 724-964-4515 馮傑仁 cubiclemuses.com [HK] +852 8123-7905 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ -- 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
Re: svn commit: r635435 - in /incubator/tuscany/java/sca/modules: assembly/src/main/java/org/apache/tuscany/sca/assembly/builder/impl/ assembly/src/test/java/org/apache/tuscany/sca/assembly/builder/im
Simon Laws wrote: Hi There is now a test in the binding name creation code that checks that two service bing types are the same before testing for duplicate names. I don't think the binding type is relevant here. We should actually be testing that the scheme that the bindings intend to use are the same but that information is not easily available. With the current change we can say binding.ws name=fred/ binding.jsonrpc name=fred/ and I don't believe the code will complain. and that's OK I think :) as binding.ws and binding.jsonrpc could end up on different port numbers for example (depending on their node configuration). Actually, I was struggling to understand why we needed this test for duplicate names at all. Does the spec forbids two bindings with the same name? By trying hard to detect duplicate names early on (without having all the info about what the binding URIs will end up to be), won't we raise errors even for cases that should work? One example of the issues I was running into: service... binding.jsonrpc/ binding.ws uri=/whatever /service throwing a duplicate name exception as the two bindings had the same name. On a fun note, I think that: service name=aservice binding.jsonrpc name=whatever/ binding.ws uri=/whatever /service would probably not have thrown an exception, but should have :) So my recommendation would be to not try too hard to detect these duplicates early on based on binding names (as the detection algorithm is too fragile at that point), instead detect duplicates at the very end when we see that we end up with duplicate URIs. Also can you give a quick example the problems you found relating to avoid adding binding name to itself, and consider binding URI when specified in the composite in the single service case too so I can understand the other code changes. One issue was that the code was not considering the binding URI when there was only one service on a component, for example IIRC: component name=Store service name=Widget binding.http uri=/ui/ /service /component was bound to /Store (the component URI) instead of /ui. I understand that the binding name should be omitted from the computed URI in the single service case, but the binding URI should be considered if specified, leading to the requirement to distinguish between binding name (always know, not always considered) and binding URI (not always specified, always considered when specified). About the adding the binding name to itself part, this is a little complicated. IIRC the issue was that CompositeConfigurationBuilder would first convert: component name=Foo service... binding.sca/ /service /component into: component name=Foo service... binding.sca uri=Foo/ /service /component Then when an SCANode would consume that, CompositeBuilder.build would turn it into: component name=Foo service... binding.sca uri=Foo/Foo/ /service /component as I think the old CompositeConfigurationBuilder code used in that case used to concatenate the component URI and the binding URI. Thanks Simon -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Support for binding config in definitions.xml
Venkata Krishnan wrote: Hi Ant, I suppose this is going to simply use the StAX processor that we currently have for jms binding. That being the case I see there is going to be circular dependency issues I may be able to help with the circular dependencies issues, could you help me understand what circular dependencies you are seeing? -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Suggestion for Replying with comments to a specific committ
It would be great if people could start changing the subject when replying with comments to a given committs, this would allow others to better identify what's going on and possible jump and help on the discussion. Just my 2c Thanks -- 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]
[DISCUSS] Using Feedback from Asia OS Code Fest WAS Fwd: Asia Open Source Symposium Code Fest is looking for help,
There is positive feedback on Tuscany from J. Aaron who conducted Asia OS Tuscany Code fest session [1]. Some comments are: One interesting observation was that the Tuscany team (students) got started faster thanks to good project documentation and fewer software prerequisites. However, they (students) ended up picking a bug that might have been a little too tricky given the time (2 days) we had to solve it. ... ... Frameworks can only do so much in helping to eliminate the fundamental costs of the Java development cycle... The framework topic raises the question if there is a way to further enhance development documentation and simplify the environment to help new developers come on board quickly? I'd like to propose that we create a list of what might be useful/helpful. It would be great to hear the challenges that new developers might be running into. Are you getting what you need to get started? If not, what would help. Here is my observation for what would help me. Please add. - Mid level module structure for SCA and key debug break points (entry and exit) for core and extensions using a simple sample as an example [1] http://cubiclemuses.com/cm/blog/2008/codefest.html -- Forwarded message -- From: Luciano Resende [EMAIL PROTECTED] Date: Mar 10, 2008 12:20 PM Subject: Re: Asia Open Source Symposium Code Fest is looking for help, was Fwd: Low hanging bugs for students To: tuscany-dev@ws.apache.org FYI, here is a post [1] from J. Aaron about what happened on the AOSS Code Fest. [1] http://cubiclemuses.com/cm/blog/2008/codefest.html 2008/3/5 Luciano Resende [EMAIL PROTECTED]: Please review the page with the suggestions discussed on this thread. I plan to send this tomorrow for the event organizer. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Asia+Open+Source+Symposium%0D%0AAsia+Open+Source+Symposium+Code+Fest 2008/3/5 Luciano Resende [EMAIL PROTECTED]: We need to get something proposed really soon, as the event is over the weekend. I'd suggest the JIRAs under Tools and Sample categories, but make it open if someone wants to address JIRAs in any other area. As for projects, we could identify projects that need enhanced testing (e.g implementation-data-xml). Thoughts ? 2008/3/4 haleh mahbod [EMAIL PROTECTED]: this is only a 2 day event. Can you identify a project that can be done in such a short time? That would be great. On 3/4/08, Venkata Krishnan [EMAIL PROTECTED] wrote: My 2c. More than bugs it would be interesting for the students if we could suggest some minor enhancements to our tools or extensions. - Venkat 2008/3/5 haleh mahbod [EMAIL PROTECTED]: It looks like they are looking for short, 1-2 day, projects to expose students to how to provide patches in open source. How about suggesting a few of sample bugs for this exercise? This will expose the students to Tuscany and show them how to run samples. This will also give them a chance to fix smaller scoped problems and gain the experience that is looked for. On 3/3/08, Luciano Resende [EMAIL PROTECTED] wrote: This is a good opportunity for increasing awareness for Apache Tuscany. We could identify some JIRAs and/or very small projects (e.g enhancements to specific extensions) that we could send to J Aaron Farr to be used with the Chinese students. Thoughts ? Any suggestions ? -- Forwarded message -- From: J Aaron Farr [EMAIL PROTECTED] Date: Mon, Mar 3, 2008 at 1:27 AM Subject: Low hanging bugs for students To: Apache Community [EMAIL PROTECTED] This next weekend I'm going to be at the Asia Open Source Symposium Code Fest. What was going to be a hackathon-like event is now a student focused event with something like 50 university students attending for two days to learn something about open source. So now I'm trying to come up with ideas on what to have these students do. My preference is to have the students work on a bunch of patches over two days rather than work on a single application to be released at the end of the event. To me, the patch process is a fairly unique open source skill, so that's what I want to emphasize. I already have some bugs, features and code in mind, most related to the ApacheCon website. But if anyone has some ideas of other low hanging bugs or features that I could task a few students with, please let me know. Think of it as a two-day summer of code. If anyone has any other thoughts or suggestions, please
Re: About StAXArtifactProcessor
Maybe you could describe a little more what is the issue you are having, and we could try helping finding another solution for your issue, particularly related to targetNamespace, as it might be available trough the parser API. Also, I usually try to avoid context objects, as they usually grow out of control very fast causing various side effects. On Mon, Mar 10, 2008 at 10:39 AM, Luciano Resende [EMAIL PROTECTED] wrote: I was going to take a quick look at this, but before I do, let me ask if svn revision #635604 is related to the issue you are asking here. On Mon, Mar 10, 2008 at 2:40 AM, Venkata Krishnan [EMAIL PROTECTED] wrote: Hi, I recently faced a situation where I wished to passed some context from one StAXArtifact Processor to others down the chain. More specifically, to get the 'targetNamespace' of the definitions.xml file apply to PoliyIntent and PolicySet names, I wished to pass the 'targetNamespace' value from the Definitions Processor (which is where it is read) down to the PolicyIntent and PolicySet processors. I could not figure out a way to do this. Am I missing something here or would it make sense to add an argument named 'context' to the read methods of our StAXProcessor ? I guess there could be other situations when we might need some information from parent element to be passed down. Thoughts ? Thanks - Venkat -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is it possible to define a customizable value for an intent or policy?
ant elder wrote: On Fri, Mar 7, 2008 at 12:01 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: On Wed, Mar 5, 2008 at 9:46 AM, ant elder [EMAIL PROTECTED] wrote: On Tue, Mar 4, 2008 at 6:19 PM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: ant elder wrote: Ok thanks. The binding.ws element is also extensible so this axis2 config could be added as extra attributes or elements there couldn't it, eg binding.ws timeOut=30 /? Which seems simpler if allowed so why is the policySet approach better? binding.ws timeout=30 connections=10 will require you to go open your application jar and change the .composite provided by the application developer to adjust the timeout or number of connections. Policies allow you to configure and adjust qualities of service like timeouts, connection pools etc. without touching the logical composition. -- Jean-Sebastien Ok that makes sense. But how does this compare to say the JMS binding which does support configuring QOS related things (priority, time to live etc) via binding attributes? ...ant No replies yet so I'll expand a little in case i was misunderstood, I'm trying to get better understanding of this area as there's been little on the ML to date and I'd guess it may not be just me thats a bit unclear. One issue is that currently the samples we have just include the definitions.xml file within the contribution so the point about being able configure things externally isn't being demonstrated, maybe this is just a point in time thing as its being implemented in Tuscany. It's a point in time limitation of the sample (not the Tuscany implementation). I think we should improve the bigbank sample to place definitions.xml in a separate contribution. Venkat has been working on it recently so he may already be looking into that? But if its in another contribution then you still have to crack open the jar to alter it so is that so much better than being included within the contribution its applying to? The key word here is another contribution. This allows people with different roles (developer, assembler, administrator) to work on the artifacts that they are interested in in the different contributions that they work with and own. For example with the policy approach you'll be able to resize the connection pools for 100 Web services by making a change to the-admin's-contribution/definitions.xml, without touching at all the 30 application-contributions containing the Web services. BTW a contribution does not have to be a JAR, the domain administrator should be able to contribute a definitions.xml file by pointing to the directory that contain them. Another issue i have with the policySet using an appliesTo xpath for the service is that it's invisible when looking at a contribution, maybe if there was good tooling it would get highlighted in some graphical display but from just looking at the contribution its not obvious so i don't like it so much. If you don't like references to elements outside of your contribution then you'll have a more general issue with many other such references, to WSDLs, other composites, classes etc. which will often be in a different contribution as well. Maybe I'm just not getting what you meant here :) I don't mind explicit references to elements outside the contribution which is why the requestConnection on the jms binding seems more intuitive to me. IMO the ability to apply policySets to services without polluting the logical composition and the application contribution is a key feature. OASIS JIRA POLICY-15 for example introduces the concept of external policy attachements to provide support for that scheme. I think it's much better than referencing policySets directly from the composition artifacts as direct references to policySets will make a composition much more difficult to reuse (for example if you want to change the level of security or connection pool size in different deployments of the same composite). Perhaps you can raise the issues you have with policySets to the OASIS policy spec workgroup? I can see I may want to change the timeout on a reference externally to the contribution but it feels like I'd much more often want to change the actual target endpoint uri on the WS binding but we don't have a way to do that without opening the contribution. IMO endpoint URIs do not change so often, but with SCA wiring and promotion you can (and in most cases should, IMO) limit the configuration of endpoint URIs to domain-level deployment composites. When you do that, you're doing something very similar to what is done for policies in definitions.xml files (which are domain-wide definitions as well). Right, so then when you're doing that why not have the binding just support these extra attributes to avoid the complication of needing the policySet in a definstions.xml :-) There are significant differences between
Component Service Not Coming up.
Hi, I have an issue with the component service not coming up. below mentioned is my scenario. I have a JSP (default.jsp) which does the following: %@ page import=org.apache.tuscany.sca.host.embedded.SCADomain% %@ page contentType=text/html;charset=UTF-8 language=java % % SCADomain scaDomain = SCADomain.newInstance(RunTime.composite); System.out.println(RunTime Composite Started); % and the Runtime.composite is as follows: component name=TwoWSService implementation.java class=eai.Compose / service name=Compose interface=http://eai#wsdl.interface(TwoWSService) / binding.ws uri=http://localhost:8080/TwoWSService; / /service /component Now I create a war of all my Java classes , wsdl , composite files and with the default.jsp as the default run target. This war gets deployed in tomcat and the jsp page comes up. It creates a new instance of Runtime.composite too , but it doesnt seem to be starting the component service which i have mentioned in the composite file : binding.ws uri=http://localhost:8080/TwoWSService; /. What could be wrong in this, Can you please guide me. Regards Sandeep Raman. =-=-= 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: Support for binding config in definitions.xml
Hi Sebastien, If the SCADefinitions model must hold jms binding definitions, I guess it must add the jms binding as a dependency. On the other hand the jms binding already brings in the 'definitions' module as a downsteam dependency. I guess that some cleaning up of the Contribution might ease a bit of things. I am wondering if the 'contribution' module should be devoid of any dependency on definitions, policy and assembly. I am going to give this a stab now. Thanks. - Venkat On Tue, Mar 11, 2008 at 5:47 AM, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: Venkata Krishnan wrote: Hi Ant, I suppose this is going to simply use the StAX processor that we currently have for jms binding. That being the case I see there is going to be circular dependency issues I may be able to help with the circular dependencies issues, could you help me understand what circular dependencies you are seeing? -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
