2008/3/20, Simon Laws (JIRA) <tuscany-dev@ws.apache.org>: > > [ > https://issues.apache.org/jira/browse/TUSCANY-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580743#action_12580743 > ] > > > Simon Laws commented on TUSCANY-2099: > ------------------------------------- > > > Hi Girogio. I've committed the patch. It's difficult to comment in detail > until we have the code working. What I was wondering though is whether new > components really need to be installed dynamically, with all the code > complexity involved, or whether the same effect can be produced by relying on > separate, for example, conversational, instances of the same component for > running jobs.
I don't know. But for example in the first case, it opens the possibility to distribute new components over jvm instances. What I'm not clear on is whether 1) all of the components you start are all of the same type and just run jobs or whether 2) the jobs them selves are components. Looking at the code it seems that 1) is the case. Anyhow I'm not suggesting you change the design on the fly but there may be some opportunities for simplification down the line. Every kind of suggestion is appreciated. The case is 1). > Simon > > > > Porting Workpool-Distributed demo to current. > > --------------------------------------------- > > > > Key: TUSCANY-2099 > > URL: https://issues.apache.org/jira/browse/TUSCANY-2099 > > Project: Tuscany > > Issue Type: New Feature > > Reporter: Giorgio Zoppi > > Assignee: Simon Laws > > Fix For: Java-SCA-Next > > > > Attachments: firstpatch.diff > > > > > > This is the first patch to adapt workpool demo to current. Still it > doens't compile. > > -- > 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]
