Luciano Resende wrote:
I noticed some JIRAS around the locateService API and I will spend
some time to investigate these issues. So far, I have found
TUSCANY-1347 [1] and TUSCANY-1328 [2] :
TUSCANY-1347 current status is resolved/cannot reproduce, but I
looking at the attached test case and patch, it looks like it wasn't
applied. By reading the JIRA, looks like the original issue reported
was that an IndexOutOfBoundsException exception was being thrown
instead of "org.osoa.sca.ServiceRuntimeException: Service not found"
exception.
I'm the one who marked 1347 "cannot reproduce", as I couldn't understand
from the JIRA what the issue was about, and therefore what the patch was
supposed to fix :) I asked the reporters of the JIRA issue to please
provide a clear description of the issue. It's nice of you to "reopen it
for investigation", but the initial reporters need to step in and
provide more information. Also when I ran the test case on the trunk I
got a completely different error, see the stack trace I added to the JIRA.
TUSCANY-1328 is about not being able to locate service from a
component whose implementation is composite.
Please let me know if I have the correct understanding of the issue
described in TUSCANY-1347 as it comments are a little unclear, and
also let me know if anyone knows about other issues on this area, so I
could try to address them all together.
[1] https://issues.apache.org/jira/browse/TUSCANY-1347
[2] https://issues.apache.org/jira/browse/TUSCANY-1328
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
