[
https://issues.apache.org/jira/browse/TUSCANY-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amita Vadhavkar reassigned TUSCANY-1315:
Assignee: Amita Vadhavkar
NPE is implementation doesn't match WSDL interface
On 9/7/07, ant elder [EMAIL PROTECTED] wrote:
Right now that would be down to the ServletHost impl that you use,
currently
our Jetty and Tomcat ServletHost impls both have port 8080 as the default.
...ant
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
What is the default for the
JIRA-1665 is there with a sample patch. Please see
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg22828.html
and the readme.htm from patch for rest of the details.
In summary, DAS works well when connection is passed from caller and txn is
managed
by caller. I am trying to put a new
Until now we have always held this information in the wsa:From element.
However, in thinking about what is really going on here in WS-Addressing
terms, I believe we should be putting it in the wsa:To element instead.
The wsa:To element is mandatory for WS-Addressing, but we are not
sending it
[
https://issues.apache.org/jira/browse/TUSCANY-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws reassigned TUSCANY-1637:
---
Assignee: Simon Laws
Rationalize the SCA Domain implementations
Hi,
Some thoughts about the example simplification - really it would be good to
simplify the sample, but the client+server scenario should remain as JUnit test
I think. You can see below some problems I currently have exactly with this
scenario.
I started looking at the following issues:
1.
great idea. It'll make it easier for everyone to find this information.
I'll add it if others agreeing.
On 9/7/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Mike Edwards wrote:
Folks,
The SCA specifications which are implemented by Tuscany have just
started out a new phase - they
[
https://issues.apache.org/jira/browse/TUSCANY-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Golick closed TUSCANY-1172.
plugin LICENSE.txt file has spurious
Key:
[
https://issues.apache.org/jira/browse/TUSCANY-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Golick closed TUSCANY-1193.
unable to create data objects from dynamic metadata that match data objects
created from XSD
On 9/7/07, Ignacio Silva-Lepe [EMAIL PROTECTED] wrote:
+1
On 9/7/07, haleh mahbod [EMAIL PROTECTED] wrote:
great idea. It'll make it easier for everyone to find this information.
I'll add it if others agreeing.
On 9/7/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Mike
No comments on this for a while so if no one shouts i'm going to do this to
fix TUSCANY-1559.
...ant
On 9/5/07, ant elder [EMAIL PROTECTED] wrote:
Sure, thats just making the source and target interfaces use different
databindings caused a databinding transformation explicit on the
Comments inline. I removed some text to make the current discussion
easier to follow.
Simon
Raymond Feng wrote:
Please see my comments inline.
(cut)
I don't think we should directly use From to hold the callback
endpoint. We'll lost the caller's EPR if we do so and we cannot
support
On 8/23/07, ant elder [EMAIL PROTECTED] wrote:
On 8/23/07, Simon Laws [EMAIL PROTECTED] wrote:
On 8/23/07, haleh mahbod [EMAIL PROTECTED] wrote:
I moved all the jars from calculator-webapp to tomcat/lib.
calculator-webapp
runs fine. What else is there that might cause a
[
https://issues.apache.org/jira/browse/TUSCANY-1099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Golick closed TUSCANY-1099.
fix for TUSCANY-1083 used lookupPrefix method of Node not available to Java
1.4.2 users
+1
On 9/7/07, haleh mahbod [EMAIL PROTECTED] wrote:
great idea. It'll make it easier for everyone to find this information.
I'll add it if others agreeing.
On 9/7/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Mike Edwards wrote:
Folks,
The SCA specifications which are
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
I'm a bit concerned with this default as it would cause conflicts
if I have a Web app server active on port 8080 while I'm running a
test that uses either of these environments.
Yes, using 8080 would conflict with existing web app servers running
I'm a bit concerned with this default as it would cause conflicts
if I have a Web app server active on port 8080 while I'm running a
test that uses either of these environments.
Is there any problem with changing this default setting for our
embedded ServletHost from 8080 to 8085? This should
Right now that would be down to the ServletHost impl that you use, currently
our Jetty and Tomcat ServletHost impls both have port 8080 as the default.
...ant
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
What is the default for the environment? For a webapp deployment
this seems
On 9/7/07, ant elder [EMAIL PROTECTED] wrote:
I'd like to remove the hard coded BASE_URI constant from the Axis2 WS
binding Axis2ServiceProvider so that the default for the environment is
used
instead of always using port 8085 unless its explicitly stated in the
binding uri. Can anyone see
[
https://issues.apache.org/jira/browse/TUSCANY-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Golick closed TUSCANY-1062.
DataGraph.createRootObject implementation does not match 2.1 spec and also is
not helpful when
[
https://issues.apache.org/jira/browse/TUSCANY-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Golick closed TUSCANY-1100.
Dynamic Type tests are needed to ensure that all XSD datatypes are supported
This has come up several times but I've not seen any conclusion.
Here are the relevant JIRAs:
http://issues.apache.org/jira/browse/TUSCANY-181
http://issues.apache.org/jira/browse/TUSCANY-678
http://issues.apache.org/jira/browse/TUSCANY-1389
To resolve these JIRAs I think we should include the
Right now the SCA build with an empty local maven repository only works with
Maven 2.0.5 not with Maven 2.0.6 or 2.0.7. I've raised TUSCANY-1676 for
this, we've talked before about fixing this for 1.0 but not sure if we've
time now so i've set the Fix level to Java-SCA-Next, please say if you
Mike Edwards wrote:
Folks,
The SCA specifications which are implemented by Tuscany have just
started out a new phase - they are moving to OASIS for formal
standardization. This is being done as a series of OASIS technical
committees, each dealing with one or more of the SCA specifications.
Comments inline.
Thanks,
Raymond
- Original Message -
From: Simon Nash [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Friday, September 07, 2007 8:52 AM
Subject: Re: [jira] Updated: (TUSCANY-1674) Missing NonBlockingInterceptor
on service wire
I'm not convinced that this
Great, I think the wiki page will be very helpful. There is no need
for a web sample... I'll have to double check the license of the code
in your patch before committing it.
On 9/7/07, Amita Vadhavkar [EMAIL PROTECTED] wrote:
JIRA-1665 is there with a sample patch. Please see
On 9/7/07, ant elder [EMAIL PROTECTED] wrote:
Right now the SCA build with an empty local maven repository only works
with
Maven 2.0.5 not with Maven 2.0.6 or 2.0.7. I've raised TUSCANY-1676 for
this, we've talked before about fixing this for 1.0 but not sure if we've
time now so i've set
What is the default for the environment? For a webapp deployment
this seems meaningful, but I'm not sure what this would be for
host-embedded with http-jetty or http-tomcat.
Simon
ant elder wrote:
I'd like to remove the hard coded BASE_URI constant from the Axis2 WS
binding
[
https://issues.apache.org/jira/browse/TUSCANY-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amita Vadhavkar updated TUSCANY-1315:
-
Attachment: Findings.doc
Hi, I tried some examples and in those there were no NPEs but
ant elder wrote:
No comments on this for a while so if no one shouts i'm going to do this to
fix TUSCANY-1559.
...ant
+1 from me to move the logic to enforce pass by value into a separate
interceptor, out implementation-java-runtime.
I think it should be in the core-databinding
Here is the explanation for the issue we are having :
http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg20844.html
On 9/7/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/7/07, ant elder [EMAIL PROTECTED] wrote:
Right now the SCA build with an empty local maven repository only works
SCA build with an empty local maven repository only works with maven 2.05 not
2.0.6 or 2.0.7
Key: TUSCANY-1676
URL: https://issues.apache.org/jira/browse/TUSCANY-1676
I'd like to remove the hard coded BASE_URI constant from the Axis2 WS
binding Axis2ServiceProvider so that the default for the environment is used
instead of always using port 8085 unless its explicitly stated in the
binding uri. Can anyone see any problems with doing this? A quick try shows
I'm not convinced that this interceptor should be added on the service side.
If the binding used for the call supports a nonblocking MEP and wire protocol,
then a non-SCA caller can use this MEP to achieve nonblocking semantics.
If the binding only supports two-way blocking MEP, then we get into
On 9/7/07, Luciano Resende [EMAIL PROTECTED] wrote:
On 9/7/07, Simon Nash [EMAIL PROTECTED] wrote:
I'm a bit concerned with this default as it would cause conflicts
if I have a Web app server active on port 8080 while I'm running a
test that uses either of these environments.
Yes,
XML Parser not being closed with void return types causing memory leaks
-
Key: TUSCANY-1677
URL: https://issues.apache.org/jira/browse/TUSCANY-1677
Project: Tuscany
[
https://issues.apache.org/jira/browse/TUSCANY-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lou Amodeo updated TUSCANY-1677:
Attachment: Output2OutputTransformer.java
XML Parser not being closed with void return types
On 9/7/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
ant elder wrote:
No comments on this for a while so if no one shouts i'm going to do this
to
fix TUSCANY-1559.
...ant
+1 from me to move the logic to enforce pass by value into a separate
interceptor, out
Any particular reason for us to have two copies of Base ?
import org.apache.tuscany.sca.assembly.Base;
import org.apache.tuscany.sca.interfacedef.Base;
They seem identical, and making the change in interface-wsdl to use
the Base class from assembly seems to cause no harm and the module
seems
[
https://issues.apache.org/jira/browse/TUSCANY-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David T. Adcox updated TUSCANY-1673:
Attachment: 1673.patch
Luciano, your test case exposed some holes in the generated class
[
https://issues.apache.org/jira/browse/TUSCANY-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525818
]
Luciano Resende commented on TUSCANY-1673:
--
I'm getting NPE after applying this patch, but I'm afraid I
[
https://issues.apache.org/jira/browse/TUSCANY-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-1677:
-
Assignee: Raymond Feng
XML Parser not being closed with void return types causing
[
https://issues.apache.org/jira/browse/TUSCANY-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David T. Adcox updated TUSCANY-1673:
Attachment: (was: 1673.patch)
PackageClassInfo being override when Element and
[
https://issues.apache.org/jira/browse/TUSCANY-1673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David T. Adcox updated TUSCANY-1673:
Attachment: 1673.patch
Previous patch was generated from a revision that did not include
On 9/6/07, Simon Nash [EMAIL PROTECTED] wrote:
See inline.
Simon
ant elder wrote:
On 9/5/07, Simon Laws [EMAIL PROTECTED] wrote:
On 9/5/07, Luciano Resende [EMAIL PROTECTED] wrote:
Note that we have a similar issue that I'm looking at under the
wsdl2java tooling, described in
Luciano Resende wrote:
Any particular reason for us to have two copies of Base ?
import org.apache.tuscany.sca.assembly.Base;
import org.apache.tuscany.sca.interfacedef.Base;
They seem identical, and making the change in interface-wsdl to use
the Base class from assembly seems to cause no
[
https://issues.apache.org/jira/browse/TUSCANY-1653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525835
]
Simon Laws commented on TUSCANY-1653:
-
I have now checked in the fix suggested in the mail. The fix only
I just changed the import and compiled the module with mvn clean
install, no erros... but i didn't do a full build... i can try that
later on...
On 9/7/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Luciano Resende wrote:
Any particular reason for us to have two copies of Base ?
Beta 2 sounds right given that this is just sync'ing up with SDO version 1.0.
On 9/5/07, Amita Vadhavkar [EMAIL PROTECTED] wrote:
sounds good to me.
On 9/6/07, Luciano Resende [EMAIL PROTECTED] wrote:
Good, looks like we have most (if not all) the updates necessary to
support SDO 2.1
[snip]
Simon Nash wrote:
I'm OK with most of this, but I have some comments and concerns.
See inline.
Simon
I'm not convinced about putting callbackObject into EndpointReference.
The callbackObject can be one of the following:
1) a ServiceReference
2) a local Java instance that supports
Hi,
Usually website updates, documentation and sample readme are left for the
last minute of the release and don't get the attention that we all want to
give it because of all the other work that needs to be done. I'd like to
help get the related stuff for 1.0 done and start now. Please let me
Simon Nash wrote:
Until now we have always held this information in the wsa:From element.
However, in thinking about what is really going on here in WS-Addressing
terms, I believe we should be putting it in the wsa:To element instead.
The wsa:To element is mandatory for WS-Addressing, but we are
At this moment, the From of the Message is used for the reference of the
source component. And if the interface is bidirectional, the From EPR will
contain a callback EPR.
What's going to happen if the user customize the callback object by calling
ServiceReference.setCallback() with a
Hi,
We already have a news section on the home page which repeats most of what
is on the event page. The information on the event page seems to be old and
not being updated.
How about
a) remove the events link from the community box
b) add a new link to the community box called 'projects using
54 matches
Mail list logo
