I have a need to get the classLoader resolved from a contribution after
Node.start. I noticed a couple of things when I try to get it to work.
1. It seems NodeImpl has the list of contribution object who contains the
classLoader. So I used the following code to access it.
*for*
Issue on ExtensibleStAXArtifactProcessor.read
-
Key: TUSCANY-3713
URL: https://issues.apache.org/jira/browse/TUSCANY-3713
Project: Tuscany
Issue Type: Bug
Reporter: Yang Lei
I am
Thanks Raymond for pointing it out. I made a change to the
ExtensibleURLArtifactProcessor.read to set the monitor artifact name to null
before calling processor.read. This solve my OASIS test running problem on
ASM_12012. I will open a JIRA and attach my fixed code.
One thing I do want to point
Environment: Revision: 1003111
Reporter: Yang Lei
When running OASIS compliance test in another hosting environment, I noticed
sometimes the Monitor report wrong artifact names. I think the reason is we
never reset the monitor's artifact name . I made a change
[
https://issues.apache.org/jira/browse/TUSCANY-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Lei updated TUSCANY-3704:
--
Attachment: patch.txt
Here is the patch
Monitor report wrong artifact names
I was running oasis compliance test in another hosting environment, I
noticed some test result validation differences from what Tuscany defined in
the error message files. I think these differences may expose an issue
on how we maintain the artifact name in the MonitorImpl.
I noticed that not all
ASM_10003 is related to DefinitionsProcessor. In tuscany's error message it
is using Test_ASM_10003.composite, while in my environment for some reason
the composite file may not have been processed, so I get the definition
file's input name (the file uri from a jar) as the artifact name.
I have my own webservices binding implementation in my OASIS hosting
environment. I noticed when reference target is defined, service and
reference side will share the share InterfaceContract instance. My service
side and reference side are using (forced to use) different databinding.
This object
Yes, I am happy to create the JIRA/patch.
Yang.
When running JCA_11003, I noticed there are two services created for
component TEST_JCA_11003Component1. Both will activate a
binding.wsendpoint. Is it correct?
The content of the EndPoint object in the binding.ws code is as follows:
(@496442775)Endpoint: URI =
Thanks Ant,
I gave it a try and it works.
About if we fix this or not. As the contribution's artifact already resolved
the model, I do not see why we are returnning a dummy model on the
contribution. I wonder what is the purpose to have a dummy composite at
contribution level. Is it because we
I was trying to use Deploper to load contribution and iterate the deployable
composites' contents. The composite returned does not have any components
returned. The only thing loaded is the composite name. I would like to
understand how I should be using Deployer to get the composite with the
The test logic is added into sample-contribution-binding-sca-calculator's
CalculatorTestCase, so it is using the same contribution definition of that
sample.
Looking at the directory where the location is used to
loadContribution, Isee sca-contribution.xml under META-INF and
composite file under
Hi Ant,
I would need to specify contribution related context data and deployable
composite related context data. Then of course, a deployable composite also
needs to access its defining contribution's context..
Thanks. Yang.
I would like to bring up a requirement on contribution processing, binding
provider start, implementation provider start.
While trying to integrate Tuscany 2.x into a hosting environment, there are
times I need to know context :
Scenario 1, I need to create my own classLoader of a given
[
https://issues.apache.org/jira/browse/TUSCANY-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12870791#action_12870791
]
Yang Lei commented on TUSCANY-3558:
---
Can we explain if it is intended that for a single
[
https://issues.apache.org/jira/browse/TUSCANY-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Lei updated TUSCANY-3558:
--
Attachment: sample-store.jar
sample-store-client.jar
sample-store
[
https://issues.apache.org/jira/browse/TUSCANY-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868648#action_12868648
]
Yang Lei commented on TUSCANY-3558:
---
Issue 2 is resolved after I add the dependent
[
https://issues.apache.org/jira/browse/TUSCANY-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868663#action_12868663
]
Yang Lei commented on TUSCANY-3558:
---
I mean case 2 issue is resolved. I still see case
If you have a single contribution jar which you want to bootstrap all the
deployable composite defined in the sca-contribution.xml. Here is my code
sample to bootstrap:
String storeLocation =
File:///C:/ASV/Tuscany2x/Test/TestCase/sample-store-all.jar;
*node1* =
[
https://issues.apache.org/jira/browse/TUSCANY-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868964#action_12868964
]
Yang Lei edited comment on TUSCANY-3558 at 5/18/10 10:29 PM
[
https://issues.apache.org/jira/browse/TUSCANY-3558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868964#action_12868964
]
Yang Lei commented on TUSCANY-3558:
---
I am on r945854, both case 2 and case 3 failes
[
https://issues.apache.org/jira/browse/TUSCANY-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868422#action_12868422
]
Yang Lei commented on TUSCANY-3554:
---
I am trying to rerun the test on revision 944607
[
https://issues.apache.org/jira/browse/TUSCANY-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12868466#action_12868466
]
Yang Lei commented on TUSCANY-3554:
---
Do not see the reported issues on revision 944607
[
https://issues.apache.org/jira/browse/TUSCANY-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Lei closed TUSCANY-3554.
-
Resolution: Fixed
Verified on latest revision
Two Issues found when using SCAClientFactory
Issue Type: Bug
Components: Java SCA Assembly Model
Reporter: Yang Lei
I revised the sample-store to only config binding.sca. I have two contribution
jars: one is store client , which uses client.Shopper and client.ShoperImpl
classes, and the contribution import
Model
Reporter: Yang Lei
I tried to use SCAClientFactory to access the SCA services defined by sample
sample-implementation-java-calculator. And found two issues.
There is the code:
SCAClientFactory factory = SCAClientFactory.newInstance(new
URI(default
integration to reuse JEE applications...
Thank you.
Yang Lei
Simon Laws
simonsl...@googl
Be aware, OASIS is removing the operational level element from SCDL or
fcomponentType. There is new way to attach PolicySet to the operational
level...
Regards,
Yang Lei
Luciano Resende
[
https://issues.apache.org/jira/browse/TUSCANY-2838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yang Lei reopened TUSCANY-2838:
---
There are ML discussion on this between Luciano and Ant.
Implementation.widget works in webcontainer
Integration
Affects Versions: Java-SCA-1.4
Reporter: Yang Lei
When looking at the current implementation of implemention.widget, I noticed
that there is code like the following that hardcode the generate JS code for
different protocol. I would like to see the code done through extension
: Java SCA Web App Integration
Affects Versions: Java-SCA-1.4
Reporter: Yang Lei
I would like to know if we have test verifying implementation.widget working in
a webcontainer environment. Thank you
--
This message is automatically generated by JIRA.
-
You can reply
32 matches
Mail list logo
