Would be good if it was possible for Tuscany to work with any StAX impl,
would you raise a JIRA about the BEA one not working so we could investigate
if there's anything we can do (though from the sound of it it may well turn
out to be an Axis2 incompatibility)?
...ant
On 8/31/07,
[
https://issues.apache.org/jira/browse/TUSCANY-1482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Venkatakrishnan resolved TUSCANY-1482.
--
Resolution: Fixed
Fixed in r571391.
CompositeProcessor does not write out Property
I would suggent a improvement on WSDLInterfaceProcessor
---
Key: TUSCANY-1639
URL: https://issues.apache.org/jira/browse/TUSCANY-1639
Project: Tuscany
Issue Type: Improvement
Consolidate extended provider SPI interfaces into base interfaces
-
Key: TUSCANY-1640
URL: https://issues.apache.org/jira/browse/TUSCANY-1640
Project: Tuscany
Issue Type: Bug
@Destroy method not called for CompositeScope
-
Key: TUSCANY-1641
URL: https://issues.apache.org/jira/browse/TUSCANY-1641
Project: Tuscany
Issue Type: Bug
Components: Java SCA Java
[
https://issues.apache.org/jira/browse/TUSCANY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Combellack updated TUSCANY-1641:
-
Patch Info: [Patch Available]
Have attached patch to fix this issue
@Destroy method
[
https://issues.apache.org/jira/browse/TUSCANY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Combellack updated TUSCANY-1641:
-
Attachment: DestroyForCompositeScope.patch
@Destroy method not called for
Hi,
I have tried to use JOTM and Tomcat and would like to create a sample web
app in
DAS showing how external transaction manager can control DAS transactions.
I am creating another mail thread for any discussion for this sample + JOTM
issues.
We can demonstrate through this and accompanying wiki
I am using jotm-2.0.10 and Tomcat 5.5.23.
The HowTo from JOTM site has a few problems and the below info worked for me
-
[1]http://www.nabble.com/UserTransaction,-
JOTM-and-Tomcat-5.5.x-t1073172.html
[2]http://static.raibledesigns.com/downloads/howto-tomcat-jotm.html
Also, as mentioned in [1] for
I think it would be good to step back from details of which characters are
usable in URIs and look at the bigger picture. The major question we have
to decide is whether the pseudo-services used by callbacks are to be treated
from the user's perspective
a. exactly like SCA services in every
Hi again,
i saw tuscany ws binding and it fits my needs both OneWay Invocations
and callbacks work fine. I've put some findings at
http://g4sca.blogspot.com/ so now the next..what i've to do is bootstrap
a node with an EmbeddedNode and use that binding. Axis2 permits some
kind of data-mapping with
The Apache Tuscany team are pleased to announce the 0.99-incubating
release of the Java SCA project.
Apache Tuscany provides a runtime based on the Service Component
Architecture. SCA is a set of specifications aimed at simplifying SOA
Application Development which are being standardized at OASIS
On 8/29/07, Raymond Feng [EMAIL PROTECTED] wrote:
I just created https://issues.apache.org/jira/browse/TUSCANY-1635 to track
the aspectj-based tracing.
Thanks,
Raymond
- Original Message -
From: Jean-Sebastien Delfino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent:
Tuscany has a data binding framework so that most data bindings could be
supported, but there has to be a Tuscany databinding extension written for
each data binding and there's no JiBX one yet, would be really cool if
someone could help write one...interested in helping? There's a bit of
On 8/31/07, ant elder [EMAIL PROTECTED] wrote:
Tuscany has a data binding framework so that most data bindings could be
supported, but there has to be a Tuscany databinding extension written for
each data binding and there's no JiBX one yet, would be really cool if
someone could help write
Simon Nash wrote:
I think it would be good to step back from details of which characters
are
usable in URIs and look at the bigger picture.
Right :)
The major question we have
to decide is whether the pseudo-services used by callbacks are to be
treated
from the user's perspective
a.
On 8/31/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
Comments inline.
Thanks,
Raymond
- Original Message -
From: Simon Laws [EMAIL PROTECTED]
To: tuscany-dev tuscany-dev@ws.apache.org
Sent: Thursday, August 30, 2007 9:13 AM
Subject: Rationalizing SCA Domain implementations
[
https://issues.apache.org/jira/browse/TUSCANY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1641.
---
Resolution: Fixed
Patch applied under r571516. Thank you for the fix.
@Destroy method
[
https://issues.apache.org/jira/browse/TUSCANY-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng reassigned TUSCANY-1641:
-
Assignee: Raymond Feng
@Destroy method not called for CompositeScope
Hi,
Comments inline.
Thanks,
Raymond
- Original Message -
From: Simon Laws [EMAIL PROTECTED]
To: tuscany-dev tuscany-dev@ws.apache.org
Sent: Thursday, August 30, 2007 9:13 AM
Subject: Rationalizing SCA Domain implementations
We now have a number of domain implementations in Tuscany
[
https://issues.apache.org/jira/browse/TUSCANY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524141
]
Sean Zhou commented on TUSCANY-1642:
If I move the WSDL document to a path without spaces and change the
SCAWSDL2Java cannot handle spaces in the path on Windows
Key: TUSCANY-1642
URL: https://issues.apache.org/jira/browse/TUSCANY-1642
Project: Tuscany
Issue Type: Bug
Tutorial for ApacheCon 2007 - Services Definition
-
Key: TUSCANY-1643
URL: https://issues.apache.org/jira/browse/TUSCANY-1643
Project: Tuscany
Issue Type: Task
Components: Java SCA
[
https://issues.apache.org/jira/browse/TUSCANY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Zhou updated TUSCANY-1642:
---
Description:
WSDL2Java.bat -targetDirectory C:/Documents and
[
https://issues.apache.org/jira/browse/TUSCANY-1643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Antollini updated TUSCANY-1643:
-
Attachment: shoppingstore-v1.zip
This zip file contains the first version of the
There is a test to determine whether a WSDL operation follows the wrapped
style in accordance with JAX-WS 2.0 spec. See WSDLOperationIntrospectorImpl
(
WSDL2Java doesn't accept remote WSDL URL
Key: TUSCANY-1644
URL: https://issues.apache.org/jira/browse/TUSCANY-1644
Project: Tuscany
Issue Type: Bug
Components: Java SCA Tools
Affects
That's extremely cool! Thanks for the tip Jean Sebastien,
- Ole
Jean-Sebastien Delfino wrote:
Hi all,
I just thought I'd share this as I found it pretty useful when working
with our Webapp samples.
If you're using Eclipse WTP and want to get WTP Web Projects generated
for our Webapp
Ok. I'll try it again debugging in my lan this night.
Cheers,
Giorgio.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[
https://issues.apache.org/jira/browse/TUSCANY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524150
]
Scott Kurz commented on TUSCANY-544:
In my experience (admittedly not on the absolute latest version of the
[
https://issues.apache.org/jira/browse/TUSCANY-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524151
]
Simon Nash commented on TUSCANY-1562:
-
This problem occurs when specifying an exception on the service
[snip]
Simon Laws wrote:
Ok, so we know there is no generally acceptable logging interface. Has
been proved time and time again. All we can hope to do is use something that
suits us and doesn't mess up anyone who wants to embed our code.
I'm perfectly happy to +1 JDK logging. However
Hi,
The operation.getInput() cannot be null to qualify for the wrapper style.
There must be a part in the input message corresponding to the operation
name:
input
--- message
--- part (only one part)
--- element (the element name should be the same as the
operation
On 8/31/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
The operation.getInput() cannot be null to qualify for the wrapper style.
There must be a part in the input message corresponding to the operation
name:
input
--- message
--- part (only one part)
---
On 8/31/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
[snip]
Simon Laws wrote:
Ok, so we know there is no generally acceptable logging interface. Has
been proved time and time again. All we can hope to do is use something
that
suits us and doesn't mess up anyone who wants to
Hi,
I applied the patch4 with the following changes:
1) Remove ImplementationProvider2 and use RuntimeWireProcessorExtensionPoint
instead to add the interceptor
2) Keep the CallableReference to the Message instead of a flag for the
callback object
3) Use InterfaceContractMapper to test if the
In the same JVM, we now use a singleton object to keep all the metadata for
the deployable composites running on the node. This has been proven to be
problematic, especially in the case of Tomcat or Geronimo integration where
applications are running in isolated address spaces. The partition is
JS, Ant and Raymond,
I have uploaded the first version of the services the sample application
will provide (to my understanding)
One remark: I needed to provide an operation to start the checkout
process (to take part when the items in the cart are going to be bought
by the client/user).
XSD2JavaGenerator failed to gen on the wsdl files with only xsd:import
element in xsd:schema
Key: TUSCANY-1645
URL:
[
https://issues.apache.org/jira/browse/TUSCANY-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fuhwei Lwo updated TUSCANY-1645:
Attachment: EchoService_schema1.xsd
TUSCANY-544.wsdl
XSD2JavaGenerator failed
Simon Laws wrote:
What would be put in specific logging properties?
The usual logging configuration, what we want our default logging level to
be on a module by module bases, what handlers to use, configuration of the
handlers e.g. if it's a file handler where to put the file and what
I forgot to add where you can find the code:
https://issues.apache.org/jira/browse/TUSCANY-1643
-Original Message-
From: Antollini, Mario [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 4:25 PM
To: tuscany-dev@ws.apache.org
Subject: Services definition for tutorial @ ApacheCon
[
https://issues.apache.org/jira/browse/TUSCANY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved TUSCANY-544.
-
Resolution: Cannot Reproduce
In general, WSDL2Java is supporting WSDLs with schema
[
https://issues.apache.org/jira/browse/TUSCANY-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524179
]
Jean-Sebastien Delfino commented on TUSCANY-1636:
-
Raymond is correct, it is valid to have a
The picture on http://incubator.apache.org/tuscany/sca-java.html doesn't
look quite right to me. It seems to show a node that is split between
two domains. I think an SCA node is part of exactly one domain. It's
possible for more than one domain to run in a single JVM, but from an
What's the use case to have one JVM joining multiple SCA domains (even
theoretically it's possible)? I agree with Simon that one node should only
belong to one SCA domain but it seems that he also hinted that one JVM can
host more than one node.
Thanks,
Raymond
- Original Message -
[
https://issues.apache.org/jira/browse/TUSCANY-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-1642:
Fix Version/s: Java-SCA-1.0
WSDL2Java cannot handle spaces in the path
On 8/31/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
What would be put in specific logging properties?
The usual logging configuration, what we want our default logging level
to
be on a module by module bases, what handlers to use, configuration of
the
[
https://issues.apache.org/jira/browse/TUSCANY-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fuhwei Lwo updated TUSCANY-1645:
Attachment: 1645.patch
The NPE was caused by trying to codegen on null XSD namesapce. The SDO
[
https://issues.apache.org/jira/browse/TUSCANY-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash updated TUSCANY-1562:
Attachment: jira1562.zip
I'm attaching an itest that demonstrates this problem. It can be
[
https://issues.apache.org/jira/browse/TUSCANY-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash updated TUSCANY-1562:
Attachment: (was: jira1562.zip)
Service method's throws Exception clause create problem at
Thanks very much Raymond, and thanks for the improvements to my patch.
I have one minor comment on the changes. In CallbackInterfaceInterceptor
the invoke() method is as follows:
public Message invoke(Message msg) {
CallableReference? callableReference = msg.getCallableReference();
[
https://issues.apache.org/jira/browse/TUSCANY-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-1633:
Fix Version/s: Java-SCA-1.0
To support reference target for SCA
[
https://issues.apache.org/jira/browse/TUSCANY-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash updated TUSCANY-1562:
Attachment: jira1562.zip
Second attempt at attaching the itest: the first was deleted because of
[
https://issues.apache.org/jira/browse/TUSCANY-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524190
]
Luciano Resende commented on TUSCANY-1645:
--
I have committed the wsld and xsd from TUSCANY-544 to
See inline.
Simon
Jean-Sebastien Delfino wrote:
Simon Nash wrote:
I think it would be good to step back from details of which characters
are
usable in URIs and look at the bigger picture.
Right :)
The major question we have
to decide is whether the pseudo-services used by callbacks
Raymond Feng wrote:
What's the use case to have one JVM joining multiple SCA domains (even
theoretically it's possible)? I agree with Simon that one node should
only belong to one SCA domain but it seems that he also hinted that one
JVM can host more than one node.
We have APIs that allow
Simon Laws wrote:
On 8/31/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
What would be put in specific logging properties?
The usual logging configuration, what we want our default logging level
to
be on a module by module bases, what
On 8/31/07, Raymond Feng [EMAIL PROTECTED] wrote:
What's the use case to have one JVM joining multiple SCA domains (even
theoretically it's possible)? I agree with Simon that one node should only
belong to one SCA domain but it seems that he also hinted that one JVM can
host more than one
On 8/31/07, Simon Laws [EMAIL PROTECTED] wrote:
On 8/31/07, Raymond Feng [EMAIL PROTECTED] wrote:
What's the use case to have one JVM joining multiple SCA domains (even
theoretically it's possible)? I agree with Simon that one node should
only
belong to one SCA domain but it seems
On 8/31/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
On 8/31/07, Jean-Sebastien Delfino [EMAIL PROTECTED] wrote:
Simon Laws wrote:
What would be put in specific logging properties?
The usual logging configuration, what we want our default logging
level
[
https://issues.apache.org/jira/browse/TUSCANY-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Yoder closed TUSCANY-1548.
--
Resolution: Fixed
Resolved with applied patch.
multi-valued properties should require
I was experimenting with JMS binding to transport SOAP and XML messages.
Current JMS binding implementation supports Text and Object messages and
Text messages do allow carrying XML. I was thinking of extending this
binding to support SOAP messages as specified in
On 8/31/07, Raymond Feng [EMAIL PROTECTED] wrote:
In the same JVM, we now use a singleton object to keep all the metadata
for
the deployable composites running on the node. This has been proven to be
problematic, especially in the case of Tomcat or Geronimo integration
where
applications
[
https://issues.apache.org/jira/browse/TUSCANY-1438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brady Johnson resolved TUSCANY-1438.
Resolution: Fixed
I think enough patches have been applied to warrant resolving this
On 8/31/07, Dinesh Shahane [EMAIL PROTECTED] wrote:
I was experimenting with JMS binding to transport SOAP and XML messages.
Current JMS binding implementation supports Text and Object messages and
Text messages do allow carrying XML. I was thinking of extending this
binding to support SOAP
Hi,
I'm reviewing our support for autowiring and found out there is an issue
with our Composite/Component/ComponentReference models.
By the assembly spec, there is difference between the following two cases:
a) component name=C1
b) component name=C1 autowire=false
Case a) will inherit the
[
https://issues.apache.org/jira/browse/TUSCANY-1142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-1142:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.0
[
https://issues.apache.org/jira/browse/TUSCANY-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-1511:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.0
Raymond Feng wrote:
Hi,
I'm reviewing our support for autowiring and found out there is an
issue with our Composite/Component/ComponentReference models.
By the assembly spec, there is difference between the following two
cases:
a) component name=C1
b) component name=C1 autowire=false
Web Service binding doesn't handle wsdli:wsdlLocation
-
Key: TUSCANY-1646
URL: https://issues.apache.org/jira/browse/TUSCANY-1646
Project: Tuscany
Issue Type: Bug
Components:
Web Service binding doesn't handle SOAP1/2 policy intent
Key: TUSCANY-1647
URL: https://issues.apache.org/jira/browse/TUSCANY-1647
Project: Tuscany
Issue Type: Bug
WS Binding WSDL generation should follow the rules in section 2.3.5 of the WS
binding spec
--
Key: TUSCANY-1648
URL: https://issues.apache.org/jira/browse/TUSCANY-1648
[
https://issues.apache.org/jira/browse/TUSCANY-1494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-1494:
Fix Version/s: (was: Java-SCA-Next)
Java-SCA-1.0
Implement SCA transaction policy intents
Key: TUSCANY-1649
URL: https://issues.apache.org/jira/browse/TUSCANY-1649
Project: Tuscany
Issue Type: New Feature
Components: Java SCA Assembly
Integrate implementation.DAS with SCA Transaction Policy
Key: TUSCANY-1650
URL: https://issues.apache.org/jira/browse/TUSCANY-1650
Project: Tuscany
Issue Type: New Feature
Affects
Implement support for SCA security policy intents
-
Key: TUSCANY-1651
URL: https://issues.apache.org/jira/browse/TUSCANY-1651
Project: Tuscany
Issue Type: New Feature
Components:
[
https://issues.apache.org/jira/browse/TUSCANY-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524247
]
Jean-Sebastien Delfino commented on TUSCANY-1639:
-
Hi
Right, it is sometimes useful to be able to
[
https://issues.apache.org/jira/browse/TUSCANY-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Sebastien Delfino updated TUSCANY-1639:
Fix Version/s: Java-SCA-Next
I would suggent a improvement on
79 matches
Mail list logo
