[
https://issues.apache.org/jira/browse/TUSCANY-1403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved TUSCANY-1403.
--
Resolution: Fixed
Fixed both in trunk and beta1 branch
DAS Source distribution
[
https://issues.apache.org/jira/browse/TUSCANY-1401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luciano Resende resolved TUSCANY-1401.
--
Resolution: Fixed
Fixed both in trunk and beta1 branch
Incompatible SDO code being
[
https://issues.apache.org/jira/browse/TUSCANY-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510073
]
Adriano Crestani commented on TUSCANY-1404:
---
detailed customer sample's readme
Detail DAS samples'
[
https://issues.apache.org/jira/browse/TUSCANY-1404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adriano Crestani resolved TUSCANY-1404.
---
Resolution: Fixed
Detail DAS samples' readme
--
This error was fixed in the parent section in revision 552945,
but there are four more places in the dependencies section that
also need changing.
Simon
Luciano Resende wrote:
I have already changed that under revision #552945 as part of the fix
for tuscany-1407
On 7/3/07, Simon Nash
Ant,
Thank you for applying the patches. The code that currently looks up OSGi
services is not thread-safe, and hence the intermittent failures. I will
submit a patch.
Thank you...
Regards,
Rajini
On 7/3/07, ant elder [EMAIL PROTECTED] wrote:
The OSGi implementation and sample are
Make OSGi instance creation thread-safe, and support @EagerInit
---
Key: TUSCANY-1409
URL: https://issues.apache.org/jira/browse/TUSCANY-1409
Project: Tuscany
Issue Type: Bug
[
https://issues.apache.org/jira/browse/TUSCANY-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajini Sivaram updated TUSCANY-1409:
Attachment: tuscany-implementation-osgi-patch.txt
Make OSGi instance creation
[
https://issues.apache.org/jira/browse/TUSCANY-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ant elder closed TUSCANY-1409.
--
Resolution: Fixed
Applied, and the itests now look like they work fine so i'll add them to the
[
https://issues.apache.org/jira/browse/TUSCANY-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510173
]
Amita Vadhavkar commented on TUSCANY-1355:
--
This might be imcompatibility in SDO, not sure, will you
[
https://issues.apache.org/jira/browse/TUSCANY-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510175
]
Rajini Sivaram commented on TUSCANY-1409:
-
Thank you, Ant.
- Rajini
Make OSGi instance creation
DataHelperImpl.toCalendar() with null locale should use default locale
--
Key: TUSCANY-1410
URL: https://issues.apache.org/jira/browse/TUSCANY-1410
Project: Tuscany
Issue
Hi Jacek,
Glad that you could join this discussion. Welcome :). We
need more participants like you to join this dicussion to come out
with the best approach. I have added my comments inline on my
understanding on why we should be doing this. This is actually based
on the JEE SCA
Or better yet would be to add the po: to the types where it's missing:
xsd:element name=shipTo type=USAddress/
xsd:element name=billTo type=USAddress/
xsd:element name=items type=Items/
like this:
xsd:element name=shipTo type=po:USAddress/
Hi Raymond,
Comments Inline
On 7/4/07, Raymond Feng [EMAIL PROTECTED] wrote:
Hi,
Please see my comments inline.
Thanks,
Raymond
- Original Message -
From: Manu George [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: tuscany-dev@ws.apache.org
Sent: Tuesday, July 03, 2007
Hi Simon,
In one of the previous mails Sebastien proposed two
ways of how the SCADomain should exist in geronimo
(a) one instance of SCADomain per component running on the server,
loaded with a subset of the distributed SCA domain composite
representing that component and enough
Hi Jacek,
The spec also says in 1.10.2.2.
The contribution optionally contains a document that declares runnable
composites, exported definitions and imported definitions. The
document is found at the path of META-INF/sca-contribution.xml
relative to the root of the contribution.I
Sorry, I missed these other places. It's fixed under revision #553367.
On 7/4/07, Simon Nash [EMAIL PROTECTED] wrote:
This error was fixed in the parent section in revision 552945,
but there are four more places in the dependencies section that
also need changing.
Simon
Luciano Resende
After the great feedback you guys gave for the DAS Beta1 RC1 under
[1], Adriano and I have fixed most of the issues and new distros were
uploaded to [2].
Could you guys have a quick look at it, I'm mostly looking to see if
the build issues and the need to copy the derby canned databases are
Folks,
Believe it or not! we have 230 people who have karma to our svn:
https://svn.apache.org/repos/asf/webservices/
Out of these only about 74 people have made commits in the last 1
year. You can get this info by using the svn log:
svn log -v --revision 2006-07-05:HEAD
JDKInvocationHandler works wrong when a component references more than one WS
-
Key: TUSCANY-1411
URL: https://issues.apache.org/jira/browse/TUSCANY-1411
Project: Tuscany
When CompositeA has reference to CompositeB while CompositeB also has reference
back to CompositeA, CompositeBuilderImpl.build(composite) seems went into
endless loop.
I'm not very sure whether it's a bug or this kind of reference is illegal?
22 matches
Mail list logo