Re: [VOTE] Release Tuscany SCA Java 1.0.1-incubating (RC5)
+1, looks good to me. ...ant On Nov 7, 2007 10:35 PM, Raymond Feng [EMAIL PROTECTED] wrote: Hi, Please review and vote on the 1.0.1-incubating release artifacts of Tuscany SCA for Java. The RC5 contains a few fixes to issues discovered in RC4. Thank you for reporting and fixing the issues promptly. SVN Tag: http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0.1-RC5/ Stage maven repo: http://people.apache.org/~rfeng/tuscany/maven/http://people.apache.org/%7Erfeng/tuscany/maven/ RAT report: http://people.apache.org/~rfeng/tuscany/1.0.1-RC5/1.0.1-RC5.rat.txthttp://people.apache.org/%7Erfeng/tuscany/1.0.1-RC5/1.0.1-RC5.rat.txt Distros (zip/gz/asc/md5) : http://people.apache.org/~rfeng/tuscany/1.0.1-RC5/http://people.apache.org/%7Erfeng/tuscany/1.0.1-RC5/ The 1.0.1 release is a bit bumpy with a few RCs in a row. Thank you for your support and hopefully this will be the last one. Here is my +1. Thanks, Raymond - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (TUSCANY-1871) Classloading : Application contribution classloaders
[ https://issues.apache.org/jira/browse/TUSCANY-1871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ant elder closed TUSCANY-1871. -- Resolution: Fixed Classloading : Application contribution classloaders Key: TUSCANY-1871 URL: https://issues.apache.org/jira/browse/TUSCANY-1871 Project: Tuscany Issue Type: Improvement Components: Java SCA Core Runtime Reporter: Rajini Sivaram Assignee: ant elder Attachments: application-classloading-patch.txt Details of the discussion on classloading changes for Tuscany are on the dev mailing list on this thread: http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg24774.html And on the WIKI http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Classloading+in+Tuscany+SCA+Java Changes in this patch introduce separate classloaders for each contribution. SCA contribution import/export spec cannot be implemented using a standard Java parent-child classloader delegation model. But SCA contribution import/export spec is a subset of OSGi package import/export (wiring of import/export is more complex in OSGi since it includes versions and other attributes). Hence an OSGi-style classloader is ideal for Tuscany to enforce SCA contribution spec. Each contribution will have an associated classloader. This will be an subclass of URLClassLoader, and will have the Java application classloader based on CLASSPATH as its parent (the parent classloader will be obtained from the thread context). The defining classloader for any application class will be the classloader corresponding to the SCA contribution containing the class. ContributionClassLoader.findClass will search the contribution for the class, and if not found, it will search other classloaders of other contributions wired using SCA import/export. Like OSGi, an overlapping class space will be defined for each contribution which consists of the classes in the contribution and imported packages from other 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] Commented: (TUSCANY-1804) @OneWay repeted invocations doesn't work in web service binding
[
https://issues.apache.org/jira/browse/TUSCANY-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541275
]
Simon Laws commented on TUSCANY-1804:
-
Some interesting comments from the mail list...
Hi Giorgio
Am just applying your patch to make repeated @OneWay invocations work to the
tunk and it's looking good as I'm getting a clean build and the new onway
itest now runs. (Am just updating your workpool demo to trunk level as well
- more in this later) In the mean time I'm interested in understanding what
was actually going wrong with the axis binding. Looking at the changes you
made there are two main things.
First, setting UseSeparateListener and AUTO_RELEASE_CONNECTION on the
operation client
And setting max number operation for host.
I followed Axis Integrations tests:
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java
http://svn.apache.org/repos/asf/webservices/axis2/trunk/java/modules/integration/test/org/apache/axis2/async/AsyncService2Test.java
because in the Axis2 Ml was debated the use of async call.
Second, creating an HTTPClient if one doesn't already exist,
So, looking at this, it seems that Axis2 was not cleaning up connections
properly after a request and that the default HTTP client was not configured
correctly..
It was long debated on Axis2 ml, that Axis2 and Asynchronous
operations in several operation.
Did you specifically observe what was going on under the covers
to cause the problem?
No. I didn't debug well the axis code, because i saw this AXIS JIRA:
http://issues.apache.org/jira/browse/AXIS2-935
In the patch that i provided there's a problem, in SCA 1.0 my node
SCANodeImpl is different from yours...i found that the application
didn't clean up.
I corrected it in SCANodeImpl, when it calls stop I have:
public void stop() throws ActivationException {
// stop the components
// remove contributions
// Stop the node
nodeRuntime.stop();
//managementRuntime.stop();
// Cleanup the top level composite
nodeComposite = null;
// remove the manager objects
// go out and remove this node from the wider domain
if (isStandalone == false){
try {
domainManager.removeNode(domainUri, nodeUri);
} catch(Exception ex) {
logger.log(Level.SEVERE,
Can't connect to domain manager at: +
domainUrl);
throw new ActivationException(ex);
}
}
--- this lineif (managementRuntime!=null)
managementRuntime.stop();
}
In this way a node exits correctly. BTW Your transformer graph is
cool: the shortest path and giving weight to edges is nice :).
I still use Tuscany SCA 1.0, because a lot is changed in node
management in SCA 1.0.1.
I have the complete workpool ready and its job module binding now.
Now I have to create an autonomic manager for the workpool :). I issue
the JIRA for contributing.
Cheers,
Giorgio.
@OneWay repeted invocations doesn't work in web service binding
---
Key: TUSCANY-1804
URL: https://issues.apache.org/jira/browse/TUSCANY-1804
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.99
Environment: Eclipse/JDK 1.5 / Ubuntu Linux 7.04
Reporter: Giorgio Zoppi
Assignee: Simon Laws
Fix For: Java-SCA-1.0.1
Attachments: patch.diff
i've found the bug that it doens't permit myself to use SCA Binding over
WebService modifying the distributed-calculator. I found it (on Tuscany
1.0 rc3) following the chain towards the wire, and i discovered that
it's an Axis Fault. If you modify in your distributed calculator sample
the SubtractionService in the following way:
@Remotable
public interface SubtractService {
@OneWay
void subtract(double n1, double n2);
}
public class SubtractServiceImpl implements SubtractService {
public void subtract(double n1, double n2) {
System.out.println(SubtractService - subtract + n1 + and
+ n2);
//return n1 - n2;
}
}
I know that it doesn't nothing...but it's a proof of concept.
And in the calculator node:
for (int k = 0; k 10; ++k)
calculatorService.subtract(2*k+3, k);
The nodeC with current Axis2OneWayBindingInvoker, even if it's called 10
times..the receiver gets two messages..
So in the nodeC terminal you can see only for example:
[java] SubtractService - subtract 15.0 and 6.0
[java] SubtractService - subtract 17.0 and 7.0
The reason is due to the Axis HTTP REUSE:
If you change in Axis2OneWayBindingInvoker
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
[jira] Closed: (TUSCANY-1804) @OneWay repeted invocations doesn't work in web service binding
[
https://issues.apache.org/jira/browse/TUSCANY-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-1804.
---
Thanks for the patch Giorgio.
@OneWay repeted invocations doesn't work in web service binding
---
Key: TUSCANY-1804
URL: https://issues.apache.org/jira/browse/TUSCANY-1804
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.99
Environment: Eclipse/JDK 1.5 / Ubuntu Linux 7.04
Reporter: Giorgio Zoppi
Assignee: Simon Laws
Fix For: Java-SCA-1.0.1
Attachments: patch.diff
i've found the bug that it doens't permit myself to use SCA Binding over
WebService modifying the distributed-calculator. I found it (on Tuscany
1.0 rc3) following the chain towards the wire, and i discovered that
it's an Axis Fault. If you modify in your distributed calculator sample
the SubtractionService in the following way:
@Remotable
public interface SubtractService {
@OneWay
void subtract(double n1, double n2);
}
public class SubtractServiceImpl implements SubtractService {
public void subtract(double n1, double n2) {
System.out.println(SubtractService - subtract + n1 + and
+ n2);
//return n1 - n2;
}
}
I know that it doesn't nothing...but it's a proof of concept.
And in the calculator node:
for (int k = 0; k 10; ++k)
calculatorService.subtract(2*k+3, k);
The nodeC with current Axis2OneWayBindingInvoker, even if it's called 10
times..the receiver gets two messages..
So in the nodeC terminal you can see only for example:
[java] SubtractService - subtract 15.0 and 6.0
[java] SubtractService - subtract 17.0 and 7.0
The reason is due to the Axis HTTP REUSE:
If you change in Axis2OneWayBindingInvoker
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
to:
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.FALSE);
It works! I suspect that there's a bug or a queue full in Axis because
it seems that if you send something too fast it doesn't work (I'll see
it tomorrow, because I don't know how the http client reuse works in Axis).
The next test, I'll do it :
for (int k = 0; k 50; ++k)
calculatorService.subtract(2*k+3, k);
It seems to work, but in a strange way.
During the debugging i discovered your nice structure in order to invoke
methods over ws.
Mainly for the Remote SCA over Web Services your structure has the
following stages (correct me if i'm wrong):
1) JDKInvocationHandler, where you proxies the method call, create the
message, set the source, the target and the operation. Here still you do
some sort of initialization for handling callback.
2) DataTrasformationInterceptor, where you create the soap body of the
message given the operation and parameters, for example:
_ns_:add
xmlns:_ns_=http://calculator/xsd;_ns_:param03.0/_ns_:param0_ns_:p
aram12.0/_ns_:param1/_ns_:add
3) NonblockingInterceptor, where Tuscany schedules invocation in a
workpool (here with jdk 1.5 , you could remove dependency from commonj
package)
4) At time of scheduling, the next invoker is Axis2SCABindingInvoker,
which it's a wrapper for Axis2BindingInvoker if the invocation is
Request-response or for the Axis2BindingInvoker's child
(Axis2OneWayBindingInvoker) if the invocation is OneWay. In
Axis2*BindingInvoker you create the soap envelope, the Axis's
OperationClient, set the axis invocation options and Axis's
MessageContext and the you send all the stuff on the wire.
--
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-1804) @OneWay repeted invocations doesn't work in web service binding
[
https://issues.apache.org/jira/browse/TUSCANY-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-1804:
Fix Version/s: (was: Java-SCA-1.0.1)
Java-SCA-1.1
@OneWay repeted invocations doesn't work in web service binding
---
Key: TUSCANY-1804
URL: https://issues.apache.org/jira/browse/TUSCANY-1804
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.99
Environment: Eclipse/JDK 1.5 / Ubuntu Linux 7.04
Reporter: Giorgio Zoppi
Assignee: Simon Laws
Fix For: Java-SCA-1.1
Attachments: patch.diff
i've found the bug that it doens't permit myself to use SCA Binding over
WebService modifying the distributed-calculator. I found it (on Tuscany
1.0 rc3) following the chain towards the wire, and i discovered that
it's an Axis Fault. If you modify in your distributed calculator sample
the SubtractionService in the following way:
@Remotable
public interface SubtractService {
@OneWay
void subtract(double n1, double n2);
}
public class SubtractServiceImpl implements SubtractService {
public void subtract(double n1, double n2) {
System.out.println(SubtractService - subtract + n1 + and
+ n2);
//return n1 - n2;
}
}
I know that it doesn't nothing...but it's a proof of concept.
And in the calculator node:
for (int k = 0; k 10; ++k)
calculatorService.subtract(2*k+3, k);
The nodeC with current Axis2OneWayBindingInvoker, even if it's called 10
times..the receiver gets two messages..
So in the nodeC terminal you can see only for example:
[java] SubtractService - subtract 15.0 and 6.0
[java] SubtractService - subtract 17.0 and 7.0
The reason is due to the Axis HTTP REUSE:
If you change in Axis2OneWayBindingInvoker
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
to:
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.FALSE);
It works! I suspect that there's a bug or a queue full in Axis because
it seems that if you send something too fast it doesn't work (I'll see
it tomorrow, because I don't know how the http client reuse works in Axis).
The next test, I'll do it :
for (int k = 0; k 50; ++k)
calculatorService.subtract(2*k+3, k);
It seems to work, but in a strange way.
During the debugging i discovered your nice structure in order to invoke
methods over ws.
Mainly for the Remote SCA over Web Services your structure has the
following stages (correct me if i'm wrong):
1) JDKInvocationHandler, where you proxies the method call, create the
message, set the source, the target and the operation. Here still you do
some sort of initialization for handling callback.
2) DataTrasformationInterceptor, where you create the soap body of the
message given the operation and parameters, for example:
_ns_:add
xmlns:_ns_=http://calculator/xsd;_ns_:param03.0/_ns_:param0_ns_:p
aram12.0/_ns_:param1/_ns_:add
3) NonblockingInterceptor, where Tuscany schedules invocation in a
workpool (here with jdk 1.5 , you could remove dependency from commonj
package)
4) At time of scheduling, the next invoker is Axis2SCABindingInvoker,
which it's a wrapper for Axis2BindingInvoker if the invocation is
Request-response or for the Axis2BindingInvoker's child
(Axis2OneWayBindingInvoker) if the invocation is OneWay. In
Axis2*BindingInvoker you create the soap envelope, the Axis's
OperationClient, set the axis invocation options and Axis's
MessageContext and the you send all the stuff on the wire.
--
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] Resolved: (TUSCANY-1804) @OneWay repeted invocations doesn't work in web service binding
[
https://issues.apache.org/jira/browse/TUSCANY-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-1804.
-
Resolution: Fixed
Try again...
@OneWay repeted invocations doesn't work in web service binding
---
Key: TUSCANY-1804
URL: https://issues.apache.org/jira/browse/TUSCANY-1804
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.99
Environment: Eclipse/JDK 1.5 / Ubuntu Linux 7.04
Reporter: Giorgio Zoppi
Assignee: Simon Laws
Fix For: Java-SCA-1.1
Attachments: patch.diff
i've found the bug that it doens't permit myself to use SCA Binding over
WebService modifying the distributed-calculator. I found it (on Tuscany
1.0 rc3) following the chain towards the wire, and i discovered that
it's an Axis Fault. If you modify in your distributed calculator sample
the SubtractionService in the following way:
@Remotable
public interface SubtractService {
@OneWay
void subtract(double n1, double n2);
}
public class SubtractServiceImpl implements SubtractService {
public void subtract(double n1, double n2) {
System.out.println(SubtractService - subtract + n1 + and
+ n2);
//return n1 - n2;
}
}
I know that it doesn't nothing...but it's a proof of concept.
And in the calculator node:
for (int k = 0; k 10; ++k)
calculatorService.subtract(2*k+3, k);
The nodeC with current Axis2OneWayBindingInvoker, even if it's called 10
times..the receiver gets two messages..
So in the nodeC terminal you can see only for example:
[java] SubtractService - subtract 15.0 and 6.0
[java] SubtractService - subtract 17.0 and 7.0
The reason is due to the Axis HTTP REUSE:
If you change in Axis2OneWayBindingInvoker
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
to:
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.FALSE);
It works! I suspect that there's a bug or a queue full in Axis because
it seems that if you send something too fast it doesn't work (I'll see
it tomorrow, because I don't know how the http client reuse works in Axis).
The next test, I'll do it :
for (int k = 0; k 50; ++k)
calculatorService.subtract(2*k+3, k);
It seems to work, but in a strange way.
During the debugging i discovered your nice structure in order to invoke
methods over ws.
Mainly for the Remote SCA over Web Services your structure has the
following stages (correct me if i'm wrong):
1) JDKInvocationHandler, where you proxies the method call, create the
message, set the source, the target and the operation. Here still you do
some sort of initialization for handling callback.
2) DataTrasformationInterceptor, where you create the soap body of the
message given the operation and parameters, for example:
_ns_:add
xmlns:_ns_=http://calculator/xsd;_ns_:param03.0/_ns_:param0_ns_:p
aram12.0/_ns_:param1/_ns_:add
3) NonblockingInterceptor, where Tuscany schedules invocation in a
workpool (here with jdk 1.5 , you could remove dependency from commonj
package)
4) At time of scheduling, the next invoker is Axis2SCABindingInvoker,
which it's a wrapper for Axis2BindingInvoker if the invocation is
Request-response or for the Axis2BindingInvoker's child
(Axis2OneWayBindingInvoker) if the invocation is OneWay. In
Axis2*BindingInvoker you create the soap envelope, the Axis's
OperationClient, set the axis invocation options and Axis's
MessageContext and the you send all the stuff on the wire.
--
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] Reopened: (TUSCANY-1804) @OneWay repeted invocations doesn't work in web service binding
[
https://issues.apache.org/jira/browse/TUSCANY-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reopened TUSCANY-1804:
-
Meant to set status to resolved not closed - doh!
@OneWay repeted invocations doesn't work in web service binding
---
Key: TUSCANY-1804
URL: https://issues.apache.org/jira/browse/TUSCANY-1804
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.99
Environment: Eclipse/JDK 1.5 / Ubuntu Linux 7.04
Reporter: Giorgio Zoppi
Assignee: Simon Laws
Fix For: Java-SCA-1.1
Attachments: patch.diff
i've found the bug that it doens't permit myself to use SCA Binding over
WebService modifying the distributed-calculator. I found it (on Tuscany
1.0 rc3) following the chain towards the wire, and i discovered that
it's an Axis Fault. If you modify in your distributed calculator sample
the SubtractionService in the following way:
@Remotable
public interface SubtractService {
@OneWay
void subtract(double n1, double n2);
}
public class SubtractServiceImpl implements SubtractService {
public void subtract(double n1, double n2) {
System.out.println(SubtractService - subtract + n1 + and
+ n2);
//return n1 - n2;
}
}
I know that it doesn't nothing...but it's a proof of concept.
And in the calculator node:
for (int k = 0; k 10; ++k)
calculatorService.subtract(2*k+3, k);
The nodeC with current Axis2OneWayBindingInvoker, even if it's called 10
times..the receiver gets two messages..
So in the nodeC terminal you can see only for example:
[java] SubtractService - subtract 15.0 and 6.0
[java] SubtractService - subtract 17.0 and 7.0
The reason is due to the Axis HTTP REUSE:
If you change in Axis2OneWayBindingInvoker
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
to:
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.FALSE);
It works! I suspect that there's a bug or a queue full in Axis because
it seems that if you send something too fast it doesn't work (I'll see
it tomorrow, because I don't know how the http client reuse works in Axis).
The next test, I'll do it :
for (int k = 0; k 50; ++k)
calculatorService.subtract(2*k+3, k);
It seems to work, but in a strange way.
During the debugging i discovered your nice structure in order to invoke
methods over ws.
Mainly for the Remote SCA over Web Services your structure has the
following stages (correct me if i'm wrong):
1) JDKInvocationHandler, where you proxies the method call, create the
message, set the source, the target and the operation. Here still you do
some sort of initialization for handling callback.
2) DataTrasformationInterceptor, where you create the soap body of the
message given the operation and parameters, for example:
_ns_:add
xmlns:_ns_=http://calculator/xsd;_ns_:param03.0/_ns_:param0_ns_:p
aram12.0/_ns_:param1/_ns_:add
3) NonblockingInterceptor, where Tuscany schedules invocation in a
workpool (here with jdk 1.5 , you could remove dependency from commonj
package)
4) At time of scheduling, the next invoker is Axis2SCABindingInvoker,
which it's a wrapper for Axis2BindingInvoker if the invocation is
Request-response or for the Axis2BindingInvoker's child
(Axis2OneWayBindingInvoker) if the invocation is OneWay. In
Axis2*BindingInvoker you create the soap envelope, the Axis's
OperationClient, set the axis invocation options and Axis's
MessageContext and the you send all the stuff on the wire.
--
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: [jira] Closed: (TUSCANY-1804) @OneWay repeted invocations doesn't work in web service binding
This appears to have also fixed the old connection refused problem some of
us have been getting
(http://mail-archives.apache.org/mod_mbox/ws-tuscany-dev/200708.mbox/[EMAIL
PROTECTED]
).
Never got to the bottom of that and its made one of my old machines pretty
much unusable for building Tuscany so I'm really really pleased about this
fix!
...ant
On Nov 9, 2007 10:19 AM, Simon Laws (JIRA) tuscany-dev@ws.apache.org
wrote:
[
https://issues.apache.org/jira/browse/TUSCANY-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws closed TUSCANY-1804.
---
Thanks for the patch Giorgio.
@OneWay repeted invocations doesn't work in web service binding
---
Key: TUSCANY-1804
URL: https://issues.apache.org/jira/browse/TUSCANY-1804
Project: Tuscany
Issue Type: Bug
Affects Versions: Java-SCA-0.99
Environment: Eclipse/JDK 1.5 / Ubuntu Linux 7.04
Reporter: Giorgio Zoppi
Assignee: Simon Laws
Fix For: Java-SCA-1.0.1
Attachments: patch.diff
i've found the bug that it doens't permit myself to use SCA Binding over
WebService modifying the distributed-calculator. I found it (on Tuscany
1.0 rc3) following the chain towards the wire, and i discovered that
it's an Axis Fault. If you modify in your distributed calculator sample
the SubtractionService in the following way:
@Remotable
public interface SubtractService {
@OneWay
void subtract(double n1, double n2);
}
public class SubtractServiceImpl implements SubtractService {
public void subtract(double n1, double n2) {
System.out.println(SubtractService - subtract + n1 + and
+ n2);
//return n1 - n2;
}
}
I know that it doesn't nothing...but it's a proof of concept.
And in the calculator node:
for (int k = 0; k 10; ++k)
calculatorService.subtract(2*k+3, k);
The nodeC with current Axis2OneWayBindingInvoker, even if it's called 10
times..the receiver gets two messages..
So in the nodeC terminal you can see only for example:
[java] SubtractService - subtract 15.0 and 6.0
[java] SubtractService - subtract 17.0 and 7.0
The reason is due to the Axis HTTP REUSE:
If you change in Axis2OneWayBindingInvoker
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.TRUE);
to:
requestMC.getOptions().setProperty(HTTPConstants.REUSE_HTTP_CLIENT,
Boolean.FALSE);
It works! I suspect that there's a bug or a queue full in Axis because
it seems that if you send something too fast it doesn't work (I'll see
it tomorrow, because I don't know how the http client reuse works in
Axis).
The next test, I'll do it :
for (int k = 0; k 50; ++k)
calculatorService.subtract (2*k+3, k);
It seems to work, but in a strange way.
During the debugging i discovered your nice structure in order to invoke
methods over ws.
Mainly for the Remote SCA over Web Services your structure has the
following stages (correct me if i'm wrong):
1) JDKInvocationHandler, where you proxies the method call, create the
message, set the source, the target and the operation. Here still you do
some sort of initialization for handling callback.
2) DataTrasformationInterceptor, where you create the soap body of the
message given the operation and parameters, for example:
_ns_:add
xmlns:_ns_= http://calculator/xsd;_ns_:param03.0
/_ns_:param0_ns_:p
aram12.0/_ns_:param1/_ns_:add
3) NonblockingInterceptor, where Tuscany schedules invocation in a
workpool (here with jdk 1.5 , you could remove dependency from commonj
package)
4) At time of scheduling, the next invoker is Axis2SCABindingInvoker,
which it's a wrapper for Axis2BindingInvoker if the invocation is
Request-response or for the Axis2BindingInvoker's child
(Axis2OneWayBindingInvoker) if the invocation is OneWay. In
Axis2*BindingInvoker you create the soap envelope, the Axis's
OperationClient, set the axis invocation options and Axis's
MessageContext and the you send all the stuff on the wire.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] Java SCA Release 1.1 was: Re: Re: [DISCUSS] Tuscany SCA Roadmap and next releases
On Nov 5, 2007 3:54 PM, Simon Laws [EMAIL PROTECTED] wrote: On 10/23/07, wang feng [EMAIL PROTECTED] wrote: hi Jean-Sebastien, Please see my comments below. Thanks, wangfeng On 2007-10-20, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: wang feng wrote: Hi all, We have used Tuscany 1.0 in our product and found some features is important to us. Thanks a lot for contributing here and helping us understand what you'd like to see in Tuscany! I have a few questions to make sure I understand what you're looking for. - Support hot deployable on contribution and composite. This should be have a recursive algorithm to update the correlated component when it has been referenced. Can you give a brief description of the type of hot deployment that you're trying to support? It does not have to be very detailed but maybe just an outline or an example showing what your contributions and composites look like and the steps that you'd like to go through to redeploy them. In particular I'd like to understand if you want to redeploy imported contributions (imported by import in sca-contribution.xml), nested composites, and what you'd like to be able to update in the contributions and composites, classes? component configuration? bindings? wiring? etc. My use case like that(there are three contributions): contribution A export composite A, contribution B import composite A used by composite B and export composite B, contribution C import composite B If we update composite A in contribution A,the sca runtime should be update the correlated contribution B and C and the component's relationship should be rewiring. - Support SDO namespace when using websservice. Deploy a service to webservice,a schema file used in SDO and have sdo namespace such as commonj.sdo/java or commonj.sdo/xml,we should support the feature when parsing the wsdl. Could you provide an example WSDL and XSD? My wsdl file like this: wsdl:definitions xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:sdoJava=commonj.sdo/java xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns= http://com.primeton.eos/com/primeton/eos/newcomponent; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; wsdl:types schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; import namespace=http://schemas.xmlsoap.org/soap/encoding/ / complexType name=SdoJava_java_util_List sdoJava:instanceClass=java.util.List/ complexType name=ArrayOf_soapenc_string complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=soapenc:string[]/ /restriction /complexContent /complexType complexType name=SdoJava_java_lang_String sdoJava:instanceClass=java.lang.String/ complexType name=SdoJava_stockquote_StockQuoteService sdoJava:instanceClass=stockquote.StockQuoteService/ complexType name=ArrayOf_soapenc_stockquote_StockQuoteService complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns:SdoJava_stockquote_StockQuoteService[]/ /restriction /complexContent /complexType /schema /wsdl:types wsdl:message name=newcomponent.newbiz1OutputMessage wsdl:part name=out1 type=xsd:string/wsdl:part wsdl:part name=out2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz1InputMessage wsdl:part name=param1 type=tns:ArrayOf_soapenc_stockquote_StockQuoteService/wsdl:part wsdl:part name=param2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz.bizxOutputMessage wsdl:part name=out1 type=tns:SdoJava_java_lang_String/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz.bizxInputMessage wsdl:part name=param1 type=tns:SdoJava_java_util_List/wsdl:part wsdl:part name=param2 type=tns:ArrayOf_soapenc_string/wsdl:part /wsdl:message wsdl:portType name=newcomponent wsdl:operation name=newbiz wsdl:input message=tns: newcomponent.newbiz.bizxInputMessage /wsdl:input wsdl:output message=tns: newcomponent.newbiz.bizxOutputMessage/wsdl:output /wsdl:operation wsdl:operation name=newbiz1 wsdl:input message=tns:newcomponent.newbiz1InputMessage
Re: [DISCUSS] Java SCA Release 1.1 was: Re: Re: [DISCUSS] Tuscany SCA Roadmap and next releases
On Nov 9, 2007 11:18 AM, ant elder [EMAIL PROTECTED] wrote: On Nov 5, 2007 3:54 PM, Simon Laws [EMAIL PROTECTED] wrote: On 10/23/07, wang feng [EMAIL PROTECTED] wrote: hi Jean-Sebastien, Please see my comments below. Thanks, wangfeng On 2007-10-20, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: wang feng wrote: Hi all, We have used Tuscany 1.0 in our product and found some features is important to us. Thanks a lot for contributing here and helping us understand what you'd like to see in Tuscany! I have a few questions to make sure I understand what you're looking for. - Support hot deployable on contribution and composite. This should be have a recursive algorithm to update the correlated component when it has been referenced. Can you give a brief description of the type of hot deployment that you're trying to support? It does not have to be very detailed but maybe just an outline or an example showing what your contributions and composites look like and the steps that you'd like to go through to redeploy them. In particular I'd like to understand if you want to redeploy imported contributions (imported by import in sca-contribution.xml), nested composites, and what you'd like to be able to update in the contributions and composites, classes? component configuration? bindings? wiring? etc. My use case like that(there are three contributions): contribution A export composite A, contribution B import composite A used by composite B and export composite B, contribution C import composite B If we update composite A in contribution A,the sca runtime should be update the correlated contribution B and C and the component's relationship should be rewiring. - Support SDO namespace when using websservice. Deploy a service to webservice,a schema file used in SDO and have sdo namespace such as commonj.sdo/java or commonj.sdo/xml,we should support the feature when parsing the wsdl. Could you provide an example WSDL and XSD? My wsdl file like this: wsdl:definitions xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:sdoJava=commonj.sdo/java xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns= http://com.primeton.eos/com/primeton/eos/newcomponent; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; wsdl:types schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; import namespace= http://schemas.xmlsoap.org/soap/encoding/ / complexType name=SdoJava_java_util_List sdoJava:instanceClass=java.util.List/ complexType name=ArrayOf_soapenc_string complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=soapenc:string[]/ /restriction /complexContent /complexType complexType name=SdoJava_java_lang_String sdoJava:instanceClass=java.lang.String/ complexType name=SdoJava_stockquote_StockQuoteService sdoJava:instanceClass=stockquote.StockQuoteService/ complexType name=ArrayOf_soapenc_stockquote_StockQuoteService complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns:SdoJava_stockquote_StockQuoteService[]/ /restriction /complexContent /complexType /schema /wsdl:types wsdl:message name=newcomponent.newbiz1OutputMessage wsdl:part name=out1 type=xsd:string/wsdl:part wsdl:part name=out2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz1InputMessage wsdl:part name=param1 type=tns:ArrayOf_soapenc_stockquote_StockQuoteService/wsdl:part wsdl:part name=param2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz.bizxOutputMessage wsdl:part name=out1 type=tns:SdoJava_java_lang_String/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz.bizxInputMessage wsdl:part name=param1 type=tns:SdoJava_java_util_List/wsdl:part wsdl:part name=param2 type=tns:ArrayOf_soapenc_string/wsdl:part /wsdl:message wsdl:portType name=newcomponent wsdl:operation name=newbiz wsdl:input message=tns: newcomponent.newbiz.bizxInputMessage /wsdl:input wsdl:output
Re: [DISCUSS] Java SCA Release 1.1 was: Re: Re: [DISCUSS] Tuscany SCA Roadmap and next releases
On Nov 9, 2007 11:31 AM, Simon Laws [EMAIL PROTECTED] wrote: On Nov 9, 2007 11:18 AM, ant elder [EMAIL PROTECTED] wrote: On Nov 5, 2007 3:54 PM, Simon Laws [EMAIL PROTECTED] wrote: On 10/23/07, wang feng [EMAIL PROTECTED] wrote: hi Jean-Sebastien, Please see my comments below. Thanks, wangfeng On 2007-10-20, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: wang feng wrote: Hi all, We have used Tuscany 1.0 in our product and found some features is important to us. Thanks a lot for contributing here and helping us understand what you'd like to see in Tuscany! I have a few questions to make sure I understand what you're looking for. - Support hot deployable on contribution and composite. This should be have a recursive algorithm to update the correlated component when it has been referenced. Can you give a brief description of the type of hot deployment that you're trying to support? It does not have to be very detailed but maybe just an outline or an example showing what your contributions and composites look like and the steps that you'd like to go through to redeploy them. In particular I'd like to understand if you want to redeploy imported contributions (imported by import in sca-contribution.xml), nested composites, and what you'd like to be able to update in the contributions and composites, classes? component configuration? bindings? wiring? etc. My use case like that(there are three contributions): contribution A export composite A, contribution B import composite A used by composite B and export composite B, contribution C import composite B If we update composite A in contribution A,the sca runtime should be update the correlated contribution B and C and the component's relationship should be rewiring. - Support SDO namespace when using websservice. Deploy a service to webservice,a schema file used in SDO and have sdo namespace such as commonj.sdo/java or commonj.sdo/xml,we should support the feature when parsing the wsdl. Could you provide an example WSDL and XSD? My wsdl file like this: wsdl:definitions xmlns:apachesoap= http://xml.apache.org/xml-soap; xmlns:sdoJava=commonj.sdo/java xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/ xmlns:tns= http://com.primeton.eos/com/primeton/eos/newcomponent; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; wsdl:types schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; import namespace=http://schemas.xmlsoap.org/soap/encoding/ / complexType name=SdoJava_java_util_List sdoJava:instanceClass=java.util.List/ complexType name=ArrayOf_soapenc_string complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=soapenc:string[]/ /restriction /complexContent /complexType complexType name=SdoJava_java_lang_String sdoJava:instanceClass=java.lang.String/ complexType name=SdoJava_stockquote_StockQuoteService sdoJava:instanceClass=stockquote.StockQuoteService/ complexType name=ArrayOf_soapenc_stockquote_StockQuoteService complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns:SdoJava_stockquote_StockQuoteService[]/ /restriction /complexContent /complexType /schema /wsdl:types wsdl:message name=newcomponent.newbiz1OutputMessage wsdl:part name=out1 type=xsd:string/wsdl:part wsdl:part name=out2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz1InputMessage wsdl:part name=param1 type=tns:ArrayOf_soapenc_stockquote_StockQuoteService/wsdl:part wsdl:part name=param2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz.bizxOutputMessage wsdl:part name=out1 type=tns:SdoJava_java_lang_String/wsdl:part /wsdl:message wsdl:message name= newcomponent.newbiz.bizxInputMessage wsdl:part name=param1 type=tns:SdoJava_java_util_List/wsdl:part wsdl:part name=param2 type=tns:ArrayOf_soapenc_string/wsdl:part
Processing reference targets for remote bindings
I've started putting some code in the node implementation to allow remote
bindings to make use of reference targets for identifying service endpoints.
It's very simple at the moment. The node implementation uses the
startComposite event as a trigger to
1/ scan all services in the composite and register them with the domain
I've updated the domain implementation so that when there is no remote
domain there registrations are cached locally. It's the same code
implementing the local and remote domain so the proxy effectively provides a
write through cache.
2/ scan all references in the composite and compare them against the
registered service. Replace the binding uri with the uri from the registered
service if appropriate.
The if appropriate part is the tricky bit. At the moment the code [1] does
the following.
for (Component component: composite.getComponents()) {
for (ComponentReference reference: component.getReferences()) {
for (Binding binding: reference.getBindings()) {
if (binding.isUnresolved()) {
if (binding instanceof SCABindingImpl){
// TODO - only find uri if its in a remote node
} else {
// find the right endpoint for this
reference/binding. This relies on looking
// up every binding URI. If a response is
returned then it's set back into the
// binding uri
String uri = ;
try {
uri =
((SCADomainSPI)scaDomain).findServiceEndpoint(domainURI,
binding.getURI(),
binding.getClass().getName());
} catch(Exception ex) {
logger.log(Level.WARNING,
Unable to find service: +
domainURI + +
nodeURI + +
binding.getURI() + +
binding.getClass().getName() + +
uri);
}
if (uri.equals() == false){
binding.setURI(uri);
}
}
}
}
}
}
There is a bit of slight of hand here;
It looks for all unresolved bindings (it seems that all remote bindings are
unresolved - is that right?)
It then uses the binding uri to look up a service which either finds
something or it doesn't
In the case that a binding.uri has no endpoint specified you will see
something like MyComponent/MyService in the binding uri and there's a good
chance that a service will have been registered under this name and hence
the correct target endpoint will be set back into the reference binding.
In the case that a binding uri is set by other means (via the uri attribute
for example) then it will already look something like
http://myhost:8080/MyComponent/MyService;. This will not match any
registered service name and hence will not be reset. This may not match the
real service uri but then that's the users fault for setting it incorrectly.
This processing is slightly removed from the model itself but relies on the
model and related processing to work out what the binding.uri should be
initially, based on specified target(s) (haven't done anything about the
multiplicity case yet). I welcome any feedback about whether this is going
in the right direction. If people are happy about this I will likely pull
the service registration logic out of the sca binding and treat it in a
similar, more generic, way.
Simon
[1]
http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/node-impl/src/main/java/org/apache/tuscany/sca/node/impl/SCANodeImpl.java
Re: [DISCUSS] Java SCA Release 1.1 was: Re: Re: [DISCUSS] Tuscany SCA Roadmap and next releases
+1 for Simon as RM. I added a few things to the list that I'd like to get done for 1.1. I think the distribution/packaging changes for better modularity and daployability are very important and I'd like to see these in 1.1. I think it's more realistic to aim for an early January release date rather than trying to get something out in December just before the holidays. Also, December releases tend not to get immediate pickup and adoption because of people being out for the holidays. Simon ant elder wrote: On Nov 5, 2007 3:54 PM, Simon Laws [EMAIL PROTECTED] wrote: On 10/23/07, wang feng [EMAIL PROTECTED] wrote: hi Jean-Sebastien, Please see my comments below. Thanks, wangfeng On 2007-10-20, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: wang feng wrote: Hi all, We have used Tuscany 1.0 in our product and found some features is important to us. Thanks a lot for contributing here and helping us understand what you'd like to see in Tuscany! I have a few questions to make sure I understand what you're looking for. - Support hot deployable on contribution and composite. This should be have a recursive algorithm to update the correlated component when it has been referenced. Can you give a brief description of the type of hot deployment that you're trying to support? It does not have to be very detailed but maybe just an outline or an example showing what your contributions and composites look like and the steps that you'd like to go through to redeploy them. In particular I'd like to understand if you want to redeploy imported contributions (imported by import in sca-contribution.xml), nested composites, and what you'd like to be able to update in the contributions and composites, classes? component configuration? bindings? wiring? etc. My use case like that(there are three contributions): contribution A export composite A, contribution B import composite A used by composite B and export composite B, contribution C import composite B If we update composite A in contribution A,the sca runtime should be update the correlated contribution B and C and the component's relationship should be rewiring. - Support SDO namespace when using websservice. Deploy a service to webservice,a schema file used in SDO and have sdo namespace such as commonj.sdo/java or commonj.sdo/xml,we should support the feature when parsing the wsdl. Could you provide an example WSDL and XSD? My wsdl file like this: wsdl:definitions xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:sdoJava=commonj.sdo/java xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns= http://com.primeton.eos/com/primeton/eos/newcomponent; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; wsdl:types schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; import namespace=http://schemas.xmlsoap.org/soap/encoding/ / complexType name=SdoJava_java_util_List sdoJava:instanceClass=java.util.List/ complexType name=ArrayOf_soapenc_string complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=soapenc:string[]/ /restriction /complexContent /complexType complexType name=SdoJava_java_lang_String sdoJava:instanceClass=java.lang.String/ complexType name=SdoJava_stockquote_StockQuoteService sdoJava:instanceClass=stockquote.StockQuoteService/ complexType name=ArrayOf_soapenc_stockquote_StockQuoteService complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns:SdoJava_stockquote_StockQuoteService[]/ /restriction /complexContent /complexType /schema /wsdl:types wsdl:message name=newcomponent.newbiz1OutputMessage wsdl:part name=out1 type=xsd:string/wsdl:part wsdl:part name=out2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz1InputMessage wsdl:part name=param1 type=tns:ArrayOf_soapenc_stockquote_StockQuoteService/wsdl:part wsdl:part name=param2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz.bizxOutputMessage wsdl:part name=out1 type=tns:SdoJava_java_lang_String/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz.bizxInputMessage wsdl:part name=param1 type=tns:SdoJava_java_util_List/wsdl:part wsdl:part name=param2 type=tns:ArrayOf_soapenc_string/wsdl:part /wsdl:message wsdl:portType name=newcomponent wsdl:operation name=newbiz wsdl:input message=tns:
[jira] Commented: (TUSCANY-1421) XMLHelper.save on root object of DataGraph gives serialization of href=root.xml#/
[ https://issues.apache.org/jira/browse/TUSCANY-1421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541306 ] Boris Ilyushonak commented on TUSCANY-1421: --- Issue fixed but not included in release, accesed by the http://people.apache.org/dist/incubator/tuscany/java/sdo/1.0-incubating/apache-tuscany-sdo-1.0-incubating.zip To solve it I just replace the impl/src/main/java/org/apache/tuscany/sdo/helper/XMLDocumentImpl.java to latest version: https://svn.apache.org/repos/asf/incubator/tuscany/java/sdo/impl/src/main/java/org/apache/tuscany/sdo/helper/XMLDocumentImpl.java and rebuild it is strange, that the issue noted in RELEASE_NOTES XMLHelper.save on root object of DataGraph gives serialization of href=root.xml#/ --- Key: TUSCANY-1421 URL: https://issues.apache.org/jira/browse/TUSCANY-1421 Project: Tuscany Issue Type: Bug Components: Java SDO Implementation Affects Versions: Java-SDO-beta1 Reporter: Kelvin Goodson Fix For: Java-SDO-1.0 There's an issue reported on the user list ... http://mail-archives.apache.org/mod_mbox/ws-tuscany-user/200707.mbox/[EMAIL PROTECTED] which relates to a some missing logic in XMLDocumentImpl's save method The precondition for hitting this issue is when the data object is the root data object of a DataGraph. In this case the eContainer of the root object is null, but the root object is contained in a resource. We need to replicate the unhooking and replacing behaviour that exists for the container of the data object for the case where the data object is directly contained in a resource. -- 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: Tuscany November Board Report
On Nov 5, 2007 6:13 PM, Luciano Resende [EMAIL PROTECTED] wrote: It's that time again, and I have created a placeholder for us to collaborate on the Incubator board report. Right now it's just a copy of our previous report, please jump in and help get this updated/rewritten. Let's aim to get something done by Thursday or Friday... as the deadline is this weekend. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+November+Board+Report -- 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] Hi Luciano I've done the basic updates. Take a look and see what else is needed. Simon
Re: Tuscany November Board Report
It looks fine from my perspective. Kelvin. On 09/11/2007, Luciano Resende [EMAIL PROTECTED] wrote: I have added couple more things there too... it would be great if others could review and update by EOD today, then I'd move this to the Incubator wiki at night. On Nov 9, 2007 4:56 AM, Simon Laws [EMAIL PROTECTED] wrote: On Nov 5, 2007 6:13 PM, Luciano Resende [EMAIL PROTECTED] wrote: It's that time again, and I have created a placeholder for us to collaborate on the Incubator board report. Right now it's just a copy of our previous report, please jump in and help get this updated/rewritten. Let's aim to get something done by Thursday or Friday... as the deadline is this weekend. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+November+Board+Report -- 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] Hi Luciano I've done the basic updates. Take a look and see what else is needed. Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany November Board Report
The report looks good to me. Thanks, Raymond - Original Message - From: Luciano Resende [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Friday, November 09, 2007 8:30 AM Subject: Re: Tuscany November Board Report I have added couple more things there too... it would be great if others could review and update by EOD today, then I'd move this to the Incubator wiki at night. On Nov 9, 2007 4:56 AM, Simon Laws [EMAIL PROTECTED] wrote: On Nov 5, 2007 6:13 PM, Luciano Resende [EMAIL PROTECTED] wrote: It's that time again, and I have created a placeholder for us to collaborate on the Incubator board report. Right now it's just a copy of our previous report, please jump in and help get this updated/rewritten. Let's aim to get something done by Thursday or Friday... as the deadline is this weekend. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+November+Board+Report -- 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] Hi Luciano I've done the basic updates. Take a look and see what else is needed. Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany November Board Report
I've made quite a lot of updates. ...ant On Nov 9, 2007 4:30 PM, Luciano Resende [EMAIL PROTECTED] wrote: I have added couple more things there too... it would be great if others could review and update by EOD today, then I'd move this to the Incubator wiki at night. On Nov 9, 2007 4:56 AM, Simon Laws [EMAIL PROTECTED] wrote: On Nov 5, 2007 6:13 PM, Luciano Resende [EMAIL PROTECTED] wrote: It's that time again, and I have created a placeholder for us to collaborate on the Incubator board report. Right now it's just a copy of our previous report, please jump in and help get this updated/rewritten. Let's aim to get something done by Thursday or Friday... as the deadline is this weekend. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+November+Board+Report -- 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] Hi Luciano I've done the basic updates. Take a look and see what else is needed. Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tuscany November Board Report
Good Ant, looks good to me. On Nov 9, 2007 9:50 AM, ant elder [EMAIL PROTECTED] wrote: I've made quite a lot of updates. ...ant On Nov 9, 2007 4:30 PM, Luciano Resende [EMAIL PROTECTED] wrote: I have added couple more things there too... it would be great if others could review and update by EOD today, then I'd move this to the Incubator wiki at night. On Nov 9, 2007 4:56 AM, Simon Laws [EMAIL PROTECTED] wrote: On Nov 5, 2007 6:13 PM, Luciano Resende [EMAIL PROTECTED] wrote: It's that time again, and I have created a placeholder for us to collaborate on the Incubator board report. Right now it's just a copy of our previous report, please jump in and help get this updated/rewritten. Let's aim to get something done by Thursday or Friday... as the deadline is this weekend. [1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+November+Board+Report -- 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] Hi Luciano I've done the basic updates. Take a look and see what else is needed. Simon -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://people.apache.org/%7Elresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- 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:
Welcome to Tuscany, please follow the instructions to subscribe available here [1] You need to send e-mail to the following address to subscribe : - [EMAIL PROTECTED] - [EMAIL PROTECTED] [1] http://incubator.apache.org/tuscany/mailing-lists.html On Nov 8, 2007 4:01 PM, Wangkai Zai [EMAIL PROTECTED] wrote: subscribe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fw: [jira] Commented: (TUSCANY-1884) Allow the setting of the contribution root in the web.xml
On Nov 8, 2007 11:06 AM, Simon Laws [EMAIL PROTECTED] wrote: On 11/8/07, ant elder [EMAIL PROTECTED] wrote: I like this idea a lot. For one thing it would mean applications don't have to know anything about Tuscany so could avoid all the problems with dependencies in build scripts. ...ant On Nov 2, 2007 7:29 AM, Bob Marbeck [EMAIL PROTECTED] wrote: Could there be a command line version of this so sca jars can be run outside of Tomcat? Something like java -jar tuscany.jarrepositoryFolder where repositoryFolder is the same type of thing used by the tuscany.war? - Forwarded Message From: Bob Marbeck [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: tuscany-dev@ws.apache.org Sent: Wednesday, October 31, 2007 5:33:49 PM Subject: Re: [jira] Commented: (TUSCANY-1884) Allow the setting of the contribution root in the web.xml This seems quite neat and makes running things much easier. Is it going to be included in a release soon? And are the other samples going to be updated so they all work when run in the tuscany.war? - Original Message From: Bob Marbeck [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: tuscany-dev@ws.apache.org Sent: Wednesday, October 31, 2007 4:33:34 PM Subject: Re: [jira] Commented: (TUSCANY-1884) Allow the setting of the contribution root in the web.xml It does! Thanks Ant. - Original Message From: ant elder [EMAIL PROTECTED] To: Bob Marbeck [EMAIL PROTECTED] Cc: tuscany-dev@ws.apache.org Sent: Wednesday, October 31, 2007 4:24:44 PM Subject: Re: [jira] Commented: (TUSCANY-1884) Allow the setting of the contribution root in the web.xml On 10/31/07, Bob Marbeck [EMAIL PROTECTED] wrote: That tuscany.war sounded interesting so i gave it a try but it doesn't seem to work. The Tomcat console shows: 31-Oct-2007 15:43:11 org.apache.tuscany.sca.webapp.WarContextListeneraddContribution INFO: Added contribution: file:/C:/TuscanyRepository/sample- helloworld-ws-service.jar 31-Oct-2007 15:43:11 org.apache.tuscany.sca.node.impl..SCANodeImplstartComposites INFO: http://localhost:8080/ has no composites to start Any ideas? It looks like you're trying the Tuscany sample helloworld-ws-service, looking in that jar the problem is that it doesn't have an sca-contribution.xml file or have the .composite file in the meta-inf/sca-deployables folder, so the composite wont get started by default. That can be fixed by adding one of those, i've tried that and put the resulting jar up at http://people.apache.org/~antelder/tuscany/sample-helloworld-ws-service.jarhttp://people.apache.org/%7Eantelder/tuscany/sample-helloworld-ws-service.jar http://people.apache.org/%7Eantelder/tuscany/sample-helloworld-ws-service.jar . That works ok for me with the tuscany.war, and once deployed you can see the wsdl for the service by going to http://localhost:8080/tuscany/HelloWorldServiceComponent?wsdl Can you let me know if that works for you? ...ant __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com I was thinking about going in and fixing up Sebatien's maven plugin to generate our sample build.xml files to avoid all the hand editing we have been doing. This could be a way round some (all) of that so I'm liking the sound of this too. Applications would still have to know about the SCA apis but not the details of Tuscany. Am I right in thinking that the tuscany-jar would just be the core stuff to be combined with extensions - on the classpath - in some other bigger jars buld for specific purposes - in the webapp war What was the thinking there? Simon I've committed a prototype start of this in https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/distribution/standalone/, its currently just the webapp distro striped down and changed to be started from a main method so we can test this out. To run it you build the module then something like: mvn dependency:copy-dependencies -o java -Djava.ext.dirs=target/dependency -jar target\tuscany-sca.jarC:\MyTuscanyRepository where MyTuscanyRepository is a folder containing contribution jars (which need an sca-contribution.xml file or have the .composite file in the meta-inf/sca-deployables folder as discussed earlier in this thread). There's a lot that needs be improved but this is a start so we can get some ideas.
Re: Composite and Components
Hi Giorgio
So this is about adding components to a composite dynamically. Can we do
what you need to do by either,
Allowing contributions to be updated (so that you can add a new component to
the composite through the normal contribution process)
OR
Adding a new contribution for each new component. The contribution could
still contain generated XML if required and it could depend on the first
contribution if this is where the component implementation is
This way we don't have to provide new Tuscany specific interfaces for
composite management.
Ok I agree, so i need a way to update contribution by contribution manager,
I process by the composite api the metacomponent, because i want keep
hierarchical structure that a composite could have.
I'm seeing that's a lot of code, but it's feasible.
Once you have added the component what do you want to happen to it. For
example, will it be wired to the manager that is controlling the workpool.
yes.
If so how will this wiring be introduced? Here is some psuedo code for how
the workpool manager might work without sca wiring (this does depend on the
trunk code with the latest domain implementation).
I create a new wire on fly: adding dynamically a wire is not difficult.
run() {
under normal operation pass work out to worker components
if (run out of components and max components not reached) {
create a new composite giving the new worker a name
add the composite to a new contribution
domain = SCADomainFinder.newInstance().getSCADomain(domainName);
domain.addContribution(the new contribution)
domain.startComposite(the name of the new composite)
reference to new component = domain.getService(WorkerService.class,
the name of the new component)
use the new reference to allocate work to the component
store the reference for future use
}
}
This solution is better and it's simple, but i want a hierarch
The manager is a component.
If the manager were a component in its own right I think it could be done by
making the reference to workers have a multiplicity greater than 1 and by
adding a new wire when you add the new component. This would rely on doing
some work to make contribution updates work. Don't know how hard that would
be.
Am thinking aloud here so let me know if this is useful.
It would be good to understand a little more about the requirement as we
have some similarly devious code in the current domain implementation and,
now that callable reference support is better, I think we can replace it
with code that only depends on the Tuscany API as opposed to the innards of
the runtime. I haven't done this yet but maybe this is the motivation I need
to sort it out:-)
So a method like:
void updateDeployedArtifact(Composite c, String ComponentDefintion) is
still in my contributionservice code.
I'm working on..
I'll help now you in order to provide a contribution update service,
because it's what i
need.
Cheers,
Giorgio.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [DISCUSS] Java SCA Release 1.1 was: Re: Re: [DISCUSS] Tuscany SCA Roadmap and next releases
+1 for Simon Laws as the release manager. +1 on Simon Nash's proposal to have an early-January 1.1 release. I would like to get some basic transaction support into the 1.1 release. Thanks, Raymond - Original Message - From: Simon Nash [EMAIL PROTECTED] To: tuscany-dev@ws.apache.org Sent: Friday, November 09, 2007 4:07 AM Subject: Re: [DISCUSS] Java SCA Release 1.1 was: Re: Re: [DISCUSS] Tuscany SCA Roadmap and next releases +1 for Simon as RM. I added a few things to the list that I'd like to get done for 1.1. I think the distribution/packaging changes for better modularity and daployability are very important and I'd like to see these in 1.1. I think it's more realistic to aim for an early January release date rather than trying to get something out in December just before the holidays. Also, December releases tend not to get immediate pickup and adoption because of people being out for the holidays. Simon ant elder wrote: On Nov 5, 2007 3:54 PM, Simon Laws [EMAIL PROTECTED] wrote: On 10/23/07, wang feng [EMAIL PROTECTED] wrote: hi Jean-Sebastien, Please see my comments below. Thanks, wangfeng On 2007-10-20, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote: wang feng wrote: Hi all, We have used Tuscany 1.0 in our product and found some features is important to us. Thanks a lot for contributing here and helping us understand what you'd like to see in Tuscany! I have a few questions to make sure I understand what you're looking for. - Support hot deployable on contribution and composite. This should be have a recursive algorithm to update the correlated component when it has been referenced. Can you give a brief description of the type of hot deployment that you're trying to support? It does not have to be very detailed but maybe just an outline or an example showing what your contributions and composites look like and the steps that you'd like to go through to redeploy them. In particular I'd like to understand if you want to redeploy imported contributions (imported by import in sca-contribution.xml), nested composites, and what you'd like to be able to update in the contributions and composites, classes? component configuration? bindings? wiring? etc. My use case like that(there are three contributions): contribution A export composite A, contribution B import composite A used by composite B and export composite B, contribution C import composite B If we update composite A in contribution A,the sca runtime should be update the correlated contribution B and C and the component's relationship should be rewiring. - Support SDO namespace when using websservice. Deploy a service to webservice,a schema file used in SDO and have sdo namespace such as commonj.sdo/java or commonj.sdo/xml,we should support the feature when parsing the wsdl. Could you provide an example WSDL and XSD? My wsdl file like this: wsdl:definitions xmlns:apachesoap=http://xml.apache.org/xml-soap; xmlns:sdoJava=commonj.sdo/java xmlns:soapenc= http://schemas.xmlsoap.org/soap/encoding/; xmlns:tns= http://com.primeton.eos/com/primeton/eos/newcomponent; xmlns:wsdl= http://schemas.xmlsoap.org/wsdl/; xmlns:wsdlsoap= http://schemas.xmlsoap.org/wsdl/soap/; xmlns:xsd= http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; wsdl:types schema xmlns=http://www.w3.org/2001/XMLSchema; targetNamespace= http://com.primeton.eos/com/primeton/eos/newcomponent; import namespace=http://schemas.xmlsoap.org/soap/encoding/ / complexType name=SdoJava_java_util_List sdoJava:instanceClass=java.util.List/ complexType name=ArrayOf_soapenc_string complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=soapenc:string[]/ /restriction /complexContent /complexType complexType name=SdoJava_java_lang_String sdoJava:instanceClass=java.lang.String/ complexType name=SdoJava_stockquote_StockQuoteService sdoJava:instanceClass=stockquote.StockQuoteService/ complexType name=ArrayOf_soapenc_stockquote_StockQuoteService complexContent restriction base=soapenc:Array attribute ref=soapenc:arrayType wsdl:arrayType=tns:SdoJava_stockquote_StockQuoteService[]/ /restriction /complexContent /complexType /schema /wsdl:types wsdl:message name=newcomponent.newbiz1OutputMessage wsdl:part name=out1 type=xsd:string/wsdl:part wsdl:part name=out2 type=xsd:string/wsdl:part /wsdl:message wsdl:message name=newcomponent.newbiz1InputMessage wsdl:part name=param1 type=tns:ArrayOf_soapenc_stockquote_StockQuoteService/wsdl:part wsdl:part name=param2 type=xsd:string/wsdl:part /wsdl:message wsdl:message
[jira] Created: (TUSCANY-1904) Implement distribution target for DAS ant build
Implement distribution target for DAS ant build --- Key: TUSCANY-1904 URL: https://issues.apache.org/jira/browse/TUSCANY-1904 Project: Tuscany Issue Type: Improvement Components: C++ DAS Reporter: Adriano Crestani Priority: Minor Fix For: Cpp-M4 create a distribution target for DAS ant build to auto generate the distribution files structure -- 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-1904) Implement distribution target for DAS ant build
[ https://issues.apache.org/jira/browse/TUSCANY-1904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adriano Crestani reassigned TUSCANY-1904: - Assignee: Adriano Crestani Implement distribution target for DAS ant build --- Key: TUSCANY-1904 URL: https://issues.apache.org/jira/browse/TUSCANY-1904 Project: Tuscany Issue Type: Improvement Components: C++ DAS Reporter: Adriano Crestani Assignee: Adriano Crestani Priority: Minor Fix For: Cpp-M4 create a distribution target for DAS ant build to auto generate the distribution files structure -- 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-1905) Implement distribution target for SDO ant build
Implement distribution target for SDO ant build --- Key: TUSCANY-1905 URL: https://issues.apache.org/jira/browse/TUSCANY-1905 Project: Tuscany Issue Type: Improvement Components: C++ SDO Affects Versions: Cpp-M3 Reporter: Adriano Crestani Priority: Minor Fix For: Cpp-M4 create a distribution target for SDO ant build to auto generate the distribution files structure -- 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-1906) Implement distribution target for SCA ant build
Implement distribution target for SCA ant build --- Key: TUSCANY-1906 URL: https://issues.apache.org/jira/browse/TUSCANY-1906 Project: Tuscany Issue Type: Improvement Components: C++ SCA Affects Versions: Cpp-M3 Reporter: Adriano Crestani Priority: Minor Fix For: Cpp-M4 create a distribution target for SCA ant build to auto generate the distribution files structure -- 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]
