Can't be sure without seeing the changes - including a patch would be
helpful.
In general, this sounds like an incompatible change (it's renaming
methods) so republishing the snapshots would be a good move. If it
was a less intrusive change (e.g. adding a method) then just
committing would be enough.
--
Jeremy
On Jan 10, 2007, at 5:56 PM, Jean-Sebastien Delfino wrote:
Jean-Sebastien Delfino wrote:
Jim Marino wrote:
On Jan 8, 2007, at 4:26 PM, Jean-Sebastien Delfino wrote:
The names of some of the methods on
org.osoa.sca.CompositeContext do not match the API described in
the 0.95 Java SCA C&I specification (this was reported as http://
issues.apache.org/jira/browse/TUSCANY-909).
I have checked the latest SCA spec docs and the spec mailing
lists and could not find any indication that the names on our
definition of CompositeContext are the correct ones. I'm
planning on making the following changes:
- rename getCompositeName() to getName()
- rename getCompositeURI() to getURI()
Jim, you've been following this more closely than me, is this
the right change? are the spec documents up to date and our code
needs to be adjusted? or is it the other way around?
Those have not changed to my knowledge (or at least I can't
remember), so it is probably a simple oversight on our part.
There are a number of changes where the spec needs to be updated
in other areas (e.g. scopes), that I'm in the process of doing now.
Jim
Thanks,
--Jean-Sebastien
OK thanks! I'll make the code match the spec then :)
I have the changes ready, affecting CompositeContext in the spec/
sca project and 3 other classes in kernel. What is the best way to
apply the changes? Is committing the spec and kernel changes
sufficient? or do I need to republish the spec and kernel snapshots?
Thanks,
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
